[Tinyos-help] errors on java net.tinyos.tools.Deluge --ping Any idea?
Michael Schippling
schip at santafe.edu
Tue Nov 4 15:30:22 PST 2008
Do you have something sending messages to the TOSBase mote?
You could try running the regular Oscilloscope app,
which in T1 sends messages directly to the UART "channel".
I'm not sure why your MOTECOM won't accept "telosb",
I've only used "tmote"...there may be some other special name.
More searching in code and doc is indicated.
Also try ListenRaw which doesn't try to parse anything.
MS
BAI LI wrote:
> Hi Michael,
>
> Thanks for your reply. I have gone through all the posts related to this
> topic and found a lot of your posts as well. :) But it still didn't work
> after i tried this morning. The following is wat I did. Is there
> anything missing? When I compiled the jave tools, there is no probelmes
> except some TinyDB components but i don't think it will affect the sf
> and Deluge. What do you think? Is there anyone who successfully running
> serial forwarder on telosb based on window cygwin (Tinyos1.15 version)?
>
> These results turn to be resynchronizing again as i tried this serial
> forwarder yesterday and got the same result. Do I have to get
>
> regards,
> Bai
>
>
> Bai Li at deakin-6f29b527 <mailto:Li at deakin-6f29b527> ~
> $ unset MOTECOM
> Bai Li at deakin-6f29b527 <mailto:Li at deakin-6f29b527> ~
> $ cd /opt/tinyos-1.x/apps/tosbase
> Bai Li at deakin-6f29b527 <mailto:Li at deakin-6f29b527>
> /opt/tinyos-1.x/apps/tosbase
> $ make telosb install,1
> mkdir -p build/telosb
> compiling TOSBase to a telosb binary
> ncc -o build/telosb/main.exe -O -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d
> -Wnesc-al
> l -target=telosb -fnesc-cfile=build/telosb/app.c -board=
> -DTOSH_MAX_TASKS_LOG2=8
> -I%T/lib/Deluge
> -Wl,--section-start=.text=0x4800,--defsym=_reset_vector__=0x400
> 0 -DIDENT_PROGRAM_NAME=\"TOSBase\" -DIDENT_USER_ID=\"BaiLi\"
> -DIDENT_HOSTNAME=\"
> deakin-6f29b527\" -DIDENT_USER_HASH=0x75bf6332L
> -DIDENT_UNIX_TIME=0x4910c52aL -D
> IDENT_UID_HASH=0xbbde367dL -mdisable-hwmul
> -I/opt/tinyos-1.x/tos/lib/CC2420Radio
> TOSBase.nc -lm
> C:/tinyos/cygwin/opt/tinyos-1.x/tos/lib/CC2420Radio/CC2420RadioM.nc:116:
> warning
> : `Send.sendDone' called asynchronously from `sendFailed'
> compiled TOSBase to build/telosb/main.exe
> 11066 bytes in ROM
> 1848 bytes in RAM
> msp430-objcopy --output-target=ihex build/telosb/main.exe
> build/telosb/main.ihex
> writing TOS image
> /opt/tinyos-1.x/tools/make/msp/set-mote-id --objcopy msp430-objcopy
> --objdump ms
> p430-objdump --target ihex build/telosb/main.ihex
> build/telosb/main.ihex.out-1 1
> found mote on COM10 (using bsl,auto)
> installing telosb bootloader using bsl
> msp430-bsl --telosb -c 9 -r -e -I -p
> C:/tinyos/cygwin/opt/tinyos-1.x/tos/lib/Del
> uge/TOSBoot/build/telosb/main.ihex
> MSP430 Bootstrap Loader Version: 1.39-telos-6
> Mass Erase...
> Transmit default password ...
> Invoking BSL...
> Transmit default password ...
> Current bootstrap loader version: 1.61 (Device ID: f16c)
> Changing baudrate to 38400 ...
> Program ...
> 1796 bytes programmed.
> Reset device ...
> installing telosb binary using bsl (without mass erase)
> msp430-bsl --telosb -c 9 -r -I -p build/telosb/main.ihex.out-1
> MSP430 Bootstrap Loader Version: 1.39-telos-6
> Invoking BSL...
> Transmit default password ...
> Current bootstrap loader version: 1.61 (Device ID: f16c)
> Changing baudrate to 38400 ...
> Program ...
> 11098 bytes programmed.
> Reset device ...
> rm -f build/telosb/main.exe.out-1 build/telosb/main.ihex.out-1
> Bai Li at deakin-6f29b527 <mailto:Li at deakin-6f29b527>
> /opt/tinyos-1.x/apps/tosbase
> $ motelist
> Reference CommPort Description
> ---------- ---------- ----------------------------------------
> XBR0LS4Y COM10 Crossbow Telos Rev.B
> Bai Li at deakin-6f29b527 <mailto:Li at deakin-6f29b527>
> /opt/tinyos-1.x/apps/tosbase
> $ export MOTECOM="serial at COM10:telosb <mailto:serial at COM10:telosb>"
> Bai Li at deakin-6f29b527 <mailto:Li at deakin-6f29b527>
> /opt/tinyos-1.x/apps/tosbase
> $ java net.tinyos.tools.Listen
> Failed to parse the baudrate telosb (value telosb), defaulting to 19200
> serial at COM10:19200 <mailto:serial at COM10:19200>: resynchronising
>
> Bai Li at deakin-6f29b527 <mailto:Li at deakin-6f29b527>
> /opt/tinyos-1.x/apps/tosbase
> $ unset MOTECOM
> Bai Li at deakin-6f29b527 <mailto:Li at deakin-6f29b527>
> /opt/tinyos-1.x/apps/tosbase
> $ export MOTECOM="serial at COM10:57600 <mailto:serial at COM10:57600>"
> Bai Li at deakin-6f29b527 <mailto:Li at deakin-6f29b527>
> /opt/tinyos-1.x/apps/tosbase
> $ java net.tinyos.tools.Listen
> serial at COM10:57600 <mailto:serial at COM10:57600>: resynchronising
>
> On Wed, Nov 5, 2008 at 4:41 AM, Michael Schippling <schip at santafe.edu
> <mailto:schip at santafe.edu>> wrote:
>
> Do you have a SerialForwarder process running? It looks like Deluge
> is trying to connect to one... Most likely what you need to do is
> set a MOTECOM environment variable to point to the serial port
> connected to your basestation mote. If there's no MOTECOM things
> default to trying to use the S.F. on a network port. Here's a
> couple samples from my env:
>
> export MOTECOM="serial at COM3:mica2"
> export MOTECOM="serial at COM16:tmote"
>
> Your port names and devices may be different.
> Search this list and the doc for more MOTECOM information.
>
> MS
>
> BAI LI wrote:
>
> Hi All,
> I am following Deluge 2.0 quick start. I got the following
> errors as follows. Any ideas on how to fix them? I am using
> Tinyos1.15 and telosb nodes as our project application is
> developed based on this version. I can't use Tinyos2.x instead.
> Any help would be highly appreciated.
> Bai Li at deakin-6f29b527 <mailto:Li at deakin-6f29b527
> <mailto:Li at deakin-6f29b527>>
> /opt/tinyos-1.x/apps/TestDeluge/DelugeBasic
>
> $ java net.tinyos.tools.Deluge --ping
> java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
> at
> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
> at java.net.Socket.connect(Socket.java:426)
> at java.net.Socket.connect(Socket.java:376)
> at java.net.Socket.<init>(Socket.java:291)
> at java.net.Socket.<init>(Socket.java:119)
> at net.tinyos.packet.SFSource.openSource(SFSource.java:56)
> at
> net.tinyos.packet.AbstractSource.open(AbstractSource.java:77)
> at
> net.tinyos.packet.PhoenixSource.run(PhoenixSource.java:167)
> java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
> at
> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
> at java.net.Socket.connect(Socket.java:426)
> at java.net.Socket.connect(Socket.java:376)
> at java.net.Socket.<init>(Socket.java:291)
> at java.net.Socket.<init>(Socket.java:119)
> at net.tinyos.packet.SFSource.openSource(SFSource.java:56)
> at
> net.tinyos.packet.AbstractSource.open(AbstractSource.java:77)
> at
> net.tinyos.packet.PhoenixSource.run(PhoenixSource.java:167)
> sf at localhost:9001 <mailto:sf at localhost
> <mailto:sf at localhost>:9001> died - exiting
> (java.net.ConnectException: Connection refused:
> connect)
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Tinyos-help mailing list
> Tinyos-help at millennium.berkeley.edu
> <mailto:Tinyos-help at millennium.berkeley.edu>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
>
> --
> Platform: WinXP/Cygwin
> TinyOS version: 1.x, Boomerang
> Programmer: MIB510
> Device(s): Mica2, MicaZ, Tmote
> Sensor board: homebrew
>
>
--
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew
More information about the Tinyos-help
mailing list