AWRL6432: RFS boot timeout error on Custom Hardware

Hi Vishnu,

I will look into this. A couple of questions for you below:

1. Can you please tell me the process you are using to run the example? Flashing the .appimage file and running in functional mode or loading the example code through CCS? 
2. Are you using the prebuilt demo code without any modifications? 
3. Could you share an image of the specific error message that you see?

Best Regards,

Josh

Hi Josh

1. Can you please tell me the process you are using to run the example? Flashing the .appimage file and running in functional mode or loading the example code through CCS? 
   1. Loading example code through CCS
2. Are you using the prebuilt demo code without any modifications? 
   1. Made two changes in the code
      1. CLI_BYPASS is defined in mmw_cli.c
      2. In MmwDemo_calibInit() function, hard coded gATECalibDataStorage values as ATE calib binary is not flashed
3. Could you share an image of the specific error message that you see?
   1. 

Thanks & Regards

Vishnu

Hi Vishnu,

Thank you for the answers.

Can you please list each of the steps you are taking when loading code to the device and running in CCS? Please refer to the guide called 8132.xWRL6432_APL_CCS_debug_guide.pdf on this FAQ page. Have you completed the same steps as described in this guide?

 Can you please read below addresses and get me the value to make sure configuration is correct?

0x52000018

0x5A040500

vishnu vikash said:

In MmwDemo_calibInit() function, hard coded gATECalibDataStorage values as ATE calib binary is not flashed

We have not done much if any testing with the ATE calibration values hardcoded in this way. Have you confirmed this is working with the xWRL6432L EVM from TI where the ATE calibration data is not flashed?

 Best Regards,

Josh

Hi Josh,

Can you please list each of the steps you are taking when loading code to the device and running in CCS? Please refer to the guide called 8132.xWRL6432_APL_CCS_debug_guide.pdf on this FAQ page. Have you completed the same steps as described in this guide?

We are following all the steps as mentioned in 8132.xWRL6432_APL_CCS_debug_guide.pdf documents except last step as mentioned in page 10 in the document. we are not loading "mmwave_rfs.bin" file into the 0x21208000 memory location. Even without this step are able to get proper output using EVM in the debug mode.

 Can you please read below addresses and get me the value to make sure configuration is correct?

0x52000018

0x5A040500

Below I have attached an image with memory browser containing values for your reference. And I am getting the same value in the xWRL6432 EVM from TI and it is working properly there.

We have not done much if any testing with the ATE calibration values hardcoded in this way. Have you confirmed this is working with the xWRL6432L EVM from TI where the ATE calibration data is not flashed?

Yes, we have confirmed that it working properly with xWRL6432 EVM from TI.

Best Regards,

Vishnu

Hi Vishnu, 

vishnu vikash said:

Even without this step are able to get proper output using EVM in the debug mode.

Clarification needed here. Can you confirm, before running debug procedure on the EVM, have you flashed the empty example appimage (MMWAVE_L_SDK_05_01_00_04\examples\empty\xwrL64xx-evm\m4fss0-0_freertos\ti-arm-clang\empty.debug.appimage)? Without first flashing that image or manually loading the rfs binary to memory as described on page 10 of the guide, the device is not expected to give proper output in debug mode. This is why I'm suspecting that you have flashed the empty.appimage. 

vishnu vikash said:

we are not loading "mmwave_rfs.bin" file into the 0x21208000 memory location

Can you please try the debug procedure again including this step and see if the error persists? 

Best Regards, 

Josh

Hi Josh

Clarification needed here. Can you confirm, before running debug procedure on the EVM, have you flashed the empty example appimage (MMWAVE_L_SDK_05_01_00_04\examples\empty\xwrL64xx-evm\m4fss0-0_freertos\ti-arm-clang\empty.debug.appimage)? Without first flashing that image or manually loading the rfs binary to memory as described on page 10 of the guide, the device is not expected to give proper output in debug mode. This is why I'm suspecting that you have flashed the empty.appimage.

We have not flashed any empty example appimage in the xWRL6432 EVM from TI and also we are formatting the flash memory with the help of uniflash. By doing so in xWRL6432 EVM, I am able to run the code properly in the debug mode and getting proper output. As this method was working properly for us, Followed the same steps in the Customer Board and getting "RFS boot time error".

we are not loading "mmwave_rfs.bin" file into the 0x21208000 memory location

I am sorry. We are following this step already in both EVM & Customer hardware. The java script we use already includes these steps as shown below.

//RFS Firmware. Edit this
rfsfw_bin = sdkPath+"/firmware/mmwave_dfp/rfsfirmware/xWRL6432/mmwave_rfs.bin"

print("Loading RFS Firmware!");
dsM4F_0.memory.loadRaw(0, 0x21208000, rfsfw_bin, 32, false);

Can you please try the debug procedure again including this step and see if the error persists?

We also tried the steps exactly mentioned in the user guide, including flash empty example appimage, then loading rfs binary into 0x21208000 adress location. Still my code is getting stuck at same place with same error as shown below.

Calibration Validated for restore
Debug: CLI is operational
ASSERT: 0.35311s: ../../../motion_detect.c:mmwDemo_factoryCal:2496: 0 failed !!!

Best Regards,

Vishnu