Post Go back to editing

PLL Charge Pump Calibration error

Category: Hardware
Product Number: ADRV9029

Hello,

I'm trying to debug our custom board that has the ADRV9029 chip. I'm getting an error during the post MCS sequence (adi_adrv9025_PostMcsInit). This is the first time we've encountered this issue. The error from the ADI API log file is:

2020-02-07 15:51:48: ADI_HAL_LOG:adi_adrv9025_SpiByteRead(...)
2020-02-07 15:51:48: API_PRIV_LOG:adi_adrv9025_SpiDataPack(...)
2020-02-07 15:51:48: SPI_LOG:adi_adrv9025_SpiByteRead(0x00CD, 0xE0)
2020-02-07 15:51:48: ERROR:Error number 3 (0x00000003), Recovery action -2.In file public/src/adi_adrv9025_cpu.c, in function adi_adrv9025_CpuCmdStatusWait, in line 1065, variable name device.Error message CpuCmdStatusWait() failed due to thrown CPU error. Is device in correct state for calling command?.

2020-02-07 15:51:48: API_LOG:adi_common_ErrorClear(...)
2020-02-07 15:51:48: ADI_HAL_LOG:adi_adrv9025_SpiByteRead(...)
2020-02-07 15:51:48: API_PRIV_LOG:adi_adrv9025_SpiDataPack(...)
2020-02-07 15:51:48: SPI_LOG:adi_adrv9025_SpiByteRead(0x00D5, 0x02)
2020-02-07 15:51:48: ADI_HAL_LOG:adi_adrv9025_SpiByteRead(...)
2020-02-07 15:51:48: API_PRIV_LOG:adi_adrv9025_SpiDataPack(...)
2020-02-07 15:51:48: SPI_LOG:adi_adrv9025_SpiByteRead(0x00D6, 0xFF)
2020-02-07 15:51:48: ERROR:Error number 680718 (0x000a630e), Recovery action -2.In file private/src/adrv9025_cpu.c, in function adrv9025_CpuCmdErrorHandler, in line 2512, variable name detErr.Error message ADRV9025 CPU Command Error
.

2020-02-07 15:51:48: ERROR:Error number 65282 (0x0000ff02), Recovery action -2.In file private/src/adrv9025_cpu.c, in function adrv9025_CpuCmdErrorHandler, in line 2524, variable name mailboxErrCode.Error message System:PLL Charge Pump Calibration error.

2020-02-07 15:51:48: ERROR:Error number 3 (0x00000003), Recovery action -2.In file public/src/adi_adrv9025_utilities.c, in function adi_adrv9025_PostMcsInit, in line 1919, variable name ((void *)0).Error message System:PLL Charge Pump Calibration error.

Any suggested software/hardware debug steps to fix this issue?