In reviewing the drivers download page it appears there are NO drivers for Windows 10 for the USB based Blaster programmer cables.Is this really true ?
I've done it on Windows 10. After plugging the USB blaster II then go to Install Drivers and navigate to the install directory and there is a drivers directory. I've done it twice on this machine and it's worked.
--- Quote Start --- I've done it on Windows 10. After plugging the USB blaster II then go to Install Drivers and navigate to the install directory and there is a drivers directory. I've done it twice on this machine and it's worked. --- Quote End --- I am trying to do it now and it isn't working. I just installed the tool and plugged in the USB Blaster and Windows 10 reports an 'Unknown device'. I go to 'Update driver' using files at C:\intelFPGA\16.1\qprogrammer\drivers with the 'Include subfolders' checked. and it gets it to load the Altera USB-Blaster into the USB controllers but it still has an exclamation point. When I try to update the driver it says the best drivers are already installed. I have tried this several times and it still does not work. Lenovo Thinkpad laptop.
I too am unable to install drivers on Windows 10 - although I was able to do so on other Windows 10 machines.I think I have identified the difference. The issue is that the drives are not "digitally signed" (windows tells me that "the hash for the file is not present in the specified catalog file") and won't install the driver - previously it has given me a warning and allowed me to install anyway. I first tried turning off driver signature enforcement using BCDEDIT - but that bounced because of the Secure Boot Policy. Then looked at disabling Secure Boot Policy but fell down because of BitLocker. I'll keep bashing away at this - BUT THE ACTUAL ANSWER IS FOR ALTERA(INTEL) TO PRODUCE SIGNED DRIVERS FOR ALL WIDELY USED PROGRAMMING DEVICES FOR THE INCREASINGLY UBIQUITOUS WINDOWS 10 !
I was able to install the drivers. You first have to disable driver signature enforcement. This is the sequence:1 - Go to windows 10 settings and search for "advanced startup options" 2 - Under Advanced startup, hit "Restart now" 3 - After a moment, you'll get a "choose an option" screen - choose "Troubleshoot", then "Advanced options", then "Startup Settings" 4 - You'll get a screen telling you what you will be able to change and a single "Restart" button - press it. 5 - If your boot drive is BitLocker encrypted, you'll need to enter the recovery key (press return, enter the key in the text box then hit return again - it took me three goes to realize I had to hit return before I could enter they key !) 6 - You'll be given a menu of options, number 7 disables driver signature enforcement 7 - When the PC restarts, use Device manager to update the drivers - this time you'll get a warning about the signature, but they install fine. 8 - When you've finished, restart normally to re-enable signature enforcement
Hi All,So I am doing development on two different PCs, using the same target and USB Blaster 2. One PC is win 7 the other win 10. The win 7 PC worked fine. Today I am using the Win 10 PC and have run into problems. When I first tried programming, Quartus didn't find the USB blaster. I checked device manager and the driver hadn't installed, so I did a driver update from device manager and pointed to the IntelFPGA_lite directory and the driver correctly installed and *appeared* to operate correctly. However, in-spite of going through the motions and "looking" like it is working, it is not programming my target board. My target board is using the MAX10M50SCE144. When I program, the CONF_DONE output goes tri-state for a short while, about a second, then lights again. I am using a new design that successfully compiles and an older design from the Win 7 PC that loads and runs OK under win 7 with the same USB blaster 2. Any thoughts? Thanks, Scott
Here's an update to yesterday's post. It isn't the USB blaster or the PC driver that is the problem. Yesterday I made a hardware change that has affected the MAX 10's auxiliary programming pins. Immediately after programming completes, configuration is reactivated by signal activity on nCONFIG.
Hi all-Having similar issues. I followed the excellent instructions from the March 1st post and (as far as I can tell) disabled driver signature enforcement. However, when updating the driver windows comes back and reports that the best drivers are already installed. Also, my initial symptoms were slightly different. When the cable was attached to the DE10-standard board, windows automatically installed a driver for USB Serial Port (COM4) instead of showing it as an "unknown device". Can anyone provide additional help? Thanks
Hi,Right click on "unknown device"->UPdate Driver Software->Browser to the Quartus installation directory ("C:\intelFPGA\17.0\quartus\drivers\usb-blaster")->click next. If it does not solve the problem try previous post by garypace. Or Reinstall the Quartus tool. Let me know if this has helped resolve the issue you are facing or if you need any further assistance. Best Regards, Anand Raj Shankar (This message was posted on behalf of Intel Corporation)
--- Quote Start --- Hi, Right click on "unknown device"->UPdate Driver Software->Browser to the Quartus installation directory ("C:\intelFPGA\17.0\quartus\drivers\usb-blaster")->click next. If it does not solve the problem try previous post by garypace. Or Reinstall the Quartus tool. Let me know if this has helped resolve the issue you are facing or if you need any further assistance. Best Regards, Anand Raj Shankar (This message was posted on behalf of Intel Corporation) --- Quote End --- Hi Anand- Thanks for replying. The connection does not show up as "unkown device". Instead it shows up as a fully configured "USB Serial Port (COM4)". Could this be a part of the problem? Windows does not change the driver after: UPdate Driver Software->Browser to the Quartus installation directory ("C:\intelFPGA\17.0\quartus\drivers\usb-blaster")->click next. Thanks, -J
Hi,Have you connected the Blaster to right header/port(jtag) on your board? Which Dev Kit are you using? Best Regards, Anand Raj Shankar (This message was posted on behalf of Intel Corporation)
Hi Anand-The confusion is on my part. I thought it was possible to download to the DE10-standard (terasic) via the USB connector... of course this explains why windows shows it as a usb com port... because it is. I may end up purchasing the USB-Blaster cable. I'll have to see how far I can get w/o it setting up configurations via the HPS. Thanks so much for your prompt replies. It is nice to know I will not be left hanging even for minor issues like this one. -J
I'm having no luck installing drivers for a DE10-Lite demo board on windows 10.
I've tried two computers and both end with the exact same message:
"Windows found drivers for your device but encountered an error while attempting to install them", "A problem was encountered while attempting to add the driver to the store".
I tried one option for eliminating driver signing (command line) and tried the advanced restart settings suggestion above but that ended with a bricked computer and a call to IT to get a bitlocker key. I'm not trying it again.
Are there any updates to this problem?
2021, this is still the case. Astonishing that they ship drivers that will simply not work for 99% of win10 users
The drivers in Quartus 20.1 are unsigned
I attach screenshot of what my Windows 10 says
Doesn't even complain about hash, just says no.
Had to turn off driver signing enforcement, then worked fine via JTag
When you install driver after that, it will warn you and ask if you are sure.
I even went and bought another USB Blaster, thinking that mine was faulty!
Did you try option 1?
I tried both. The first didn't seem to work though I'll try again. The second bricked my computer. If you have an encrypted drive you need the encryption key to use option 2. IT fixed it but I'm not doing it again.
Option 1 did nothing for me
I don't have an encrypted drive for Option 2 was fine, for me
Of course the real answer is for Intel to release proper signed s/w
If I'd paid for Quartus and couldn't get it working because of broken drivers I'd be furious
Maybe see if you can get a human from Intel to help