• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 99 subscribers
  • Views 792 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TDA4VM: Lauterbach debugging

Nancy Wang
Expert 8210 points

Part Number: TDA4VM

Hi,

Does TI have a script and guide for Lauterbach debugging?

The customer wants to use Lauterbach to debug the TDA4VM chip, however, Lauterbach's script currently does not meet their requirements. For example, they want to use Lauterbach to directly attach a certain core after each core of TDA4 has been boot through emmc, and then load the relevant symbol for debugging.

  • 0
    TI__Mastermind 25425 points
    Hello,
    All cores which are JTAG visible on the TDA4VM chip can be debugged by Lauterbach (Cortex-A72s, Cortex-R5s, Cortex-M3, DSP-C6, DSP-C7, PRU).  It is possible to attach to any of them at run time.  However, in some situations software might need to setup for a safe-attachment point.  Often the easiest way to do this is to code a while(1) loop in some early code on a given core, then attach with JTAG manually.  There are ways to have the debugger take control at the reset vector and then load code but that can have practical complications for some slave cores due to how the complex HLOS code handles the resets.   One useful technique I use is, its possible to set time-relative event insertions which allow for attaching and setting break points without the need for a hand coded loop.  We do make available a number of examples for common Lauterbach usage scenarios (bare metal, RTOS, HLOS).  I'll attach some scripts and a PPT which shows them used on different cores.  The embedded readme's give a rough guide of when to use which scripts.
    If you have up to date support with Lauterbach they can help you on the tool side if you are able to clearly communicate your debug scenario with them.
    Regards,
    Richard W.