Hi Øyvind and Pavel, Some of the e-mails went into the mailing list digest and I did not get them in sequence. Now that I have read all the e-mails in sequence I understand.
A "reset" will be the same as "reset run". If I want to reset and halt the target, then I have to use "reset run_and_init" explicitly. I agree that this is more intuitive. Thanks, Pieter -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Øyvind Harboe Sent: 18 July 2008 10:17 AM To: Pieter Conradie Cc: [EMAIL PROTECTED]; openocd-development@lists.berlios.de Subject: Re: [Openocd-development] Retire reset_mode option to target On Fri, Jul 18, 2008 at 10:13 AM, Pieter Conradie <[EMAIL PROTECTED]> wrote: > Hi Øyvind and Pavel, > > Sorry for being obtuse, but I am still not exactly clear on what you are > trying to achieve. I'm trying to make commands do predictable and expected things across configurations. I don't have to read the fine print in configuration scripts to figure out what "halt" and "resume" does. Why should reset be any different? > Let's take the AT91SAM7S as an example. The only way to halt this target > and get it into a known "reset" state is to define the configuration as: Since I'm currently leaning towards "reset run" for the reasons Pavel pointed out to me, I don't really have many comments on this anymore. Note that "reset init" is automatically tranlsated to "reset run_and_init" for the case where srst pulls trst. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer Notice This email is intended for the addressee only and may contain legally privileged and/or confidential information. If you have received this email in error and are not the intended recipient, you are hereby informed that you are not entitled to read, broadcast, distribute or in any manner whatsoever use the contents of this email or any attachments thereto. You are requested to please notify Psitek that you have received the email and then delete it. Unless clearly stated otherwise, the content and sentiments expressed in this email or any attachments thereto are those of the sender and not of Psitek (Proprietary) Limited. Psitek does not accept liability for any damages, loss or expense of any nature whatsoever arising (a) out of or in connection with the email or any attachments thereto and/or (b) from any act or omission by the recipient relying upon the content of the email or attachments. Psitek further disclaims liability for any damages caused by computer and/or software viruses. Should this email contain the terms of a contract, no binding agreement will result until such time as a written (hardcopy) document is signed on behalf of Psitek. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
