• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Subscribers 82 subscribers
  • Views 459 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.

LAUNCHXL-F2800137: How to flash code through XDS110 Debug Probe

Ankit Saxena
Prodigy 210 points
Part Number: LAUNCHXL-F2800137

We are exploring option to flash code through XDS110 Debug Probe. But getting error while test connection.

Error:

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].

Following is Pin mapping for the reference:

XDS110 Debug Probe
LaunchXL-F2800137
Expansion Header - pin 25
J1/J3 GND
Expansion Header - pin 27
3v3
Debug 20 to 14 pin extension - pin 1
TMS
Debug 20 to 14 pin extension - pin 11
TCK
Debug 20 to 14 pin extension - pin 7
TDO
Debug 20 to 14 pin extension - pin 3
TDI

we have also check with below mapping, but getting same error.

XDS110 Debug Probe LaunchXL-F2800137
Debug 20 to 14 pin extension - pin 8 J1/J3 GND
Debug 20 to 14 pin extension - pin 5 3v3
Debug 20 to 14 pin extension - pin 1 TMS
Debug 20 to 14 pin extension - pin 11 TCK
Debug 20 to 14 pin extension - pin 7 TDO
Debug 20 to 14 pin extension - pin 3 TDI
One more thing, we have checked voltage at VTREF pin (pin 5) but no voltage is there.
Thanks in advance, and also let me know if more details are required.
  • 0
    TI__Mastermind 33116 points

    Hi,

    Are you trying to program the device using the 14-pin JTAG header on the launchpad? 

    Best Regards,

    Ben Collier

  • 0 in reply to Ankit Saxena
    TI__Mastermind 33116 points

    You are having this issue with the onboard XDS110 on the launchpad? 

  • 0 in reply to Benjamin Collier
    Prodigy 210 points

    We are using external XDS110 Debug Probe and bypassing on board debugger.

  • 0 in reply to Ankit Saxena
    TI__Mastermind 33116 points

    You have connected VTREF to the launchpad 3V3 signal? And you see 0V on that pin? 

  • 0 in reply to Benjamin Collier
    Prodigy 210 points

    Yes, we are connecting VTREF (PIN 5) to 3v3 LAUNCHXL. Also while checking voltage on VTREF, getting 0V on digital miltimeter. 

  • 0 in reply to Ankit Saxena
    TI__Mastermind 33116 points

    Ankit,

    What voltage are you supplying to the launchpad? Do you see any voltage on any of the launchpad pins? 

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 210 points

    Hi Banjamin, sorry for the delay reply.

    Through External XDS110 Debug Probe, we are connecting to 3v3 port on the LAUNCHPAD, and  not getting any supply on board. Also no voltage on TVRef pin (Pin 5) while checking through multimeter. Below is the connection  table for the reference.

    XDS110 Debug Probe LaunchXL-F2800137
    Debug 20 to 14 pin extension - pin 8 J1/J3 GND
    Debug 20 to 14 pin extension - pin 5 3v3
    Debug 20 to 14 pin extension - pin 1 TMS
    Debug 20 to 14 pin extension - pin 11 TCK
    Debug 20 to 14 pin extension - pin 7 TDO
    Debug 20 to 14 pin extension - pin 3 TDI

     

    Here I am also sharing CCS's target setting

    and after Test connection we are getting error

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

    The value is '-267' (0xfffffef5).
    The title is 'SC_ERR_XDS110_TARGET_SUPPLY'.

  • 0 in reply to Ankit Saxena
    TI__Mastermind 33116 points

    Hi Ankit,

    Are you trying to supply power through the XDS110? I think you are using the wrong pin to do this. Could you try supplying power from another source (USB Cable for example) to see if that resolves this error? 

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 210 points

    Do you found something wrong with above connection? I also tried with giving power to board via USB cable and connecting on board XDS jumper to give power to board, but no success.

  • 0 in reply to Ankit Saxena
    TI__Mastermind 33116 points

    Hi,

    I am really sorry about the delays, but I will need a day or two to get back to you. 

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 210 points

    Thanks Benjamin, for the response.

    Till now, we have tried various combinations, but unfortunately, we haven't achieved success in flashing code on the LaunchPad via the XDS110 Debug Probe.
     
    Could you provide guidance on the pin connections necessary to flash code on the LaunchPad using the XDS110 Debug Probe? We're specifically aiming to utilize the cJTAG 2-pin configuration. Additionally, please advise if any adjustments/settings are required within CCS.
  • 0 in reply to Ankit Saxena
    TI__Mastermind 33116 points

    Ankit,

    To use cJTAG, you should only need GND, 3V3, TCK, and TMS connected.

    The major issue for now is that there is no power on the board. Could you try just supplying 3V3 to the board from any DC voltage source? 

    Best Regards,

    Ben Collier

  • 0 in reply to Benjamin Collier
    Prodigy 210 points

    Benjamin, you are right. We got it working by supplying power to the board using the expansion block on the debugger. Below is our connection which helped us to get it done.

    XDS110 Debug Probe

    LaunchXL-F2800137

    Expansion Header - pin 25

    GND

    Expansion Header - pin 27

    3v3

    Debug 20 to 14 pin extension - pin 1

    TMS

    Debug 20 to 14 pin extension - pin 11

    TCK

    Pin 5 (VTREF)

    3v3

    Pin 8

    GND

    Please also help us with UART (RX and TX pin). How do we connect RX and TX pin of LaunchPad to Debugger.