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

limitations of XDS100V1 Emulator

Nagaprakash Nagarajan
Prodigy 50 points

I use TI Piccolo Controller (F28035) for synchronous motor control development. For debugging, I used TI XDS100V1 USB Emulator. I created a variable as an array to watch the position data whose length is 16. My algorithm running time is 100 us. For a constant speed (15 ms for 1 revolution), i expected 150 position data since my algorithm running at 100 us. But I observed that only 5 data available for 1 revolution in Watch Window. I found that data is refreshed for every 3ms (approximately).But I want to see the variable in a faster rate (say every 20 us).

Is it possible to adjust any settings in TI XDS100V1 USB emulator to have desired refresh rate?

If not, what is the limiting factor/limitations in TI XDS100V1 USB emulator?

Kindly suggest  suitable TI supported Emulator to meet the desired requirements.

Thanks,

NNP

  • 0
    Guru 192875 points

    Nagaprakash Nagarajan said:
    For a constant speed (15 ms for 1 revolution), i expected 150 position data since my algorithm running at 100 us. But I observed that only 5 data available for 1 revolution in Watch Window. I found that data is refreshed for every 3ms (approximately).But I want to see the variable in a faster rate (say every 20 us).

    I'm not sure how you're able to observe 3ms refresh via CCS!

    Nagaprakash Nagarajan said:
    Is it possible to adjust any settings in TI XDS100V1 USB emulator to have desired refresh rate?

    Check this extract:

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    TI__Expert 4595 points
    Hi NNP,

    Gautam's guidance on continuous refresh of the Watch Window is correct.

    Keep in mind, your software has control over the "realtime" saving of data and CCS is a Windows application where the data is updated on the screen in non-realtime, but the data that is displayed is realtime data that your SW saved at the rate your SW controls. So you could save data every 100 us in a circular buffer and then display this array (declared as a global variable) in the Expressions Window that is configured for continuous refresh. You will then see the latest realtime data, with CCS displaying the target's circular buffer stored in local RAM.

    If you were trying to save the data for post-analysis and you wanted to save the actual data, then the communication data rate is more critical. In that case you could use a high-speed serial port connected directly to the PC and save the data to a file.

    Jeff