my DE2 Board doesn't see programming cable (USB Blaster). USB Blaster is embedded in DE2 Board. my other Altera board works fine. Quartus recognize the USB Blaster as soon as I connect to the board. Same cable is connected to DE2. But it doesn't show anything. It used to work. Is there anything to do with swithches. SW19 I set it to both RUN and PROG. But in either case, it fails to recognize USB BLASTER.
--- Quote Start --- my DE2 Board doesn't see programming cable (USB Blaster). --- Quote End --- I guess, the pc doesn't see the USB Blaster? In this case, does the USB device show in system control manager? The 93C46 configuration EEPROM may be corrupted, then it would be displayed as default FTDI device instead. If no USB device shows at all, it's likely a hardware defect, including possible missing 5V power supply. If an USB Blaster is shown, but doesn't work, the CPLD may have been reprogrammed. It can be restored to factory default configuration with a standard Altera programming cable.
You are right.It shows FTDI device instead of USB Blaster. how can I fix 93C46 configuration EEPROM corruption???????DE2 has own 9V power supply. You said in your e-mail 5V power supply. Is there any other power supply (5V)? DE2 doesn't have regular Altera Programming Cable input. You said in your e-mail "It can be restored to factory default configuration with a standard Altera programming cable." What do you mean? Thank you very much.
--- Quote Start --- DE2 doesn't have regular Altera Programming --- Quote End --- Yes, JP3 is an assembly option only. Also, the MAX CPLD image file apparently isn't supplied with DE2 support files. I simply assumed, this would be the case as with Altera Dev kits. --- Quote Start --- Is there any other power supply (5V)? --- Quote End --- It's an internal regulator and probably O.K. in your case. --- Quote Start --- how can I fix 93C46 configuration EEPROM corruption. --- Quote End --- I'm not aware of an official procedure, but it should work by copying the data from another DE2-board or an USB-Blaster using FTDI MProg tool. The problem has been reported by other forum users before. I wonder how an EEPROM corruption happens at all. It may be also the case, that the EEPROM data are O.K., but the FT245 initialization fails for some reason, e. g. inappropriate reset.