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.

CCS/TMS470MF06607: what is setup required for Developing and flashing code of TMS470M custom board using ccs and uniflash

Part Number: TMS470MF06607
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

Hello ti,

I am working on TMS470M06607  .

Currently we have TMS470M06607   usb stick ,  I am able to flash and execute the sample codes of TMS470M06607 using ccs and uniflash .

we developed a custom board with TMS470M06607 which is equivalent to TMS470M06607 usb mode, with a change removing usb format  debug and replaced with  JTAG   for debugging .

so for flashing  TMS470M006607 custom board ,we used a smartrf06 evaulation board JTAG pins to flash it , but we are unsuccessful . 

link of evaluation board is .... http://www.ti.com/tool/SMARTRF06EBKb .

please help me to flash our board using smartrf06 evaulation board JTAG.

  • I have never used the XDS100v3 on a SMARTRF06EBKb . If the issue is using that hardware as an emulator, I will transfer this thread to that group. Did you create a target configuration for the XDS100v3 and the TMS470M06607? If you look at the "Advanced" tab of the target configuration file in Code Composer, it should look like this:

    From that window you can test various parts of the scan chain by selecting a point on the chain and then clicking the "Test Connection" button. In the image above, the first level, IcePick, is selected.

  • Hi Bob Crosby,

    I have created a target configuration for the XDS100v3 and the TMS470M06607. In the "Advanced" tab of the target configuration file in Code Composer, it is showing the same as you have shared.
    From that window I have tested the first level, IcePick and clicked on "Test Connection" button and I got the following response



    [Start: Texas Instruments XDS100v3 USB Debug Probe_0]

    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\RAVI~1.IBO\AppData\Local\TEXASI~1\
    CCS\ti_7.3\0\1\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 'Jul 21 2017'.
    The library build time was '19:36:41'.
    The library package version is '7.0.48.0'.
    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]


    so can you suggest me a solution to flash TMS470M06607 using JTAG

    Best Regards,
    Ravi
  • That error message suggests a hardware problem. Do you have a diagram (or schematic) of the connections between the TMS470 and the SMARTRF06 board?

  • I have not heard back from you and assume you have resolved this problem. If not, please respond to this thread with your additional questions.