Post Go back to editing

adrv9009 TALISE_waitInitCals() API failed

Category: Hardware

The TALISE_waitInitCals() API function return error code is 0x07. I use TALISE_getInitCalStatus() API function to get initCalError code is 0xE and initError code is 0x5. I checked the manual, but the corresponding Bit seems to be reserved.

  • The TALISE_waitInitCals() API function return error code is 0x07

    Looking at the error code seems like its failing in calibration.

    I use TALISE_getInitCalStatus() API function to get initCalError code is 0xE and initError code is 0x5

    From the initErrCal status seems its failing in RX QEC init cal .

    Can you check whether the RX QEC cal is running using getRxQecStatus() API , you should see no error code and iter and update count incrementing.

    What is the RF PLL frequency used ?

    Are all the default init and tracking cals running?  Hope you are using the default calibration mask as given in headless.c. 

    uint32_t initCalMask = TAL_TX_BB_FILTER | TAL_ADC_TUNER | TAL_TIA_3DB_CORNER
    | TAL_DC_OFFSET | TAL_TX_ATTENUATION_DELAY | TAL_RX_GAIN_DELAY | TAL_FLASH_CAL |
    TAL_PATH_DELAY | TAL_TX_LO_LEAKAGE_INTERNAL | TAL_TX_QEC_INIT |
    TAL_LOOPBACK_RX_LO_DELAY | TAL_LOOPBACK_RX_RX_QEC_INIT |
    TAL_RX_LO_DELAY | TAL_RX_QEC_INIT;

    uint32_t trackingCalMask = TAL_TRACK_RX1_QEC |
    TAL_TRACK_RX2_QEC |
    TAL_TRACK_TX1_QEC |
    TAL_TRACK_TX2_QEC;

    Is this eval or custom board? Matching could be a reason which might impact QEC cals . 

    Can you try disabling RX QEC cal and see if you are successfully able to go through the initialization ?

    Please refer to the below post.

    https://ez.analog.com/wide-band-rf-transceivers/design-support-adrv9008-1-adrv9008-2-adrv9009/f/q-a/166582/error-294-talise_waitarmcmdstatus-failed-due-to-thrown-arm-error-is-device-in-correct-state-for-calling-command