• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 959 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.

TMS320C5535 eZDSP XD100 emulator driver vid/pid

Abdul Aziz Ali
Prodigy 10 points

Other Parts Discussed in Thread: TMS320C5535

Hi, this is my first post here and my first time trying out TI product (i have only had experience with x86 dev board and pic programming before this). System: XP SP3.

Bought a ezDSP TMS320C5535. Installed CCS4 according to the quick start. Everything seems ok until i try to 'Connect to Target' where i get the infamous :

Error connecting to the target:
(Error -151 @ 0x0)
This utility failed to open the adapter for a custom emulator.
The adapter returned an error.
(Release 5.0.429.0)

So it turns out after reading a few posts that the inbuilt emulator on the board hasnt been programmed yet and i have to reprogram the VID/PID myself. Im highly dissapointed in Spectrum Digital (or TI?) that i can receive a 'defective'/unprogrammed board but pointing fingers isnt going to get me started on dsp programming, And im not willing to wait by sending the board back etc.

1. However! I reprogrammed the PID/VID incorrectly with ft_prog (i had missed this http://support.spectrumdigital.com/boards/ezdsp5535/revc/files/ezdsp5535_faq.htm ) using an EPT on the ti site instead of the one from SD. And now neither ft_prog and mprog can seem to scan the device (it could before). However with usbview i can still see the board connected

idVendor:           0x0403 (Future Technology Devices International Limited)
idProduct:          0xA6D1

2. I used libusb to create a driver for the board but ft_prog and mprog still cant scan it.

3. I have used FTDI clean to clean my system. And tried to select the FTDI drivers for the board but it (VID/PID?) doesnt match ("No drivers found that ...") so it cant use the FTDI drivers.

So i think my solution is this, modify  the FTDI drivers to match the VID/PID that i changed the board to so i can scan the board in ftprog again and reprogram the eeprom correctly, how do i modify the drivers? Anybody have a tool for this? tried diffing the libusb *.inf with FTDI *.inf but they seem really dissimilar.

Or is there another solution?

Quite new at this, so dont know all the tools of the trade yet

Thanks all in advance! (cross fingers)

  • 0
    TI__Guru**** 171839 points

    Hi,

    Abdul Aziz Ali said:

    So i think my solution is this, modify  the FTDI drivers to match the VID/PID that i changed the board to so i can scan the board in ftprog again and reprogram the eeprom correctly, how do i modify the drivers? Anybody have a tool for this? tried diffing the libusb *.inf with FTDI *.inf but they seem really dissimilar.

    Although I am not very familiar with the FTDI device driver utilities, I think you can use the utility FTDI_INF 1.2 (download here) to adjust the VID/PID and thus allow the driver to recognize the misprogrammed device. Then use the FT_Prog to properly re-program the device.

    That said, the VID/PID you mentioned matches TI's XDS100 emulator - thus the device drivers provided with CCSv4/5 should properly recognize the FTDI device and allow programming using the FT_Prog utility.

    An installer for these device drivers is usually located at:

    For CCSv4: <CCS_INSTALL_DIR>\ccsv4\common\uscif\ftdi

    For CCSv5: <CCS_INSTALL_DIR>\ccsv5\ccs_base\emulation\windows\xds100_drivers

    Hope this helps,

    Rafael