Keegan1
New ContributorUser Profile
New Contributor
User Widgets
Contributions
Re: USB-BlasterII mounts as "USB-Blaster variant"
I will show you how it looks in our device manager, task manager, and services panel. It's just the default executable included with the Quartus installation. We installed everything normally, including installing the JTAG drivers when prompted to by the main installer, and we haven't done anything involving windows services. The VID/PID does indeed show up differently when it is showing as "Usb blaster variant" vs "Usb-BlasterII", specifically the "REV". And again, you can hear the windows device connect noise and see the device manage refresh when reopen Quartus Programmer after killing jtagserver.exe While not working: Altera USB-Blaster II (JTAG interface) USB\VID_09FB&PID_6010&REV_0127&MI_00 USB\VID_09FB&PID_6010&MI_00 Altera USB_Blaster II (System Console interface) USB\VID_09FB&PID_6010&REV_0127&MI_01 USB\VID_09FB&PID_6010&MI_01 While working: Altera USB-Blaster II (JTAG interface) USB\VID_09FB&PID_6010&REV_0142&MI_00 USB\VID_09FB&PID_6010&MI_00 Altera USB_Blaster II (System Console interface) USB\VID_09FB&PID_6010&REV_0142&MI_01 USB\VID_09FB&PID_6010&MI_01 Device Manager: Windows Process: Service:Re: USB-BlasterII mounts as "USB-Blaster variant"
I found a workaround in another thread about this issue here: [USB-Blaster] Detected as "USB-Blaster Variant" on SLES12 – Causing Detection Issues | Altera Community - 319603 The pattern is that the device shows up incorrectly as "USB blaster variant" if it got plugged in while "jtagserver.exe" is running in the background. In task manager it is called Background Processes > Intel Quartus Prime Pro Edition Software (jtagserver.exe). **Kill this process before plugging in the device**, then open Programmer. You hear the Windows device connect sound when the software opens, and then it shows up correctly as "USB-BlasterII".Re: USB-BlasterII mounts as "USB-Blaster variant"
We have the exact same problem. You plug in the blaster and sometimes it works (shows up as USB-BlasterII) and sometimes it doesn't work at random (shows up as USB-Blaster variant). We use the Quartus Prime Programmer included with Quartus Prime Pro 23.2. Upgrading to a new quartus version is not trivial for us, since this is the last version that still supports Nios II, which we require. We have never identified any pattern as to make sure it doesn't happen, we usually just disconnect and reconnect and/or restart the PC until it shows up correctly. It will not work for programming if it shows up as "USB-Blaster variant" Of course we have the driver installed, it works sometimes. I'm fairly sure it's only a Windows 11 problem, as I had Windows 10 personal machine for a long time and never had the issue until I upgraded. Our other machines are all Windows 11.Re: Nios-V with FreeRTOS
We are now on Quartus 24.3 and attempting to start using FreeRTOS. I think we see the same issue as original poster. When generating the BSP for a Nios V + FreeRTOS project, only the altera_avalon_uart and altera_avalon_jtag_uart drivers are available in the generated BSP. No other drivers, such as SPI, I2C, PIO are present. However the two drivers which are copied build succesfully. Meanwhile on Quartus 23.4 as suggested -- the drivers are copied, but the BSP has build errors regarding OS_FLAG_etc not found. From my perspective FreeRTOS is not possible to use with NiosV. Do you have any suggestion?
