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.

C5515 eZdsp USB Stick Install Problem

I am having trouble during installation of this kit. I have followed the directions and installed everything from the CD before connecting the USB Stick. When I do connect the board it does not find the drivers. I have installed 5 different times and tried multiple USB ports (direct connections, no external hubs).

I am running Windows XP SP3.

All the other posts on the forum that relate to this keep pointing back to the installation instructions which I have followed to the letter.

Can anyone help with this.

  • Hi,

    I am sorry you are having difficulty connecting to the C5515 eZdsp.

    Are you seeing the problem right when you plug in the USB Stick or from within Code Composer? Is Windows opening the "Found New Hardware" wizard?

    If you used the CD in the eZdsp box, you should already have the drivers installed. Maybe you can search for them on your PC and then direct the Found New Hardware wizard or Windows Device Manager to these files.

    The drivers are needed to communicate with the on-board XDS100 emulator, an FTDI USB to JTAG chip. The file names of those drivers are  ftdibus.sys,  ftbusui.dll,  ftd2xx.dll,  FTLang.dll

    Here is how the eZdsp should look from within Device Manager...

     

    Can you try to install on another PC as an experiment?

    Regards,
    Mark

  • Windows is opening the found new hardware wizard. I installed from the CD but those drivers are not installed. 

    Are they in a directory on the cd or are they in a compressed file of some kind?

    Thank you for the prompt response.

  • I did go to the CD and installed the XDS100 drivers from the ti_xds100_setup.exe.

     

    Same result. No drivers installed. I am running as admin.

  • From the Found New Hardware Wizard have you tried pointing to the Spectrum Digital Folder on the CD.  This is where the USB install files are located.  There are 2 sub folders: one for 32-bit and another for 64-bit processors.

    BTW, I just installed on WinXP SP2 machine and everything worked as expected.  The eZdsp was recognized as soon as I plugged it in.

    Regards.

  • I did try pointing the wizard to that folder with no luck. Can someone send me the four files (or a link) mentioned above?

    Thanks for all the help.

  • You may be able to find some help on this wiki page: http://processors.wiki.ti.com/index.php/XDS100#Troubleshooting.

    Also search through the Code Composer forum for a similar case: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81.aspx

    Could you post a screen shot of what the XDS100 USB devices show up as in your Device Manager?

    Thanks,
    Mark

  • I have been scouring both of those pages and I have not seen anything similar.

  • Something went wrong with the driver installation.  The XDS100 emulator should be listed under the Universal Serial Bus controllers as:
         TI XDS100 Channel A
         TI XDS100 Channel B

    When you said you pointed at the Spectrum Digital folder, did you point to the folder with the .inf file in it or the top level Spectrum Digital folder on the CD?  You need to point to the .inf file appropriate for your CPU.  If you didn't point to the .inf folder, then I suggest uninstalling the 2 drivers above with the yellow question marks and trying again.  There appears to be some issue with your USB driver install that I have not seen before.

    Regards.

  •  

     

     

     

    Thanks Tommy.

    I did point to the proper directory (SpectrumDigital\usbdrivers\i386) on the CD. It comes back with a Cannot Install.

     

    I appreciate the help and I realize this has not happened before. I have also tried to run the DPInst.exe. It finishes with a success, but no drivers installed.

    Here are the log files. I do appreciate any help.

  • Can you check the UID/PID? http://processors.wiki.ti.com/index.php/XDS100#Q:_How_can_I_check_if_the_VID.2FPID_for_the_EEPROM_are_programmed_correctly.3F

    Also, in another message, can you confirm that it worked on a windows XP, sp2 machine, but not on this windows xp sp3 machine? (Assuming same  CCS installed, same HW, etc.).

     

  • Have not tried on an SP2 machine.

  • Ok, it looks like the eeprom is programmed correctly. We have not seen that before. I will move this post to the CCS forum where other experts can comment.

  • Thank you for the help. I have not seen this before either.

  • Couple of items:

    1)       XP SP3 is my default platform and historically has worked much better then SP2 on USB install.

    2)       For XDS100 class emulation the FTDI files are included as part of the TI CCS install.  These files will be located at<ccs_install_dir>\ccsv4\common\uscif\ftdi.

     

    Suggestions to fix:

    At this point it is probably best to try and unwind possible bad install.

    1)       Plug in the Stick.

    2)       Go to device manager and under the Other Devices have it remove those drivers for XDS100.  Unplug the stick once deleted.

    3)       Optionally go to registry (regedit) and delete all FTDI driver entries for XDS100 VID/PID. The base key will be at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0403&Pid_a6d0.  There may be some other variants so delete anything with Vid_0403&Pid_a6d0 in the key name.

    4)       Go to <ccs_install_dir>\ccsv4\common\uscif\ftdi and execute DPINST32.exe.  This is the true location of where FTDI drivers reside, not in the SD tree. In theory during the CCS install DPINST32.exe is called by the CCS installer to pre-load FTDI drivers.  By running this manually it may provide some insight into the root cause of the problem.

    5)       Plug in the Stick and in theory it should automatically install the drivers but if not then point the installer to directory in item 4. 

  • Thank you Tony.

    I was able to point the hardware wizard to the FTDI files you mentioned at the top of your post.. They installed.

    I appreciate the help everyone provided.

    I still do not know why this did not work . I am likely to chalk it up to Windows and move on.

  • I have the same problem but unfortunately when i went through the same steps that Tony provided, the device still can't find the drivers. However, the install wizard indicated that there weren't any problems. Yet when I plug in the device I still have the problem where Windows can't find the device drivers.

    In Tony's procedure there is an instruction to clear any keys in the registry that may be a close variant to the correct VID/PID, but regedit won't let me delete it. (Vid_0403&Pid_6001). Is this a clue?

    Is there a log somewhere to look at that may give me more details of why CCSV4 could't install the drivers properly?

    Apprciate any help.

    Regards,

    carl h.

     

  • My problem is specific to my PC only. I installed the drivers on another PC without any problems.

    /carl

  • Hello,

    I have a very similar problem:

    My PC (Windows XP SP3) doesn't detect my stick correctly although the right driver is installed

    (The exclamation point appears because I haven't rebooted the PC after anew try detecting the stick right)

    The right driver have these values: VID=0404, PID=a6d0

    The false one have: VID=0403, PID=6010

    I've already tried to uninstall over the device manager the false one (the registry entries were also deleted) and plugged in the stick, but the false one was installed again

    How can I delete the false one completely and force the PC to take the right one?

    I'm appreciate for any help

    Lena

    BTW: I've also started a thread: http://e2e.ti.com/support/microcontrollers/hercules/f/312/t/223915.aspx

  • Hello again,

    The problem has been settled!

    Lena

  • Hello again,

    The problem has been settled!

    Lena

  • Great! Can you share your finding/solution to close this posting?

    Regards.

  • No, unfortunately not everything.

    To get the right driver, I reprogrammed the device with MProg (the programm read sth. with BeagleBone, after the programming it was sth. with TI). Then the PC took the right driver.

    But I had problems flashing the device in CCS and nowFlash and I don't know, why it works now. I tried to change the device configuration in ccs, that didn't help. Then I resetted the changes and it worked, although I had the configuration already before.

    So I'm confused, but it works and I hope this error doesn't appear again.

    Confused greetings

    Lena