> Not really. The script that would have to be used is "post_reset_run", I > guess. Overriding this with something that does a "run_and_halt" would > prevent the same config from doing a plain "reset_run", wouldn't it?
I think there are two things going on here: - the target config script must be able to implement reset halt/init/run to the users expectations. This is possible today and more powerful tools care coming up. run_and_halt/init are not required for this, nor are they powerful enough to solve anything but trivial problems. - user convenience. The user may want to reset & run & halt or reset & run & init for whatever reason. Here there are other tools available. Importantly the target configuration script can define whatever commands it needs to that are appropriate for convenient handling of that target. run_and_halt/init are not required, nor the best tool to solve this problem. It is important that the definition of reset is as crisp as possible, both from the point of view of those that need to implement reset handling(scripts) and from the users point of view and here reset_run_halt/init is muddying matters in that it appears that they implement something that is inheritely impossible to achieve by other means. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
