On Tue, 2009-07-07 at 23:18 +0200, Øyvind Harboe wrote: > >> How about modifying reset_config to simply *set* the > >> state based *only* on the arguments to reset_config, > >> ignoring the current reset_config state? > > > > That makes it impossible to combine constraints that come > > from different spots, so I don't like that notion. > > That assumption is false. This can be done in tcl. Look > at how tapid's are done. > > The reset_config should be a primitive, not a new programming > paradigm. > > > Is there some problem the current scheme has? > > Yes. > > Lets say I have no idea what the default target script does, > but I know *precisely* what my board needs: srst_only > srst_pulls_trst. > > What the heck should I write in the board config file to be *sure* > to override anything that the board config file defined?
I would intuitively expect to be able to write: reset_config none srst_only srst_pulls_trst The key bit is the 'none', which blows it back to a cleared state. Cheers, Zach _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
