Hi TinyOS developers. Our company is starting some new embedded development, and would like to do this development in TinyOS 2.x rather than 1.x (nicer docs and easier development. Includes Dissemination and Collection network algorithms, etc).
Our main problem with using TinyOS 2.x is that Deluge T2 has a few problems (I understand that it is an experimental port from TinyOS 1.x). We're interested in sponsoring a TinyOS developer to fix these problems. Changes can of course go back into the main TinyOS codebase. Here is a summary of the problems I've found so far and would like to be fixed (in decreasing order of severity): 1) Deluge T2 dissemination breaks easily 2) Rollback gesture does not work in Deluge T2. 3) Deluge T2 only supports 2 images per mote. 4) The "tos-deluge" tool does not report which image is active We are offering $400 (US Dollars) for the above to be fixed. Are there any takers? If you're interested, here is more specific information: 1) Deluge T2 dissemination breaks easily: If a (non-base station) mote (running Deluge) starts receiving an update, and then it is interrupted (for instance, you press the reset button, or you send the mote a "reprogram" command over deluge), then the mote stops downloading updates. Also, the mote no longer wants to download newer program images disseminated from the Base Station. It just ignores disseminate commands after that point. To fix this problem the mote needs to be re-connected to a PC so we can update it with a "tos-deluge -i" command. 2) Rollback gesture does not work in Deluge T2: Pressing reset several times does not do anything (besides resetting). I've compared the tinyos-1.x and 2.x code, it doesn't seem to be implemented yet in tinyos 2.x's Deluge. 3) Deluge T2 only supports 2 images per mote. This is a problem because we would like to run several different tinyos applications on our wireless networks. With Deluge T2 we would need to write a single application which reads the mote "type" from flash and then activates different sub-programs based on the "type". This is not ideal. 4) The "tos-deluge" tool does not report which image is active "tos-deluge -p" in Deluge T2 doesn't (as far as I can tell) report which image is currently active on a mote. However, this info is available in the tinyos-1.x command-line tools. Regards, David. PS: If you make these changes, please update your CVS and your Ubuntu repository (http://tinyos.stanford.edu/tinyos/dists/ubuntu) so we can easily install your updated versions (we run Debian, but your Ubuntu installers are compatible). _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
