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.

TMS470MF06607: JTAG communication with only VSS, VSS and OSCIN

Part Number: TMS470MF06607

Hello,

I am trying to avoid superfluous detail and over explaining - in short I am curious as to if you can 'test the connection' in CCS with the TMS470MF06607 through the JTAG when the only thing given to the chip is power and ground. 

I have never designed a PCB for a uC before but it seems to me the chip would require more than just VCC and VSS to communicate with an emulator (XDS100-v3).

To clarify: Customer has given me a PCB with a TMS470MF06607 that only supplies power, an external oscillator for OSCIN, and pins for necessary JTAG pins. Can an XDS100-V3 emulator send and receive data to the uC with only VCC, VSS, and OSCIN or is more required?

Best Regards,

-C

  • Hi,

      I think VCC, VSS and OSCIN should be all you need to connect the XDS100 debug probe to the target. In CCS, I suppose you already have a target configuration file for your target device using XDS100. If not, please create one. You can click the "Test Connection" for scan-chain testing. If it passes, then you are good to go. You should be able to connect to the target with no problem. 

  • Hi Charles,

    Thank you for your response. That is very reassuring and may point to a potential hardware issue. I have created the target configuration file and have been trying to debug the error '-233':

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

    [Result]


    -----[Print the board config pathname(s)]------------------------------------

    C:\Users\AMEARS\AppData\Local\TEXASI~1\CCS\
    ccs1031\0\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'jioserdesusbv3.dll'.
    The library build date was 'Jun 25 2021'.
    The library build time was '11:45:30'.
    The library package version is '9.4.0.00129'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '4' (0x00000004).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the FTDI FT2232 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for FTDI FT2232 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    An error occurred while hard opening the controller.

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-233' (0xffffff17).
    The title is 'SC_ERR_PATH_BROKEN'.

    The explanation is:
    The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
    An attempt to scan the JTAG scan-path has failed.
    The target's JTAG scan-path appears to be broken
    with a stuck-at-ones or stuck-at-zero fault.

    [End: Texas Instruments XDS100v3 USB Debug Probe_0]

    I am using a signal generator for the OSCIN pin and am in the process of trying to provide a cleaner signal. A little stumped on this one and very much appreciate any feedback.

    TIA

  • Hi Chris,

      Looks like the scan-chain is broken. Is this the only PCB board behaving as such? Do you have other boards of the same kind that are working? I just wanted to know if this is an isolated incident. 

  • Hello Charles,

    I have two PCBs both delivering the same error. I am using an OLIMEX TMS320-P28016 that has an XDS100 V3 emulator to try and establish a connection with the TMS470. Do you know if the XDS 100 V3 is backwards compatible? 

    Thanks again,

    Chris

  • Hi Chris,

      I'm not familiar with OLIMEX TMS320-P28016. Looks like a third party development board. In any case, I don't understand why you meant that OLIMEX TMS320-P28016 has an XDS100V3 emulator. Looking at the diagram, I don't see the XDS100 emulator. 

    I also look at the development tools for TMS470MF06607 and I don't see XDS100. Below are the debug probes listed in the product page.  What debug probe does your customer use? I will suggest you try XDS200. 

    https://www.ti.com/product/TMS470MF06607#hardware-development

  • Yes it is a third party device and as I understand it has the hardware of the XDS100V3 emulator on it, here is the reference: https://www.mouser.com/datasheet/2/306/TMS320-XDS100v3_UM-336636.pdf

    Do you know if the devices compatible with the XDS100V2 are compatible with XDS100V3? Meaning can you use a XSD100V3 on any device you can use an XDS100V2 on? I know the XDS100V3 supports cJTAG which the V2 does not, but they should both support IEEE 1149.1 correct?

    I have a TMS470M USB Development Stick with an On-Board USB XDS100v2 JTAG for on-board emulation (no need for external JTAG emulator) which I can connect to without problems. 

    V/R,

    Chris

  • Hi Chris,

    Do you know if the devices compatible with the XDS100V2 are compatible with XDS100V3? Meaning can you use a XSD100V3 on any device you can use an XDS100V2 on? I know the XDS100V3 supports cJTAG which the V2 does not, but they should both support IEEE 1149.1 correct?
    I have a TMS470M USB Development Stick with an On-Board USB XDS100v2 JTAG for on-board emulation (no need for external JTAG emulator) which I can connect to without problems. 

    I think XDS100V3 will be backward compatible with XDS100V2. Can you answer a few questions?

      - How long ago did you use the XDS100V3? I want to know if this probe is still working. Can you try this XDS100V3 on another good known board?

      - What debug probe does your customer use?

      - What is the reason your customer shipped the boards to you? Is it for the same reason that they are unable to connect? 

      - How many boards does your customer have? I only know two of boards shipped to you which you are unable to connect. 

  • Hi Charles,

      - How long ago did you use the XDS100V3? I want to know if this probe is still working. Can you try this XDS100V3 on another good known board?

    Yesterday I was able to plug into a TMS320 with the XDS100V3 onboard emulator and successfully connect, so I do not believe it is the emulator.

      - What debug probe does your customer use?

    To my knowledge they use the onboard XDS100V3.

      - What is the reason your customer shipped the boards to you? Is it for the same reason that they are unable to connect? 

    It is not the same reason, shipped in order to do specific stress testing.

      - How many boards does your customer have? I only know two of boards shipped to you which you are unable to connect. 

    We only have the two boards.

    My follow on question - could this be a bootloader issue? From the factory and (assuming all the hardware is correct) would it be possible to plug in immediately or does a bootloader need to be loaded onto the uC?

    Thanks again and best regards,

    Chris

  • Hi Chris,

      Maybe I was not clear with my earlier questions. What I wanted to know if your customer ever use XDS100v3 to successfully connect any of the boards with TMS470M MCU in it, not just the two boards they sent you but also other boards of the same kind they still have. 

    My follow on question - could this be a bootloader issue? From the factory and (assuming all the hardware is correct) would it be possible to plug in immediately or does a bootloader need to be loaded onto the uC?

    Normally, a bootloader is a small piece of program residing in the beginning of the flash that will boot up and load your application firmware from a chosen interface such as UART port. Whether there is a bootloader on your device or not should not prevent a debug probe from connecting.