Hi,

one advantage of the user specifying the reset parameter to the target is
that openocd knew what
default behaviour the user wanted - often reset halt.

for example the gdb server uses this knowledge in the following two places.
detach_mode and extended remote protocol (R packet).

now when either of these are called gdb will perform a reset (which now will
run the target).
This is not always the desired operation - especially when developing an
app.

I know gdb will perform a halt when connecting - but this will only ever be
done once for the extended remote protocol.

save = target->reset_mode
target->reset_mode = RESET_INIT;
target_process_reset(connection->cmd_ctx);
target->reset_mode = save

i suppose would solve the problem, but is this inline with the new reset
ideas?
But then the user may not want this behaviour - how do they specify what
behaviour they want?

Cheers
Spen

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to