• State Answer Suggested
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 672 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.

CCSv.5 & XDS100 emulator debug launch session errors:

Genatco
Guru 56043 points
Other Parts Discussed in Thread: LM3S8971, STRIKE

Day #2 with a XDS100v2 emulator needed to bring a LM3s8971 Stellaris controller back from a FAULT lockout condition which killed its Ethernet connection. The text included in the Black Hawk emulator box suggest a path .\Uscif \Ftdi is necessary but even adding that folder manually with debug library files for the Stellaris emulator makes no difference. Possibly the BlackHawk emulator the xds100v2 instruction card is making false a statement about needing this \ftdi folder when CCsV5?

Thanks for any help in advance :) 

 Blackhawk technical support has confirmed the USB emulation folder is now in a different location than was documented on the card stock instructions accompanying the XDS100v2 boxed device. The Explorer tree below shows the new CCsV.5.1.x emulation path \FTDI  system files.

  • 0
    Guru 56043 points

    Was actually expecting some, even a little member input here to help explain this -600 error in CCS5 when invoking a debug session. Don't feel bad it was not the typical scenario of events nor I the expert of design making it even more a challenge to uncover the facts as is in any Sherlock Holmes adventure this one had a major clue block.

    The power source for the xds100 was questionable while the Jtag debug port has +3.3 volt power source shown in the schematics of the on board port. Knowing that clue anyone would typically assume the +5 volts of the USB is not being used why would it be when only it need share a common ground for electron flow return. The LED of the xds100 never turned on when it was connected to the Jtag debug port under power or when all alone simply plugged into the USB port no Jtag cable connection.

    It would then strike anyone who plugged in this USB device to a computer that it is not being powered by the USB port so it will not auto enumerate as a USB device unless the JTAG port ribbon cable is plugged into the TARGET board there by providing power to the xds100 emulator. When even that failed to work logic was blown out the Windows until the schematic of the xds100 was discovered in TI-Wiki info pages, yet another clue Sherlock needed to unravel this mystery.

    Well that single clue removed all assumptions at least up to the point of confusion since indeed a power inverter was present on the xds100 bucking +5 vdc down to +3.3 for the xds100 MPU. Windows XP or 7 typically would auto enumerate any powered USB device  however Blackhawks instruction card sent not one but two mixed messages with one simple little word (if) to any programmer suggest a conditional branch test exists, any how they make a statement that suggest the xds100 might not be auto enumerated although fail to elaborate as to why (if) leaving the (then) part completely out of the conditional branch equation. Then what call your local congressional leader and complain to them? The other mixed message the location of the \ftdi folder which was entirely incorrect since it does not show up under \common\uscif as the instruction card suggest it does. Check the above folder tree for a clue.

    That was plainly wrong Sherlock moves to strike the word (if) from the instructions mainly because CCS5 will not enumerate the USB class device low level drivers Windows would typically install as part of the USB auto enumeration process, when the USB class device is being powered or is otherwise a functional USB device. This xds100 was never enumerated by Windows a necessary step required of CCS5 prior to entering a Debug session -- the prosecution moves to rest its case.