Esto es lo que dice la documentación:
— Command: reset
— Command: reset run
— Command: reset halt
— Command: reset init
Perform as hard a reset as possible, using SRST if possible. All defined
targets will be reset, and target events will fire during the reset sequence.
The optional parameter specifies what should happen after the reset. If there is
no parameter, a reset run is executed. The other options will not work on all
systems. See Reset Configuration.
run Let the target run
halt Immediately halt the target
init Immediately halt the target, and execute the reset-init script
Abro OpenOCD, luego en otro terminal ejecuto arm-none-eabi-gdb end ejecuta monitor reset halt para decirle al objetivo que reinicie y detenga el procesador, para luego configurar braekpoints y correr.
Sin embargo, la respuesta del procesador suele ser diferente:
(gdb) monitor reset halt
JTAG tap: sam7x512.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787, part: 0xf0f0, ver: 0x3)
srst pulls trst - can not reset into halted mode. Issuing halt after reset.
target state: halted
target halted in ARM state due to debug-request, current mode: FIQ
cpsr: 0x600000d1 pc: 0x00000050
NOTE! DCC downloads have not been enabled, defaulting to slow memory writes. Type 'help dcc'.
NOTE! Severe performance degradation without fast memory access enabled. Type 'help fast'.
Otras veces, va por este camino:
target state: halted
target halted in ARM state due to debug-request, current mode: Abort
cpsr: 0x600000d7 pc: 0x00000044
Otra vez más (dentro de la misma ejecución, acabo de abrir gdb y ejecutar el reinicio del monitor detener un montón de veces):
target state: halted
target halted in ARM state due to debug-request, current mode: Undefined instruction
cpsr: 0x600000db pc: 0x00000038
¿Qué son esos estados?