[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] Paparazzi File Download

From: Reegan M
Subject: Re: [Paparazzi-devel] Paparazzi File Download
Date: Sat, 8 May 2010 20:51:08 -0500

I think that the problem might be in the undev rule. 

When I follow the process for compiling and flashing the board from the wiki this is what I receive:

address@hidden:~$ sudo cp $PAPARAZZI_HOME/conf/system/udev/rules/10-paparazzi.rules /etc/udev/rules.d/
[sudo] password for reegan:
cp: cannot stat `/conf/system/udev/rules/10-paparazzi.rules': No such file or directory

Here is the location of the file, and the file text itself:

BUS=="usb", SYSFS{serial}=="*_fbw", NAME="test_fbw", SYMLINK="paparazzi/%s{serial}", MODE="0666"

MaxStream xbee pro box
BUS=="usb", SYSFS{product}=="MaxStream PKG-U", KERNEL=="ttyUSB*", SYMLINK+="paparazzi/xbee", GROUP="plugdev"

bare FTDI chip without EEPROM
BUS=="usb", SYSFS{idVendor}=="0403", SYSFS{idProduct}=="6001", KERNEL=="ttyUSB*", SYMLINK+="paparazzi/serial", GROUP="plugdev"

 all (fake VID 0x7070) LPCUSB devices (access through libusb)
BUS=="usb", SYSFS{idVendor}=="7070", GROUP="plugdev"

FTDI 2232 parallel converter / Amontec JTAG-Tiny (access through libftdi)
BUS=="usb",  SYSFS{idVendor}=="0403", SYSFS{idProduct}=="cff8", GROUP="plugdev"

 make joysticks/gamepads readable on event interface (writeable for force feedback), see
KERNEL=="event*", IMPORT{program}=" %p", NAME="input/%k", GROUP="plugdev", MODE="0640"
ENV{FF_DEVICE}=="1", MODE="0660"


On Sat, May 8, 2010 at 8:45 PM, antoine drouin <address@hidden> wrote:
you could "tail -f /var/log/syslog" when you plug the tiny and see if
the usb device gets detected ( should be called lpcusb )
the command "lsusb", after the tiny has been connected should also
display the lpcusb device
if the usb device is really there, you problem could then be be a
permission issue.
There's a udev rule contained in the file



reply via email to

[Prev in Thread] Current Thread [Next in Thread]