• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 1613 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 XDS100V2 CANNOT program VID/PID

A-noname-ous
Prodigy 20 points

Other Parts Discussed in Thread: TMS320C5535

I've purchased the eZdsp USB kit and I'm following the instructions to run the sample project.  When connecting, Code Composer errors with -151. 

I followed the instructions listed in the wiki

http://processors.wiki.ti.com/index.php/XDS100#Q:_How_can_I_check_if_the_VID.2FPID_for_the_EEPROM_are_programmed_correctly.3F

And noted that my VID/PID did not match with that of the XDS100V2.  Under Windows XP Device manager, the devices came up as Serial A & Serial B.

I followed the steps under Q: What should the USB device's UID (VID/PID) be? And got the mprog utility along with the ept file.  I scanned the devices (Device->Scan) and the program reported 2 devices, 0 programmed. 

I then erased the devices and got a message that devices were erased successfully.  I then went to program the devices and that's when I received No Devices Found error. 

As far as I can tell, the processor is functional in that  I was able to run the audio demo.

Any suggestions to fix this issue? 






  • 0
    TI__Guru**** 482811 points

    Use FT_Prog instead of MProg. I also had MProg issues but FT_Prog worked fine for me.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 482811 points

    Ki-Soo Lee said:
    Use FT_Prog instead of MProg. I also had MProg issues but FT_Prog worked fine for me.

    You can get it from here

    http://www.ftdichip.com/Support/Utilities.htm

  • 0 in reply to Ki
    Prodigy 20 points

    Thank you for your response, however FT_Prog utility requires the configuration file in a format that's incompatible with the .ept file referred to by the TI WIKI.  Did you have to make your own configuration file?  Because TI doesn't provide one anywhere on their sites, neither forum nor the wiki.  Other posters in the forum recommend downloading and using MPROG as that is the only way that's known to work.

    I was able to resolve my issue by removing all installed FTDI Drivers using the FTClean utility

    http://www.ftdichip.com/Support/Knowledgebase/index.html?ftcleanutility.htm

    Then downloading the D2XX Drivers

    http://www.ftdichip.com/Drivers/D2XX.htm

    Finally, after failing to load the recommended .ept file in the TI Wiki, I was able to get my board programmed with the FT2232 H EPT file that was buried near the bottom of the wiki.  

    Bottom Line:  It took 2 days out of my schedule to just get a pre-built dev.  board up and running with a basic blinking LED demo code.  For you TI reps out there- please make sure any dev boards you ship out are functional.  If the bring up had taken any longer, I would've been forced to switch to an alternate DSP to move forward with my project.       

    Here's my board id and system configuration for reference:

    TMS320C5535 eZdsp USB Kit

    TMX320C5535 eZDSP

    TMDX5535EZDSP MULTI-RELEASE

    702365-1001 REV D  19 Apr 12

    S/N: C5J_1204108

    ASSY 514580 Rev D

    FYI: I'm doing firmware/driver co-dev on MacMini 8GB RAM, running Oracle VirtualBox WinXP VM and Centos VM.  Talk about killing 3 birds with one stone!