Error during ARM System Programming

Great, thanks: https://temp.sh/owiXc/TES.taxidi

After modifying various TES settings, we finally got both arm_System_Program and initial calibrations working by simply changing the Rx ADC Optimization from High Performance to Low Power. The corresponding TES setup line is:

"Rx1.AdcOptimization": "ADRV9001_ADC_LP" (We are only using Rx1 for now)

The corresponding fields in the code are:

adcType = ADI_ADRV9001_ADC_LP
adcTypeMonitor = ADI_ADRV9001_ADC_LP

Nothing changed in either the ARM or Stream binaries.

Can you help us better understand the implications of this Rx ADC Optimization feature?

Also, while diagnosing the issue, we noticed that the device and pfir checksums both matched between Build and Run, but the FW Run checksum always reported 0 (Build checksum looked correct). Everything appears to work, just want to make sure this is not an issue.

Thanks!

Hello,

Sorry for the delay. I tried to download your taxid` file, but our system blocked the file-hosting website as malicious. Could you attach the profile another way, preferably directly to the thread?

Regarding the Rx ADC optimization question: LP and HP use two different ADC paths, with different power and performance characteristics. Since switching from HP to LP allows the system to initialize and calibrate successfully, this may point to a marginal hardware condition that is exposed when using the HP ADC path.

Could you attach a relevant schematic snippet around the ADRV9001/ADRV9002 Rx path, power supplies, and clocking? If the schematic is sensitive, I can follow up with you directly by email.

This article may also be helpful: Transceiver with Scalable Power and Performance: A Solution to Mission Critical Communications | Analog Devices

For the checksum issue, could you share the exact output you are seeing, including the Build and Run checksum values?

Also, please send the output from running the following utilities:

adi_adrv9001_Utilities_SystemDebugPreCalibrate()
adi_adrv9001_Utilities_SystemDebugPostCalibrate()

These outputs should help determine whether the issue is related to hardware margins, profile configuration, or calibration behavior.

Best regards,

Unfortunately I cannot find how to uploading the `.taxidi` files to this forum page. I can email the `.taxidi` file and the schematics to you directly.

Checksum issue:

FW Build=0xEBCE097A Run=0x00000000
Device Build/Run=0x79AF359E
Pfir Build/Run=0x5B4A96F8


I ran:

adi_adrv9001_Utilities_SystemDebugPreCalibrate();
adi_adrv9001_Utilities_SystemDebugPostCalibrate();


Both Low Power and High Performance start with the following :

*** ADRV9001 Pre-Calibrate System Debugging Started ***

--> . Hardware Reset

OK

--> . API Version

OK - API Version = 0.22.64

--> . Configure SPI

OK

--> . Check SPI

OK

--> . Check Power Supplies

OK

--> . Load Stream Processor Image

OK

--> . Verify Stream Processor Image Load

OK - Version = 0.7.18.0

--> . Load ARM Image

OK


But then Low Power (`ADI_ADRV9001_ADC_LP`) produces:

--> . Verify ARM Image Load

OK - Version = 0.22.64.0

--> . Check Dev_Clk

OK

*** ADRV9001 Pre-Calibrate System Debugging Completed ***

ARM up, die temp=36 C

Part=0x1989 SiRev major=0xc minor=0x0

System_Program mask=0x01

All enabled channels verified

*** ADRV9001 Post-Calibrate System Debugging Started ***

--> . Check RF PLLs

OK

*** ADRV9001 Post-Calibrate System Debugging Completed ***


With High Performance (`ADI_ADRV9001_ADC_HP`):


--> . Verify ARM Image Load

Failed PreCal: ret=-2, Firmware version=0.22.64

src=0x0 code=0x3 act=-2 lastAct=-2

file=../src/ADRV_Driver/adi_adrv9001_utilities.c func=adi_adrv9001_Utilities_SystemDebugPreCalibrate line=401 var=NULL

msg=ARM Start Status Check Error.

Following up on this: The 9006 Data sheet seems to only document performance specs for the low power ADCs (no mention of the high performance). Looking at the feature differences in UG1828 page 12, under "ADC Option" ADRV9006 is listed only as LP, rather than HP/LP.

Should we take all of this to mean that High Performance is simply not an available option on the 9006, and that's why the ARM System Program is failing?