I tried running dmesg, and this was the output:

[19273.514811] usb 1-1: USB disconnect, address 4
[20029.640124] usb 2-2: USB disconnect, address 6
[20029.640375] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now
disconnected from ttyUSB0
[20029.640407] ftdi_sio 2-2:1.0: device disconnected
[20029.640593] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now
disconnected from ttyUSB1
[20029.640622] ftdi_sio 2-2:1.1: device disconnected
[20633.028063] usb 2-2: new full speed USB device using uhci_hcd and address
7
[20633.230286] usb 2-2: configuration #1 chosen from 1 choice
[20633.237184] ftdi_sio 2-2:1.0: FTDI USB Serial Device converter detected
[20633.237233] usb 2-2: Detected FT2232C
[20633.237239] usb 2-2: Number of endpoints 2
[20633.237245] usb 2-2: Endpoint 1 MaxPacketSize 64
[20633.237251] usb 2-2: Endpoint 2 MaxPacketSize 64
[20633.237256] usb 2-2: Setting MaxPacketSize 64
[20633.238193] usb 2-2: FTDI USB Serial Device converter now attached to
ttyUSB0
[20633.242187] ftdi_sio 2-2:1.1: FTDI USB Serial Device converter detected
[20633.242233] usb 2-2: Detected FT2232C
[20633.242238] usb 2-2: Number of endpoints 2
[20633.242244] usb 2-2: Endpoint 1 MaxPacketSize 64
[20633.242250] usb 2-2: Endpoint 2 MaxPacketSize 64
[20633.242255] usb 2-2: Setting MaxPacketSize 64
[20633.243185] usb 2-2: FTDI USB Serial Device converter now attached to
ttyUSB1
[22761.856130] usb 2-2: USB disconnect, address 7
[22761.856399] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now
disconnected from ttyUSB0
[22761.856432] ftdi_sio 2-2:1.0: device disconnected
[22761.856636] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now
disconnected from ttyUSB1
[22761.856664] ftdi_sio 2-2:1.1: device disconnected
[22770.162437] UDF-fs: No VRS found
[22770.162444] UDF-fs: No partition found (1)
[22770.214581] ISO 9660 Extensions: Microsoft Joliet Level 3
[22770.244764] ISOFS: changing to secondary root
[31170.780060] usb 2-2: new full speed USB device using uhci_hcd and address
8
[31170.983957] usb 2-2: configuration #1 chosen from 1 choice
[31170.996445] ftdi_sio 2-2:1.0: FTDI USB Serial Device converter detected
[31170.996473] usb 2-2: Detected FT2232C
[31170.996475] usb 2-2: Number of endpoints 2
[31170.996478] usb 2-2: Endpoint 1 MaxPacketSize 64
[31170.996480] usb 2-2: Endpoint 2 MaxPacketSize 64
[31170.996482] usb 2-2: Setting MaxPacketSize 64
[31170.997753] usb 2-2: FTDI USB Serial Device converter now attached to
ttyUSB0
[31171.001840] ftdi_sio 2-2:1.1: FTDI USB Serial Device converter detected
[31171.001865] usb 2-2: Detected FT2232C
[31171.001868] usb 2-2: Number of endpoints 2
[31171.001870] usb 2-2: Endpoint 1 MaxPacketSize 64
[31171.001872] usb 2-2: Endpoint 2 MaxPacketSize 64
[31171.001874] usb 2-2: Setting MaxPacketSize 64
[31171.002881] usb 2-2: FTDI USB Serial Device converter now attached to
ttyUSB1

I didn't the see error message about 'brltty' and still 'no devices found'
when I type motelist.
I am running in Ubuntu 9.10 and using tinyos 2.1.0.

On Thu, Feb 25, 2010 at 12:08 AM, Giuseppe Cardone <
[email protected]> wrote:

> Hi,
>
> after plugging in your mote try running dmesg; you should expect an
> output like this:
>
> [ 9212.660180] usb 2-1.1: new full speed USB device using ehci_hcd and
> address 4
> [ 9212.777209] usb 2-1.1: configuration #1 chosen from 1 choice
> [ 9212.838695] usbcore: registered new interface driver usbserial
> [ 9212.838709] USB Serial support registered for generic
> [ 9212.838733] usbcore: registered new interface driver usbserial_generic
> [ 9212.838736] usbserial: USB Serial Driver core
> [ 9212.846601] USB Serial support registered for FTDI USB Serial Device
> [ 9212.846663] ftdi_sio 2-1.1:1.0: FTDI USB Serial Device converter
> detected
> [ 9212.846685] usb 2-1.1: Detected FT232BM
> [ 9212.846688] usb 2-1.1: Number of endpoints 2
> [ 9212.846690] usb 2-1.1: Endpoint 1 MaxPacketSize 64
> [ 9212.846692] usb 2-1.1: Endpoint 2 MaxPacketSize 64
> [ 9212.846694] usb 2-1.1: Setting MaxPacketSize 64
> [ 9212.847085] usb 2-1.1: FTDI USB Serial Device converter now
> attached to ttyUSB0
> [ 9212.847105] usbcore: registered new interface driver ftdi_sio
> [ 9212.847108] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver
>
> as you can see the kernel reports the name of the USB device. It
> happended to me that after these log entries there was a message
> saying that brltty disconnected the USB device (it is a known bug of
> brltty, see for example
> https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/90172 ) If it is
> your case consider removing brltty.
>
> Hope this helps.
>
> --
> Giuseppe Cardone
>
>
>
> On Wed, Feb 24, 2010 at 3:38 PM, Mark Patrick Cabrera
> <[email protected]> wrote:
> > This is what I got:
> >
> > /opt/tinyos-2.1.0/apps/tests/TestSerial$ motelist
> > No devices found.
> >
> >
> > On Wed, Feb 24, 2010 at 10:35 PM, Lim Jong Chern <
> [email protected]>
> > wrote:
> >>
> >> Hi,
> >>
> >> You probably specified the wrong usb port.
> >>
> >> Type motelist in ur console. it should return something like this
> >>
> >> Reference  Device           Description
> >> ---------- ----------------
> ---------------------------------------------
> >> XBR0LCDZ   /dev/ttyUSB0     XBOW Crossbow Telos Rev.B
> >> XBR0LF7Y   /dev/ttyUSB1     XBOW Crossbow Telos Rev.B
> >>
> >> use the appropriate usb port:
> >>
> >> java TestSerial -comm serial@/dev/ttyUSB0:micaz
> >>
> >> hope this helps.
> >>
> >> cheers,
> >> Jong Chern
> >>
> >>
> >>
> >> ________________________________
> >> Date: Wed, 24 Feb 2010 22:20:50 +0800
> >> From: [email protected]
> >> To: [email protected]
> >> Subject: [Tinyos-help] Serial Communication Test Problem
> >>
> >> I have a prototype board based on the micaz mote using Atmega128L and
> >> CC2420 running on tinyos-2.1.0. I am testing the board using the
> tutorials
> >> available, but when I got to Lesson 4: Mote-PC serial communication and
> >> tried java TestSerial I got the following errors:
> >>
> >> opt/tinyos-2.1.0/apps/tests/TestSerial$ java TestSerial
> >> serial@/dev/ttyUSB1:57600 died - exiting (java.io.IOException: Could
> not
> >> open /dev/ttyUSB1: TOSComm JNI library runtime error: open: No such file
> or
> >> directory)
> >>
> >> Can anyone help me with my problem?
> >>
> >> -----
> >> Mark Patrick Cabrera
> >> Instrumentation, Robotics and Control Laboratory
> >> University of the Philippines Diliman
> >>
> >> ________________________________
> >> Hotmail: Trusted email with powerful SPAM protection. Sign up now.
> >
> >
> > --
> > "There is always a time for everything."
> >
> > Mark Patrick B. Cabrera
> > engineering student
> >
> > _______________________________________________
> > Tinyos-help mailing list
> > [email protected]
> > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >
>



-- 
"There is always a time for everything."

Mark Patrick B. Cabrera
engineering student
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to