• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 99 subscribers
  • Views 2300 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.

External JTAG for TMS320C5505

Alexandre Rosa
Intellectual 300 points
Other Parts Discussed in Thread: TMS320C5505

Hi,

I've developed an audio processor using the TMS320c5505. Wich JTAG can I use to upload and debug the software? I left all JTAG pins the same way it was on the usbstick Kit (see schematic). Will the TMDSEMU100V2U-14T work for this? Can it be used with CCS V.4?


Regards,

Alex

  • 0
    TI__Mastermind 30140 points

    Hi Alex,

    The TMDSEMU100V2U-14T will definitely work with CCS4 (for free!) - the 14 pin version is what we use to debug our EVMs.

    The eZdsp uses an on-board version of the XDS100 emulator, but the TMDSEMU100V2U-14T emulator requires the 14-pin JTAG header to connect to the JTAG signals. There is no header on the eZdsp because the signals go directly to the onboard XDS100 and then to USB port.

    You would be better off referring to the JTAG schematics of the C5515 EVM, which has a JTAG header. Just make sure that the signals are in the same pin locations of the JTAG header (looks good) and the pull-ups & pull-downs match...

    You can ignore the embedded JTAG part of the EVM, and just strip out the J8, the 14-pin JTAG header, and the connections to the DSP. Notice that TCK is shorted to RTCK at the JTAG header (pins 9 & 11). We also have an additional 15pF cap on TCK close to the DSP pin. And we use 100K pull-ups on EMU0 & EMU1.

    Hope this helps,
    Mark

     

  • 0 in reply to Mark M
    Intellectual 300 points

    Hi Mark,

    very helpful!

    Thank you very much,

    Alex

  • 0 in reply to Steve2181
    Intellectual 300 points

    Hi Mark and Steve

    I've done those hardware changes you suggested and my TMDSEMU100V2U-14T has just arrived.

    Following the Start Guide instructions I should be able to select a "TI XDS100v2 USB Emulator" from the "New Target Configuration" menu, but that "v2" doesn't show up...

    Now, when I try to connect I get an Error 0x80000240/-151 (on the first try) and 0x80002240/-121 (on retry).

    From the Device Menu I've tried TMS320C5505 and USBSTK5505.

    I'm using CCSv4.0.0.16000.

    What can be wrong?

    Regards,

    Alex

     

  • 0 in reply to Steve2181
    Intellectual 300 points

    Hi Steve,

    tks for the advice.

    After the upgrade my version is 4.2.3.00004. The XDS100v2 option does appear now.

    The Error I get now is:

     

    Error connecting to the target:

    (Error -1136 @ 0x400)

    Driver lost track of current debug frame. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).

    (Release 5.0.333.0)

    The dbgjtag.exe doesn't  tell what is wrong...

    Any tips?

    Regards,

    Alex

     

     

     

  • 0 in reply to Alexandre Rosa
    TI__Expert 4995 points

    We need mroe information. Please check http://processors.wiki.ti.com/index.php/Troubleshooting_CCS on what's needed to support.

    Generally, need info like ccxml file and results from the http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems at this point.

  • 0 in reply to Steve2181
    Intellectual 300 points

    Hi Steve,

    the whole scenario is:

     

    OS: Windows Vista, SP1, 32bits

    CCS: V4.2.3.00004 

    JTAG: TMDSEMU100V2U-14T

    Target: TMS320C5505

     

    Error:

    Error connecting to the target:

    (Error -1023 @ 0x5F)

    Requested JTAG operation failed. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).

    (Release 5.0.333.0)

     

     

    Hardware Diagnostics:

    Pin TCK & RTCK: Clocking 1MHz

    Pin TDO: There is some Data...

    Pin TDI: There is some Data...

     

    Target Config:

     

    xds100v2.ccxml:

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>

    <configurations XML_version="1.2" id="configurations_0">

    <configuration XML_version="1.2" id="Texas Instruments XDS100v2 USB Emulator_0">

            <instance XML_version="1.2" desc="Texas Instruments XDS100v2 USB Emulator_0" href="connections\TIXDS100v2_Connection.xml" id="Texas Instruments XDS100v2 USB Emulator_0" xml="TIXDS100v2_Connection.xml" xmlpath="connections"/>

            <connection XML_version="1.2" id="Texas Instruments XDS100v2 USB Emulator_0">

                <instance XML_version="1.2" href="drivers\tixds100v2c55x.xml" id="drivers" xml="tixds100v2c55x.xml" xmlpath="drivers"/>

                <platform XML_version="1.2" id="platform_0">

                    <instance XML_version="1.2" desc="TMS320C5505_0" href="Devices\c5505.xml" id="TMS320C5505_0" xml="c5505.xml" xmlpath="Devices"/>

                </platform>

            </connection>

        </configuration>

    </configurations>

     

     

    ccBoard0.dat:

    # config version=3.5

    $ sepk

      pod_drvr=jioserdesusb.dll

      pod_port=0

    $ /

    $ product

      title="Texas Instruments XDS100v2 USB"

      alias=TI_XDS100v2_USB

      name=FTDI_FT2232

    $ /

    $ ftdi_ft2232

      usb_vid=0x0403

      usb_pid=0xa6d0

      gpio_l0="TRSTn,Active_Low"

      gpio_l1="EMU_Pin_Enable,Active_Low"

      gpio_l2="EMU_Pin_0,Active_Low"

      gpio_l3="Adaptive_Clock,Active_High"

      gpio_h0="SRSTn,Active_High"

      gpio_h1="SRSTn_In,Active_Low"

      gpio_h2="Power_Loss_Detect,Active_Low"

      gpio_h3="Power_Loss_Reset,Active_High"

      gpio_h4="EMU_Pin_1,Active_Low"

      gpio_h5="Cable_Disconnect,Active_High"

      gpio_h6="Loopback,Active_High"

    $ /

    $ uscif

      tdoedge=FALL

      jtagboot_mode=disable

      jtagboot_value=hiz

      powerboot_mode=disable

      powerboot_value=hiz

      tclk_program=SPECIFIC

      tclk_frequency=1.0

      loopback_mode=disable

      loopback_value=disable

    $ /

    @ c55xx family=tms320c55xx irbits=38 drbits=1

    # /

     


    dbgJtag:    pathlength

     

    dbgJtag:    integrity

    Please ask for more info if you need.

    Regards,

    Alex

  • 0 in reply to Alexandre Rosa
    TI__Expert 4995 points

    This looks the same as the configuration I have. Also, since your dbgjtag tests all passed, it means your hardware and low level JTAG drivers is working through to the JTAG TAP. For some reason, when you press connect, the core is not responding, which is causing the error. I assume you tried resetting the hardware, there is no ready signal being asserted, etc.

    I will ask some other experts what else could cause this. Do you have another 55x target card like 5515 EVM or eZdsp?

  • 0 in reply to Steve2181
    Intellectual 300 points

    Hi Steve,

    I did some tests with my usbstick kit and figured out that the problem was my target hardware actually.

    I fixed the VIDSP_LDO supply and now I am able to program and debug the DSP!

    The problem is that my schematic is based on the VC5505 UsbStick, which uses the VC5505 DSP instead of the final version of the chip (C5505) . The Pin F13 (USB_LDO_IN) is connected to ground because it's not used on VC5505. But on the C5505 it's wired to DSP_LDO_IN (F14) and ANA_LDO_IN (B12) inside the chip.

    Since in my schematic the Pin F13 is connected to ground at an internal layer, the solution was to remove the solder ball on Pin F13 before soldering the DSP, leaving it disconnected.

    Many thanks for your help.

    Regards,

    Alex