Have you ever encountered the problem that FT245 and FT232 cannot coexist?

wsmysyn

Have you ever encountered the problem that FT245 and FT232 cannot coexist? [Copy link]

RT This problem has existed for a long time, but I am too lazy to fix the system: win10 64-bit. I bought a USB blaster downloader online, FT245RL and CPLD solution. There is also a FT232R USB to serial port module. The drivers are all installed normally. The USB blaster uses the one in the quartus installation directory, and the FT232 is downloaded from the official website; there is no problem using it alone. The performance is that if the FT232 is selected to open the serial port with the serial port tool, the USB blaster cannot be seen in quartus, but the device manager can see this device. If the USB blaster is recognized first, and then the serial port of FT232 is opened, FT245 will be squeezed out and cannot be scanned in quartus; unless the serial port is closed but the device is not unplugged, the USB blaster can be scanned again at this time;; It seems that FT232 has a high priority, and FT245 will always be squeezed out, but FT232 will not be squeezed out by FT245. What could be the problem? ? Is it a problem with the FTDI driver? Is there a bug? I originally needed to use the signal tap of Quartus to send some data to the serial port and capture the waveform, but they cannot coexist, which is very troublesome. I don’t have any other USB to serial port modules at the moment, all of them are FT232 solutions.

懒猫爱飞

1) Have never used it together 2) Install a virtual machine on your computer and use it in the virtual machine, such as the serial port. Although it is troublesome, it can theoretically solve your problem.