• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 83 subscribers
  • Views 682 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.

Hints for use of debugger, watching variables evolve as in Instaspin labs?

Janet Stillman
Prodigy 90 points

Other Parts Discussed in Thread: DRV8312, MOTORWARE

Hello,

We have a setup with the DRV8312 kit that we have run through the labs with a USB connection, watching variables evolve as programs progress as instructed in the labs. We have also made our own boards that we can connect to through jtag, using motorware code that is still quite close to the code from the lab examples. With our jtag connection, which I know of course is slow, I can't seem to find a debugger setting that lets us watch a set of variables during program execution. We are instead setting breakpoints and examinign variables when execution pauses. 

Is it possible to watch variables with a low update rate during execution over the slow jtag link, similarly to how we watch and manipulate them over the USB link in the labs? If so, what are the relevant settings? I have the build and debug settings set up now to load symbols, and have made a quick first pass comparing debug and build settings for our custom code to the settings in the labs, and see no additional obvious differences (aside from USB vs JTAG). In the debugger window, I select real-time mode and continuous refresh for the variables.

Suggestions most appreciated.

Regards,

JS

  • 0
    TI__Guru** 119680 points
    which JTAG emulator are you using?
    The one included on the controlCARDS, LaunchPads, and some EVMs is one of the slowest available (XDS100).
    When you say "USB" it is just USB to JTAG through the XDS100 emulator.

    Any external pod you've connected should also use a USB cable and give at least as fast of access.

    You may want to check the GPIO pull-ups for the JTAG capability on your own board. On the controlCARD this capability is managed with switches....but if you did this incorrect you would get NO communication over JTAG not just slow communication.
  • 0 in reply to ChrisClearman
    Prodigy 90 points
    Chris,

    Yes, this is USB to JTAG with the XDS100v2 JTAG emulator.
    The JTAG does work: we can download, program, set breakpoints, pause, step, etc. Just can't figure out how to see variables while running, as in the labs setup without the JTAG emulator.
  • 0 in reply to Janet Stillman
    Guru 13185 points

    Did you already enable "Continuous Refresh" in CCS? It is an icon in the right of "Refresh" icon.

    What do you mean by "to see variables while running, as in the labs setup without the JTAG emulator."

    I use SCI (modbus) for my project to see some variables (and also to give input, enable flags) while running.

    Best regards,

    Maria

  • 0 in reply to Maria Todorova
    Prodigy 90 points
    Maria,

    Yes, continuous refresh is selected. Also realtime mode.
    By seeing variables while running, I mean while spying on the processor while it is running, be able to watch in real-time mode the values of variables change, as updated over the jtag line and fed directly into the watch window of the debugger.