• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 770 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Speed up the Loading time with Blackhawk XDS100v2 emulator

Ayaka Ohira
Intellectual 440 points

Hi people,

I have a custom board with F28377D, using CCSv6 IDE for programming.

We have been using Blackhawk XDS100v2 device to debug/program the chip and it has been working quite well apart from the loading speed.

To speed up the loading time we purchased Spectrum Digital's XDS200 USB JTAG emulator and tried it out, only to find that we cannot use the emulator because we are using the free version of CCSv6. 

Moving on, we have gone back to using Blackhawk XDS100v2 emulator but emulator settings have somehow been overwritten by the last emulator.

First thing we noticed that it did differently was that It started loading programs for CPU1 and CPU2. Just before loading the program, a window popped up and asked if we wanted to program CPU1 and CPU2. First time it popped up, we selected both, which then started loading both CPUs. We wanted to switch this off but could not find where we could do this (Could someone let me know?) Anyway, some how we got the same window coming up again and this time we selected CPU1 only, so it's loading the program for CPU1 only now.

However loading the CPU1 takes 10 times slower than what it used to do.

Could someone please let me know how to speed up the loading time with Blackhawk XDS100v2 emulator?

Also why would plugging in Spectrum Digital XDS200 USB JTAG emulator overwrite the previous debugger settings?

Would appreciate if someone could help us!

Thanks,

Ayaka

  • 0
    TI__Guru 57255 points

    Hi Ayaka,

    I've moved your question to the Code Composer forum where your question should get the best support.


    Thank you,
    Brett

  • 0
    TI__Guru**** 168367 points

    Ayaka,

    Ayaka Ohira said:
    We wanted to switch this off but could not find where we could do this (Could someone let me know?)

    This is defined in the Debug Configurations settings for your debug session. For details and overall information, check section 2.3 of the page below:

    http://processors.wiki.ti.com/index.php/Debug_Handbook_for_CCS

    Ayaka Ohira said:
    However loading the CPU1 takes 10 times slower than what it used to do.

    That is a very odd scenario, but one of the settings of the Debug Configurations is the Full verification - if enabled, the code will perform a complete verification of the data written, which may take time. For details about this, check section 3.1 of the page above.

    Another detail that may help you are the TCLK settings, but this is set on the .ccxml file and would require manual change of its Advanced settings tab (section 2.2.1 of the page above).

    Also, never forget that something may have coincidentally gone wrong with the hardware (cables, etc.) - I have seen this happen before.

    Ayaka Ohira said:
    Also why would plugging in Spectrum Digital XDS200 USB JTAG emulator overwrite the previous debugger settings?

    I am not sure what may have happened, as Debug Configurations are automatically created for each individual target configuration file (.ccxml). What could have happened is that you simply modified your existing .ccxml to use the XDS200 (which would recreate this file, overwriting the previous parameters) and reverting this to XDS100v2 would have restored the workspace default settings.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 440 points

    Hi desouza,

    Thanks for the help.

    It seems that the speed issue has been fixed by fiddling around with some things. I can't tell you exactly what but one thing we tried was re-install the XDS100v2 driver. That didn't fix it straight away but when we restarted the PC XDS100v2 was behaving the same way as before.

    Really puzzling but fixed the issue for now.

    Thanks,

    Ayaka

  • 0 in reply to Ayaka Ohira
    TI__Guru**** 168367 points
    Ayaka,

    Thanks for reporting your conclusions, and feel free to reply if this comes back at you.

    Regards,
    Rafael