Arduino Communications Device Naming with udev
Jvaughters (Talk | contribs) |
Jvaughters (Talk | contribs) |
||
| Line 12: | Line 12: | ||
==Installation== | ==Installation== | ||
| − | {{Note|All scripts will assume that there is a '{{ic|/dev/ | + | {{Note|All scripts will assume that there is a '{{ic|/dev/arduino_1}}'.}} |
The drivers for the FTDI chip is included in the kernel, so it should be detected as soon as it's plugged in, and assigned to device {{ic|/dev/ttyUSB[0-9]}}. | The drivers for the FTDI chip is included in the kernel, so it should be detected as soon as it's plugged in, and assigned to device {{ic|/dev/ttyUSB[0-9]}}. | ||
To check where it got assigned, run: | To check where it got assigned, run: | ||
| − | dmesg | | + | dmesg | grep FTDI |
The output will contain a line that looks something like this: | The output will contain a line that looks something like this: | ||
| Line 25: | Line 25: | ||
===udev=== | ===udev=== | ||
| − | It can be annoying to have to look up what {{ic|/dev/ttyUSB[0-9]}} the device gets assigned, so it's a good idea to add a simple udev rule that creates the | + | It can be annoying to have to look up what {{ic|/dev/ttyUSB[0-9]}} the device gets assigned, so it's a good idea to add a simple udev rule that creates the renames the device when it is plugged in. |
First of all, you will need to find out the serial number of FTDI chip on the bus pirate. This can be achieved by running the following, assuming your device is plugged in and was assigned to {{ic|/dev/ttyUSB0}}: | First of all, you will need to find out the serial number of FTDI chip on the bus pirate. This can be achieved by running the following, assuming your device is plugged in and was assigned to {{ic|/dev/ttyUSB0}}: | ||
| Line 33: | Line 33: | ||
Now add/create the following file: | Now add/create the following file: | ||
| − | {{hc|/etc/udev/rules.d/98- | + | {{hc|/etc/udev/rules.d/98-arduino.rules|2= |
<nowiki> | <nowiki> | ||
| − | SUBSYSTEMS=="usb", ATTRS{serial}==" | + | SUBSYSTEMS=="usb", ATTRS{serial}=="XXXXXXXX", ATTRS{product}=="FT232R USB UART", ATTRS{idProduct}=="6001", ATTRS{idVendor}=="0403", NAME="arduino_1" |
</nowiki>}} | </nowiki>}} | ||
| Line 42: | Line 42: | ||
udevadm control --reload-rules | udevadm control --reload-rules | ||
| − | At this point, whenever you plug in the device, the | + | At this point, whenever you plug in the device, the device should be renamed to {{ic|/dev/ttyUSB0}} |
==Communication== | ==Communication== | ||
| Line 54: | Line 54: | ||
* {{ic|picocom}} | * {{ic|picocom}} | ||
picocom -b 115200 -p n -d 8 /dev/buspirate | picocom -b 115200 -p n -d 8 /dev/buspirate | ||
| − | |||
| − | |||
Revision as of 01:59, 21 October 2012
| Summary |
|---|
| This article covers the installation and basic usage of the Bus Pirate. |
The Bus Pirate is a versatile tool for communicating with various hardware.
Interfacing a new microchip can be a hassle. Breadboarding a circuit, writing code, hauling out the programmer, or maybe even prototyping a PCB. We never seem to get it right on the first try.
The ‘Bus Pirate’ is a universal bus interface that talks to most chips from a PC serial terminal, eliminating a ton of early prototyping effort when working with new or unknown chips. Many serial protocols are supported at 0-5.5volts, more can be added. See more at the google code site for the Bus Pirate.
Installation
The drivers for the FTDI chip is included in the kernel, so it should be detected as soon as it's plugged in, and assigned to device /dev/ttyUSB[0-9].
To check where it got assigned, run:
dmesg | grep FTDI
The output will contain a line that looks something like this:
usb 1-4.4: FTDI USB Serial Device converter now attached to ttyUSB0
udev
It can be annoying to have to look up what /dev/ttyUSB[0-9] the device gets assigned, so it's a good idea to add a simple udev rule that creates the renames the device when it is plugged in.
First of all, you will need to find out the serial number of FTDI chip on the bus pirate. This can be achieved by running the following, assuming your device is plugged in and was assigned to /dev/ttyUSB0:
udevadm info --attribute-walk -n /dev/ttyUSB0
Now add/create the following file:
/etc/udev/rules.d/98-arduino.rules
SUBSYSTEMS=="usb", ATTRS{serial}=="XXXXXXXX", ATTRS{product}=="FT232R USB UART", ATTRS{idProduct}=="6001", ATTRS{idVendor}=="0403", NAME="arduino_1"
Change 'ATTRS{serial}=="XXXXXXXX"' to the serial on your device and force udev to load the new rule:
udevadm control --reload-rules
At this point, whenever you plug in the device, the device should be renamed to /dev/ttyUSB0
Communication
To communicate with the device, you can use any of the following, to name a few:
-
minicom
minicom -b 115200 -8 -D /dev/buspirate
-
screen
screen /dev/buspirate 115200 8N1
-
picocom
picocom -b 115200 -p n -d 8 /dev/buspirate
