Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17268 Discussions

USB-BlasterII [3-11] Unable to read device chain- JTAG chain broken

Altera_Forum
Honored Contributor II
‎03-08-2017 05:05 PM
2,873 Views

I am having issues getting my Cyclone V GT dev kit to connect with my computer with the built in USB Blaster II. My computer is running Centos6.8. I have installed Quartus II 15.0. 

 

 

I have followed the instructions at https://www.altera.com/en_us/pdfs/literature/ug/ug_usb_blstr_ii_cable.pdf for Installing the USB-Blaster II Driver on Linux Systems by changing the /etc/udev/rules.d/51-usbblaster.rules file. 

 

I then rebooted. When I run: 

 

sudo killall -9 jtagd 

sudo jtagd 

jtagconfig 

 

I get: 

 

1) USB-BlasterII [3-11] 

Unable to read device chain - JTAG chain broken 

 

I know the computer is able to recognize the USB port; when I type lsusb, I get: 

 

Bus 003 Device 005: ID 09fb:6010 Altera  

 

Does anyone have an idea what the problem may be? It wouldn't surprise me if I was missing some simple dependency, but I can't find a list of the dependencies that are needed anywhere. 

 

Thanks, 

 

joe
0 Kudos

Link Copied

1 Reply
HFred1
Beginner
‎02-17-2019 02:49 PM
1,545 Views

NO answer.

I got exactly the same problem!

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.