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

CCS/TMDSEMU110-U: TMDSEMU110-U not working

Apurva Ankleshwaria89
Intellectual 460 points
Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: CC1310,

Tool/software: Code Composer Studio

Hi,

I just bought a new TMDSEMU110-U to program CC1310 based custom board. I used a cTI 20 pin to ARM 10 pin adapter along with TMDSEMU110-U JTAG programmer. I tried both CCS and Flash Programmer 2. However, in both the cases CC1310 IC is not detecting. Also, note that custom board is working fine. I am able to program the same board through XDS110 on CC1310 launchpad. Posting the Error below when I verify the connection in CCS. Any suggestion would be greatly appreciated. 

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


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

C:\Users\apurv\AppData\Local\TEXASI~1\CCS\
ti\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 'jioxds110.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.

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 '-267' (0xfffffef5).
The title is 'SC_ERR_XDS110_TARGET_SUPPLY'.

The explanation is:
The controller could not detect valid target supply. Check target
JTAG connection and/or connection setting specifying voltage level.

[End]

  • 0
    TI__Guru**** 171254 points

    Apurva,

    This error happens when the XDS110 is configured to provide power to the target but the HW connection itself is somehow broken.

    If your intention is for the XDS110 to provide power to the device, can you double check the connections and jumpers?

    If your intention is to provide power to the device through a different power supply, then change the configuration setting to "Target Supplied Power" as highlighted below:

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 460 points

    Hi Rafael,

    Thanks for your response. Tried both "Target Supplied power" and "Probe supplied power" while providing power supply and removing power supply to the custom board respectively. Debug probe still not working. Attaching snip of the process. Please look for grayed out "Test Connection".

  • 0 in reply to Apurva Ankleshwaria89
    TI__Guru**** 171254 points

    Apurva,

    One detail: the Test Connection button is only active when the configuration is saved. Your is not (I see a small asterisk near the filename, which indicates unsaved changes).

    Apart from that, the "Probe Supplied Power" setting requires entering the desired supply voltage in the box immediately below.

    When you power your target board via an external supply, can you check if pin 5 of the JTAG is board has 3.3V? That pin corresponds to the TVRef pin and additional details can be seen in the reference below:

    http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds_target_connection_guide.html#tvref

    If you want to double-check your connections, also refer to the bottom of the page above for details - there are some example diagrams there with pull ups and downs.

    One detail: in your original post I understood the custom board was working without problems, but in your last post you mentioned it isn't. What is correct?

    If you have a launchpad and want to check if the XDS110 is working fine, can you try to connect to your CC1310 as shown below. Don't forget to remove the jumpers to isolate the embedded XDS110.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 460 points

    Hi Rafael,

    Tried by saving the configuration file and tested XDS110 debugger on CC1310 launchpad this time. Receiving below error on Test Connection:

    [Start: Texas Instruments XDS110 USB Debug Probe_0]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

    [Result]


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

    C:\Users\apurv\AppData\Local\TEXASI~1\CCS\
    ti\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 'jioxds110.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 '5' (0x00000005).
    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 XDS110 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for XDS110 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 '-242' (0xffffff0e).
    The title is 'SC_ERR_ROUTER_ACCESS_SUBPATH'.

    The explanation is:
    A router subpath could not be accessed.
    The board configuration file is probably incorrect.

    [End: Texas Instruments XDS110 USB Debug Probe_0]

    Also note that the custom board is working perfectly fine. I have tested it by programming through Embedded XDS110 in CC1310 Launchpad. However, XDS110 debugger is not able to program either my custom board nor CC1310 in Launchpad.

    Also, tried programming through Flash Programmer 2. XDS110 debugger is not detecting the target controller ( CC1310 ).

  • 0 in reply to Apurva Ankleshwaria89
    TI__Guru**** 171254 points
    Apurva,

    Thanks for sending the photograph; the connection is reversed. In my working connection the XDS110 cable flows towards the emulator side of the launchpad, while yours is flowing towards the device side.

    Reversing this connection causes the same problem here.

    Regards,
    Rafael
  • 0 in reply to desouza
    Intellectual 460 points

    Hi Rafael,

    I have been able to program now by choosing "Target supplied power" and providing external power to the board. However, problem still persists with "Probe supplied power option". I also checked VCC pin of the probe. I see 0V at that pin. Please find below error and snip of options chosen in configuration file.

    [Start: Texas Instruments XDS110 USB Debug Probe_0]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

    [Result]


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

    C:\Users\apurv\AppData\Local\TEXASI~1\CCS\
    ti\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 'jioxds110.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.

    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 '-267' (0xfffffef5).
    The title is 'SC_ERR_XDS110_TARGET_SUPPLY'.

    The explanation is:
    The controller could not detect valid target supply. Check target
    JTAG connection and/or connection setting specifying voltage level.

    [End: Texas Instruments XDS110 USB Debug Probe_0]

  • 0 in reply to Apurva Ankleshwaria89
    TI__Guru**** 171254 points

    Apurva,

    Apurva Ankleshwaria89 said:
    I have been able to program now by choosing "Target supplied power" and providing external power to the board.

    That is good to hear; it is a sign that the JTAG connections are correct. 

    Apurva Ankleshwaria89 said:
    However, problem still persists with "Probe supplied power option". I also checked VCC pin of the probe. I see 0V at that pin.

    What pin are you probing? To provide power to the target you need to use the Auxiliary cable. A brief video explains the method used:

    https://youtu.be/2999x1oGjao

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 460 points

    Hi Rafael,

    Thanks for providing the video link. Following the process mentioned in the video, my XDS110 debug probe is able to power the target(through Aux. functions) and program it as well. 

    However, I had an understanding that VTRef pin of JTAG provides power in case the target is not powered. If I connect XDS110 in CC1310 LP to my custom board, my custom board is powered and programmed through same 10 pin ARM JTAG. However, while using XDS110 debug probe, we have to power the target through Aux functions. Please clarify the difference in VTRef pin of XDS110 CC1310 LP and VTRef pin of XDS110 debug probe. Thank you!

  • 0 in reply to Apurva Ankleshwaria89
    Intellectual 460 points

    Hi Rafael,

    Looking forward to your response on above mentioned points. Thank you!

  • 0 in reply to Apurva Ankleshwaria89
    TI__Guru**** 173310 points
    Apurva,

    Sorry about the delayed reply. Rafael is out of the office this week and will pick this up again when he returns next week. Thanks for your patience.
  • 0 in reply to Apurva Ankleshwaria89
    TI__Guru**** 171254 points
    Apurva,

    I am not entirely sure how the CC1310 is designed, but the VTRef pin is not intended to provide power in any circumstances - it is an input pin from the standpoint of the Debug Probe.

    What may happen is that, since the launchpad provides power to the CC1310 target device through the same USB jack as the Debug Probe, it is possible the 3.3Vcc net is directly connected to the VtRef net on the board, thus giving a false impression the VTRef is actually providing power.

    For a generic Debug Probe such as the TMDSEMU110-U, the power requirements of the target board are completely unknown and therefore claiming to provide power could lead to all sorts of improper functionality.

    Hope this helps,
    Rafael