• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Alchitry Loader - Could not detect an Alchitry Au
#1
Question 
I bought an Alchitry Au about a year ago from SparkFun and finally got around to checking it out this past weekend, however I can't get it to be recognized by the Alchitry Loader. I am running on Ubuntu Linux 20.10 and am not using alchitry labs (am using Vivado/Verilog instead of Alchitry Labs and Lucid).

The board seems to power on just fine and the leds do this wave pattern and an alternating LED pattern when the reset button is pressed down, so I assume its working ok.

I also checked dmesg and it appears that everything is being hooked up just fine there, so I am not really sure what is going on.


Code:
[ 6799.321641] usb 1-4: new high-speed USB device number 16 using xhci_hcd
[ 6799.476432] usb 1-4: New USB device found, idVendor=0403, idProduct=6010, bcdDevice= 7.00
[ 6799.476445] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6799.476450] usb 1-4: Product: Alchitry Au
[ 6799.476454] usb 1-4: Manufacturer: Alchitry
[ 6799.476458] usb 1-4: SerialNumber: FT4ZS6I3
[ 6799.480471] ftdi_sio 1-4:1.0: FTDI USB Serial Device converter detected
[ 6799.480587] usb 1-4: Detected FT2232H
[ 6799.482908] usb 1-4: FTDI USB Serial Device converter now attached to ttyUSB0
[ 6799.484528] ftdi_sio 1-4:1.1: FTDI USB Serial Device converter detected
[ 6799.484646] usb 1-4: Detected FT2232H
[ 6799.485002] usb 1-4: FTDI USB Serial Device converter now attached to ttyUSB1
  Reply
#2
I'm encountering the same problem on Ubuntu 20.04. After reading this thread https://forum.alchitry.com/thread-267.html, I have checked using FT_Prog on a Windows 10 machine that the FTDI chip is programmed and has "Alchitry Au" as product description.
  Reply
#3
This usually has to do with the FTDI SIO driver taking over and blocking Alchitry Labs from getting access.

You should be able to fix this by adding a Udev rule.

Create the file /etc/udev/rules.d/99-alchitry.rules and add the following to it.

Code:
SUBSYSTEM!="usb|usb_device", GOTO="ft2232_rules_end"
ACTION!="add", GOTO="ft2232_rules_end"

ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", RUN+="/bin/sh -c 'echo $kernel > /sys/bus/usb/drivers/ftdi_sio/unbind'", MODE="0666", GROUP="dialout", ENV{ID_MM_DEVICE_IGNORE}="1"

LABEL="ft2232_rules_end"

This requires that you have a group named "dialout" and that your user account is a member of it.
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)