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.

CCS/TMDX570LC43HDK: FreeRTOS debugging options on TMDX570LC43HDK

Part Number: TMDX570LC43HDK
Other Parts Discussed in Thread: HALCOGEN

Tool/software: Code Composer Studio

Good morning,

I'm interested to know all available debug opportunity for FREERTOS applications on TMDX570LC43HDK.

It seems that Tools --> RTOS Object View

is not available due to XDC not covering "ARM® Cortex® - R5F 32-Bit RISC CPU", is it true?

Also "Tools-->Hardware trace analyzer" seems to be not availablemaybe due to the same reason,

the same for "Tools-->System analyzer" and "Tools-->RTOS analyzer".

And also, is available some tutorial to use "freertos trace" on this board?

Thanks,

Antonio

menu requires

  • Hello Antonio,

    Unfortunately, I am not familiar with the tools that you have listed. Our product overview pages has some of our 3rd party support options for both debug and trace.

    The hercules device debug is supported through several standard emulators such as XDS100V2, XDS110, XDS200, and XDS560v2. The complete list can be found here: www.ti.com/.../tools-software.page

    For trace capability, there are several options available. The most notable of these is the TRACE32 PowerView by Lauterbach. Again, the complete list can be found here: www.ti.com/.../tools-software.page
  • I used HalCoGen with "freeRTOS trace" enabled on a different chip. I suspect they capabilities would be the same. It generates a good number of stubs for various RTOS behaviors that FreeRTOS supports. The user is then to add any debug/trace actions. I found it a valuable capability, even though all the trace actions had to be created. Once I solved the problems, I removed that feature. A simple example would be to have printf lines in the stubs.
  • I'm interested but do you think it is possible to use this freertos trace with XDS100V2 default JTAG  for this board?

    Thanks

    Antonio

  • I am not familiar with XDS100V2 default JTAG, I use XDS100V2 USB debug probe, and connect to running code by breakpoints.

    I have used JTAG on other devices, and hardware breakpoints were minimal but available.

    So, one way to use this is the create the trace stubs and fill in code that selects a state or condition you want to confirm exists.  Then place a break point there.

    Another way to use trace stubs, would be to fill in code that changes an LED or IO point (no break points involved).

    If you can connect to debug session, then it might be irrelevant to use the rtos trace; you might simply be able to get most things done with printf statements.  

  • Thanks for your answer,
    my interest is not strictly on debug but also to check freertos behaviour for our real time application,
    this is the reason why I'm interested to FREE-RTOS trace free edition
    percepio.com/.../