Hi. Thanks for your fixes. It looks like the following are fixed: - Deluge resumes when receiving mote is reset - Able to disseminate slots 1-3 - No longer getting strange "currently executing" UIDs.
I'm busy doing testing, have come up with a few more problems. Some of these are related to my original request (ie auto resuming after interruption). But I'll also forward other problems as I find them. When the original 4 requests are addressed I'll arrange for payment. (I'm still waiting for account details to transfer to). Also, I'm busy writing a shell script to help automate my Deluge testing, I'll forward it to this list when it's ready. Here are a few more problems I've encountered: * Unable to write to a basestation slot if that slot is busy being disseminated. eg, when attempting to inject: -------------------------------------------------- Ihex read complete: Total bytes = 30962 Sections = 2 -------------------------------------------------- [-% 25% 50% 75% 100%] ERROR: Unable to write to the flash volume (file offset: 176) Also, the tos-delge -e command succeeds, but it doesn't actually erase. Is this "blocking" behaviour intentional? * Dissemination doesn't resume if the transmitting mote is reset I've only tested this so far with 2 motes, so I reset the basestation and observed this problem. Not sure if this will also affect non-basestation motes which are reset while transmitting updated images. Might be related to the next problem. * Initial disseminate (basestation -> nearby motes) does not always work. For simplicity: 1st generation: Basestation 2nd generation: Motes which got an update directly from the Basestation 3rd generation: Motes which got an update from the 2nd generation. If the 2nd gen motes are off during the initial disseminate, then they don't get the update when they come online again. This is confusing, because 3rd gen motes do get the update from 2nd gen when they come online. Is the transmit from basestation to 2nd gen special? * Sometimes motes don't want to reboot and reprogram after a disseminate. This happened when I started a dissemination to 2 motes, and then sent a few reboot commands (which they ignored) during the update. But after the update they still don't want to reboot. * Motes sometimes stop receiving disseminations. This happened a few times during testing. I'm note sure what the cause is. But basically, when the motes get like this then they don't want to receive updates on any slot. Basically Deluge gets disabled. Resetting the bad mote and retrying the inject & disseminate (on any slot) doesn't have any effect on the mote. I'll try to track it down (I didn't have a golden image on at the time so I couldn't check if it was restored with the gesture). * "GoldenImage" deluge test doesn't want to do do dissemination When all motes are running the GoldenImage test app, and you inject an image into eg slot 3 and attempt to disseminate it, then the other motes don't start flashing their green LED. However, the Blink test app works fine. _______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
