Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

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.

RM57L843: Crash dump analysis on CCS for RM57

Part Number: RM57L843

Tool/software:

Hi,

Does Code composer support crash dump analysis for RM57? If so, in what format should I save the crash dump for it to be analyzed in CCS?

Thanks,

Ravi

  • 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.

  • Hi Jagadish,

    I think my question is about crashes that occur in production. We would like to save the context such as register values, stack contents to somewhere in flash whenever the system crashes/aborts which can be retrieved later for analysis. I remember reading somewhere in ti forums that those crashdumps can be analyzed offline in CCS but it has to be in a certain format for it to be analyzed in CCS.

    Thanks,

    Ravi

  • Hi Ravi,

    I remember reading somewhere in ti forums that those crashdumps can be analyzed offline in CCS but it has to be in a certain format for it to be analyzed in CCS.

    Can you please point me out where exactly you find those information.

    As per my knowledge i didn't see anything like that for Hercules controllers.

    --
    Thanks & regards,
    Jagadish.