AWRL6432BOOST: Secondary boot loader cannot successfully load the mmw_demo code example

Hey Johnny,

Thanks for reaching out regarding the SBL example. As mentioned in the SBL example documentation, you should flash only one image at a time and reset the board between flashes - i.e., flash SBL image in partition one, reset board, flash application image in partition four, then reset board.

Additionally, is the frame counter in the GUI iterating or does it freeze up past a certain point? 

Regards,

Kristien

I tested two different code examples, not using them at the same time, and no modifications were made to the code examples.

Hey Johnny,

Just a heads up, most of our engineers will be out until July 8th due to a United States holiday. If you have any updates or questions, please hold off on replying until next week when we can respond to you then.

I understand that you tried two different appimages, but I want to clarify that when you are attempting to run the SBL example, you are first flashing the SBL appimage in Meta Image 1, resetting the board, then flashing either the mmWave demo or motion and presence detection demo in Meta Image 4, and doing a final reset before you run the program, correct?

If that is the case, and you're still having issues, then I would recommend uncommenting line 108 of parseFrame.py and running the Python visualizer from source to see if you are receiving TLVs in the visualizer in the first place assuming the frame counter is iterating. This could be a parsing issue, but it could be an issue with the program not outputting TLVs.

Regards,

Kristien

Yes, the steps I followed are the same as the ones you described.

Hey Johnny,

Thanks for the clarification! As mentioned in my previous reply, I would recommend checking to verify the visualizer is receiving TLVs by uncommenting the print statement for tlvType on line 108 of parseFrame.py under <RTB_INSTALL_DIR>/tools/visualizers/Applications_Visualizer/common and running the visualizer from the Python source, gui_main.py. The TLV types are defined in the tlv_defines.py file, so if you aren't receiving any detected point TLVs, then there could be an issue with program not outputting TLVs.

If that is the case, then you can debug the mmWave demo after its been reloaded by the SBL by loading the symbols in the CCS debugger of the mmWave demo after the sbl_switchtoapp function has been called. The TLVs are outputted over UART using the mmw_UartWrite function during the mmwDemo_TransmitProcessedOutputTask.

Regards,

Kristien

The possible cause of the problem is that the shared memory settings of SBL and APP are different. Do you know how to adjust them?

I modified SBL

=== makefile_ccs_bootimage_gen file ===

BOOT_VECTOR_ADDRESS=0x400000
SH_MEM_CONFIG=0x0

=================================

and

=== linker.cmd file ===

MEMORY
{
M4F_VECS : ORIGIN = 0x00400000 , LENGTH = 0x00000200
M4F_SHA_RAM : ORIGIN = 0x00400200 , LENGTH = 0x00040000 - 0x00000200
M4F_RAM : ORIGIN = 0x00460000 , LENGTH = 0x00010000
}

==================

Unable to load other apps.

Hey Johnny,

Its unlikely that the memory configuration for the SBL would cause issues for the secondary image that is loaded. Additionally, is there a reason why you have changed the memory settings for the SBL?

Again, I would recommend following the debugging steps I outlined before, especially the CCS debugger steps, as this will likely be the quickest way for us to understand what is going wrong in better detail. If you could set a breakpoint before the first mmw_UartWrite and any of the subsequent calls in the mmwDemo_TransmitProcessedOutputTask and verify whether they're successful, we can check the call stack if it fails.

Regards,

Kristien

Hey Johnny,

Thank you for letting us know updating to the latest SDK fixed this issue. I will close out this thread now.

Regards,

Kristien