Honored Contributor
Honored ContributorHi Alex
Thank you for your reply. I know this possibility. But for a variety of reasons, there is a big advantage for us in not having to define the programming interface: a) We only need one programming interface on a PC at one time, but it would be good if the interface type could vary (...so we remain independent of which programming interface we use, "ByteBlaster" or "ByteBlaster_II", ...). b) When we use our FTDI device in BitBang mode, "quartus_pgm.exe" recognizes it as "USB-Blaster [USB-?]" as soon the COM interface is opend. The problem is, that for some reasons sometimes the real "ByteBlaster" remains at "[USB-0]" sometimes it changes to "[USB-1]". c) Third problem is, that the given cable name in "quartus_pgm.exe" ("[USB-0]" or "[USB-1]") depends on the order you connect your interfaces to the pc (and also on the order the COM interfaces are opened). For these reasons, it would be good if we could continue to use the tool in the same way as we did under previous operating systems (like WinXP/32, Win10/64). Does anyone know what is technically the reason for this new behavior? Best regards Dietmar
