--- Quote Start ---
Yes, as I mentioned in my original post, I installed the driver. Before the driver installation, the USB Blaster was recognized as as an unknown device with some numbers on it. After the installation it's recognized as Altera Nios II Evaluation Board.
--- Quote End ---
What does your USB-Blaster actually look like? Is it an Altera USB-Blaster a Terasic USB-Blaster or a development kit with an on-board USB-Blaster or a clone?
Under Linux you can use lsusb to look at the USB Vendor ID and Product ID. Under Windows you can use the device manager.
The USB-Blaster Vendor ID is 0x9FB ... which you can see here
http://www.altera.com/download/drivers/dri-usb_b-lnx.html The product ID is typically 0x6001. If your product ID is different, then it will be recognized with a different name. The Windows .inf file probably has the mapping ... yep ... this is from 12.1sp1 web edition
USB\VID_09FB&PID_6001.DeviceDesc="Altera USB-Blaster"
USB\VID_09FB&PID_6002.DeviceDesc="Altera Cubic Cyclonium"
USB\VID_09FB&PID_6003.DeviceDesc="Altera Nios II Evaluation Board"
USB\VID_09FB&PID_6004.DeviceDesc="Altera Cyclone III EP3C25 Starter Kit"
USB\VID_09FB&PID_6005.DeviceDesc="Altera Cyclone III EP3C120 Development Kit"
USB\VID_09FB&PID_6006.DeviceDesc="Altera Stratix III EP3SL150 Development Kit"
USB\VID_09FB&PID_6007.DeviceDesc="Altera Stratix III EP3SL340 Development Kit"
USB\VID_09FB&PID_6008.DeviceDesc="Altera Nios Embedded Evaluation Kit"
USB\VID_09FB&PID_6009.DeviceDesc="Altera Nios Development Kit, Cyclone III Edition"
So for some reason your USB-Blaster has a product ID of 6003. You can use FT_PROG to re-program the EEPROM if it bothers you, however, it should work just fine as it is.
Cheers,
Dave
Honored Contributor
