Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
18 years ago

USB 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

Malcolm

21 Replies

Show More
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    9 years ago

    Thanks for confirming the issue. I'm not sure yet if generally occurs with recent Windows versions and newer USB Blaster drivers, or only under particular circumstances.

    --- Quote Start ---

    I 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.

    --- Quote End ---

    Yes, I believe that has worked for me too. Considering that the USB Blaster reconnects in various situations (e.g. always after reconfiguring the FPGA, starting a different JTAG debug tool) the method is more a last resort than a solution.

    Still hope there's an actual solution other than switching to USB Blaster 2 or possibly a Cypress based USB Blaster clone.

    Regards,

    Frank
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    8 years ago

    I am also getting the same issue with Quartus 16.1, Windows 7 x64.

    The workaround described by ep1015 and kflynn works, but is a bit tedious.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    8 years ago

    Could anyone solve this issue?

    I am facing it too and could not find a solution.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    8 years ago

    I got a USB Blaster II and now no problem. Expensive fix for what should be easily fixable. Maybe it's to allow Altera/Intel to sell more blasters.

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    8 years ago

    Because they can?

    Seriously, it's not like the original doesn't work there's just an annoying caveat to its use.

    There is a FAQ on the FTDI website that mentions something similar and gives a solution but that is for the person implementing the application.

    But it would be nice if Altera would respond with at least an explanation! I doesn't seem anybody from Altera read is reading this.

    So get a usb blaster II or be aware of what FTDI device you need to use at the same time as the blaster I.
  • AGuan's avatar
    AGuan
    Icon for New Contributor rankNew Contributor
    7 years ago

    Ten years already... This combination works for me:

    The Blaster driver is the one from Quartus II 14.1, which is v2.4.16, released on 4/21/2009.

    And the USB Serial Converter driver is: 2.12.28.0, released on 8/16/2017.

    Hope it helps.

  • NJuser's avatar
    NJuser
    Icon for New Contributor rankNew Contributor
    7 years ago

    Has anyone tried to run Signaltap (over the Byte blaster) while being connected to the FTDI device? I am trying to provide a command over the USB Serial COM port (Tera Term), and wish to see the response of the FPGA through Signaltap. But as discussed in this thread, I can either use the Tera Term or the Byte Blaster. I am using the Rev C Byte Blaster (which I think is the latest).

    Thanks