Re: [Tinyos-help] Problem with serial communication using telosa

[Urs Hunkeler]

Hi Luís,

These are interesting findings. I don't think it is a problem related to 
Java as a language. It appears to me that the microcontroller is reset 
as soon as the serial port is opened. Maybe the Java programs that you 
have tried set some handshaking lines that cause a reset.

If you look at the schematics:
http://www.tinyos.net/scoop/special/hardware

You can see (on the last page) that the reset handling differs between 
TelosA and TelosB. If I understand this correctly, a certain combination 
of RTS and DTR causes a reset on the TelosA, while on the TelosB one 
needs to send a special sequence RTS and DTR (and possibly other 
handshaking signals).

Cheers,
Urs


On 10/26/11 11:27 PM, Luís Pereira wrote:
> Hi guys,
>
> Following that tip Bíró gave, i found a little program that uses rxtx to
> find and open the usb port. When I run the program it find the door and
> my mote stop blink again. I'm starting to think that the problem is with
> java and usb ports.
>
> I have a little program in C that reads data from a serial port. When I
> try to read from the mote it works and I have the following output:
>
> Transmission 1:
> 0x0 0x63 0x6F 0x75 0x6E 0x74 0x3D 0x30 0x30 0x31 0x65 0x2C 0x20 0x6C
> 0x65 0x64 0x3D 0x30 0x30 0x30
>
> count=001e, led=000
>
> Transmission 2:
> 0x36 0xD 0xA 0x63 0x6F 0x75 0x6E 0x74 0x3D 0x30 0x30 0x31 0x66 0x2C
> 0x20 0x6C 0x65 0x64 0x3D 0x30
>
> 6
> count=001f, led=0
>
> Transmission 3:
> 0x30 0x30 0x37 0xD 0xA 0x63 0x6F 0x75 0x6E 0x74 0x3D 0x30 0x30 0x32
> 0x30 0x2C 0x20 0x6C 0x65 0x64
>
> 007
> count=0020, led
>
> Transmission 4:
> 0x3D 0x30 0x30 0x0 0x30 0x30 0xD 0xA 0x63 0x6F 0x75 0x6E 0x74 0x3D
> 0x30 0x30 0x32 0x31 0x2C 0x20
>
> =
> count=0021,
>
>
> I'm not synchronizing, only reading data. The first line after
> "Transmission X:" is the hexadecimal code i read, and the second is
> converted to text, and as you can see I'm receiving what I'm suppose to,
> so it's something related to java programs right?
>
>
> Luís Pereira
>
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Problem with serial communication using telosa

[Luís Pereira]

Hi guys,

Following that tip Bíró gave, i found a little program that uses rxtx to
find and open the usb port. When I run the program it find the door and my
mote stop blink again. I'm starting to think that the problem is with java
and usb ports.

I have a little program in C that reads data from a serial port. When I try
to read from the mote it works and I have the following output:

Transmission 1:
0x0 0x63 0x6F 0x75 0x6E 0x74 0x3D 0x30 0x30 0x31 0x65 0x2C 0x20 0x6C 0x65
0x64 0x3D 0x30 0x30 0x30

count=001e, led=000

Transmission 2:
0x36 0xD 0xA 0x63 0x6F 0x75 0x6E 0x74 0x3D 0x30 0x30 0x31 0x66 0x2C 0x20
0x6C 0x65 0x64 0x3D 0x30

6
count=001f, led=0

Transmission 3:
0x30 0x30 0x37 0xD 0xA 0x63 0x6F 0x75 0x6E 0x74 0x3D 0x30 0x30 0x32 0x30
0x2C 0x20 0x6C 0x65 0x64

007
count=0020, led

Transmission 4:
0x3D 0x30 0x30 0x0 0x30 0x30 0xD 0xA 0x63 0x6F 0x75 0x6E 0x74 0x3D 0x30 0x30
0x32 0x31 0x2C 0x20

=
count=0021,


I'm not synchronizing, only reading data. The first line after "Transmission
X:" is the hexadecimal code i read, and the second is converted to text, and
as you can see I'm receiving what I'm suppose to, so it's something related
to java programs right?


Luís Pereira
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Problem with serial communication using telosa

[Bíró András]

Sorry, those codes are lost, but it's easy to simplify an rxtx
example. Acutally, you only need to list the available serial ports,
since it tries to open them. And again: it only worked on windows.

Andris

2011/10/26 Luís Pereira :
> Hi Bíró,
> Ok I will try to open the usb port with rxtx to see what happen..can you
> send me what program you use to do that?
> Thanks for your help
> Luís Pereira
>
>
> 2011/10/26 Bíró András 
>>
>> Hi Luis,
>>
>> I had similar problems with telosa motes, and I don't know what caused
>> the problem, or how to resolve it, but I found a workaround.
>> Unofrtunatly it only worked on windows (xp)+cygwin:
>> Before opening the serial port with the tinyos java apps, I opened it
>> with rxtx (http://users.frii.com/jarvi/rxtx/). After that, everything
>> worked as it should.
>> I used telosb, micaz/mib520a and iris/mib520b motes on that machine
>> without a problem, both on linux and windows.
>>
>> Andris
>>
>> 2011/10/26 Luís Pereira :
>> > Hi Urs,
>> > I am already using the telos platform. I post a command with tmote
>> > because I
>> > read in some other question to try that way, and it doesn't make any
>> > difference. I am trying to communicate with the mote using the
>> > apps/tests/TestLed/Multiled program and I got this outputs:
>> > MAKE TELOS:
>> >
>> > mkdir -p build/telosa
>> >     compiling TestAppC to a telosa binary
>> > ncc -o build/telosa/main.exe  -Os -O
>> > -I/home/luis/documents/tinyos-main-read-only//tos/lib/printf
>> > -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosa
>> > -fnesc-cfile=build/telosa/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22
>> > -DIDENT_APPNAME=\"TestAppC\" -DIDENT_USERNAME=\"luis\"
>> > -DIDENT_HOSTNAME=\"luis-eee\" -DIDENT_USERHASH=0x26cd4331L
>> > -DIDENT_TIMESTAMP=0x4ea848c1L -DIDENT_UIDHASH=0x63dafe9eL  TestAppC.nc
>> > -lm
>> >     compiled TestAppC to build/telosa/main.exe
>> >             4994 bytes in ROM
>> >               77 bytes in RAM
>> > msp430-objcopy --output-target=ihex build/telosa/main.exe
>> > build/telosa/main.ihex
>> >     writing TOS image
>> >
>> > MAKE TELOS INSTALL:
>> >
>> > mkdir -p build/telosa
>> >     compiling TestAppC to a telosa binary
>> > ncc -o build/telosa/main.exe  -Os -O
>> > -I/home/luis/documents/tinyos-main-read-only//tos/lib/printf
>> > -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosa
>> > -fnesc-cfile=build/telosa/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22
>> > -DIDENT_APPNAME=\"TestAppC\" -DIDENT_USERNAME=\"luis\"
>> > -DIDENT_HOSTNAME=\"luis-eee\" -DIDENT_USERHASH=0x26cd4331L
>> > -DIDENT_TIMESTAMP=0x4ea84969L -DIDENT_UIDHASH=0x59c6b937L  TestAppC.nc
>> > -lm
>> >     compiled TestAppC to build/telosa/main.exe
>> >             4994 bytes in ROM
>> >               77 bytes in RAM
>> > msp430-objcopy --output-target=ihex build/telosa/main.exe
>> > build/telosa/main.ihex
>> >     writing TOS image
>> > cp build/telosa/main.ihex build/telosa/main.ihex.out
>> >     found mote on /dev/ttyUSB0 (using bsl,auto)
>> >     installing telosa binary using bsl
>> > tos-bsl --telos -c /dev/ttyUSB0 -r -e -I -p build/telosa/main.ihex.out
>> > rm -f build/telosa/main.exe.out build/telosa/main.ihex.out
>> > MSP430 Bootstrap Loader Version: 1.39-telos-8
>> > Mass Erase...
>> > Transmit default password ...
>> > Invoking BSL...
>> > Transmit default password ...
>> > Current bootstrap loader version: 1.10 (Device ID: f149)
>> > Adjust SP. Load PC with 0x0C22 ...
>> > Transmit default password ...
>> > Patch for flash programming required!
>> > Load and verify patch ...
>> > Program ...
>> > 5220 bytes programmed.
>> > Reset device ...
>> >
>> > MOTELIST:
>> >
>> > Reference  Device           Description
>> > -- 
>> > -
>> > M4MWCK4F   /dev/ttyUSB0     Moteiv Telos (Rev A 2004-04-27)
>> >
>> > java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB0:telos
>> >
>> > serial@/dev/ttyUSB0:115200: resynchronising
>> >
>> > I already put my ttyUSB0 in chmod 666, and I also tried reset the device
>> > and
>> > plug off and plug in the device while in resynchronising like some
>> > people
>> > advice in other posts and nothing work so far.
>> > Thanks for all the help so far. Hope I can get a solution for this
>> > Luís Pereira
>> >
>> >
>> > 2011/10/26 Urs Hunkeler 
>> >>
>> >> Hi Luís,
>> >>
>> >> I just had a look. It appears that telosa, telosb and tmote all use the
>> >> same baud rate, and that the platform name for telosa on TinyOS is just
>> >> "telos" (not tmote).
>> >>
>> >> TelosA and TelosB/Tmote are similar, but not identical. It is entirely
>> >> possible that if you compile your programs for the platform "tmote"
>> >> they
>> >> will install on the TelosA and maybe even blink the LEDs, but that
>> >> other
>> >> things (like serial communication) will not work. When you compile the
>> >> test
>> >> programs, did you do a "make telos" (and not "make tmote")? (and
>> >> similarly
>> >> "make telos install")
>> >>
>> >> If i

Re: [Tinyos-help] Problem with serial communication using telosa

[Luís Pereira]

Hi Bíró,

Ok I will try to open the usb port with rxtx to see what happen..can you
send me what program you use to do that?

Thanks for your help
Luís Pereira


2011/10/26 Bíró András 

> Hi Luis,
>
> I had similar problems with telosa motes, and I don't know what caused
> the problem, or how to resolve it, but I found a workaround.
> Unofrtunatly it only worked on windows (xp)+cygwin:
> Before opening the serial port with the tinyos java apps, I opened it
> with rxtx (http://users.frii.com/jarvi/rxtx/). After that, everything
> worked as it should.
> I used telosb, micaz/mib520a and iris/mib520b motes on that machine
> without a problem, both on linux and windows.
>
> Andris
>
> 2011/10/26 Luís Pereira :
> > Hi Urs,
> > I am already using the telos platform. I post a command with tmote
> because I
> > read in some other question to try that way, and it doesn't make any
> > difference. I am trying to communicate with the mote using the
> > apps/tests/TestLed/Multiled program and I got this outputs:
> > MAKE TELOS:
> >
> > mkdir -p build/telosa
> > compiling TestAppC to a telosa binary
> > ncc -o build/telosa/main.exe  -Os -O
> > -I/home/luis/documents/tinyos-main-read-only//tos/lib/printf
> > -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosa
> > -fnesc-cfile=build/telosa/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22
> > -DIDENT_APPNAME=\"TestAppC\" -DIDENT_USERNAME=\"luis\"
> > -DIDENT_HOSTNAME=\"luis-eee\" -DIDENT_USERHASH=0x26cd4331L
> > -DIDENT_TIMESTAMP=0x4ea848c1L -DIDENT_UIDHASH=0x63dafe9eL  TestAppC.nc
> -lm
> > compiled TestAppC to build/telosa/main.exe
> > 4994 bytes in ROM
> >   77 bytes in RAM
> > msp430-objcopy --output-target=ihex build/telosa/main.exe
> > build/telosa/main.ihex
> > writing TOS image
> >
> > MAKE TELOS INSTALL:
> >
> > mkdir -p build/telosa
> > compiling TestAppC to a telosa binary
> > ncc -o build/telosa/main.exe  -Os -O
> > -I/home/luis/documents/tinyos-main-read-only//tos/lib/printf
> > -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosa
> > -fnesc-cfile=build/telosa/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22
> > -DIDENT_APPNAME=\"TestAppC\" -DIDENT_USERNAME=\"luis\"
> > -DIDENT_HOSTNAME=\"luis-eee\" -DIDENT_USERHASH=0x26cd4331L
> > -DIDENT_TIMESTAMP=0x4ea84969L -DIDENT_UIDHASH=0x59c6b937L  TestAppC.nc
> -lm
> > compiled TestAppC to build/telosa/main.exe
> > 4994 bytes in ROM
> >   77 bytes in RAM
> > msp430-objcopy --output-target=ihex build/telosa/main.exe
> > build/telosa/main.ihex
> > writing TOS image
> > cp build/telosa/main.ihex build/telosa/main.ihex.out
> > found mote on /dev/ttyUSB0 (using bsl,auto)
> > installing telosa binary using bsl
> > tos-bsl --telos -c /dev/ttyUSB0 -r -e -I -p build/telosa/main.ihex.out
> > rm -f build/telosa/main.exe.out build/telosa/main.ihex.out
> > MSP430 Bootstrap Loader Version: 1.39-telos-8
> > Mass Erase...
> > Transmit default password ...
> > Invoking BSL...
> > Transmit default password ...
> > Current bootstrap loader version: 1.10 (Device ID: f149)
> > Adjust SP. Load PC with 0x0C22 ...
> > Transmit default password ...
> > Patch for flash programming required!
> > Load and verify patch ...
> > Program ...
> > 5220 bytes programmed.
> > Reset device ...
> >
> > MOTELIST:
> >
> > Reference  Device   Description
> > --  -
> > M4MWCK4F   /dev/ttyUSB0 Moteiv Telos (Rev A 2004-04-27)
> >
> > java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB0:telos
> >
> > serial@/dev/ttyUSB0:115200: resynchronising
> >
> > I already put my ttyUSB0 in chmod 666, and I also tried reset the device
> and
> > plug off and plug in the device while in resynchronising like some people
> > advice in other posts and nothing work so far.
> > Thanks for all the help so far. Hope I can get a solution for this
> > Luís Pereira
> >
> >
> > 2011/10/26 Urs Hunkeler 
> >>
> >> Hi Luís,
> >>
> >> I just had a look. It appears that telosa, telosb and tmote all use the
> >> same baud rate, and that the platform name for telosa on TinyOS is just
> >> "telos" (not tmote).
> >>
> >> TelosA and TelosB/Tmote are similar, but not identical. It is entirely
> >> possible that if you compile your programs for the platform "tmote" they
> >> will install on the TelosA and maybe even blink the LEDs, but that other
> >> things (like serial communication) will not work. When you compile the
> test
> >> programs, did you do a "make telos" (and not "make tmote")? (and
> similarly
> >> "make telos install")
> >>
> >> If it still doesn't work, could you send us the exact commands that you
> >> use (make, make install, java ...Listen...) and the output that you get
> for
> >> each of the commands (e.g., copy/past the text from your terminal)?
> >>
> >> Cheers,
> >> Urs
> >>
> >>
> >> On 10/25/11 11:48 PM, Luís Pereira wrote:
> >>>
> >>> Hi Rafael,
> >>>
> >>> well when I run motelist i have:
> >>>
> >>> Referenc

Re: [Tinyos-help] Problem with serial communication using telosa

[Bíró András]

Hi Luis,

I had similar problems with telosa motes, and I don't know what caused
the problem, or how to resolve it, but I found a workaround.
Unofrtunatly it only worked on windows (xp)+cygwin:
Before opening the serial port with the tinyos java apps, I opened it
with rxtx (http://users.frii.com/jarvi/rxtx/). After that, everything
worked as it should.
I used telosb, micaz/mib520a and iris/mib520b motes on that machine
without a problem, both on linux and windows.

Andris

2011/10/26 Luís Pereira :
> Hi Urs,
> I am already using the telos platform. I post a command with tmote because I
> read in some other question to try that way, and it doesn't make any
> difference. I am trying to communicate with the mote using the
> apps/tests/TestLed/Multiled program and I got this outputs:
> MAKE TELOS:
>
> mkdir -p build/telosa
>     compiling TestAppC to a telosa binary
> ncc -o build/telosa/main.exe  -Os -O
> -I/home/luis/documents/tinyos-main-read-only//tos/lib/printf
> -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosa
> -fnesc-cfile=build/telosa/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22
> -DIDENT_APPNAME=\"TestAppC\" -DIDENT_USERNAME=\"luis\"
> -DIDENT_HOSTNAME=\"luis-eee\" -DIDENT_USERHASH=0x26cd4331L
> -DIDENT_TIMESTAMP=0x4ea848c1L -DIDENT_UIDHASH=0x63dafe9eL  TestAppC.nc -lm
>     compiled TestAppC to build/telosa/main.exe
>             4994 bytes in ROM
>               77 bytes in RAM
> msp430-objcopy --output-target=ihex build/telosa/main.exe
> build/telosa/main.ihex
>     writing TOS image
>
> MAKE TELOS INSTALL:
>
> mkdir -p build/telosa
>     compiling TestAppC to a telosa binary
> ncc -o build/telosa/main.exe  -Os -O
> -I/home/luis/documents/tinyos-main-read-only//tos/lib/printf
> -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosa
> -fnesc-cfile=build/telosa/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22
> -DIDENT_APPNAME=\"TestAppC\" -DIDENT_USERNAME=\"luis\"
> -DIDENT_HOSTNAME=\"luis-eee\" -DIDENT_USERHASH=0x26cd4331L
> -DIDENT_TIMESTAMP=0x4ea84969L -DIDENT_UIDHASH=0x59c6b937L  TestAppC.nc -lm
>     compiled TestAppC to build/telosa/main.exe
>             4994 bytes in ROM
>               77 bytes in RAM
> msp430-objcopy --output-target=ihex build/telosa/main.exe
> build/telosa/main.ihex
>     writing TOS image
> cp build/telosa/main.ihex build/telosa/main.ihex.out
>     found mote on /dev/ttyUSB0 (using bsl,auto)
>     installing telosa binary using bsl
> tos-bsl --telos -c /dev/ttyUSB0 -r -e -I -p build/telosa/main.ihex.out
> rm -f build/telosa/main.exe.out build/telosa/main.ihex.out
> MSP430 Bootstrap Loader Version: 1.39-telos-8
> Mass Erase...
> Transmit default password ...
> Invoking BSL...
> Transmit default password ...
> Current bootstrap loader version: 1.10 (Device ID: f149)
> Adjust SP. Load PC with 0x0C22 ...
> Transmit default password ...
> Patch for flash programming required!
> Load and verify patch ...
> Program ...
> 5220 bytes programmed.
> Reset device ...
>
> MOTELIST:
>
> Reference  Device           Description
> --  -
> M4MWCK4F   /dev/ttyUSB0     Moteiv Telos (Rev A 2004-04-27)
>
> java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB0:telos
>
> serial@/dev/ttyUSB0:115200: resynchronising
>
> I already put my ttyUSB0 in chmod 666, and I also tried reset the device and
> plug off and plug in the device while in resynchronising like some people
> advice in other posts and nothing work so far.
> Thanks for all the help so far. Hope I can get a solution for this
> Luís Pereira
>
>
> 2011/10/26 Urs Hunkeler 
>>
>> Hi Luís,
>>
>> I just had a look. It appears that telosa, telosb and tmote all use the
>> same baud rate, and that the platform name for telosa on TinyOS is just
>> "telos" (not tmote).
>>
>> TelosA and TelosB/Tmote are similar, but not identical. It is entirely
>> possible that if you compile your programs for the platform "tmote" they
>> will install on the TelosA and maybe even blink the LEDs, but that other
>> things (like serial communication) will not work. When you compile the test
>> programs, did you do a "make telos" (and not "make tmote")? (and similarly
>> "make telos install")
>>
>> If it still doesn't work, could you send us the exact commands that you
>> use (make, make install, java ...Listen...) and the output that you get for
>> each of the commands (e.g., copy/past the text from your terminal)?
>>
>> Cheers,
>> Urs
>>
>>
>> On 10/25/11 11:48 PM, Luís Pereira wrote:
>>>
>>> Hi Rafael,
>>>
>>> well when I run motelist i have:
>>>
>>> Reference Device Description
>>> --  -
>>> M4MWCK4F /dev/ttyUSB0 Moteiv Telos (Rev A 2004-04-27)
>>>
>>> Then i run:
>>>
>>> java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB0:tmote
>>>
>>> and i got:
>>>
>>> serial@/dev/ttyUSB0:115200: resynchronising
>>>
>>> and the leds of the mote stop blinking.
>>>
>>> Luís Pereira
>>>
>>>
>>> 2011/10/25 Rafael de Oliveira Costa >> 

Re: [Tinyos-help] Problem with serial communication using telosa

[Luís Pereira]

Hi Urs,

I am already using the telos platform. I post a command with tmote because I
read in some other question to try that way, and it doesn't make any
difference. I am trying to communicate with the mote using the
apps/tests/TestLed/Multiled program and I got this outputs:

MAKE TELOS:


mkdir -p build/telosa
compiling TestAppC to a telosa binary
ncc -o build/telosa/main.exe  -Os -O
-I/home/luis/documents/tinyos-main-read-only//tos/lib/printf
-fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosa
-fnesc-cfile=build/telosa/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22
-DIDENT_APPNAME=\"TestAppC\" -DIDENT_USERNAME=\"luis\"
-DIDENT_HOSTNAME=\"luis-eee\" -DIDENT_USERHASH=0x26cd4331L
-DIDENT_TIMESTAMP=0x4ea848c1L -DIDENT_UIDHASH=0x63dafe9eL  TestAppC.nc -lm
compiled TestAppC to build/telosa/main.exe
4994 bytes in ROM
  77 bytes in RAM
msp430-objcopy --output-target=ihex build/telosa/main.exe
build/telosa/main.ihex
writing TOS image


MAKE TELOS INSTALL:


mkdir -p build/telosa
compiling TestAppC to a telosa binary
ncc -o build/telosa/main.exe  -Os -O
-I/home/luis/documents/tinyos-main-read-only//tos/lib/printf
-fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosa
-fnesc-cfile=build/telosa/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22
-DIDENT_APPNAME=\"TestAppC\" -DIDENT_USERNAME=\"luis\"
-DIDENT_HOSTNAME=\"luis-eee\" -DIDENT_USERHASH=0x26cd4331L
-DIDENT_TIMESTAMP=0x4ea84969L -DIDENT_UIDHASH=0x59c6b937L  TestAppC.nc -lm
compiled TestAppC to build/telosa/main.exe
4994 bytes in ROM
  77 bytes in RAM
msp430-objcopy --output-target=ihex build/telosa/main.exe
build/telosa/main.ihex
writing TOS image
cp build/telosa/main.ihex build/telosa/main.ihex.out
found mote on /dev/ttyUSB0 (using bsl,auto)
installing telosa binary using bsl
tos-bsl --telos -c /dev/ttyUSB0 -r -e -I -p build/telosa/main.ihex.out
rm -f build/telosa/main.exe.out build/telosa/main.ihex.out
MSP430 Bootstrap Loader Version: 1.39-telos-8
Mass Erase...
Transmit default password ...
Invoking BSL...
Transmit default password ...
Current bootstrap loader version: 1.10 (Device ID: f149)
Adjust SP. Load PC with 0x0C22 ...
Transmit default password ...
Patch for flash programming required!
Load and verify patch ...
Program ...
5220 bytes programmed.
Reset device ...

MOTELIST:

Reference  Device   Description
--  -
M4MWCK4F   /dev/ttyUSB0 Moteiv Telos (Rev A 2004-04-27)

java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB0:telos

serial@/dev/ttyUSB0:115200: resynchronising


I already put my ttyUSB0 in chmod 666, and I also tried reset the device and
plug off and plug in the device while in resynchronising like some people
advice in other posts and nothing work so far.

Thanks for all the help so far. Hope I can get a solution for this
Luís Pereira


2011/10/26 Urs Hunkeler 

> Hi Luís,
>
> I just had a look. It appears that telosa, telosb and tmote all use the
> same baud rate, and that the platform name for telosa on TinyOS is just
> "telos" (not tmote).
>
> TelosA and TelosB/Tmote are similar, but not identical. It is entirely
> possible that if you compile your programs for the platform "tmote" they
> will install on the TelosA and maybe even blink the LEDs, but that other
> things (like serial communication) will not work. When you compile the test
> programs, did you do a "make telos" (and not "make tmote")? (and similarly
> "make telos install")
>
> If it still doesn't work, could you send us the exact commands that you use
> (make, make install, java ...Listen...) and the output that you get for each
> of the commands (e.g., copy/past the text from your terminal)?
>
>
> Cheers,
> Urs
>
>
> On 10/25/11 11:48 PM, Luís Pereira wrote:
>
>> Hi Rafael,
>>
>> well when I run motelist i have:
>>
>> Reference Device Description
>> --  --**
>> ---
>> M4MWCK4F /dev/ttyUSB0 Moteiv Telos (Rev A 2004-04-27)
>>
>> Then i run:
>>
>> java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB0:tmote
>>
>> and i got:
>>
>> serial@/dev/ttyUSB0:115200: resynchronising
>>
>> and the leds of the mote stop blinking.
>>
>> Luís Pereira
>>
>>
>> 2011/10/25 Rafael de Oliveira Costa 
>> 
>> > >>
>>
>>
>>Hi Luís,
>>
>>please show what command did you executed.
>>
>>Rafael de Oliveira Costa,M.Sc. Student
>>
>>PPGI - UFRJ
>>Rio de Janeiro, RJ, Brazil
>>http://www.labnet.nce.ufrj.br 
>> 
>> >
>>
>>"The first step to getting the things you want out of life is this :
>>decide what you want", Ben Stein
>>
>>
>>
>>2011/10/24 Luís Pereira >>
>>
>>
>>Hi All,
>>
>>I'm starting a project at my school using telosa. I'm trying to
>>do the tutorial and i got stuck

[Tinyos-help] Re : Urgent! How to generate PWM signal to excite a sensor on IRIS ?

[hafid bbbbbbbbb]

Hi,
Thanks for your valuable reply, I read the chapters that suggested to me and i 
understand now how to use PRR1, OCR3A,TCCR3B. One problem left is how to count 
N pulses and then stop Timer 3 by disabling the correspondent bit in PRR1?. I 
do not know if this is doable but if the correspondent Output compare match 
interrupt is enabled , and its interrupt routine can be changed  somehow to 
count N pulses, maybe, it would solve this. Frankly, i don`t know how to do 
this! Any idea?
Best Regards !
Massinissa


De : antonio rosa 
À : hafid b 
Envoyé le : Mercredi 26 Octobre 2011 15h10
Objet : Re: [Tinyos-help] Urgent! How to generate PWM signal to excite a sensor 
on IRIS ?


Hi, 

I have worked with PWM in atmega 1281 and TinyOS-1.1.15. I use the Timer3 
(Timer2 (reserved by  radio) and Timer1 is used by TinyOS) and the following 
registers:
PRR1
OCR3A
TCCR3B


Also you should read the datsheet: chapter: 16. 8-bit Timer/Counter0 with PWM 
and the chapter 17.



2011/10/26 hafid b 

Hi everybody,
>I want to excite a sound transmitter  with a train of N pulses at about 17.5 - 
>20KHZ. So, I made a basic sensorboard as described here 
>http://www.etantdonnes.com/Motes/MicaBOB/  to get all the 51 pins connector 
>pins and after consulting the atmega1281 datasheet i noticed that manipulating 
>the timer/ counter registers is the only way to generate such a signal 
>(PWM). Therefore, I have a couple of questions:
>Which timer is most suitable in my case without interfering with the Radio  
>and TimerMillic and other components using timers?
>Is there any interfaces to manipulate safely these registers in tinyos 2.1? 
>any similar example, or code snippet  ? 
>Please shareyour experience with me.
>Thanks in advance for your help.
>Massinissa
>___
>Tinyos-help mailing list
>Tinyos-help@millennium.berkeley.edu
>https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Minimun Voltage IRIS

[Correo de Wacka]

Hi everyone,

I would like to monitor the batteries of some IRIS nodes and as far as I know 
the minimun power voltage they need is 2V. Is it correct? It would be helpful 
to know the minimun voltage they need to operate, just to send an alarm wether 
I detect  that critical level and replace the bateries. 

Thanks in advance


  ___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Different compilers within the same TinyOS-2.1

[Bíró András]

You can install the packages with "rpm -ivh --ignoreos --force", this
will overwrite the conflicting files.

Andris

On Wed, Oct 26, 2011 at 12:24 PM, David Rodenas Herráiz
 wrote:
> Thanks Eric. I had some problems installing the xscale compiler (for
> Imote2):
> rpm -ivh --ignoreos xscale-elf-gcc-3.4.3-1.cygwin.i386.rpm
> Preparing... ### [100%]
> file /usr/man/man7/fsf-funding.7 from install of xscale-elf-gcc-3.4.3-1
> conflicts with file from package avr-gcc-4.1.2-1
> file /usr/man/man7/gfdl.7 from install of xscale-elf-gcc-3.4.3-1 conflicts
> with file from package avr-gcc-4.1.2-1
> and more...
> I suppose that I'll have to install it manually. Therefore, I don't know
> when but I'll tell you if it finally works.
> David Rodenas Herráiz
>
> 
> Date: Wed, 26 Oct 2011 03:10:34 -0700
> Subject: Re: [Tinyos-help] Different compilers within the same TinyOS-2.1
> From: cire...@gmail.com
> To: drod...@hotmail.com
> CC: tinyos-help@millennium.berkeley.edu
>
> take a look a different .platform files
> A pattern will become apparent.
> You'll see things like...
> -gcc=msp430-gcc
> -mmcu=msp430x1611
> -fnesc-target=msp430
> and like
> -gcc=avr-gcc
> -mmcu=atmega128
> -fnesc-target=avr
>
> I don't know of any documentation for these things.   I mostly fly by the
> seat of my pants when it comes to what these switches do.
>
>
> On Wed, Oct 26, 2011 at 12:44 AM, David Rodenas Herráiz
>  wrote:
>
> Hi Eric
> thanks for your answer. Would you mind giving me some brief instructions to
> do those switches?
> David
>
> 
> Date: Tue, 25 Oct 2011 16:14:58 -0700
> Subject: Re: [Tinyos-help] Different compilers within the same TinyOS-2.1
> From: cire...@gmail.com
> To: drod...@hotmail.com
> CC: tinyos-help@millennium.berkeley.edu
>
>
>
> On Tue, Oct 25, 2011 at 11:25 AM, David Rodenas Herráiz
>  wrote:
>
> Hi everyone
> I am working with Imote2 and MicaZ motes and I want to ask if PXA27x
> (compiler for Imote2) Atmel AVR tools (compiler or MicaZ) might work within
> the same TinyOS-2.1 installation.
>
> Sure.   The toolchain invoked is determined by switches in the .platform
> file for the platform being compiled.
> So it should work fine.
>
>
> Thanks in advance
> David
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
>
>
> --
> Eric B. Decker
> Senior (over 50 :-) Researcher
>
>
>
>
>
> --
> Eric B. Decker
> Senior (over 50 :-) Researcher
>
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Problem: TimeSyncPacket and TimeSyncAMSend interfaces

[Amin Amin]

Hi all,

I used TimeSyncPacket and TimeSyncAMSend interfaces in my module, and
wiring in configuration with TimeSyncMessageC component like this:

MyConfigurationC.SendPairSyncMsg -> TimeSyncMessageC.TimeSyncAMSendMilli[id];
//id=138 in my header file

pbsC.TimeSyncPacket ->  TimeSyncMessageC;

When i uses make micaz, there is no problem.
But by make micaz sim, the errors are the following:

--
In file included from
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageC.nc:57,
 from
/opt/tinyos-2.1.1/tos/platforms/micaz/TimeSyncMessageC.nc:64,
 from pbsAppC.nc:18:
In component `CC2420TimeSyncMessageP':
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc:53:
interface PacketTimeSyncOffset not found
In file included from
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageC.nc:57,
 from
/opt/tinyos-2.1.1/tos/platforms/micaz/TimeSyncMessageC.nc:64,
 from pbsAppC.nc:18:
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc: In
function `Packet.clear':
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc:73:
interface has no command or event named `cancel'
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc: In
function `TimeSyncAMSend32khz.send':
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc:163:
interface has no command or event named `set'
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc: In
function `TimeSyncAMSend32khz.cancel':
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc:169:
interface has no command or event named `cancel'
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc: In
function `TimeSyncPacket32khz.isValid':
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc:241:
`CC2420_INVALID_TIMESTAMP' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc:241:
(Each undeclared identifier is reported only once
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc:241: for
each function it appears in.)
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc: In
function `TimeSyncPacketMilli.isValid':
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageP.nc:252:
`CC2420_INVALID_TIMESTAMP' undeclared (first use in this function)
In file included from
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420ActiveMessageC.nc:37,
 from
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageC.nc:57,
 from
/opt/tinyos-2.1.1/tos/platforms/micaz/TimeSyncMessageC.nc:64,
 from pbsAppC.nc:18:
In C file:
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420.h: At top level:
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420.h:132: syntax error before `nx_bool'
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420.h:132: warning: no semicolon
at end of struct or union
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420.h:133: syntax error before `ack'
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420.h:134: syntax error before `timesync'
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420.h:143: syntax error before `}'
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420.h:143: warning: type
defaults to `int' in declaration of `cc2420_metadata_t'
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420.h:143: warning: data
definition has no type or storage class
In file included from
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageC.nc:57,
 from
/opt/tinyos-2.1.1/tos/platforms/micaz/TimeSyncMessageC.nc:64,
 from pbsAppC.nc:18:
In component `CC2420ActiveMessageC':
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420ActiveMessageC.nc:53:
interface CC2420Packet not found
In file included from
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageC.nc:57,
 from
/opt/tinyos-2.1.1/tos/platforms/micaz/TimeSyncMessageC.nc:64,
 from pbsAppC.nc:18:
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420ActiveMessageC.nc:56:
interface RadioBackoff not found
In file included from
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420ActiveMessageC.nc:67,
 from
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420TimeSyncMessageC.nc:57,
 from
/opt/tinyos-2.1.1/tos/platforms/micaz/TimeSyncMessageC.nc:64,
 from pbsAppC.nc:18:
In component `CC2420RadioC':
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420RadioC.nc:62: component
CC2420CsmaC not found
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420RadioC.nc:63: component
UniqueSendC not found
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420RadioC.nc:64: component
UniqueReceiveC not found
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420RadioC.nc:65: component
CC2420TinyosNetworkC not found
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420RadioC.nc:66: component
CC2420PacketC not found
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420RadioC.nc:67: component
CC2420ControlC not found
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420RadioC.nc:70: component
DefaultLplC not found
/opt/tinyos-2.1.1/tos/chips/cc2420/CC2420RadioC.nc:78: component
PacketLinkDummyC not found
/opt/tinyos-2.1.1/tos/chi

Re: [Tinyos-help] Different compilers within the same TinyOS-2.1

[David Rodenas Herráiz]

Thanks Eric. I had some problems installing the xscale compiler (for Imote2):
rpm -ivh --ignoreos xscale-elf-gcc-3.4.3-1.cygwin.i386.rpm
Preparing...### [100%]
file /usr/man/man7/fsf-funding.7 from install of xscale-elf-gcc-3.4.3-1 
conflicts with file from package avr-gcc-4.1.2-1
file /usr/man/man7/gfdl.7 from install of xscale-elf-gcc-3.4.3-1 
conflicts with file from package avr-gcc-4.1.2-1
and more...
I suppose that I'll have to install it manually. Therefore, I don't know when 
but I'll tell you if it finally works.
David Rodenas Herráiz

Date: Wed, 26 Oct 2011 03:10:34 -0700
Subject: Re: [Tinyos-help] Different compilers within the same TinyOS-2.1
From: cire...@gmail.com
To: drod...@hotmail.com
CC: tinyos-help@millennium.berkeley.edu

take a look a different .platform files
A pattern will become apparent.  
You'll see things like...
-gcc=msp430-gcc-mmcu=msp430x1611
-fnesc-target=msp430
and like
-gcc=avr-gcc-mmcu=atmega128-fnesc-target=avr

I don't know of any documentation for these things.   I mostly fly by the seat 
of my pants when it comes to what these switches do.



On Wed, Oct 26, 2011 at 12:44 AM, David Rodenas Herráiz  
wrote:






Hi Eric
thanks for your answer. Would you mind giving me some brief instructions to do 
those switches?
David

Date: Tue, 25 Oct 2011 16:14:58 -0700
Subject: Re: [Tinyos-help] Different compilers within the same TinyOS-2.1

From: cire...@gmail.com
To: drod...@hotmail.com
CC: tinyos-help@millennium.berkeley.edu




On Tue, Oct 25, 2011 at 11:25 AM, David Rodenas Herráiz  
wrote:







Hi everyone
I am working with Imote2 and MicaZ motes and I want to ask if PXA27x (compiler 
for Imote2) Atmel AVR tools (compiler or MicaZ) might work within the same 
TinyOS-2.1 installation. 


Sure.   The toolchain invoked is determined by switches in the .platform file 
for the platform being compiled.
So it should work fine. 


Thanks in advance
David 

___

Tinyos-help mailing list

Tinyos-help@millennium.berkeley.edu

https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help




-- 
Eric B. Decker
Senior (over 50 :-) Researcher


  


-- 
Eric B. Decker
Senior (over 50 :-) Researcher



  ___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Different compilers within the same TinyOS-2.1

[Eric Decker]

take a look a different .platform files

A pattern will become apparent.

You'll see things like...

-gcc=msp430-gcc
-mmcu=msp430x1611
-fnesc-target=msp430

and like

-gcc=avr-gcc
-mmcu=atmega128
-fnesc-target=avr


I don't know of any documentation for these things.   I mostly fly by the
seat of my pants when it comes to what these switches do.



On Wed, Oct 26, 2011 at 12:44 AM, David Rodenas Herráiz  wrote:

>  Hi Eric
>
> thanks for your answer. Would you mind giving me some brief instructions to
> do those switches?
>
> David
>
> --
> Date: Tue, 25 Oct 2011 16:14:58 -0700
> Subject: Re: [Tinyos-help] Different compilers within the same TinyOS-2.1
> From: cire...@gmail.com
> To: drod...@hotmail.com
> CC: tinyos-help@millennium.berkeley.edu
>
>
>
> On Tue, Oct 25, 2011 at 11:25 AM, David Rodenas Herráiz <
> drod...@hotmail.com> wrote:
>
>  Hi everyone
>
> I am working with Imote2 and MicaZ motes and I want to ask if PXA27x
> (compiler for Imote2) Atmel AVR tools (compiler or MicaZ) might work within
> the same TinyOS-2.1 installation.
>
>
> Sure.   The toolchain invoked is determined by switches in the .platform
> file for the platform being compiled.
>
> So it should work fine.
>
>
>
> Thanks in advance
>
> David
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
>
>
>
> --
> Eric B. Decker
> Senior (over 50 :-) Researcher
>
>
>


-- 
Eric B. Decker
Senior (over 50 :-) Researcher
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Different compilers within the same TinyOS-2.1

[Nelson Dopico]

Hello!

As for installing both compilers (AVR and iMote2) on the same system, you may 
see instructions on http://docs.tinyos.net/tinywiki/index.php/IMote2_Compiler 
to install an imote2 compiler that does not conflict with avr compiler.

Cheers,

Nelson
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Problem with serial communication using telosa

[Urs Hunkeler]

Hi Luís,

I just had a look. It appears that telosa, telosb and tmote all use the 
same baud rate, and that the platform name for telosa on TinyOS is just 
"telos" (not tmote).

TelosA and TelosB/Tmote are similar, but not identical. It is entirely 
possible that if you compile your programs for the platform "tmote" they 
will install on the TelosA and maybe even blink the LEDs, but that other 
things (like serial communication) will not work. When you compile the 
test programs, did you do a "make telos" (and not "make tmote")? (and 
similarly "make telos install")

If it still doesn't work, could you send us the exact commands that you 
use (make, make install, java ...Listen...) and the output that you get 
for each of the commands (e.g., copy/past the text from your terminal)?

Cheers,
Urs


On 10/25/11 11:48 PM, Luís Pereira wrote:
> Hi Rafael,
>
> well when I run motelist i have:
>
> Reference Device Description
> --  -
> M4MWCK4F /dev/ttyUSB0 Moteiv Telos (Rev A 2004-04-27)
>
> Then i run:
>
> java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB0:tmote
>
> and i got:
>
> serial@/dev/ttyUSB0:115200: resynchronising
>
> and the leds of the mote stop blinking.
>
> Luís Pereira
>
>
> 2011/10/25 Rafael de Oliveira Costa  >
>
> Hi Luís,
>
> please show what command did you executed.
>
> Rafael de Oliveira Costa,M.Sc. Student
> PPGI - UFRJ
> Rio de Janeiro, RJ, Brazil
> http://www.labnet.nce.ufrj.br 
> "The first step to getting the things you want out of life is this :
> decide what you want", Ben Stein
>
>
>
> 2011/10/24 Luís Pereira  >
>
> Hi All,
>
> I'm starting a project at my school using telosa. I'm trying to
> do the tutorial and i got stuck in lesson 4.
>
> I can't receive data from telosa. When I try
> "java.net.tinyos.tools.Listen" or "java TestSerial" or even the
> serialForwarder programs it shows me the "resynchronizing"
> message and nothing else happens. With the application that the
> mote blinks it's leds in an binary count, when i try to connect
> it stops counting.
>
> I already search in all the mailing list i nothing i found about
> this solve my problem.
>
> Can anyone help me please?
>
> Thanks for your help
> Luís Pereira
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> 
> 
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
>
>
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Different compilers within the same TinyOS-2.1

[David Rodenas Herráiz]

Hi Eric
thanks for your answer. Would you mind giving me some brief instructions to do 
those switches?
David

Date: Tue, 25 Oct 2011 16:14:58 -0700
Subject: Re: [Tinyos-help] Different compilers within the same TinyOS-2.1
From: cire...@gmail.com
To: drod...@hotmail.com
CC: tinyos-help@millennium.berkeley.edu



On Tue, Oct 25, 2011 at 11:25 AM, David Rodenas Herráiz  
wrote:






Hi everyone
I am working with Imote2 and MicaZ motes and I want to ask if PXA27x (compiler 
for Imote2) Atmel AVR tools (compiler or MicaZ) might work within the same 
TinyOS-2.1 installation. 

Sure.   The toolchain invoked is determined by switches in the .platform file 
for the platform being compiled.
So it should work fine. 

Thanks in advance
David 

___

Tinyos-help mailing list

Tinyos-help@millennium.berkeley.edu

https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help



-- 
Eric B. Decker
Senior (over 50 :-) Researcher


  ___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Problem with serial communication using telosa

[Eric Decker]

2011/10/25 Luís Pereira 

> Hi Rafael
>
> I don't have a ttyUSB1 on /dev/ only USB0. Is this a problem with my
> computer?
>

No.

I'm not sure what the other guy is using and why he is saying that an FTDI
interface results in two USB devs in the /dev/ttyUSB* tree but that is not
my understanding of how it works.

Every FTDI device that I've messed with results in the Linux USB driver
stack producing one /dev/ttyUSB interface.


>
> Thanks for your help so far
> Luís Pereira
>
> On 26/10/2011, Rafael de Oliveira Costa 
> wrote:
> > I will say something like Igglezakis. here serial works on ttyUSB1 and to
> > deploy ttyUSB0
> >
> > Rafael de Oliveira Costa, M.Sc. Student
> > PPGI - UFRJ
> > Rio de Janeiro, RJ, Brazil
> > http://www.labnet.nce.ufrj.br
> > "The first step to getting the things you want out of life is this :
> decide
> > what you want", Ben Stein
> >
> >
> >
> > 2011/10/25 Luís Pereira 
> >
> >> Hi Igglezakis,
> >>
> >> Sorry but here only ttyUSB0 exist. I have no USB1.
> >> By the way i'm using archlinux but i don't think that is the problem.
> >>
> >>
> >> Luís Pereira
> >>
> >>
> >>
> >> On Tue, Oct 25, 2011 at 23:07, Igglezakis Antonios
> >> wrote:
> >>
> >>>  Try
> >>> java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB1:tmote
> >>>
> >>> instead.
> >>> FTDI creates 2 USB ports, one for reading and one for writing!
> >>>
> >>>  On 10/26/2011 12:48 AM, Luís Pereira wrote:
> >>>
> >>> Hi Rafael,
> >>>
> >>>  well when I run motelist i have:
> >>>
> >>>  Reference  Device   Description
> >>> -- 
> -
> >>> M4MWCK4F   /dev/ttyUSB0 Moteiv Telos (Rev A 2004-04-27)
> >>>
> >>>  Then i run:
> >>>
> >>>  java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB0:tmote
> >>>
> >>>  and i got:
> >>>
> >>>  serial@/dev/ttyUSB0:115200: resynchronising
> >>>
> >>>  and the leds of the mote stop blinking.
> >>>
> >>> Luís Pereira
> >>>
> >>>
> >>> 2011/10/25 Rafael de Oliveira Costa 
> >>>
>  Hi Luís,
> 
>  please show what command did you executed.
> 
>  Rafael de Oliveira Costa, M.Sc. Student
>  PPGI - UFRJ
>  Rio de Janeiro, RJ, Brazil
>  http://www.labnet.nce.ufrj.br
>   "The first step to getting the things you want out of life is this :
>  decide what you want", Ben Stein
> 
> 
> 
>  2011/10/24 Luís Pereira 
> 
> >  Hi All,
> >
> >  I'm starting a project at my school using telosa. I'm trying to do
> the
> > tutorial and i got stuck in lesson 4.
> >
> >  I can't receive data from telosa. When I try
> > "java.net.tinyos.tools.Listen" or "java TestSerial" or even the
> > serialForwarder programs it shows me the "resynchronizing" message
> and
> > nothing else happens. With the application that the mote blinks it's
> > leds in
> > an binary count, when i try to connect it stops counting.
> >
> >  I already search in all the mailing list i nothing i found about
> this
> > solve my problem.
> >
> >  Can anyone help me please?
> >
> >  Thanks for your help
> > Luís Pereira
> >
> >  ___
> > Tinyos-help mailing list
> > Tinyos-help@millennium.berkeley.edu
> >
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >
> 
> 
> >>>
> >>>
> >>> ___
> >>> Tinyos-help mailing
> >>> listTinyos-help@millennium.berkeley.eduhttps://
> www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >>>
> >>>
> >>>
> >>> ___
> >>> Tinyos-help mailing list
> >>> Tinyos-help@millennium.berkeley.edu
> >>>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >>>
> >>
> >>
> >> ___
> >> Tinyos-help mailing list
> >> Tinyos-help@millennium.berkeley.edu
> >>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >>
> >
>
>
> --
> Luís Pereira
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>



-- 
Eric B. Decker
Senior (over 50 :-) Researcher
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Problem with serial communication using telosa

[Urs Hunkeler]

Hi Luís,

The FTDI drivers actually only create one serial port (the others were 
probably thinking of the X-Bow MIB520 programming boards for the 
Mica-series of motes).

The telosa platform is distinct from the telosb / tmote platform. If you 
really have a telosa platform, maybe you could try the command:

java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB0:telosa

I did not verify this, but it is possible that the telosa platform uses 
a different baud-rate than the telosb/tmote platforms (and by specifying 
telosa instead of tmote this should be rectified).

Cheers,
Urs


On 10/25/11 11:48 PM, Luís Pereira wrote:
> Hi Rafael,
>
> well when I run motelist i have:
>
> Reference Device Description
> --  -
> M4MWCK4F /dev/ttyUSB0 Moteiv Telos (Rev A 2004-04-27)
>
> Then i run:
>
> java net.tinyos.tools.Listen -comm serial@/dev/ttyUSB0:tmote
>
> and i got:
>
> serial@/dev/ttyUSB0:115200: resynchronising
>
> and the leds of the mote stop blinking.
>
> Luís Pereira
>
>
> 2011/10/25 Rafael de Oliveira Costa  >
>
> Hi Luís,
>
> please show what command did you executed.
>
> Rafael de Oliveira Costa,M.Sc. Student
> PPGI - UFRJ
> Rio de Janeiro, RJ, Brazil
> http://www.labnet.nce.ufrj.br 
> "The first step to getting the things you want out of life is this :
> decide what you want", Ben Stein
>
>
>
> 2011/10/24 Luís Pereira  >
>
> Hi All,
>
> I'm starting a project at my school using telosa. I'm trying to
> do the tutorial and i got stuck in lesson 4.
>
> I can't receive data from telosa. When I try
> "java.net.tinyos.tools.Listen" or "java TestSerial" or even the
> serialForwarder programs it shows me the "resynchronizing"
> message and nothing else happens. With the application that the
> mote blinks it's leds in an binary count, when i try to connect
> it stops counting.
>
> I already search in all the mailing list i nothing i found about
> this solve my problem.
>
> Can anyone help me please?
>
> Thanks for your help
> Luís Pereira
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> 
> 
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
>
>
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help