CCS hangs when attempting to connect to target VC5505 USB Stick

Gary,

CCS 4.0.2 is still quite an old version. Could you try out the latest version v4.2.4 and see if the problem persists? You can download 4.2.4 from this page, and even install it side-by-side with your current version. As long as it is installed in a different folder it should be fine.

If the connection still hangs with CCS 4.2.4 please let us know.

Just adding to Aarti's response: when running the new release of CCS, just make sure you also create a different workspace directory and import the project into it, so you won't risk disrupting any of your current work. 

Regards,

Rafael

I installed CCS 4.4.4.00033 and it no longer hangs but gives an error message:

C55xx: Error connecting to the target: (Error -1136 @ 0x400) Driver lost track of current debug frame. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Release 5.0.429.0) 

There were two XDS100 simulators when I set up the target configuration XDS100v1 and XDS100v2, I chose the first. There was a new device in the list, USBSTK5505_VC5505 in addition to the USBSTK5505 that was in the earlier version of CCS. I chose the new device.

I don't know how to lower TCLK.

Gary

That is CCS 4.2.4.00033 not 4.4.4.00033

Gary,

I recall that throughout the years the 5505 USB sticks were upgraded from VC5505 (up to Rev C) to C5505 (Rev D). Therefore, if yours read Rev A/B/C on the board or VC5505 on the device, then your configuration seems correct (XDS100v1, TMS320VC5505 or USBSTK5505_VC5505) - check the attached picture on my RevB board.

In either revisions, the correct connection/emulator is XDS100v1, and the only change is the device itself. Although the error message mentions the reduction in the TCLK speed, the XDS100-class of emulators already use a very slow speed (1MHz), therefore the issue may be somewhere else - a wild guess could be the device is entering low power mode, maybe? Could also be a watchdog or an unexpected reset, but I imagine the emulator would report that condition.

Another thing to try is to see if the JTAG connection is reliable. You can use the DBGJTAG Graphical User Interface to test the low-level connection (a link is shown in this page).

Hope this helps,

Rafael

My board is rev. C.

I did try the DBGJTAG and it found no problems.

I stumbled upon an answer while handling the board while it was plugged into USB. The XF LED on the board had always been continuously on, but it now started to alternate between on and off. While it was doing this, I could connect to the target with no errors. And while it was not mentioned in the quick start booklet, I do seem to remember that it should have been flashing. So, there is a mechanical intermittent in my board. Some solder joint is bad or a small SMD part is cracked. I also noted that the RTC_CLKOUT has no signal and it comes and goes as I push on the board. I also hear a click from headphones that are plugged into the headphone jack when pushing on the board and 1kHz and 2kHz tones are heard. The XF LED blinks faster when the 2kHz tone is present. I only just opened the ESD envelope last week even though I have had the board for a while.

Do you think I might be able to get a replacement?

Gary

Sorry, it is not the RTC_CLKOUT TP but the CLKOUT TP that has the 32.768kHz that comes and goes when pushing on the board.