??? 01/08/05 13:48 Read: times |
#84571 - 90:10 rule Responding to: ???'s previous message |
As I have previously noted, the effort to drive things when everything goes right amounts to only 10% or so of the effort to handle all the things that could possibly go wrong!
http://www.8052.com/forum/read.phtml?id=81002 http://www.8052.com/forum/read.phtml?id=76017 It is particularly important in this type of application because, if you end up with trash in your flash, it could be completely and utterly useless. You need to ensure that you always have good code to fall-back to - at least enough to re-try the update... |
Topic | Author | Date |
Use SRAM as code memory. | 01/01/70 00:00 | |
Yes, but | 01/01/70 00:00 | |
thanks for answer | 01/01/70 00:00 | |
ibid | 01/01/70 00:00 | |
There are so many options... | 01/01/70 00:00 | |
Answer partially wrong: Can't Write CODE | 01/01/70 00:00 | |
No need for switching | 01/01/70 00:00 | |
Oh yes... | 01/01/70 00:00 | |
Take care - wherewer your code is :-) | 01/01/70 00:00 | |
Once again thanks | 01/01/70 00:00 | |
Self-modifying code | 01/01/70 00:00 | |
Self-modifying code - good or bad | 01/01/70 00:00 | |
Self-modifying code | 01/01/70 00:00 | |
90:10 rule | 01/01/70 00:00 | |
In System Programming Application Note | 01/01/70 00:00 | |
In-System v. In-Application Programming | 01/01/70 00:00 | |
IAP v ISP | 01/01/70 00:00 | |
Philips IAP | 01/01/70 00:00 | |
It's easier with Atmel![]() | 01/01/70 00:00 |