I'm not sure how people normally deal with this. On a different linux
machine (not BBB), I have several USB serial adapters attached and I need
them to be assigned specific device names so that software can find them.
(i.e. can't trust the ttyUSBn ordering) I found the best way was to add an
entry to /etc/udev/rules.d/usbtty.rules
# Something like this....
SUBSYSTEM=="tty", ATTRS{manufacturer}=="Prolific Technology Inc.",
ATTRS{product}=="USB-Serial Controller D", KERNEL=="ttyUSB*",
SYMLINK+="uniquename"
# (all one line in the file!)
Your matching rules may vary. I believe the SUBSYSTEM and KERNEL clauses
will help udev match your device, especially if the device has multiple
interfaces.
Of course you will need to change the manufacturer and product (or use
{idProduct} and {idVendor} instead) to match your product. Once this is
done (and maybe kill -HUP on the systemd-udev process), the device should
be recognized and you can find your device at /dev/uniquename.
Craig
On Friday, November 15, 2013 5:07:25 PM UTC-5, [email protected] wrote:
>
> Hi,
>
> I working on a project where I need to use the USB host interface to
> connect a FTDI module. The problem is that I can't see the ttyUSB0. If I
> do lsusb this is what I get:
>
> Bus 001 Device 002: ID 0403:6001 Future Technology Devices International,
> Ltd FT232 USB-Serial (UART) IC
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> So the FTDI module is loaded, but still can't see the ttyUSB0. The kernel
> version is 3.8.13. Does anyone have any advice on how to make this work? Do
> I need to add a bone_cape or something else?
>
> Richard
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
