-------- Original-Nachricht -------- > Datum: Fri, 18 Jul 2008 09:56:34 +0200 > Von: "Øyvind Harboe" <[EMAIL PROTECTED]> > An: "openocd-development@lists.berlios.de" > <openocd-development@lists.berlios.de> > Betreff: [Openocd-development] Make "reset run" default?
> Any objections? > > I'd like to make "reset run" the behaviour of "reset" without arguments. > > Pavel(willingly or not :-) convinced me that this is the right thing to > do. > > The reason is simply that a target in a halted state after a reset > raises a lot of questions: is the target initialized or not? Did it run > part of the startup code? > > "reset run" is unambigious. > > The target was reset and it is currently running. If it is halted, then > it was because the application hit a breakpoint/exception and it > has nothing to do with the configuration. > > reset still takes init/halt/run_and_halt/run_and_init as arguments > and they always do what the argument says. Do we still have a "daemon_startup" setting? If we do, we need the reset_mode as well. Otherwise there's no way of specifying what that "daemon_startup reset" is supposed to do. I really have no idea what happend during all the changes to the reset/startup stuff. Another question that comes to my mind is this - do we really need "reset"? Apparently different people expect it to do different things, so maybe we should drop it? One comment regarding the use of TCL in this discussion: I completely dislike the idea of having to write TCL code to be able to conserve functionality that used to work before. Scripting isn't everyone's favourite hobby... so please - keep TCL out of the OpenOCD. Offer it as an interface /to/, but don't make it an integral part. Regards, Dominic -- -- Dominic Rath <[EMAIL PROTECTED]> _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
