Hi!

On Tue, 15 Jan 2008, Dimas Abreu Dutra wrote:

Hello,

I discovered my stupid mistake... I am using the tmote-bsl by hand on
another (windows) machine because I couldn't use it on linux and had some
weird permission errors. I had only installed the applications ihex but had
not installed tosboot's ihex. Anyway, after I discovered it I downloaded the
tosboot ihex (with a mass erase) and after that the application's ihex
(without a mass erase). When I turn the mote on now it does the 3 led fading
tosboot indicator and goes to the application afterwards.

I still can't inject an image to the golden image slot (keep getting the
python exception) but my worst problem is that I can't reboot into another
image after I successfully inject it and disseminate it. The mote reboots,
the bootloader runs the fading leds but the app executing is still the one
downloaded from the tmote-bsl, as can be seen from the flashing red leds and
the ping information.

What image slot are you using? There was a bug that prevented the -r to use only the first slot. I just committed a fix that should take care of that.

I suppose this has something to do with my manual installation procedure. Is
it correct? Should I concatenate the files or just download them, one after
the other? Is there any magical step missing?

Can you please describe in detail the your steps? Can you also describe the permission errors you got on linux? :P

--
Razvan ME

2008/1/14, Razvan Musaloiu-E. <[EMAIL PROTECTED]>:

Hi!

On Mon, 14 Jan 2008, Dimas Abreu Dutra wrote:

Hello

I am using the deluge T2 from the last commit you did to the CVS and am
having some problems to inject an image to a node. First of all, in the
tos-deluge script the PATH_PY_BUILD_IMAGE variable is configured to
'./tos-build-deluge-image', which caused some problems.

Sorry about that. I committed a fixed for that.

Anyway, the main problem is that whenever I run any command from
tos-deluge I always get an "error: 0 data: []".

Please ignore the "error: 0 data: []". A 0 doesn't indicate an error. I'll
remove it soon.

For example:

[EMAIL PROTECTED]:~/tinyos-2.x-cvs/apps/tests/deluge/Blink/build/telosb
$ tos-deluge /dev/ttyUSB0 telosb -dr 0
error: 0 data: []
Command sent

Note: you cannot disseminate image 0 because it should be the Golden
Image.

or
d1ma5@ portinari:~/tinyos-2.x-cvs/apps/tests/deluge/Blink/build/telosb
$ tos-deluge /dev/ttyUSB0 telosb -e 1
error: 0 data: []
Image number 1 erased
or
[EMAIL PROTECTED]:~/tinyos-2.x-cvs/apps/tests/deluge/Blink/build/telosb
$ tos-deluge /dev/ttyUSB0 telosb -b 1
error: 0 data: []
Command sent

The above two should work fine.

When I want to inject an image I also get the same error, but in a
different
place:

[EMAIL PROTECTED]:~/tinyos-2.x-cvs/apps/tests/deluge/Blink/build/telosb
$ tos-deluge /dev/ttyUSB0 telosb -i 2 tos_image.xml
Pinging node ...
Connected to Deluge nodes.
No valid image was detected.
--------------------------------------------------
Create image: /home/d1ma5/local/bin/tos-build-deluge-image -i 2
tos_image.xml
Ihex read complete:
 32976 bytes starting at 0x4A00
    32 bytes starting at 0xFFE0
 33008 bytes in 2 sections
CRCs:
 0x378B 0x9DB4 0xCAE9 0xC99F 0x1410 0x9A61 0x88B0
 0x5F28 0x9956 0x8E48 0xC2B5 0x5A98 0x4279 0x7D0E
 0x7022 0x2B9E 0x0A0E 0x6BD6 0x6310 0xF3D6 0x8CA3
 0x7742 0x96FE 0x76BC 0xB283 0x9C08 0x753F 0xB368
 0x7502 0x9450
--------------------------------------------------
error: 0 data: []
33504 bytes in 24.38 seconds (1374.2404 bytes/s)
error: 0 data: []
--------------------------------------------------
Replace image with:
 Prog Name:   BlinkAppC
 UID:         0x3187DD1E
 Compiled On: Mon Jan 14 16:53:24 2008
 Platform:    telosb
 User ID:     d1ma5
 Host Name:   portinari
 User Hash:   0xAC510E87
 Size:        33504
 Num Pages:   30
--------------------------------------------------

The above looks like a normal injection.

When trying to overwrite the golden image there is also another error, a
python exception not caught:

[EMAIL PROTECTED]:~/tinyos-2.x-cvs/apps/tests/deluge/Blink/build/telosb
$ tos-deluge /dev/ttyUSB0 telosb -i 0 tos_image.xml
Pinging node ...
Connected to Deluge nodes.
No valid image was detected.
--------------------------------------------------
Create image: /home/d1ma5/local/bin/tos-build-deluge-image -i 0
tos_image.xml
Ihex read complete:
 32976 bytes starting at 0x4A00
    32 bytes starting at 0xFFE0
 33008 bytes in 2 sections
CRCs:
 0x378B 0x9DB4 0xCAE9 0xC99F 0x1410 0x9A61 0x88B0
 0x5F28 0x9956 0x8E48 0xC2B5 0x5A98 0x4279 0x7D0E
 0x7022 0x2B9E 0x0A0E 0x6BD6 0x6310 0xF3D6 0x8CA3
 0x7742 0x65EA 0x76BC 0xB283 0x1F3E 0x753F 0xB368
 0x7502 0x9450
--------------------------------------------------
error: 0 data: []
33504 bytes in 24.38 seconds (1374.2323 bytes/s)
error: 0 data: []
--------------------------------------------------
Replace image with:
Traceback (most recent call last):
 File "/home/d1ma5/local/bin/tos-deluge", line 417, in <module>
   inject(imgNum, sys.argv[5])
 File "/home/d1ma5/local/bin/tos-deluge", line 313, in inject
   print formatIdent(getIdent(imgNum))
 File "/home/d1ma5/local/bin/tos-deluge", line 257, in formatIdent
   r += "  Compiled On: %s\n" % 
(datetime.fromtimestamp(i.timestamp).strftime('%a
%h %d %T %Y'))
ValueError: timestamp out of range for platform time_t

Do you get this error at each injection? The -p and -i use the same
mechanism to show the information about an image.

When I ping the mote I can see the images were successfully writen (or
so it
appears) but I cannot put them into execution.

You should be able to reprogram the directly-connected mote using the '-r'
command. Let me know if it doesn't work.

--
Razvan ME

~Dimas~

2008/1/14, Razvan Musaloiu-E. <[EMAIL PROTECTED]>:

I just made a big commit to CVS with everything I have so far. I didn't
have time to update the manual and the testing scripts yet. If you have
time to give a try in the current shape it would be great. :-)




_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to