On 6/21/06, Tobias Frost <[EMAIL PROTECTED]> wrote:
I currently thinking about using TinyOS in a commercial project, which I am the responsible (software) design engineer.But there is one information I was able to obtain: What is the memory footprint of a typical tiny-os application? Well, I know, this is hard to say, as it depends on several features "used", but a rough figure would be really useful. (It is planned to use a AtMeag48, with 4k of Flash) The main questionis, will this be enough memory.
At a guess, probably no. The earliest TinyOS motes had 8k of flash and 512 bytes of RAM, so it is possible to do TinyOS-like things in that kind of space. However, our current devices have 48k+ of flash and 4k+ of RAM, and the code in TinyOS is written with that in mind. You might be able to use the TinyOS tools, methodology, etc. You might also be able to extract some code from some existing TinyOS components, but you would probably need to specialise them to your task. If you want to check things, the attached module_memory_usage script (courtesy of Cory Sharp's perl skills :-)) displays RAM and ROM usage by component given an executable. Note that the ROM usage attribution is approximate (there's a lot of inlining across component boundaries...). David Gay
module_memory_usage
Description: Binary data
_______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
