--- On Fri, 12/3/10, Spencer Oliver <[email protected]> wrote:
> > On 02/12/2010 12:42, [email protected] > wrote: > >> "Spencer Oliver"<[email protected]> > napisał(a): > >> > As we know the current behaviour of cortex_m3 > reset_config is to > >> > override the std 'reset_config' setting - I've lost track of the discussion here, but this sounds wrong. The only time commands should care about "std" (standard)/default settings is when restoring them. Otherwise, they should work with *current* settings. One bug that old versions of "rset_config" had was that they'd mangle unrelated settings ... e.g. you couldn't update SRST handling without trashing TRST handling (or similar; now fixed.). The two (?) reset implementation options on M3 parts should respect the same policy sanity: don't muck with options that could/should be orthogonal, and don't embed "knowledge" that may already be wrong, and will likely become so before long as new boards, silicon, and JTAG adapters roll out. - Dave > >> > This does create an issue for all the > luminary scripts however. > >> > They would need the 'reset_config srst_only' > removing and this would > >> > break all the older scripts in the wild. And this is an example o how I've lost the thread here. Not all Stellaris boards have SRST, since that JTAG command works on those M3 parts. Some have it, but not TRST ... So again, don't be hard-wiring incorrect "facts" anywhere. _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
