Forum Discussion

SeongLim's avatar
SeongLim
Icon for New Contributor rankNew Contributor
8 months ago

[USB-Blaster] Detected as "USB-Blaster Variant" on SLES12 – Causing Detection Issues

Hi, I'm facing an issue where the USB-Blaster is automatically detected as USB-Blaster [Variant] in a Linux environment (SLES12), instead of the standard USB-Blaster. Because of this, my system is ...
Programmable Logic Device
FvM's avatar
FvM
Icon for Super Contributor rankSuper Contributor
2 months ago

Hi,
USB\VID_09FB&PID_6010&REV_0142&MI_00 looks suspicious. It's not listed in usbblasterii.inf shipped with recent Quartus versions. You may check which oem.inf file is linked with this device instance and post its content here.

Regards
Frank

  • Milan_S's avatar
    Milan_S
    Icon for New Contributor rankNew Contributor
    2 months ago

    My old Blaster 1 is:

    USB\VID_09FB&PID_6001&REV_0400
    USB\VID_09FB&PID_6001

    with driver from: C:\altera_pro\25.1.1\quartus\drivers\usb-blaster\usbblstr.inf

    Blaster II is:

    USB\VID_09FB&PID_6010&REV_0142&MI_00
    USB\VID_09FB&PID_6010&MI_00

    with driver form: C:\altera_pro\25.1.1\quartus\drivers\usb-blaster-ii\usbblasterii.inf

    I do not know why the REV_XXXX is there when the INF file doesnt contain it. 

    Both blasters are stable in the device manager but both fails with the Quartus and Agilex 5 board. They can load board 1x or 2x,.. but frequently the Blaster II changes to the variant (in the Quartus programmer hardvare list) and do not work more. The old Blaster simlpy diappears from the Quartus programmer hardware list.

     

  • Milan_S's avatar
    Milan_S
    Icon for New Contributor rankNew Contributor
    2 months ago

    Ok, the oem192.inf (C:\Windows\INF) file is used insted of the usbblasterii.inf, but the file content is identical.

    • FvM's avatar
      FvM
      Icon for Super Contributor rankSuper Contributor
      2 months ago

      usblasterii.inf is copied to oemxxx.inf during install, that's normal operation.

      I was under the impression, there could be a different driver *.inf loaded in non-function state which should reflect in device control manager, but apparently it's not the case.