Hi Ravi, If controller crash anywhere then you can see the memory window and disassembly code where exactly the controller stuck. For example: The highlighted project is running in the controller without debug mode, and usually the controller should stuck at while(1) after executing main code. Now i want to see where the controller is in code without downloading the actual code. To do this you need to follow below steps: 1. Open target configurations window and launch the target configuration of this project: 2. After launching the configuration, now in debug window do right click on the core and click on connect target. 3. As you can see after connecting the target, i could see the assembly code running in the core and i can also see the required data in the memory window. And also, i could see the arrow to indicate where exactly the core is now. And now you can analyze using memory data and you can do step by step execution in diassembly code. So, CCS can only support up to this point, if you need more debugging data then you should need to use external debugger which can support trace functionality. For more details refer below app notes: Hercules TMS570LC/RM57Lx Safety MCUs Development Insights Using Debug and Trace -- Thanks & regards, Jagadish.
↧