Mike -
That seemed to do it, thanks for patching it up so quickly! Here are my
initial impressions of Deluge T2:
- Transfer speed similar to or slightly slower than Deluge 2.0
I haven't really done a comparison of any kind this was just based on my
expectation of how long a transfer should take from working the Deluge
2.0. Perhaps I was feeling impatient and that's why it seemed a bit
slower. ;)
- Changes to "ping" behavior
In Deluge 2.0, I believe the ping command would display all of the
volumes together and also showed which volume it was currently running
from. I think the old behavior was simpler if you want to get a quick
overall picture of the Deluge status of a mote. With T2, you need to
ping once for each volume and I don't think it shows which is running.
- Dissemination reboots automatically
I think it is a bad idea to automatically reboot the mote after it
receives a disseminated program. With Deluge 2.0, you needed to issue a
separate reboot command. Let's say you'd like to load up several test
programs all in one go by injecting each one into its own volume on the
base and then disseminating each one. When you are ready to start the
first program, you can then issue a reboot command. This gives the user
more control over Deluge's behavior.
However, these are just minor points. Great work on porting Deluge over
to T2! This should be a big help for everyone.
- Ryan
Chieh-Jan (Mike) Liang wrote:
Hi Ryan,
The fix was just checked into the TinyOS tree. Could you please try again?
Thank you
Mike
J. Ryan Stinnett wrote:
Mike -
Sorry I left that part out! I am using MicaZ, so perhaps that is
where the difference lies. I've included the commands I used below.
They all appear to complete successfully.
(Hook up mote 0)
cd /opt/tinyos-2.x/apps/tests/deluge/GoldenImage
make micaz install,0 mib510,/dev/ttyS4
(Note that -DDELUGE_BASESTATION is included in the GoldenImage Makefile)
tos-deluge /dev/ttyS4 micaz -i 0 build/micaz/tos_image.xml
tos-deluge /dev/ttyS4 micaz -r 0
tos-deluge /dev/ttyS4 micaz -p 0
(This shows version 0 of GoldenImageC in volume 0)
(Hook up mote 1)
make micaz reinstall,1 mib510,/dev/ttyS4
tos-deluge /dev/ttyS4 micaz -i 0 build/micaz/tos_image.xml
tos-deluge /dev/ttyS4 micaz -r 0
tos-deluge /dev/ttyS4 micaz -p 0
(This shows version 0 of GoldenImageC in volume 0)
(Hook up mote 0, turn on mote 1)
make micaz
tos-deluge /dev/ttyS4 micaz -i 0 build/micaz/tos_image.xml
tos-deluge /dev/ttyS4 micaz -r 0
tos-deluge /dev/ttyS4 micaz -p 0
(This shows version 1 of GoldenImageC in volume 0)
tos-deluge /dev/ttyS4 micaz -d 0
(Mote 0's red LED turns on, Mote 1 does nothing)
(...waiting for something to happen, but nothing appears to...)
(Hook up mote 1)
tos-deluge /dev/ttyS4 micaz -p 0
(Still has version 0, not version 1)
Hope that helps!
Thanks,
Ryan
Chieh-Jan (Mike) Liang wrote:
Hi Ryan,
I tried to reproduce the problem, but I couldn't. Could you please
tell me the platform you are using (I currently assume Telosb), and
the commands you typed?
Thank you
Mike
J. Ryan Stinnett wrote:
I'm trying out Deluge T2, but I'm having trouble getting the images
to transmit beyond the base station. I started by flashing
GoldenImageC on to two motes, and then injecting same image onto
volume 0 of each as well. When I ping volume 0, each one reports
that the image is there. I then recompiled GoldenImageC to generate
a new "version" to see if it would be disseminated. At this point
both the base station mote and the other mote are turned on. I
injected the updated version into the base station and rebooted it.
When I ping the base station, it reports that it has version 1
instead of version 0, so that looks good. I then issued the
disseminate command to send the image to the other mote. The red
LED on the base station turned on and remained solid, but no other
LEDs blinked on the base station, and none of the LEDs blinked on
the other mote. When I hook up the second mote to the computer, it
still has version 0. How do I get the updated image to disseminate?
Thanks,
Ryan Stinnett
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
