David Brownell wrote:
> > Basically, I'd like OpenOCD to refuse to start until the script
> > defines the clock rate.
> 
> Script is the right place, yes.  Not *ANY* of
> the adapter drivers, or embedded in OpenOCD
> framework code either.

I like this. And specifically I think that trying to set speed in
those files must generate a fatal error.


Laurent Gauch wrote:
> Bad! For me.
..
> The best, for me, is to fix a low 1MHz frequency as default
> frequency without the use of RTCK (disabling RTCK) at the startup

Isolating and enforcing exactly where the setting is allowed is of
course a neccessary step in the right direction.

Usability may be slightly worse in the immediate term with such a
change, but having the infrastructure in place to allow verifying
that settings can only be done in the correct fashion in the correct
places is a fundamental requirement for improving usability *later*
e.g. with an algorithm that selects a safe default frequency.


//Peter
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to