ADRV9008/ADRV9009 5G收发器硬件参考手册

ADRV9009

9009

1星需积分: 44 99 浏览量更新于2024-07-16 1 收藏 4.39MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"ADI公司的ADRV9008-1-W-9008-2-W-9009-W-Hardware-Reference-Manual-UG-1295.pdf是针对5G通信领域的重要硬件参考手册，专注于ADRV9008-1、ADRV9008-2和ADRV9009收发器的详细技术文档。这份用户手册是对数据手册的补充，提供了关于如何配置、操作和初始化这些高性能收发器的关键信息，对于进行收发器开发的工程师来说极其重要。" 本文档全面介绍了ADI公司推出的5G通信核心组件——ADRV9008-1接收器（Rx）、ADRV9008-2发射器（Tx）以及ADRV9009收发器。手册的目的是帮助系统工程师和软件开发者更好地理解和利用这些器件的功能，以构建高效的无线通信系统。在介绍部分，手册强调了其作为主要信息来源的角色，涵盖了从基本概念到复杂操作的所有细节。系统概述部分详细描述了这些收发器的体系结构和设计，包括它们如何适应不同通信标准和应用需求。系统架构描述了ADRV9008-1、ADRV9008-2和ADRV9009在整体通信链路中的位置，以及它们与其他组件的交互方式。软件架构部分则讨论了与硬件配合使用的软件框架，包括文件夹结构、私有与公共API函数的区分，以及硬件抽象层（HAL）。HAL是软件与硬件之间的桥梁，通过定义接口、数据类型和枚举，确保软件能够透明地控制和管理硬件资源。详细的HAL函数定义进一步解释了如何通过软件来控制和配置ADRV9008系列的各个功能模块。软件集成章节指导用户如何将这些器件集成到自己的应用中，包括实现硬件抽象接口的具体步骤和开发应用程序的流程。SPI（串行外设接口）是ADRV9008系列的关键控制接口，手册提供了使用API函数配置SPI的指导，并详细阐述了SPI总线信号的特性。此外，手册还可能涵盖了错误处理、调试工具、性能优化以及电源管理等方面的详细信息，以确保用户能够充分利用ADRV9008系列收发器的潜力，实现高效、可靠的5G通信解决方案。这些内容对于任何涉及5G无线通信系统设计和开发的专业人士来说，都是不可或缺的技术参考资料。

资源详情

资源推荐

UG-1295 ADRV9008-1/ADRV9008-2/ADRV9009 Hardware Reference Manual

Rev. 0 | Page 16 of 247

ADIHAL_spiWriteField Synopsis

The synopsis for the ADIHAL_spiWriteField HAL is as follows:

adiHalErr_t ADIHAL_spiWriteField(void *devHalInfo, uint16_t addr, uint8_t fieldVal, uint8_t

mask, uint8_t startBit);

Parameters include the following



void*devHalInfo. This parameter is a void pointer to the targeted device state container. The device state provides the SPI device

chip select information.



addr. This parameter provides the SPI register address on which to perform an SPI read. The address value must not exceed

15 bits because the MSB bit is used for the read/write bit in the SPI implementation.



fieldVal. This parameter provides the desired new value for the targeted field within the register specified by addr parameter.



mask. Field mask, describing the targeted bits within the register specified by addr parameter.



startBit. This parameter provides the field LSB position in the register (0 to 7).

Return value: an error of type adiHalErr_t, ADIHAL_OK indicates a successful operation. Any other value may represent an error

code to be returned to the application. Refer to the adiHalErr_t section for details.

Dependencies: the

ADIHAL_spiWriteField HAL function is dependent on application and platform specific modules, as well as

ADIHAL_openHW and ADIHAL_closeHW. In general, it is expected that ADIHAL_openHW initializes all hardware resources for the

transceiver. This function depends on the SPI. Therefore, it is expected that the required SPI is initialized in ADIHAL_openHW. Do not

call ADIHAL_spiWriteField before ADIHAL_openHW and not call ADIHAL_spiWriteField after ADIHAL_closeHW.

ADIHAL_spiWriteField Remarks

Analog Devices devices support various modes of the SPI protocol, such as 3-wire or 4-wire mode (see the SPI Data Transfer Protocol

section). The HAL can implement any of the supported modes. However, the transceiver must be configured to the same mode as the

HAL implementation. The SPI mode configuration of the transceiver is set by the initialization API and the desired SPI mode defined by

taliseSpiSettings_t of the initialization parameter.

ADIHAL_spiReadField

The ADIHAL_spiReadField HAL function performs a read to a specific field within an SPI register. This function performs a read

operation on a single SPI register.

The

mask and startBit parameters specify the field of bits within the register to be read. The mask is expected to be applied to the

8-bit value read back from register. The startBit

startBit specifies the LSB of the targeted field within the register, which is used to shift

the desired field value down to the Bit 0 position.

An example of pseudo code is as follows:

/*Read a specific register*/

spiRead(regAddr, &regVal);

*fieldVal = ((regVal & mask) >> startBit);

The SPI read/write implementations must support 15-bit addressing and 8-bit data bytes. Full details of the SPI protocol required for SPI

communication with the transceiver is described in the SPI section and the HAL Interface Definition section.

This HAL function is used by most transceiver APIs. Therefore, any necessary SPI drivers or resources are expected to be already opened

by the

ADIHAL_openHw() function call.

ADRV9008-1/ADRV9008-2/ADRV9009 Hardware Reference Manual UG-1295

Rev. 0 | Page 17 of 247

ADIHAL_spiReadField Synopsis

The synopsis for ADIHAL_spiReadField is as follows:

adiHalErr_t ADIHAL_spiReadField(void *devHalInfo, uint16_t addr, uint8_t *fieldVal, uint8_t

mask, uint8_t startBit);

Parameters include the following:



void*devHalInfo. This parameter is a void pointer to the targeted device state container. The device state provides the SPI device

chip select information.



addr. This parameter provides an SPI register address on which to perform an SPI read. The address value must not exceed 15 bits

because the MSB is used for the read/write bit in the SPI implementation.



fieldVal. This parameter is a pointer variable to return the value of the desired field specified by the mask parameter.

 mask. Field mask, describing the targeted bits within the register specified by addr parameter.



startBit. Field LSB bit position in the register (0 to 7).

Return value: an error of type adiHalErr_t, ADIHAL_OK indicates successful operation. Any other value may represent an error code

to be returned to the application. Refer to the adiHalErr_t section for details.

Dependencies: the

ADIHAL_spiReadField HAL function is dependent on application and platform specific modules, as well as

ADIHAL_openHW and ADIHAL_closeHW. In general, it is expected that ADIHAL_openHW initializes all hardware resources for the

transceiver. This function depends on the SPI. Therefore, it is expected that the required SPI is initialized in ADIHAL_openHW. Do not

call ADIHAL_spiReadField before ADIHAL_openHW and not call ADIHAL_spiReadField after ADIHAL_closeHW.

ADIHAL_spiReadField Remarks

Analog Devices devices support various modes of the SPI protocol, such as 3-wire or 4-wire mode (see the SPI Data Transfer Protocol

section). The HAL can implement any of the supported modes. However, the transceiver must be configured to the same mode as the

HAL implementation. The SPI mode configuration of the transceiver is set by the initialization API and the desired SPI mode defined by

taliseSpiSettings_t of the initialization parameter.

ADIHAL_wait_us

The ADIHAL_wait_us HAL function performs a thread blocking/sleeping delay of the specified time in milliseconds. This function

must wait for this specified amount of time, at least.

ADIHAL_wait_us Synopsis

The synopsis for ADIHAL_wait_us is as follows:

uint32_t ADIHAL_wait_us(void *devHalInfo, uint32_t time_us);

Parameters include the following:



void*devHalInfo is a void pointer to the targeted device state container. The device state provides details of the targeted device.



uint32_t time_us is the desired amount of time in (in ms) for which the function blocks or thread sleeps.

Return value: an error of type adiHalErr_t, ADIHAL_OK indicates successful operation. Any other value may represent an error code

to be returned to the application.

Dependencies: the

ADIHAL_wait_us HAL function is dependent on application and platform specific modules

ADIHAL_wait_us Remarks

The ADIHAL_wait_us HAL function is used for delay/sleep between checking status events.

ADIHAL_writeToLog

The ADIHAL_writeToLog HAL function writes a message to a log file for debugging purposes. This function uses the logLevel

parameter to specify what type of message, warning, or error to write to the log file. The API functions call this function to log errors

detected during the execution of the transceiver API. Logging and file details are platform specific and the

devHalInfo parameter is

expected to provide this information.

UG-1295 ADRV9008-1/ADRV9008-2/ADRV9009 Hardware Reference Manual

Rev. 0 | Page 18 of 247

ADIHAL_writeToLog Synopsis

The synopsis for ADIHAL_writeToLog is as follows:

adiHalErr_t ADIHAL_writeToLog(void *devHalInfo, adiLogLevel_t logLevel,

uint32_t errorCode, const char *comment);

Parameters include the following:



void*devHalInfo is a void pointer to the targeted device state container. The device state provides details of the targeted device.



adiLogLevel_t logLevel is an enumerated value to specify the type of log message being logged. The value is one of the

following

adiLogLevel_t enumerator types:

 ADIHAL_LOG_MSG

 ADIHAL_LOG_WARN

 ADIHAL_LOG_ERR

 ADIHAL_LOG_SPI; refer to adiLogLevel_t section for details



uint32_t errorCode is a 32-bit integer value representing the API error code reference for the error being logged.



const char *comment is a character array that holds the desired comment to represent the error.

Return value: an error of type adiHalErr_t, ADIHAL_OK indicates successful operation. Any other value may represent an error code

to be returned to the application.

Dependencies: the

ADIHAL_writeToLog HAL function is dependent on application and platform specific modules

ADIHAL_writeToLog Remarks

This function is used to write a message to a log file for debugging purposes.

ADIHAL_setLogLevel

The ADIHAL_setLogLevel HAL function sets the HAL logging options for the device. This function sets the desired logging options

for the logging feature. The device API calls this function based on the logging options set by the API user in the API layer. The HAL

implementation maintains this logging option and defines its use with the ADIHAL_writeToLog function. Logging and file details are

platform specific and the

devHalInfo parameter is expected to provide this information. The devHalInfo parameter can be used to

maintain the logging options for a particular device.

ADIHAL_setLogLevel Synopsis

The synopsis for ADIHAL_setLogLevel is as follows:

adiHalErr_t ADIHAL_setLogLevel(void *devHalInfo, uint16_t halLogLevel)

Parameters inlcude the following:



void*devHalInfo is a void pointer to the targeted device state container. The device state provides details of the targeted device.



uint16_t logLevel is a bit mask to indicate the desired logging options. The value is one of the following adiLogLevel_t

enumerator types:

 ADIHAL_LOG_NONE

 ADIHAL_LOG_MSG

 ADIHAL_LOG_WARN

 ADIHAL_LOG_ERR

 ADIHAL_LOG_ALL



uint32_t errorCode is a 32-bit integer value representing the API error code reference for the error being logged.



const char *comment is a character array that holds the desired comment to represent the error.

Return value: an error of type adiHalErr_t, ADIHAL_OK indicates successful operation. Any other value may represent an error code

to be returned to the application.

Dependencies: the

ADIHAL_setLogLevel HAL function is dependent on application and platform specific modules

UG-1295 ADRV9008-1/ADRV9008-2/ADRV9009 Hardware Reference Manual

Rev. 0 | Page 20 of 247

SOFTWARE INTEGRATION

The API package was developed on a Xilinx Zynq ZC706 reference platform and utilizes a Cortex®-A9 processor that runs a Linux

variant. Using the provided API in a custom hardware and software environment is readily accomplished because the API was developed

abiding by ANSI C constructs and maintaining Linux system call transparency. The ANSI C standard was followed to ensure agnostic

processor and operating system integration with the API code.

IMPLEMENTING HARDWARE ABSTRACTION INTERFACE

Users develop code to target custom hardware platforms and therefore use different drivers for the peripherals, for example, SPI and

GPIO, in comparison to the drivers chosen for the Analog Devices evaluation platform. The HAL interface is a library of functions that

the API uses when the API must access the target platform hardware. The HAL is defined by adi_hal.h. The implementation of this

interface is platform dependent and is implemented by the developer in the adi_hal.c file. The prototypes of the required functions

defined in the adi_hal.h file must not be modified because doing so breaks the API.

Table 1 lists the functions required by the HAL interface for integration. For full details on the definition and required operation of these

functions, see the Hardware Abstraction Layer section and the HAL Interface Definition section.

Table 1. HAL Interface Functions for User Integration

Function Name

Function Description

ADIHAL_openHw Open and initialize all platform drivers/resources and peripherals required to control the device (SPI, timer, logging)

ADIHAL_closeHw Close any resources opened by ADIHAL_openHw

ADIHAL_resetHw Toggle the hardware reset signal for the device

ADIHAL_setTimeout Set the maximum time in which the API expects the HAL functions to complete and return

ADIHAL_spiWriteByte Write a single byte of data to a 15-bit register address on the targeted SPI device

ADIHAL_spiReadByte Read a single byte of data from a 15-bit register address on the targeted SPI device

ADIHAL_spiWriteBytes Write an array of data bytes to an array of register addresses on the targeted SPI device

ADIHAL_spiReadBytes Read an array of data bytes from an array of register addresses on the targeted SPI device

ADIHAL_spiWriteField Perform a read/modify/write to a bit field in a particular SPI register

ADIHAL_spiReadField Read a particular bit field of data from a SPI register

ADIHAL_wait_us Perform a wait/thread/sleep operation in units of μs

ADIHAL_setLogLevel

Mask to set the severity of information to write to the log (error/warning/message)

ADIHAL_writeToLog Log a debug message (message/warning/error) from the API to the platform log

DEVELOPING THE APPLICATION

The /src/app/example/headless.c file provides a user example demonstrating top level configuration and control. The example

application was written to support the control of one device. The API was written to support the control of multiple devices. Because the

API is written in C, a pointer to a

taliseDevice_t data structure is used to describe or point to a particular device. To support

multiple devices, the application layer code must instantiate multiple

taliseDevice_t structures to describe each physical device.

Many initialization settings also have data structures that are defined by the API.

Include Files

The API has multiple .h header files. For core API functionality, Table 2 shows the mandatory .h header files that must be included in the

application layer program. Optional add on API functions can be included if the application requires those features as shown in Table 3.

Note that the places

typedef definitions in files with _types suffixes, for example, talise_types.h. These _types.h files are included

within their corresponding .h files and do no need to be manually included in the application layer code.

Table 2. Mandatory .h Header Files for the Application Layer

Mandatory Include Files Description

talise.h

Core run-time functions

talise_error.h

Core error handling functions

talise_arm.h

Arm related functions

talise_cals.h

Calibration related functions

talise_gpio.h

GPIO related functions

talise_jesd204.h

JESD204B interface related functions

talise_radioctrl.h

Functions for controlling the radio

talise_rx.h

Receiver related functions

talise_tx.h

Transmitter related functions

剩余246页未读，继续阅读

matrix9527

粉丝: 1
资源: 6

ADRV9008/ADRV9009 5G收发器硬件参考手册

ADRV9009文档

ADRV9009-W-PCBZ-Schematic-RevB.pdf

ADRV9008-x-ADRV9009-profile-config-tool-filter-wizard-v2.4.zip

adrv9009-w-pcbz-schematic-revb.pdf

adrv9009-w/pcbz

adRV9364-7020

adrv9009 使用教程

adrv9009配置

adrv9009配置文件

adrv9009芯片手册中文版

adrv9009 zcu706 sdk的生成

adrv9009 adrv9026有什么区别

adrv9029 FPGA

adrv9009 参数

adrv9009 9026 9029 有什么区别

ZC745+ADRV9009

ADRV9009和AD9361区别

adrv9009 9026 有什么区别

adrv9009和adrv9029的区别

adrv9009分辨率

最新资源