Using Vitis currently running debug to try and narrow down the scope of where our in house custom board is failing. In a cluster of known good and passing production boards this one tends to fail the ADI_ADRV9001_INIT_CAL_TX_ATTEN_DELAY and the ADI_ADRV9001_INIT_CAL_RX_GAIN_PATH_DELAY. These fails come with similar errors as other forum posts. Mainly just "calibration failed with error code 7". Along side this when i remove these init cals from the cal mask for the channels i can successfully initialize the radio and our in house automated tests sees some pretty catastrophic failures on both TX lines.
This is where i can begin to more effectively describe my issue at hand.
The adi code debug utility has 4 arguments(device pointer data structure, pointer to initialize data structure, absolute path for the arm image to be programmed, absolute path for the stream image to be programmed)
my efforts thus far seem to allow only some of the debug utility to act accordingly. I've had to comment out the hardware reset because the system seems to hang up waiting for an assert each time this is called. I pass all of the tests up until "Load Stream processor image", the same goes for what occurs with the ARM image later in the debug utility.
I currently write the initialize_binary_9 and initialize_binary_10 arrays out to a *.bin file on the SD card using modified versions of functions in sdFiles.c, although this is working the debug utility still freezes any time it is loading the image.
My current DebugPreCalibrate call looks as such:
adi_adrv9001_Utilities_SystemDebugPreCalibrate(adi_adrv9001_device_pointer, &initialize_init_7, "armImage.bin", "streamImage.bin");
I have also confirmed that these are being written appropriately in a non corrupted state to the same SDCard that houses the BOOT.bin, and later on in product use houses our I and Q data captures
Any information or steering into a clearer direction would be greatly appreciated, I'm beginning to think that the absolute path provided to the function isn't correct because these images are supposed to be written to the ADRV
