Hello, I believe that has to do with the locking that happens. Depending ib what you told the mote before, you have to stop before giving a new command, to unlock the mote. And you also don't need the image number after the -s.
~Dimas~ 2008/1/18, weiping SONG <[EMAIL PROTECTED]>: > > Hi David, > > I have faced also the similar problem for burn-net so I give it up. I > think before run > > "tos-deluge -dr 1", you might run "tos-deluge -s 1" first. > > Regards, > > Weiping SONG > > David wrote: > > Apologies in advance if I'm doing something dumb again ;-) > > > > It looks like dissemination is broken. When you run tos-deluge -d or > > -dr, nothing happens on the non-basestation motes. > > > > I've seen this with my own testing, and also with > > apps/tests/deluge/Blink/burn-net. > > > > burn-net works fine up until the final step, where it runs "tos-deluge > > -dr 1". There isn't any error message, and a green LED does blink > > momentarily on the basestation mote (indicating it got comms over > > USB). But the green LED on the 2nd mote doesn't start flickering, and > > it never switches over to the 2nd program (blink green LED). > > > > Can somebody confirm this problem? > > > > David. > > _______________________________________________ > > 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 >
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
