Hi!
On Tue, 15 Jan 2008, Dimas Abreu Dutra wrote:
Hello,
2008/1/15, Razvan Musaloiu-E. <[EMAIL PROTECTED]>:
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.
The last commit solved a lot of problems ! =]
My manual installation was correct, I tried it with the non-cvs version and
it worked fine, besides working sometimes with the updated version from the
cvs. Anyway, the cvs version is still not very stable, things work in a
different manner depending on the order of the commands issued and the order
I turn the motes on.
Let me try to explain a little what happens. When you power on a mote it
will check the deluge volumes and all the damaged ones will be erased. The
radio is off at this point and the access to the volumes is locked. After
the checking is done and the locks are released the radio is turned on. If
there was a -d or -dr the mote will learn about it and it will try to get
the new image if it doesn't already have it. If the active command is -dr
it will check if the current application is the one indicated by the
command. If it's not it will reboot.
And the inject to the slot 0 is still not working.
:-( I checked again using a fresh CVS and worked fine for me.
For example, after I have two images injected and disseminated to two motes,
on slots 2 and 3, here is what happens:
- reset manually the remote mote
- turn on the base
- issue a -dr command, get :
- ERROR: Unable to send the command
The flushing of the serial port is disabled and that's why you might get
this error. You can enable it by changing "flush=False" to "flush=True" in
the following line from the tos-deluge:
405 s = tinyos.Serial(sys.argv[1], baudrate, flush=False)
- reissue the -dr command and it works, the remote mote is
reprogrammed and reset.
- reissue again the -dr command and get
- ERROR: Unable to disseminate-and-reboot error: 1 data: []
- Keep getting the same error every time I issue the -dr command
again.
This is normal. After you issued a -d or -dr the volume will be locked. To
unlock it you can use -s or -ls. The -s will stop the image dissemination
in the whole network while -ls will disable it only for the
directly-connected mote.
Now if I do the following procedure, here are my results:
- turn on the base
- turn on the remote mote
- issue a -dr command to a new image and it works
- reissue the -dr and keep getting the Unameble to
disseminate-and-reboot for each new try
Similar things happen with the -d and sometimes I get Unable to erase errors
with the inject.
Erasing is also disable in similar fashion with -d and -dr.
Anyway, I must go now and tomorrow I'll do more testing and
describe the problems in more detail.
Have a nice evening! :P
Razvan ME
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
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
