Hi!
Can you give it another try now? There was one more bug that prevented the
dissemination to work properly. I just committed the fix in the CVS. :-)
Big-big thanks for your patience!
Razvan ME
On Tue, 28 Apr 2009, Henry Medeiros wrote:
Injection works perfectly. Thanks. There still seems to be a problem with
dissemination though. I tried to disseminate the application into a single
node programmed with the GoldenImage application but the mote does not get
reprogrammed. Instead, it keeps turning on the three LEDs and then slowly
turning them off (as in a regular boot).
Please find below the detailed steps I followed and their corresponding
outputs.
1) Attach mote 0 to the mib510.
$ cd /opt/tinyos-2.x/apps/tests/deluge/Basestation
$ make micaz install.0 mib510
(output suppressed, but it compiles and uploads the program without problems)
$ cd my_application_folder
$ make micaz
(output suppressed, but it successfully generates a 77k image)
$ tos-deluge serial@/dev/ttyUSB0:230400 -i 3 build/micaz/tos_image.xml
Flushing the serial port...
Checking if node is a Deluge T2 base station ...
Pinging node ...
Connected to Deluge nodes.
No valid image was detected.
--------------------------------------------------
Create image: /usr/bin/tos-build-deluge-image -i 3 build/micaz/tos_image.xml
Ihex read complete:
77682 bytes starting at 0x0
77682 bytes in 1 sections
CRCs:
0x7B8D 0x527C 0x3C17 0xC1FD 0x8AB4 0xBC71 0x4D2F
0x9FF4 0xD5A3 0xD9DC 0x05CA 0x0B11 0xF1CB 0x6872
0x9F2B 0xC81B 0xACB1 0xB0CA 0x2F2F 0x1AFC 0x2077
0x2232 0x39E3 0x330C 0x10DD 0xD896 0x4867 0x0F76
0xA6BA 0x1DBC 0x52EE 0x153A 0x72C8 0x6E75 0x6CD8
0xCF59 0xC5A0 0x0B5B 0x5140 0x0AC4 0x2AE2 0x4A51
0xF839 0xF117 0x1BA4 0x46D8 0x29ED 0x7A55 0x7FCC
0xEC57 0x4F76 0xFE15 0x0A1A 0xE1B6 0xF686 0xF0C0
0xF725 0xAA23 0xCD3C 0x3081 0xE86A 0x1890 0xB1FF
0x10C3 0x5576 0xB49C 0x3958 0x8224 0x4E03 0xE066
0x7437
--------------------------------------------------
78768 bytes in 660.70 seconds (119.2197 bytes/s)
--------------------------------------------------
Replace image with:
Prog Name: DynClusterTrack
UID: 0x7F0CDD6B
Compiled On: Tue Apr 28 07:58:19 2009
Platform: micaz
User ID: hmedeiro
Host Name: hmedeiro-laptop
User Hash: 0x17EEDC36
Size: 78768
Num Pages: 71
--------------------------------------------------
$ tos-deluge serial@/dev/ttyUSB0:230400 -p 3
Flushing the serial port...
Checking if node is a Deluge T2 base station ...
Pinging node ...
--------------------------------------------------
Currently Executing:
Prog Name: BasestationAppC
UID: 0x63BF2D9F
Compiled On: Tue Apr 28 07:57:36 2009
Node ID: 0
Stored image 3
Prog Name: DynClusterTrack
UID: 0x3344A5B2
Compiled On: Tue Apr 28 10:00:57 2009
Platform: micaz
User ID: hmedeiro
Host Name: hmedeiro-laptop
User Hash: 0x17EEDC36
Size: 78768
Num Pages: 71
--------------------------------------------------
2) Remove mote 0 from the mib510 and insert mote 1
$ cd /opt/tinyos-2.x/apps/tests/deluge/GoldenImage
$ make micaz install.1 mib510
(output suppressed, but everything works)
3) Remove mote 0 and insert mote 1 again
$ tos-deluge $MOTECOM -dr 3
Flushing the serial port...
Checking if node is a Deluge T2 base station ...
Command sent
After that I see the green LED in mote 1 blinking for 30 seconds or so and
then it starts turning the LEDs on and off as described above (apparently
rebooting itself repeatedly). I have been staring at it for over one hour and
nothing changed so far. I tried the same procedure with different motes in
order to rule out hardware problems, and I always get the same results.
Here is my version of GoldenImageAppC.nc, in case you need it:
configuration GoldenImageAppC {}
implementation
{
components DelugeC;
components LedsC;
DelugeC.Leds -> LedsC;
}
My volumes-at45db.xml files (see previous message) are the same for all three
applications (BaseStation, GoldenImage, and my own application).
I don't know if that is relevant, but if I send a stop dissemination command
from the deluge base station, the node stops rebooting:
$ tos-deluge serial@/dev/ttyUSB0:230400 -s
Flushing the serial port...
Checking if node is a Deluge T2 base station ...
Command sent
After that, LED blinking stops, but my application is not running. This is
what I get when I attach mote 1 to the mib510 and ping it:
$ tos-deluge serial@/dev/ttyUSB0:230400 -p 3
Flushing the serial port...
Checking if node is a Deluge T2 base station ...
Pinging node ...
--------------------------------------------------
Currently Executing:
Prog Name: GoldenImageAppC
UID: 0x7BFF9BAA
Compiled On: Tue Apr 28 10:12:41 2009
Node ID: 1
Stored image 3
Prog Name: DynClusterTrack
UID: 0x3344A5B2
Compiled On: Tue Apr 28 10:00:57 2009
Platform: micaz
User ID: hmedeiro
Host Name: hmedeiro-laptop
User Hash: 0x17EEDC36
Size: 78768
Num Pages: 71
--------------------------------------------------
But if I try to reboot it to image 3 using deluge, I get a "no response"
answer (even after sending the stop and/or local stop commands):
$ tos-deluge serial@/dev/ttyUSB0:230400 -r 3
Flushing the serial port...
Checking if node is a Deluge T2 base station ...
No response
Please let me know if you need further information, or if I am missing
something important here.
Thanks again,
Henry
Razvan Musaloiu-E. wrote:
Hi!
I just committed a fix for this problem. You'll have to reinstall the tools
(or copy tos-deluge and tos-build-deluge-image by hand to their final
destination) and recompile tosboot.
Please let me know if this fix doesn't work.
All the best!
Razvan ME
On Tue, 21 Apr 2009, Henry Medeiros wrote:
Thanks Razvan. Please let me know if you need further information.
Razvan Musaloiu-E. wrote:
Hi!
I can confirm this bug and I'll work in fixing it. I'll let you know
as soon as I have a solution.
Sorry for the delay!
Razvan ME
On Mon, 20 Apr 2009, Henry Medeiros wrote:
Hello everyone,
I have a 74k application that I am trying to inject it into a micaz mote
using Deluge T2 without success. The mote is programmed with the deluge
Basestation, and I can inject and reprogram smaller applications without
any problem.
This is the content of volumes-at45db.xml:
<volume_table>
<volume name="GOLDENIMAGE" size="131072" base="0" />
<volume name="DELUGE1" size="131072"/>
<volume name="DELUGE2" size="131072"/>
<volume name="DELUGE3" size="131072"/>
</volume_table>
(I have tried several different arrangements, but none seems to work)
Here is the output of tos-deluge serial@/dev/ttyUSB0:57600 -i 1
build/micaz/tos_image.xml:
Flushing the serial port...
Checking if node is a Deluge T2 base station ...
Pinging node ...
Connected to Deluge nodes.
No valid image was detected.
--------------------------------------------------
Create image: /usr/bin/tos-build-deluge-image -i 1
build/micaz/tos_image.xml
Ihex read complete:
65536 bytes starting at 0x0
7316 bytes starting at 0x0
72852 bytes in 2 sections
CRCs:
0x4208 0xACF7 0x81F2 0xD24F 0x9EED 0x76EB 0xE83E
0x7923 0xF8DE 0x0286 0xA116 0x69B5 0x6BAA 0xC73A
0x2B6F 0x5DE1 0xBCC1 0x63AB 0x501B 0x600C 0xA259
0x64CF 0x7380 0xE6DD 0x8811 0xE238 0xC337 0x5E8F
0x68D6 0xB5BF 0x94BC 0x27A6 0x8CA7 0xC7D6 0x2493
0x5A99 0xC819 0x8667 0x443A 0xBF80 0x3109 0x0498
0xA812 0x895B 0x5933 0x957F 0xDC39 0x9966 0xC61A
0xA548 0x2BEC 0x06DC 0xCFE1 0x3FD6 0x8A54 0x9FEC
0x19D8 0x2747 0x6CD4 0x205E 0x6941 0x69E2 0x09CE
0x54EB 0xCCA5 0xBA8E 0xDEBD
--------------------------------------------------
74352 bytes in 609.53 seconds (121.9822 bytes/s)
--------------------------------------------------
Replace image with:
Prog Name: ?...@???ˉ??????.???,Ý ì
UID: 0│0879C357
C⎺└⎻␋┌␊␍ O┼: F⎼␋ O␌├ 03 19:56:01 2036
P┌▒├°⎺⎼└: ??)¡:¡K¡\¡Õ└?
U⎽␊⎼ ID: .à°..?????????.?????????.
Host Name: /?????? /???-?????????
User Hash: 0x9C910E94
Size: 3746544003
Num Pages: 168
For completeness, this is the result of make micaz:
mkdir -p build/micaz
tos-storage-at45db /opt/tinyos-2.x/tos/platforms/micaz
<volumes-at45db.xml >build/micaz/StorageVolumes.h || rm -f
build/micaz/StorageVolumes.h
compiling DynClusterTracking to a micaz binary
ncc -o build/micaz/main.exe -Os -fnesc-separator=__ -Wall -Wshadow
-Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb
-DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=100000
-Ibuild/micaz -DIDENT_APPNAME=\"DynClusterTrack\"
-DIDENT_USERNAME=\"hmedeiro\" -DIDENT_HOSTNAME=\"hmedeiro-laptop\"
-DIDENT_USERHASH=0x17eedc36L -DIDENT_TIMESTAMP=0x49e7880aL
-DIDENT_UIDHASH=0x0879b826L -DDELUGE -I/opt/tinyos-2.x/tos/lib/net
-I/opt/tinyos-2.x/tos/lib/net/drip -I/opt/tinyos-2.x/tos/lib/net/Deluge
-I/opt/tinyos-2.x/tos/lib/net/Deluge/FlashVolumeManager
-I/opt/tinyos-2.x/tos/lib/net/Deluge/BlockStorageManager
-I/opt/tinyos-2.x/tos/lib/net/Deluge/extra
-I/opt/tinyos-2.x/tos/lib/net/Deluge/extra/avr
-I/opt/tinyos-2.x/tos/lib/net/Deluge/extra/micaz
-I/opt/tinyos-2.x/tos/lib/net/Deluge/extra/mica2 -fnesc-dump=wiring
-fnesc-dump='interfaces(!abstract())'
-fnesc-dump='referenced(interfacedefs, components)'
-fnesc-dumpfile=build/micaz/wiring-check.xml DynClusterTracking.nc -lm
/opt/tinyos-2.x/tos/chips/cc2420/lpl/DummyLplC.nc:39:2: warning:
#warning "*** LOW POWER COMMUNICATIONS DISABLED ***"
compiled DynClusterTracking to build/micaz/main.exe
72852 bytes in ROM
3692 bytes in RAM
avr-objcopy --output-target=srec build/micaz/main.exe
build/micaz/main.srec
avr-objcopy --output-target=ihex build/micaz/main.exe
build/micaz/main.ihex
writing TOS image
Am I missing something?
Thank you,
Henry
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
