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.

TMDSEMU200-U: XDS200 creating an open when connecting to target device

Part Number: TMDSEMU200-U

I have followed all of the hw installation procedures to a T. 

However, when i connect the XDS200 to my laptop via USB cable, the "left" LED turns on and stays on. I then supply power to the target board. Using a variety of tools, I can see there is a voltage drop across the board, but no power consumption or current flow (i.e., an open). consequently, I am unable to flash f/w to the target device since it is not powered. (let's call this State A).

After some t/s, I've realized that if I disconnect the debugger when in State A, then current flows and the target board consumes power. Therefore, I know the debug pod is precluding the target device from realizing the voltage drop across it. 

After some more troubleshooting, and returning to State A I've found that if I attempt to flash f/w to the device (due to no power), it will fail and both LEDs on the XDS200 turn off. BUT at this point, the target board now starts consuming power again and if I try a subsequent f/w flash (immediately following the first), it works like a charm. 

What could be the issue where the XDS200 is preventing the target device from realizing its power supply and how do I make it so that I don't have "fail-to-flash" first, just to get it in a state where I can successfully flash f/w? 

  • Hi James,

    Which version of XDS200 are you using? Are you able to share your schematic for your target board? Are you using 4-pin JTAG or cJTAG? 

    It sounds like there is somehow a short with the XDS200 until you try to flash the device, and I am not yet sure how that is happening.

    Best Regards,

    Ben Collier

  • Good morning Ben,

    Unfortunately, I cannot post a schematic online. Currently using the 4pin JTAG. I'm using the Blackhawk XDS200 (s/n TC57929) with the 20e_cTI-14t_TI pin converter header.

    Maybe we could set up a point to point phone call? 

    Do you think this could be related to the clock source for the target board? Currently working through an issue where I'm stuck in an infinite loop since the target device is expected an external clock to stabilize. However, I've switched to the internal oscillator using the device.h file.

    thanks

    james

  • James,

    I have sent you a friend request so I can send you a private message and we can try to schedule a call for tomorrow. 

    I could see a problem with the clock source causing the issue that you called State A, but I am not sure how trying to flash the device would resolve that. Which C2000 device are you using? 

    Best Regards,

    Ben Collier