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

XDS200 or XDS560v2 in combination with TI Concerto

Ken Heuwer
Prodigy 40 points
Other Parts Discussed in Thread: F28M36P63C2

Hi,

We are going to use a TI-Concerto (F28M36P63C2) for a prototype-development and are looking for a emulator which fits our needs. In this context we are interested in the traceability of the ARM Cortex-M3. Following the TI “Trace Analyzer User’s Guide” (http://www.ti.com/lit/ug/spruhm7b/spruhm7b.pdf -> see page 71 & 72), “Data Variable Tracing” and “Interrupt Analyzer” uses SWO trace transport type and requires a XDS200-type emulator. According to the processor wiki (http://www.processors.wiki.ti.com/index.php/Cortex_M3_ITM_Support_for_Concerto_F28M35x), the required emulator for trace functionality is the XDS560v2.

Questions concerning this information:

  1. Which statement is correct? Does the XDS200 really support trace functionality or do we need the XDS560v2?
  2. Which additional features are provided by the USB560v2?

Additionally we are wondering, which JTAG-Header we should use and how to connect the Concerto to it. TI recommends to use the TI 20 pin JTAG Header, if using the Cortex-M3 ITM trace signals (http://www.ti.com/lit/ds/symlink/f28m36p63c2.pdf -> see page 85 & 87). Unfortunately it is not possible to connect both, EMU0 & EMU1 of the standard JTAG-Port and TRACED0…3 & TRACECLK(see page 87). According to the Data Manual, without EMU0 & EMU1 the emulation functions associated with these two signals are not available(see page 85).

 

Questions:

 

  1. Which functions are missing, without EMU0 & EMU1 ? software-breakpoints? Other standard debug features?
  2. Is there an option to keep full standard debug functionality and use the trace functions simultaneously?

              Maybe by using a different Header?     If yes:   Which header and how to connect it to the concerto?

                                                                                                 Which emulator works with this combination?

 

I’m searching for answers to these questions for a while. Blackhawk-Support told me to ask TI-Support for specific features, because their emulator are based on TI reference design. I would appreciate if you could help me to answer these questions and find the right emulator for my project.


Best regards

Ken

  • 0
    Guru 192875 points

    Hi Ken,

    Ken Heuwer said:
    Which statement is correct? Does the XDS200 really support trace functionality or do we need the XDS560v2?

    http://www.ti.com/lit/ug/spruhm7b/spruhm7b.pdf

    You can check this doc for more details:

    Ken Heuwer said:
    Which additional features are provided by the USB560v2?

    Check these out:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/229395.aspx

    Here's the best comparison table: http://www.blackhawk-dsp.com/support/compare.aspx

    Ken Heuwer said:
    • Which functions are missing, without EMU0 & EMU1 ? software-breakpoints? Other standard debug features?

    http://processors.wiki.ti.com/index.php/JTAG_Connectors#Q:_What_are_the_EMU0.2F1_pins_used_for.3F

    Ken Heuwer said:
    • Is there an option to keep full standard debug functionality and use the trace functions simultaneously?

    The above doc and this link together might help you get answers for above query:

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

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Prodigy 40 points

    Hi Gautam,

     

    first of all I want to thank you for your quick answer and collection of links!

     

    The first link concerning the XDS200 trace functions is a link to the document I referred to in my question. In that document there are two trace functions specified (Data Variable Tracing & Interrupt Profiling) which use the SWO and can be accessed by the XDS200. In the above mentioned wiki it is claimed, that a XDS560v2 is necessary for using trace functionality.

     

    Once again: Dose the XDS200 really provide this trace functions? And if yes: Which additional functions does the XDS560v2 provide?

     

    At least: What is the benefit of buying a much more expensive emulator according to the trace functions?

     

    Referring to the Connector: In the Wiki is mentioned, which functions EMU0 & EMU1 could have. The Information I need is which specific function of the F28M36P63C2 will I miss, without EMU0 & EMU1 and is there an option to keep them?

     

    Best regards

     

    Ken

  • 0 in reply to Ken Heuwer
    TI__Guru* 89465 points

    Hi Ken,

    The trace available on the M3 subsystem of F28M35x and F28M36x is ITM as described in this wiki.  An XDS560v2 is required.  The wiki was authored by the developers of the trace support.

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

    For EMU0/EMU1 there is a wait in reset mode that holds the CPU in reset until a emulator/code composer can be connected.  This can be helpful but a few of our devices are missing EMU0/EMU1 at poweron.

    What some of our customers have done is use a XDS200 for most development setups and then have one setup with XDS560 with the full 20pin connector for trace/debug.

    Hope this helps

    Lori

  • 0 in reply to Lori Heustess
    Prodigy 40 points

    Hi Lori,

    This helps a lot! As I wrote in my first post, it is quite difficult to get information concerning this problem. Finally I want to verify, whether I understand your statements correctly.

    1.) The Concerto doesn't support trace via SWO. Correct? The traceability is only provided by the ITM and therefore it is necessary to use a XDS560v2?

    2.) Concerning the EMU-Pins: Without EMU0/EMU1 there is no wait in reset available, what means, it is not possible to program the Flash in this setup? Right? So the option you mentioned is to have one setup using EMU0/EMU1 for Programming and one setup using TRACED0…3 + TRACECLK for debugging?

    Best regards

    Ken

  • 0 in reply to Ken Heuwer
    TI__Guru* 89465 points

    Ken Heuwer said:
    1.) The Concerto doesn't support trace via SWO. Correct? The traceability is only provided by the ITM and therefore it is necessary to use a XDS560v2?

    Correct - there are two types of emulation ports on the device: JTAG and ITM.  SWO is not on the device. Per the data manual:

    Ken Heuwer said:
    2.) Concerning the EMU-Pins: Without EMU0/EMU1 there is no wait in reset available, what means, it is not possible to program the Flash in this setup? Right?

    No you can still program the flash.  The wait in reset keeps the CPU from booting and then running off into the weeds or starting execution of a program before code composer can be connected.   This avoids things like the PWM toggling when you don't want it to.  Or the device continuously resetting because of a watchdog timeout.


    My suggestion was to save $$ in having to populate all development stations with an XDS560v2.  They are are quite pricy when compared to a XDS200. 

    There are some diagrams in the data manual showing the pinout / connections for each on pages 81-82  This may help.   I agree the text is not clear about EMU0/1 "emulation features are not available" should be updated.  I think the description of wait in reset (EMU0/1 pin descriptions is not clear).  I will submit feedback to the doc team for an update to these.

  • 0 in reply to Lori Heustess
    Prodigy 40 points

    Thanks a lot for your support, Lori. I will discuss that with my colleagues. I’m sure, with this information we will be able to find a reasonable solution.

    Best regards

    Ken