Sujet : Re: "RESET"
De : blockedofcourse (at) *nospam* foo.invalid (Don Y)
Groupes : sci.electronics.designDate : 25. May 2025, 10:59:17
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <100uplm$1abd9$2@dont-email.me>
References : 1 2
User-Agent : Mozilla Thunderbird
On 5/25/2025 2:07 AM, Theo wrote:
Don Y <blockedofcourse@foo.invalid> wrote:
I don't quite understand the need for "reset" buttons on products.
>
That function is always available by cycling power -- even for devices
where that is difficult for the user (e.g., PoE, BBU, etc.)
>
Shouldn't a device be able to get itself out of a "pickle" without
requiring the user to intervene? Particularly devices that are
intended to "run forever"?
>
I.e., it seems like the presence of a reset button is a tacit admission
that the engineering is "lacking"...
Nowadays 'reset' often means 'reset to factory settings' rather than
'reboot'. The factory settings reset is needed because maybe you forgot the
password and have no other way to reconfigure the thing. Or you need to
make it go back into the initial pairing mode so you can attach it to
another network/etc.
As I said elsewhere, that's different than something that actually RESETS
the processor. You could just as easily have a BUTTON labeled "restore
factory defaults" and a protocol as to when it is recognized, when it
takes effect, etc.
The "reset" that I am talking about tugs on the reset pin of the processor(s)
and ensures it/they return to a known state comparable to initial power up.
It doesn't rely on the software "cooperating" in order to take effect.
Having a physical factory reset button means that somebody with physical
access can always regain access to it. You can also use it to verify
destructive actions (eg 'to wipe all the data, now hold the button') so that
they can't be done remotely.
But, again, that can be labeled as such and INTERPRETED by the software;
not ENFORCED by the hardware.
In practical terms such a button might just be a GPIO rather than wired to a
reset line, and the software pays attention to it at certain times such as
during boot.
Yes. Or, at any other point in the UX.
For more developer-focused devices, a true reset button is also better than
yanking the power cord which can cause wear on the connectors. So when
version 497 of your code crashes you can hit the button and upload v498.
But, you can do that by tacking something across the reset/ground lines.
No need to bear a recurring cost for it.