On 2010-11-12 12:16, Spencer Oliver wrote:
Mmm - Think i may be incorrect here, the cortex_m3 reset_config does
override the standard reset_config.
Looking back this was done so it did not break any stellaris scripts
that define reset config.
Would that be enough to change behavior so that hardware reset would be
used if available, no matter what option of "cortex-m3 reset_config" was
selected? Option to select "srst" may be then removed, and this command
could be renamed to "soft_reset_config".
Another solution is to change "cortex-m3 reset_config" to capabilities
model - you list all supported reset options, OpenOCD selects what's
best. For example "cortex-m3 reset_config srst sysresetreq vectreset"
would define a chip that can use any method - if srst is available, use
that, else use sysresetreq. "cortex-m3 reset_config srst vectreset"
would define a chip that does not handle sysresetreq, so in case of lack
of srst, use vectreset. As it's hard to imagine a chip that has no srst,
that option can be removed too, and command renamed some way.
What do you think?
4\/3!!
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
