??? 03/06/07 16:52 Modified: 03/06/07 16:55 Read: times |
#134388 - All manufacturers have problems Responding to: ???'s previous message |
Richard said:
Gee ... I've got no idea what these AVR-Freaks have encountered. Those are ATMEL (yechhh!) parts. Richard, ALL manufacturers suffer from flash code memory corruption. Here are two examples more: http://www.sst.com/downloads/app_note/S72042.pdf and even the "Rolls-Royce": http://www.cygnal.org/ubb/Forum1/HTML/000676.html Richard said:
Once upon a time, the PIC folks had reset issues, too, but they've managed to fix that without a supervisor, though their manufacturer does produce one. They still have problems. Richard said:
Despite the fact that the supervisor produces a 90% reduction in ONE of the, perhaps, multiple problems, there's no guarantee that it's done even that until someone tests, and rigorously so, a set of multiple hundreds for a significantly large number of iterations as to make the one or two failures per thousand, statistically significant. Until someone does that, we're all shooting in the dark. We are always in the dark! And even if YOU will find a slew rate related problem or anything else, it will only be valid for YOUR certain setup. More: Assume you find out, that an external oscillator and your reset scheme with the flip-flop and XOR-feedback will help you in your situation, then I still can hardly implement this in our products. Why? I had to tell my boss: "Look, Boss, there's guy in Denver, Colorado, and he found out, that we need an external oscillator and a reset scheme using a flip-flop and XOR-feedback to solve the flash problem." Then he will state: "But we never had any problems with the flash since we use the reset chip!" I could never explain why to use your scheme... Kai |