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

RM48L952: XDS100v2 vs XDS200 speed comparisons

Andrew Hartnett
Intellectual 890 points

Part Number: RM48L952

Hello,

We are designing a custom PCB with the RM48. We saw charts that showed how it's very processor dependent on whether the XDS100v2 is faster or slower than the XDS200 (http://processors.wiki.ti.com/index.php/XDS_Performance_comparison, but couldn't find one for the RM48L952. Are there any comparisons out there? Specifically between the following modes

  • XDS200 SWD mode
  • XDS200 JTAG mode 
  • XDS100v2 5 MHz TCLK
  • XDS100v2 1 MHz TCLK

This will impact how we decide to build up our PCB to be able to load our files on it, as we've found an XDS100v2 design that we could integrate on the board. Otherwise, we would use an external XDS200 programmer

Thanks,

Andrew

  • 0
    TI__Guru**** 163015 points
    Andrew,

    I don't have any CortexR based benchmarks on hand. I will ask around and see if anyone has some observations or if someone has a RM board with a JTAG header populated that we could run some tests on.

    Another option is the XDS110. Its performance falls in-between the two on most tests.

    Regards,
    John
  • 0 in reply to JohnS
    Intellectual 890 points

    Any benchmark data would be very useful.

    We were able to identify a design for the XDS100v2 which is why we're investigating the XDS100 vs XDS200. The idea would be that it would be nice if our device could just plug in via USB without having to have any other special hardware (if required in it's lifetime). But if the XDS100 design is slow enough relative to the XDS200 that testing and debugging it would be unpleasant, we would just set it up such that the extra hardware (a USB to JTAG XDS200 programmer) is required to reprogram it if needed during the devices lifetime. 

  • 0 in reply to Andrew Hartnett
    TI__Guru**** 163015 points
    If you are using most of the memory on the device then programming via the XDS100v2 could be slow. Would having a dual setup be an option? i.e. do your development with an external XDS200 but still have the XDS100v2 on the board just in case you need to do an in-field update. Given your environment you may want some or all of the testing to also use the XDS100v2 to ensure that everything will work for in-field updates.

    Some of our newer LaunchPad development boards work in a similar way where they have an onboard XDS110 but then we also have a JTAG header present if you want to use a different debug probe. You just pop off a couple jumpers to disable the onboard and enable the header. Section 2.3.3 of this document shows an example: www.ti.com/.../slau597d.pdf

    That way you benefit from the faster speed during development but also from the simple setup if you need to do an in-field update.

    I am still looking for some numbers.

    Regards,
    John
  • 0 in reply to JohnS
    TI__Guru**** 163015 points
    I found a side by side comparison video on a Hercules device.


    It is about 7 minutes into the video

    training.ti.com/hercules-how-tutorial-selecting-jtag-emulator
  • 0 in reply to JohnS
    Intellectual 890 points
    That's enough to convince me that we want to utilize the 200 on this. Thank you!
  • 0 in reply to JohnS
    Intellectual 890 points
    Definitely a reasonable suggestion, but in our specific application this would not pan out.