| ??? 08/03/07 16:12 Read: times |
#142711 - the second example ... Responding to: ???'s previous message |
Jan Waclawek said:
Richard Erlacher said:
Unfortunately, neither of the examples you cite have anyting to do with either RC reset or a supervisor. The second example shows the inadequacy of RC reset quite clearly; as well as shows how the problem is completely removed by proper use of a reset IC. Richard Erlacher said:
I suspect that any number of failures may be attributed to RESET failure due to lack of careful observation. When a supervisor is added, the circuit is changed, and, even the reset behavior may be changed. Does that mean that the problem initially gaining attention was repaired? That's not certain at all! Richard, this slightly insults our engineering capabilities. Please believe me, when I say that I had no intention of insulting anyone. However, your second example DOES, indeed, point to what I've considered to be the REAL problem all along. What sort of proof would persuade you that:
1. without a proper reset, you are in troubles 2. with a proper reset, you still might be in troubles (as there are other influences to the circuit, in extremum, if I smash it with a sledgehammer, even a reset IC won't guarantee proper operation), but if everything else is OK, you are safe. It's not "proof" that I seek, but, rather, a different approach to the analytical logic. Peripherals, including memories, as you point out, need to be protected, but I don't think they need to be protected from the change in Vcc. I have become persuaded that they need to be protected from the MCU. The RESET circuitry doesn't do that if the voltage is fluctuating slowly. I believe, and perhaps you'll agree, that the "reset-related" difficulties that people describe, can also be attributed to power-down-related misbehavior of the MCU, at a time when the effect of RESET is undefined, namely, when Vcc is falling and outside the range within which the MCU's behavior is characterized. Richard Erlacher said:
Your examples do point up a potentially serious problem, namely that different components will behave differently as power is lost. CMOS MCU's can tolerate quite low voltages, and, additionally, can draw power from their inputs. Sure. As I stated above, the reset not protecting the MCU; it's protecting the peripherals (including memories). Richard Erlacher said:
Perhaps more attention should be given to Vcc rise and fall times, and management of the entire system during brownout and not just the MCU. Yes and not. You can relatively simply influence the minimum rise/fall times of VCC - simply add more capacitance. In most of the applications you cannot (or is very impractical to) influence the maximum rise/fall times of VCC; the circuit shall handle any. JW in the cited example Jan Waclawek said:
The second case involved an RC-resetted 8031 (MHS branded, but I don't think it does matter) in a coin operated device. It had a NVRAM atttached to keep the bookkeeping, plus an electromechanical counter. The complaint was, that regularly a few coins were missing. The reason (found after a lot of investigation) was, that when the board was powered down, the peripherals (74LS) died earlier than the '31 and the latter got the impression that a coin is on it's way inside and succeeded to record that into the NVRAM. Upon powerup, it updated the bookkeping and pulsed the counter... The error did not exhibit itself on the workbench, where the 5V was switched and died away much faster than in the actual machine, which was switched on/off on by pulling the power cord... Jan, I believe the problem to which everyone likes to refer as the RESET problem, the REAL issue is Vcc rise and fall time, not to the logic or the external peripherals, but to the MCU, because that's the engine that can run away and do things while power is fluctuating. I believe that these problems will "go away" if a RESET/Supervisor IC is used not just to assert RESET, the consequence of which is not so well defined, but to stop the oscillator and/or lower Vcc to within a silicon junction of GND. It's easier to use the negative-RESET from, say, a MAX1232 to stop the oscillator than it is to drive a transistor with the positive reset, processed in some as yet undefined way to delay it so it really can generate a RESET pulse to the MCU when appropriate, but dropping Vcc nearly to GND each time the RESET signal is asserted might provide a clue. I do believe these problems are infrequent enough that truly testing and monitoring a circuit, in a way that would make the result applicable to a large majority of other circuits, might be quite a challenge. I've never doubted that there's an inherent weakness in Intel's approach of using positive-going reset and interrupt signals to its processors, but I also believe that the problems often attributed to RESET in this forum are probably less RESET-related and more Vcc-rise/fall-time related. I'd like to shift the focus of this particular thread, which is very relevant to this set of problems, from a virtual argument over whether use of a RESET/Supervisor IC is warranted, to a more precise discussion of how the problems associated with RESET are observed and how their "solutions" are verified. I'm presently persuaded that the problems are cursorily observed, in most cases, without any thorough study, and the "fix" of introducing a RESET/Supervisor IC produces a significant change in circuit behavior that the technician/engineer implementing it finds to be a relief, and, therefore, gives it his blessing, despite the fact he's actually done no thorough, rigoroous testing to verify that the "problem" itself has been alleviated. He's simply happy that the obvious observability of the perceived problem has been shifted in some way. RE |



