• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 102 subscribers
  • Views 2850 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.

TMS320C6748: JTAG with XDS200 Emulator: Emulator Insertion sequence

Valerio Giampa
Prodigy 145 points
Other Parts Discussed in Thread: TMS320C6748

I have a board with a Texas Instruments DSP TMS320C6748.

The jtag interface connection is based on the attacched schematic diagram.

The next emulator sequence doesn't work:

1. Insert the connector of the XDS200 JTAG Emulator,

2. Power Up the device.

3. Run the debug session

Code Composer is not able to find the target.

The next emulator sequence works fine:

1. Power up the device;

2. Insert the connectior of the XDS200 JTAG Emulator,

3. Run the debug session

Code Composer is able to find the target and to start the debug session.

Can anyone suggest a possible solution?

  • 0
    TI__Mastermind 43660 points
    Valerio,

    I don't see any issue in your schematics. What is the error message you are getting when you are not able to connect to the target ?

    Did you try these sequence on LCDK board ?

    Regards,
    Senthil
  • 0 in reply to Senthilkumar Srinivasan
    Prodigy 145 points

    The error is:

    Error initializing emulator:
    (Error -2083 @ 0x0)
    Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.
    (Emulation package 5.1.641.0)

    with the LCD Board I haven't this problem.

  • 0
    TI__Guru** 116100 points
    Dear Valerio,

    I have also seen this behavior, it might happen if you remove or insert the JTAG cable forcely...

    1. Power up the device;

    2. Insert the connectior of the XDS200 JTAG Emulator,

    3. Run the debug session

    Code Composer is able to find the target and to start the debug session.

    Power OFF the board and power ON again (don't remove the JTAG ).

    1. Connect the core in CCS.

    2. Run the debug session

    Now, what is the status ?
    Able to connect the core and debug ??
  • 0 in reply to Titusrathinaraj Stalin
    Prodigy 145 points
    Hi,
    Yes, I can execute the sequence.
    After the second power off-on, I can tun a code composer debug session without remove/insert the emulator again.
    It is normal?
    ...I have fear that the first jtag insertion with the powered board can broke the DSP jtag pins for ESD.
  • 0 in reply to Valerio Giampa
    TI__Guru** 116100 points
    Dear Valerio,
    How this problem came initially ?
    I hope this problem could come if we didn't use the JTAG properly.

    Once its started working then you can follow the correct procedure to connect and disconnect the JTAG session & JTAG insertion and removal.
  • 0 in reply to Valerio Giampa
    TI__Mastermind 43955 points
    Hi valerio,

    valerio said:
    Error initializing emulator:
    (Error -2083 @ 0x0)
    Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.
    (Emulation package 5.1.641.0)


    This is one of the common erros noticed, captured and projected in this TI WIKI :
    processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems
    and the below are the listed reasons for it.

    An extract from the WIKI:

    Host connection error
    The error below is thrown by CCS when the device driver is unable to communicate with the JTAG debugger either via USB or Ethernet.
    Due to the nature of the different debug probes, the error messages vary according to the XDS family.

    This can have several sources:

    The Windows device drivers are not properly installed or failed to initialize. Check the Windows Control Panel or the XDS200 known issues.
    The Linux udev rules are not properly configured. Either check Linux lsusb and udev rules, run the install_drivers.sh script as shown here or check the XDS200 known issues.
    The JTAG debugger failed to boot properly (XDS200 and XDS560v2)
    The JTAG debugger is not powered (some variants of XDS560 and XDS560v2)
    The USB cable has loose contacts or not connected at all

    --------------------------
  • 0 in reply to Shankari G
    Prodigy 145 points

    I think that it is not a problem involved by Windows driver, jtag debugger boot failed or jtag debugger power missing becouse with the LCDK kit I have not this problem.

  • 0 in reply to Valerio Giampa
    Prodigy 145 points

    In the TMS320C6748 Datasheet at page 82 - section 6.4.1, there is this description:

    "JTAG controllers from Texas Instruments actively drive TRST high. However, some third-party JTAG controllers may not drive TRST high but expect the use of a pullup resistor on TRST. When using this type of JTAG controller, assert TRST to intialize the device after powerup and externally drive TRST high before attempting any emulation or boundary scan operations."

    Also, in the electrical interconnection between the XDS200 JTAG Emulator and the TMS320C6748 that I have implemented, there is an external pull down on the TRST# pin.

    Is it possible that the XDS200 Emulator would see the TRSTN high at power up in order to permit the correct POR sequence of the DSP?


    """ 

  • 0 in reply to Valerio Giampa
    TI__Mastermind 43660 points
    Valerio,

    Yes, it is recommended to have a pull down resistor on TRST# pin and it all the way working fine in all of our EVMs. Please refer below wiki page for more details.

    processors.wiki.ti.com/.../XDS_Target_Connection_Guide

    Regards,
    Senthil