On Monday 25 May 2009, David Brownell wrote:
> - Bugfix the "reset_config" description (it didn't match the code)
To recap, current code says the syntax is:
reset_config signals [combination [trst_type [srst_type]]]
PROPOSAL 1: make it so any of those magic keywords can be provided,
in any order. Example, "trst_and_srst" after "srst_open_drain",
omitting the "separate" combination (which should be the default
in any case).
Why? (a) Makes it easier to override things at the
right level (adapter, board, target). You can just
specify the thing you *know* instead of having to
somehow "know" things earlier in that sequence.
(b) Removing needless error paths is always good;
that sequencing shouldn't matter.
PROPOSAL 2: Add "srst_disable" and "trst_disable", which would
be "sticky" and used to infer the "signals".
Why? Any of {target, board, adapter} could filter
out one of those signals. This makes it easy for
them to declare they've done so, and impossible
for some other component to lie and say the signal
magically re-appeared.
PROPOSAL 3: Make "reset_config" be available only during the
server configuration stage.
Why? Looks to me like there's no valid reason to
change these after server startup. Same may be
true of the [st]rst_delay parameters. Once the
working setup is established, it should stay forever.
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
