• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 536 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.

Connection to Target failed

Muri Philipp
Prodigy 40 points

Hello

I'd like to connect to the Eval-Board for the first time but I didn't get it.

In below follows the error-message from th Code Composer

Error connecting to the target:
Error 0x80000240/-150
Fatal Error during: Initialization, OCS,

The Device Manager from Windows says that there is a problem with the Texas Instruments Emulator XDS560 PCI JTAG Emulator

Is this the right device? Has anyone found another driver for the 5505 eZdsp board?

Thanks

  • 0
    Prodigy 40 points

    I'd like to add more Information.

    I use the new evalboard for the TMX320CV5505 DSP from Spectrum Digital. I use the  Code Composer Studio Version: 4.0.0.16000 licenced over Internet and licencefile.

    I think that there is a hardware-problem on the evalboard.

    The Device Manager from Windows shows a right installation for the XDS100 Emulator. But the Error described above is still there.

  • 0 in reply to Muri Philipp
    Intellectual 395 points

    This board features a XDS100. An installation error of a XDS560 device is "normal", see e.g. http://tiexpressdsp.com/index.php/XDS100 under "what are the known issues". Furthermore, the board should be configured in CCS to use a XDS100 for the connection. Did you specify the XDS100? If not, try it out!

     

    I hope I could help. Let me know.

     

    Best regards,

    Michael

  • 0 in reply to Michael Rietz
    Prodigy 40 points

    Thank you!

    It is the TMDX5505EZDSP board. I specified the XDS100 as Emulator. The Installation for the Emulator is ok, the Device Manager says that all is right.

    Interestingly, the Errormassage apears in the same way as if the board is connected to USB or not.

  • 0 in reply to Muri Philipp
    Prodigy 40 points

    I found the solution!

    The USB-Adapter for the XDS100 Emulator is shown in the Device Manager as a COM-Port (by me it was COM7). The problem was, that I had a USB-to-Serial adapter with the same FTDI-chip connected to my computer (emulating COM4). So the XDS100 was properly installed, and the debugger was looking for a serial connection to a FTDI-Chip. Counting up from COM1 first match was COM4 but there was no XDS100 and the connection faild.

    Disconnect of the FTDI USB-to-Serial adapter solved my problem.

    I think this is a bug in the debugger of CCS4!

    Regards, happy Philipp

  • 0 in reply to Muri Philipp
    TI__Expert 4995 points

    The issue with the second FTDI chip is documented in the section: http://www.tiexpressdsp.com/index.php/Xds100#What_are_the_known_issues.3F

    "When a second FTDI device is plugged in (ex: FT232RL), and it receives a lower chain number, the XDS100 SW will address it instead of the FT2232 used by the XDS100. Solution: only plug the XDS100 HW into the PC. "

    This is a known issue for which a fix is being worked on.