• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 81 subscribers
  • Views 1121 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.

Debugging motor control with TMDSHVMTRINSPIN + TMDSCNCD28069MISO

Alexandre Contrepois
Prodigy 130 points

Other Parts Discussed in Thread: TMDSHVMTRINSPIN

Hello everybody,

I'm trying to develop a motor drive (space vector control) on the evaluation board "TMDSHVMTRINSPIN" and with the control card "TMDSCNCD28069MISO".

I must use the on-board JTAG emulator "XDS100" (since the JTAG signals are not connected on the control card's pins).

But with this emulator I can't do real-time debug. And I need to see the evolution of many variables in real-time (at a sampling frequency equals to 18kHz) to be able to debug my motor drive.  

So my question is: how can I do it? How can I do display variables' evolution in real-time?

Thank you very much for your consideration.

Alexandre 

  • 0
    TI__Guru 57255 points

    Hi Alexandre,

    You mention that the XDS100v2 on the TMDSCNCD28069MISO cannot do real-time debug.

    However, it can.  The following video may help:
    https://www.youtube.com/watch?v=gVDRo9m-4ng

    That being said, it will not be able to enable the refresh rate of 18kHz for your variable (but this is too fast for the eye to see anyway).  A typical refresh rate of viewing variables in real-time with this emulator is about once-every-second.

    The xds100v2, however, cannot do things like emulation cross-triggering.  It will also have a lower rate of communication when compared to something like an xds510 or xds200.  However, even the faster emulators won't be able to get to 18kHz refresh rate.

    ===

    If you're looking to get data at 18kHz, you'll likely need to buffer the data you want locally (and perhaps have it trigger on the rising-or-falling edge of some value - similar to an oscilloscope.  In several of our application kits' software projects we use a structure named dlog.  CCS can then graph this buffer.

    Another option is to send your data somewhere else via an SCI (or some other interface).  This could be a buffer at a lower rate or a variable sent one-at-a-time at a high rate.  The exact implementation would vary depending on exactly what you wish to accomplish.

    Hopefully this helps.


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 130 points
    Hello Brett,

    Firstly, of course the XDS100V2 can do real-time debug. But through the graph value of CCSV6, it's impossible to display a signal corresponding to a variable which is a periodic signal with a frequency higher than 100Hz. For example we can display the speed in real time but not the voltage waveforms (at 100 or 200Hz).

    We have used the buffer solution, as you propose, before your answer (again!). And the results are good for us. We have managed to display 4 different signals, 5000 samples for each at 6kHz. So it's enough to see many things to debug the application. Your answer was correct.

    Finally, I have a question about the XDS510. What are the advantages (in terms of debugging) of the XDS510 compared to the XDS100 except for the clock speed?

    Thank you,
    Alexandre.
  • 0 in reply to Alexandre Contrepois
    TI__Guru 57255 points

    Hi Alexandre,

    Then I apologize again for getting to these questions late.  Hopefully, the extra effort forced you into learning things that will help you as you continue on :).

    For your F2806x device, the advantage of the XDS510 vs the XDS100v1 is speed.  Once you need to load a large program in flash often - because you're debugging, etc - the loading time can become a semi-significant portion of your lab time. 

    On a similar note: the emulator driver for C2000 devices was improved (for speed) in CCS6.1.1


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 130 points
    Hi Brett,

    Yes of course we can see it like that ! :).

    Ok ok. So another question comes to me: for the XDS560 emulator, it's written on your website that "The XDS560v2 PRO TRACE [...] captures all instructions executed by a core and sends them to an external memory buffer (1GB) inside the XDS560v2". I understand that whatever the variable, it's possible to store their datas at the µC clock speed in the XDS560 buffer.

    So it would be possible to store enough samples to display a periodic signal with a frequency of 18 kHz for example. Can you tell me why I'm wrong on this hypothesis?

    Thank you,
    Alexandre.
  • 0 in reply to Alexandre Contrepois
    TI__Guru 57255 points

    Hi Alexandre,

    The majority of the C2000 devices do not support trace capabilities (in order for trace to work, it requires logic to be put into the device - which we did not put in).  This includes your F2806x device.

    The F28M35x and F28M36x devices are the only exceptions at this time.


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 130 points

    Hi Brett,

    Ok I understand. Thank you for your answer, it was very helpful !

    Best regards,

    Alexandre.