Forum Discussion

SeongLim's avatar
SeongLim
Icon for New Contributor rankNew Contributor
1 year 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
8 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
8 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
    8 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.