[Gnuk-users] [PATCH] Simplify README instructions for OpenOCD usage

[NIIBE Yutaka]

Paul Fertser <fercerpav at gmail.com> writes:
> On Wed, Feb 01, 2017 at 05:22:47PM +0900, NIIBE Yutaka wrote:
>> >  Inside GDB, we can connect OpenOCD by:
>> >  
>> > -  (gdb) target remote localhost:3333
>> > +  (gdb) target extended-remote localhost:3333
>> 
>> I don't apply this for now, as I don't understand its effect.  Are there
>> any good thing with extended-remote for our specific use case?
>
> extended-remote tells GDB that it can use "run" (restart the target
> and let it run) and "start" (place a temporary breakpoint on main()
> and do "run") commands. I find that quite useful for debugging.

Thank you.  I understand.  I added the line, leaving "target remote".  I
agree that it's useful.  I'm not sure if it is exactly same as hardware
RESET.

I'm afraid that by "run" command, if it works as software level,
registers in some hardware module might be different (than hardware
RESET) and it might behave differently.  If the driver for a hardware
module is written robust enough, this is no problem, though.
--