A pin compatible MCU family may have 4:1, 8:1, 16:1, ... ratios.
Unlike othere embedded applications, RAM size less than 4KB
is not enough for WSN applications. To get code size down, a
MCU with small size flash can be used.
My point is that the extreme inline optimization is not necessary
especailly for the MCU with RAM size over 8KB.
Chang
==============================================
On to the future: one issue here is whether the MSP430 F1611 ratio
(4:1) is going to hold in the long term, or whether things will swing
back to older ratios (16:1) or even further (64:1?). If the
expectation is that in one year, the ratio will swing back,
completely revisiting all of the TinyOS programming methodologies and
re-implementing everything would be a huge waste of time. On the
other hand, if the ratio is going to stay, then revisiting all of
these assumptions could be really worthwhile. The murmurs I've heard
from the MCU world is that more program memory will be appearing
soon, while RAM won't. If that's the case, making sure people in edge
cases can tweak their performance tradeoffs (e.g., preventing
inlining of very common functions) in the present is good so there
can be forward progress, but re-implementing everything for this
temporary situation isn't a big priority, at least for me.
Phil
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
