Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
16556 Discussions

USB Blaster II not recognized in CentOS 7

Altera_Forum
Honored Contributor II
2,276 Views

Hello there, 

 

I am having an issue regarding the Max 10 Development Kit where I installed the drivers and set it up according to this url: "https://www.altera.com/support/support-resources/download/drivers/dri-usb_b-lnx.html

 

Thus my setup looks like this: 

 

# USB-Blaster  

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6001", MODE="0666"  

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6002", MODE="0666"  

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6003", MODE="0666"  

# USB-Blaster II 

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6010", MODE="0666"  

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6810", MODE="0666" 

 

I have another version installed on another computer with CentOS Linux release 6.4 that is working (with same configuration). 

The new configuration I am running on is CentOS Linux release 7.3.1611 (Core). 

 

Any ideas? 

 

Regards,
0 Kudos
3 Replies
Altera_Forum
Honored Contributor II
895 Views

 

--- Quote Start ---  

Hello there, 

 

I am having an issue regarding the Max 10 Development Kit where I installed the drivers and set it up according to this url: "https://www.altera.com/support/support-resources/download/drivers/dri-usb_b-lnx.html

 

Thus my setup looks like this: 

 

 

# USB-Blaster  

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6001", MODE="0666"  

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6002", MODE="0666"  

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6003", MODE="0666"  

 

# USB-Blaster II 

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6010", MODE="0666"  

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6810", MODE="0666" 

 

I have another version installed on another computer with CentOS Linux release 6.4 that is working (with same configuration). 

The new configuration I am running on is CentOS Linux release 7.3.1611 (Core). 

 

Any ideas? 

 

Regards, 

--- Quote End ---  

 

 

Did you ever resolve this issue? Or is there someone else who has any understanding of this problem? 

 

Thanks!
0 Kudos
Altera_Forum
Honored Contributor II
895 Views

 

--- Quote Start ---  

Hello there, 

 

I am having an issue regarding the Max 10 Development Kit where I installed the drivers and set it up according to this url: "https://www.altera.com/support/support-resources/download/drivers/dri-usb_b-lnx.html

 

Thus my setup looks like this: 

 

# USB-Blaster  

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6001", MODE="0666"  

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6002", MODE="0666"  

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6003", MODE="0666"  

# USB-Blaster II 

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6010", MODE="0666"  

BUS=="usb", SYSFS{idVendor}=="09fb", SYSFS{idProduct}=="6810", MODE="0666" 

 

I have another version installed on another computer with CentOS Linux release 6.4 that is working (with same configuration). 

The new configuration I am running on is CentOS Linux release 7.3.1611 (Core). 

 

Any ideas? 

 

Regards, 

--- Quote End ---  

 

 

Did you happen to figure this out? Does anyone else have any idea on what could be going wrong here? I'm currently dealing with the same issue. 

 

Thanks
0 Kudos
Altera_Forum
Honored Contributor II
895 Views

 

--- Quote Start ---  

Did you happen to figure this out? Does anyone else have any idea on what could be going wrong here? I'm currently dealing with the same issue. 

 

Thanks 

--- Quote End ---  

 

 

Hello there, 

 

There was some problem with the permissions and acess to the USB interface. The strange thing here is that for some reason the interface started to function normally after a day or so. 

I think I needed to restart the computer (the problem here is that it was a laboratory computer that I did not had root access). 

After a while it started to work properly, but then, I did not no what could have triggered this errors. 

 

Regards,
Reply