Forum Discussion
New Contributor[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 unable to detect the testcard, and scanning fails completely.
Has anyone encountered this issue before? Is there a known fix or driver workaround for this behavior?
Current OS: SUSE SLES12 SP5
Kernel Version: 4.12.14-122.255-default
Issue: USB-Blaster is consistently detected as USB-Blaster [Variant], causing device scan failures.
Previous OS: SUSE SLES12 SP5
Kernel Version: 4.12.14-122.201-default
Status: USB-Blaster was detected correctly and worked without issues.
17 Replies
WZ2Frequent Contributor
Hi there,
Previously, I have not seen any cases where the system is incompatible with the programmer or JTAG driver.
I'm not sure if reinstalling the programmer or trying a newer version might help resolve the issue.
Best regards,
WZ
SeongLimHi,
Could you please share the BKM for reinstalling the USB-Blaster driver?
Normally, I just source the path, and it works directly. However, I’ve tried several versions and none of them are working. Interestingly, if I downgrade the kernel, everything works fine.
Quartus version 19.1.0.670 -
/nfs/site/disks/hdk_cad_root_2/cad/x86-64_linux26/altera/quartus_prime/19.1.0.670/quartus/binregards,
SL
- WZ2
Hi there,
If downgrading the kernel resolves the issue, it's likely that there's a conflict between the kernel and jtagd, although I'm not exactly sure what causes it.
My suggestion is to try downloading a newer version of the Quartus Programmer to update the JTAG driver.
After downloading and installing it, you can reboot the system to apply the new driver.
Before using it, you may want to run killall jtagd to stop any existing instances, then go to the newly installed directory and run ./jtagconfig to check if the device is detected correctly.
Best regards,
WZ
- SeongLim
Hi,
I’ve tried the BKM you shared, but unfortunately, it didn’t resolve the USB-Blaster Variant issue.
Even with the latest Quartus Pro and updated driver, the problem still persists.
Please let me know if there’s anything else I can try.regards,
SL
Farabi_AlteraRegular Contributor
Hello,
Does it work at Windows PC? Just to make sure the USB Blaster II hardware is working.
regards,
Farabi
Milan_SHi,
I have the same issue on windows 11 PC and drivers from actual Quartus (25.3, or 25.1.1 or 24.3) with the original Intel/Altera USB Blaster II device (yes the expensive one I have received yesterday). USB-BlasterII [USB-1] switches to the USB Blaster variant [USB-1] and doesn't work. The solution is to remove driver in the device manager (both, JTAG interface and also System Console interface ), reboot the PC and install drivers again. Than the Blaster works but only short time. The situation repeats (switched to the variant). It is a stupid workflow to spend whole working time with the driver issue...
- FvM
Super Contributor
Hi,
it hasn't been yet described what USB Blaster variant actually is in driver and USB VID terms. What's displayed in device manager under Properties->Details->Hardware-IDs?
Which driver description (oemxxx.inf) is shown USB Blaster variant if you display Devices by Driver in device manager, is it the same as for USB Blaster II? If not, may be you have a second conflicting *.inf file on your PC that has to be deleted.
It may be related to two-step enumeration of the Cypress USB adapter that starts as unfigured device with VID 6810 and is reenumerated as JTAG adpater with VID 6010 after downloading firmware. In Windows, the second step is triggered by JTAG server, if it's stopped, device manager shows USB Blaster II (Unconfigured).
In Linux, it may be necessary to setup a rule file for correct operation of USB Blaster as described in Quartus installation manual.
Regards
Frank- Milan_S
I don’t think the OS driver is the issue. The JTAG device IDs are:
JTAG:
USB\VID_09FB&PID_6010&REV_0142&MI_00
USB\VID_09FB&PID_6010&MI_00System Console:
USB\VID_09FB&PID_6010&REV_0142&MI_01
USB\VID_09FB&PID_6010&MI_01The driver date is 1/6/2025 and the version is 0.0.0.0.
It looks like Quartus is interacting incorrectly with the USB-Blaster. Sometimes it switches from “USB-Blaster II” to the “USB-Blaster variant”, and it seems to depend on the connected hardware and the MSEL configuration. When MSEL is set to JTAG mode, the probability of a USB-Blaster failure is lower than in AS mode. I’m also not sure whether the QSPI owner setting in the device configuration (Agilex 5) plays any role in this USB-Blaster issue.
- FvM
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
My old Blaster 1 is:
USB\VID_09FB&PID_6001&REV_0400
USB\VID_09FB&PID_6001with 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_00with 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
Ok, the oem192.inf (C:\Windows\INF) file is used insted of the usbblasterii.inf, but the file content is identical.
- FvM
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.
- Milan_S
My actual workaroud about the issue is to restart jtagserver. In CMD as admin:
net stop jtagserver
net start jtagserver
- Farabi_Altera
Hello,
Every time you install new version of Quartus , it will ask you to install USB Blaster driver. Do you do this step? This step is critical to keep your driver matching with your Quartus version.
regards,
Farabi
- Milan_S
Sure
- Milan_S
Taking back, today jtagserver restart do not help. Command:
C:\altera_pro\25.1.1\quartus\bin64>jtagconfig returns:
1) USB-Blaster variant [USB-1]
Unable to lock chain - Hardware not attached
2) Remote server loc: Unable to connectIn this wrong state, the Device Manager still shows on the oem190.inf so the driver is still the same...
