AUDIO-AM62D-EVM: Steps to Debug .out File from Makefile Build Using CCS

Hi Kaviyarasan,

Please tell us for which core you want to load the example?

Please follow below guide to run & debug program via CCS.

Please refer CCS_LAUNCH_RUN 

Regards,

Tushar

I do run with c75 - core

Can I debug multiple cores simultaneously? My audio application uses both the C7x and MCU-R5F cores (config 1). What is the recommended procedure to start debugging in this case? When I attempt to connect to both cores consecutively, I receive the following error:
SMS0_HSM_0: Error connecting to the target.

I’m using Config-1 (MCU-R5F and C7x) as described in the Getting Started Guide. I have already flashed the Audio App onto the AM62D board and loaded the .out files for both cores. However, when I try to debug, I’m unable to connect AWE to the board. Could you provide the correct debug procedure?

Kaviyarasan Balakrishnan said:

I have already flashed the Audio App onto the AM62D board and loaded the .out files for both cores.

If you have already flashed the application to the SOC, you will not need to reload that from CCS again. The program is already running at this point. 

If you want to debug, you can Load Symbol from CCS by uploading the same binary flashed.

I have already flashed the Audio App onto the AM62D board and successfully loaded the .out files for both cores using the "Load Symbols" option in CCS. However, when I attempt to debug, I am unable to connect the AWE server to the board.

Could you kindly provide the correct debugging procedure? If possible, please share a step-by-step guide or a video capture of the process for better clarity.

Please add a loop forever inside main() in your application which you want to debug. Rebuild the application and re-flash it to the EVM.

Connect the core and load the symbol from CCS. Your code should stop at loop forever.

Please refer  [FAQ] AM62X/AM64X : [FAQ] Debugging SBL boot in RTOS SDK for step by step procedure. The FAQ is for SBL, but you can use the same procedure for your application.

I made the above-mentioned changes in the R5F code located at:
C:\ti\AM62D-AWE-SDK_11.00.00.17\mcu_plus_sdk\am62dx\examples\drivers\boot\sbl_null\am62dx-evm\r5fss0-0_nortos\ti-arm-clang.

After building, I loaded the generated .out (debug) file using the Load Symbols option for the WKUP R5F core in CCS, but the code was not reflected in the debugger.

I then tried the same procedure with the MCU-R5F core, but faced the same issue.
Could you please suggest what might be causing this and the correct procedure to load and debug the updated code?

Are you resetting the core before loading the binary? You should not reset the core.

Also please provide a screen record of the procedure you are performing.

please find attached.

I sincerely apologize for the confusion. Until then, I had been using the Load Symbols option, but I kept encountering the same error. Could you please provide clarification, preferably with a video demonstration?

I have not run the GEL script manually; I believe it is integrated to run in CCS in the background. However, even when I try to initialize DDR, I continue to encounter DDR initialization errors. Additionally, the code does not appear in the CCS debugger for me to debug.

I think there is a little bit of confusion here. Please confirm below points.

1. What is running on WKUP_R5F? Have you flashed any application to the WKUP_R5F core?

2. If yes, What is the application flashed to R5F core?

3. You are trying to load the SBL NULL binary on R5F core. Is this the application you flashed?

• What is running on WKUP_R5F? Have you flashed any application to the WKUP_R5F core?
  Answer: No. As per the instructions in the above FAQ, I made changes in the R5F code and loaded it in the WKUP_R5F core.
  (+) [FAQ] AM62X/AM64X : [FAQ] Debugging SBL boot in RTOS SDK - Processors forum - Processors - TI E2E support forums

• If yes, what is the application flashed to R5F core?
  Answer: N/A

• You are trying to load the SBL NULL binary on R5F core. Is this the application you flashed?
  Answer: No. I modified the code in that location, which is where I made the changes.
  
  
  

The FAQ is just for the reference. You need to add the loop forever in the application which you are flashing.

The same binary needs to be loaded from the CCS as well. You are trying to load SBL NULL which is not correct.