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.

Missing FTDI driver on 2806 iso control card

I know others have asked this question before,after getting this message

Error connecting to the target: (Error -151 @ 0x0) One of the FTDI driver functions used during the connect returned bad status or an error. The cause may one or more of: invalid emulator serial number, blank emulator EEPROM, missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utility in the 'common/uscif' folder to verify the emulator can be located.

and I'm pretty certain that the driver has got corrupted for the FTDI chip, but I can't find the driver anywhere, so can someone point me to it ?

Tried getting the driver direct from the FTDI site, but that won't run, giving an error "The requested operation requires elevation", whatever that means.

Thanks

  • Hi Geoff,

    Could you take a look at the below thread?  The .bat file will allow you to reprogram the FTDI chip (as a xds100v2):
    http://e2e.ti.com/support/microcontrollers/c2000/f/171/p/252873/887275#887275


    Thank you,
    Brett

  • Hi Brett,

    Thanks, but running the batch file isn't working. I get the following messages

    "Scanning for devices...
    No devices found !
    Index was out of range. Must be non-negative and less than the size of the collection
    Parameter name: index
    Device 0 does not exist
    Index was out of range. Must be non-negative and less than the size of the collection
    Parameter name: index

    Done!
    Press any key to continue..."

    Where do I go from here ?

    Regards,

    Geoff
  • Geoff,

    1) Can you try the jumper recommendation I made in that other thread (the one I linked)?

    2) Can you make sure that the USB mini is connected (for the emulator) and the baseboard is also powered?  (ie you should have a LED on on the left-side of the cCARD [states that emulator is powered] and a LED on the right-side of the cCARD [states that the MCU is powered])

    3) Once I linked the thread, I did I realized a mistake in the thread I linked - there was a programmer bat file attachment that didn't work in the exact response that was linked.  I've now fixed that response to reduce confusion.  Make sure you're using the zip file from this exact post:
    http://e2e.ti.com/support/microcontrollers/c2000/f/171/p/252873/889381#889381

    If, after the above, the bat file still isn't finding any FTDI chips to program, we may have a board problem.  Has this cCARD worked previously?


    Thank you,
    Brett

  • Hi Brett,

    I just tried the same card, baseboard and lead on another pc with ccs5 on it and it all works fine, it's just this one pc that seems to have the problem.

    I've had this setup working for months without a problem, on the pc that's not working now. Yesterday, I was trying to get another , non-TI, development board with an FTDI chip working on the same pc, and it's since then that the 28069 card has stopped working.

    I had to attempt to install a driver for that FTDI chip and I'm guessing that's what screwed things up, but if it has, surely I should be able to get the correct driver going again.

    The driver I've just tried to install is this one, e2e.ti.com/.../xds100v2_2D00_FT_5F00_Prog_5F00_v2.2.zip, so is that correct ?

    Regards,

    Geoff
  • Hi Geoff,

    Based on what I know and referring to:
    http://processors.wiki.ti.com/index.php/XDS100#Troubleshooting
    http://processors.wiki.ti.com/index.php/XDS100#Troubleshooting_FAQ

    ...the first thing I'd do is see what shows up in Device Manager.  This will likely tell you what your next step should be.  If you see a "Dual RS232 USB Serial Bridge", I'd focus on trying to get the FTDI reprogrammed.  Otherwise, I think you're dealing with a Windows/CCS issue.

    The xds100v2 driver generally gets installed with CCS.  If the system somehow deletes the driver I'm not sure if you can get it installed again, save reinstalling CCS.  It may be worth putting a post about these drivers in the CCS forum (or searching some posts there) if it seems that this is where you are.


    Thank you,
    Brett