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

Quartus II JTAG Server Error Code 89

Altera_Forum
Honored Contributor II
8,936 Views

I've been trying to program my DE0-Nano for over an hour and a half now, and I am always getting an error when I press start in the programmer: 

Info (209060): Started Programmer operation at Fri Jul 26 17:38:22 2013 Error (209053): Unexpected error in JTAG server -- error code 89 Error (209012): Operation failed Info (209061): Ended Programmer operation at Fri Jul 26 17:38:22 2013  

I am using the 64 bit, linux, free web edition of quartus 2. Anyone?
0 Kudos
5 Replies
Altera_Forum
Honored Contributor II
6,578 Views

I hate to bump this early, but someone? How hard can this be to fix? Really...

0 Kudos
Altera_Forum
Honored Contributor II
6,578 Views

Sometimes I face issues with the JTAG USB dev not showing up on powerup. This is what I have followed. 

Add a line to etc/rc.local to start the jtag server. http://www.alterawiki.com/wiki/quartus_for_linux#setup_jtag 

Do the step outlined in this link: http://www.altera.com/download/drivers/dri-usb_b-lnx.html 

 

You may have to restart the JTAG server. I think that would be  

$ service jtagd restart 

Otherwise you might have to powercycle your computer after doing the steps above. 

 

I think this was addressed in this thread also 

http://www.alteraforum.com/forum/showthread.php?t=4348 

 

Amol
0 Kudos
Altera_Forum
Honored Contributor II
6,578 Views

Here's one of the better threads I've seen: 

 

=== 

http://www.ict.kth.se/courses/is1500/2011/swsetup/n2errors.html 

=== 

 

UPDATE: 

 

To sift through the stuff on this site, error 89 means you don't have the correct permissions to the JTAG device on your Linux box/VM. I added the following to my USB rules (read the multitude of posts on this topic, but pay attention to what I've done as well...yours could be slightly different): 

===# USB-Blaster 

 

 

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6001", MODE="0666", SYMLINK+="usbblaster/%k" 

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6002", MODE="0666", SYMLINK+="usbblaster/%k" 

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6003", MODE="0666", SYMLINK+="usbblaster/%k" 

 

# USB-Blaster II 

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6010", MODE="0666", SYMLINK+="usbblaster2/%k" 

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6810", MODE="0666", SYMLINK+="usbblaster2/%k" 

=== 

 

Cheers!
0 Kudos
Altera_Forum
Honored Contributor II
6,578 Views

Thank you slacker, the usb rules you provided work fine with a 64-bit Fedora 19 setup! Problem was solved 

 

 

--- Quote Start ---  

Here's one of the better threads I've seen: 

 

=== 

http://www.ict.kth.se/courses/is1500/2011/swsetup/n2errors.html 

=== 

 

UPDATE: 

 

To sift through the stuff on this site, error 89 means you don't have the correct permissions to the JTAG device on your Linux box/VM. I added the following to my USB rules (read the multitude of posts on this topic, but pay attention to what I've done as well...yours could be slightly different): 

===# USB-Blaster 

 

 

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6001", MODE="0666", SYMLINK+="usbblaster/%k" 

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6002", MODE="0666", SYMLINK+="usbblaster/%k" 

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6003", MODE="0666", SYMLINK+="usbblaster/%k" 

 

# USB-Blaster II 

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6010", MODE="0666", SYMLINK+="usbblaster2/%k" 

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6810", MODE="0666", SYMLINK+="usbblaster2/%k" 

=== 

 

Cheers! 

--- Quote End ---  

0 Kudos
Yc11
Beginner
998 Views

The solution that had worked for me is as below:

  1. Copy the file 51-usbblaster.rules (provided by this repository) to /etc/udev/rules.d/51-usbblaster.rules
  2. Change the owner of this file to root (# chown root:root 51-usbblaster.rules)
  3. Reboot your system

 

Content in 51-usbblaster.rules:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6001", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6002", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6003", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6010", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="09fb", ATTRS{idProduct}=="6810", MODE="0666"

 

Source: https://github.com/simon-77/Install-Quartus-and-ModelSim-on-Linux-openSUSE

0 Kudos
Reply