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

problem in connecting Blackhawk USB100v2

jitendra panchal
Intellectual 285 points
Other Parts Discussed in Thread: AM1808

I am using customized board of AM1808 which is similar to LOGICPD AM1808 Experimenter kit.when i am connecting the blackhawk  USB100v2 to this board it is giving me the error as shown in attached file.

Please give me the solution early as possible. 

  • 0
    TI__Guru**** 162305 points

    It is best to post these types of questions in the CCS forum.  Ideally the moderator of this forum should have moved it but that doesn't always happen.

    Does the same emulator work ok with the LogicPD EVM?  What information do you get when you run "Test Connection" from the .ccxml file.  Open the ccxml file and there should be a test connection button on the right.

    I would suggest reviewing this JTAG troubleshooting page to check JTAG connection to your board :http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

    With the LogicPD board there are some things you need to check in order to be able to connect (boot mode pins and CCS settings).  Not sure about your board but some of them may apply.http://processors.wiki.ti.com/index.php/How_to_connect_to_the_OMAP-L138/C6748/AM1808_EVM_board_using_CCS%3F

    john

  • 0 in reply to JohnS
    TI__Guru**** 162305 points

    I had to ask someone about the -150 error as that is a new one for me.  The most common one we see is -151.

    -151 is a fail on open.  The software could not find and successfully open a USB connection to the FTDI chip inside the XDS100.   The most common reasons for this are the unit is not plugged in, wrong serial number, blank eeprom, defective part or corrupted OS drivers.

    -150 is that communications with the FTDI chip failed at some later point.  This would be a device that did successfully connect but the device returned extra data we didn’t expect or the device didn't respond when it should have.  This should be exceedingly rare.  Potential causes include unreliable USB connection, defective part, corrupted OS drivers, potential issue with the board (perhaps a gpio tied to something unexpected).

    john