04-19-2012 08:06 PM
Did anybody have successful experience using Digilent USB-HS1 cable to program XC9500 devices? If so what software did you use? Digilent web site mentions that the cable is compatible with CoolRuner2 CPLD only, but I wonder if they just not want to test configurations with old CPLD families.
04-23-2012 01:58 PM
I've been asking the same question about this cable that I purchased last week. I can nearly get it to work for XC9572XL using iMPACT (erase and program but not verify). For my coolrunner 2 XC2C256 I am unable to get erase to work with iMPACT. But, I can erase and program the XC2C256 using Digilent's Adept 2 software. For the XC9572XL, the Adept 2 software does not seem to work since it can not load .jed files (only .svf and I can't get the .svf programming to work).
Basically, I think Xilinx needs to get their act together on a low cost programmer for their CPLDs. This is not rocket science. Microchip has a $35 programmer for their microcontrollers which works across thier product line. I can't see or justify spending $200 for a programmer for a $1 CPLD programmer.
The problems I've run into seem to be totally software since all the JTAG chain tests pass with flying colors. I've run into 2 bugs with the ISE software and a couple major bugs with iMPACT. I've just started playing around so the quality with these tools seem rather low. I'm about ready to give Altera a try.
I also blew up a 5V tolerant device by getting it to latch up when I had weak pull-ups to 5V on a microcontroller that was left on while the 3.3V supply to the XC9572XL was turned off. I thought I was back in the 80s when this happened. Now that XC9572XL device is just a wire between the supply pins (it gets hot [burn your finger] and draws more than 1A).
Sorry. I just did not have a very good out of the box experience.
Here is an email exchange with Digilent about my problems with their product:
04-27-2012 10:56 AM
I did get word that XC9500 series parts are not suppored from the Digilent support person. But, it does work for me except for verify. I found this link for another way to go.
P.S. I seem to have found another bug (I'm up to 5 now) with ISE13.4 which I just posted a request for help.
1. Verilog equations in the report viewer are just wrong (VHDL equations seem correct)
2. When changing the speed of a device and rebuilding, the timing report continues to show the old speed. You have to quit and restart for the change to show up.
3. Fresh projects result in warnings on every build about some path not being set up correctly (known problem)
4. When a verify fails (when using Digilent cable), iMPACT disconnects from the device and the only way to gain access to the device is to exit iMPACT and restart it.
5. Bogus error when trying to FIT XC9572XL-10. change a bus from 7 bits to 8-bits and crazy error about a filetype not recognized shows up.
Shameful. Simply shameful release.