Forum Discussion
Honored ContributorUSB Blaster driver conflict with other FTDI kit
Hi,
I am using a USB blaster (Terasic) and on the same system I need to use two Asix Presto programmers that use the same FTDI device and (apparently) drivers. The Presto devices load up and work perfectly, but the (previously working) Blaster shows a yellow icon in Device Manager and Quartus 7.1 can't find it. Without the Prestos, the Blaster is happy. But I need all of them. I have heard that this is connected with the way that Altera configures the drivers, and have heard talk of a patch, but have no details. I would welcome any advice so I can get the devices to coexist. Thanks Malcolm21 Replies
Altera_ForumI found I have to close the terminal program that is using the "other" FTDI device and can't start it again until the USB Blaster is active (e.g. DS-5 debugger is connected or programmer is programming), then both will run fine until Blaster is inactive.
Tedious but is works. Regards, Kevin- Altera_Forum
I just upgraded to Quartus 16.1 and now I have this problem.
Without the FTDI cable plugged in USB-Blaster is at port USB-0, and I can program my device through JTAG. With the FTDI cable plugged in the USB-Blaster changes to USB-1, and I can still program my device through JTAG. With the FTDI cable plugged in as USB-1 and PuTTY open, then I cannot program my device through JTAG - the Quartus programmer reports "No Hardware". Closing the PuTTY window allows the programmer to work again. - Altera_Forum
Hello,
three years later, it seems to me that the "other FTDI devices" problem even gets worse with 64-Bit Windows. I was frequently using FTDI USB-to-RS232 bridges simultaneously with USB Blaster under 32-Bit WinXP. Now with 64-Bit Windows 7, it seems to be impossible at all. Plugging-in the FTDI cable shifts the USB-x assignment, as mentioned by jenglee, same thing happened under WinXP. But once the FTDI virtual COM port is opened in an application. the USB Blaster no longer shows up in Quartus hardware selection, which is a new Window 7 or 64-Bit problem. There's no difference if I use a 64-Bit or 32-Bit Quartus version. The issue might be brought up by changed FTDI drivers rather than Altera specific programming, but it's quite annoying. Did anyone fix the problem? Best regards, Frank - Altera_Forum
Really appreciated the post Stefaan as I am looking at it 5 years later, we are at Quartus 13.0 today and this still happens. The driver .sys name is now different (usbblstr.sys) but problem persists, I think it has to do with FTDI driver wants to occupy USB-0, so when USB-Blaster (or II) become USB-1, the conflict is no longer there.
- Altera_Forum
Yeah! Great!!!
I've been fighting for a while against the same problem before finding this thread... It works fine. Many thanks svhb jyl - Altera_Forum
Yes!
It works even with Vista x64! Thank you! - Altera_Forum
for windows xp there is a quite simple solution (I don't know for vista).
- In the quartus/drivers/usb-blaster/x32 (or x64) directory, rename the ftdibus.sys to something else (ftdibus1.sys), change all references to ftdibus.sys in the usbblst.inf file to the new file name. - uninstall the driver (device manager...) - uninstall all usb-serial adaptors ( although I don't know is this is ncry) - plug out the usb blaster - plug in the usb blaster - reinstall the driver - reinstall the serial port adaptors Good luck Stefaan - Altera_Forum
I have the same problem with a USB to Serial controller with a FTDI chip!
(I'm using Vista x64) I can use one or the other, but not both. AUGHHH!
