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

Quartus (13 or 12) on Ubuntu 13.04 64 bits - device go constantly offline

Altera_Forum
Honored Contributor II
1,039 Views

Hi, 

 

my Quartus II is able to recognize my device. If I go to Tools -> Programmer, select my hardware, the .sof file and click start. It works. However, If I go to Signal Tap II and try to download my bitstream on my hardware. It fails. It normally doesn't recognize my fpga but if i unplug and plug it back, it recognizes.. however It fails to download the bitstream? Any idea? 

 

what I'm seeing in my log: 

 

Jul 20 10:11:43 deathstar mtp-probe: bus: 3, device: 7 was not an MTP device 

Jul 20 10:13:00 deathstar kernel: [ 1539.370761] usb 3-2: USB disconnect, device number 7 

Jul 20 10:13:07 deathstar kernel: [ 1545.915426] usb 3-1: new full-speed USB device number 8 using xhci_hcd 

Jul 20 10:13:07 deathstar kernel: [ 1545.932715] usb 3-1: New USB device found, idVendor=09fb, idProduct=6001 

Jul 20 10:13:07 deathstar kernel: [ 1545.932728] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 

Jul 20 10:13:07 deathstar kernel: [ 1545.932736] usb 3-1: Product: USB-Blaster(Altera) 

Jul 20 10:13:07 deathstar kernel: [ 1545.932743] usb 3-1: Manufacturer: Altera 

Jul 20 10:13:07 deathstar kernel: [ 1545.932748] usb 3-1: SerialNumber: 8D8434794952 

Jul 20 10:13:07 deathstar mtp-probe: checking bus 3, device 8: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1" 

Jul 20 10:13:07 deathstar mtp-probe: bus: 3, device: 8 was not an MTP device 

 

 

my udev rules: 

# Altera USB-Blaster rule to set mode to 666.  

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6001", MODE="0666"
0 Kudos
1 Reply
VVois
Beginner
160 Views

This is related to a recent change in the default Udev rules to set a catch-all rule for devices to be handled by MTP if they don't match any other udev rules for USB devices.

 

Use the following udev rules:

 

# USB-Blaster

SUBSYSTEM=="usb", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6001", MODE="0666", ENV{MTP_NO_PROBE}="1"

SUBSYSTEM=="usb", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6002", MODE="0666", ENV{MTP_NO_PROBE}="1"

SUBSYSTEM=="usb", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6003", MODE="0666", ENV{MTP_NO_PROBE}="1"

 

# USB-Blaster II

SUBSYSTEM=="usb", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6010", MODE="0666", ENV{MTP_NO_PROBE}="1"

SUBSYSTEM=="usb", ATTR{idVendor}=="09fb", ATTR{idProduct}=="6810", MODE="0666", ENV{MTP_NO_PROBE}="1"

 

Reply