| ??? 11/16/05 22:18 Read: times |
#103832 - Depends Responding to: ???'s previous message |
Erik Malund said:
No, it is not a "design limitation" for embedded use because SRAM can not hold the code during power off. Code in non-permanent memory defines "non-embedded" code in permanent memory defines "emebdded". Is that the definition of "embedded"? Because I've never been able to find two definitions of "embedded" that agree with each other. Anymore, embedded is just about anything "small." Heck, you hear reference to "embedded Linux" which, to me, is as much of an oxymoron as "embedded Windows." In your opinion, would a system that has both permanent and non-permanent code memory qualify as embedded? Erik Malund said:
except when something time-critical goes awry and you spend time and more time fincding out that it is not your code, but your tool. Intrusive tools are worse than none. The latter is probably true in the case of the former. It isn't necessarily as true when the code isn't time-critical. Somethings are time critical, some aren't. The mix is going to depend on your field. Regards, Craig Steiner |
