Hi Experts
The customer use scripts in SDK 03.05.0.40 to create the image, they already fix that due to their application that the image can not work. Is there any tools to help debug
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi Experts
The customer use scripts in SDK 03.05.0.40 to create the image, they already fix that due to their application that the image can not work. Is there any tools to help debug
Hi,
The first step for this would be to confirm that the JTAG debug binaries (.xer4f and .xe674) are working as intended with the device in CCS debug mode.
Then, I would recommend double checking the usage of the scripts to create the app image (.bin file). The OOB demo makefiles can be used as a reference for this. First both .xer4f and .xe674 binaries need to be converted to the RPRC format, and then combined into a single multicore image (.bin file). There are scripts to do this. For sanity checking, it would be worth trying to see if you can create a working OOB demo image from OOB demo's .xer4f and .xe674 files successfully.
If this is the case and the image (.bin) still doesn't work when flashed, we can get an idea of the issue with CCS.
CCS is capable of debugging the device with custom images flashed (the debugging capability will be reduced as compared to the normal mode of debugging with CCS where CCS debug image is flashed). You can connect the cores with CCS, and instead of using "load program", use the "load symbols" option and load the symbols (the .xe674 and .xer4f files) corresponding to the flashed image. With this, you would be able to debug the flashed program.
Regards,
Aayush