We can, and sometimes we want to, write to  memory while the CortexA8 
core is running,
but for gbd  to load a program and the i-caches to be cleared to core 
must be halted.

So I think there must be a monitor halt after the monitor omap3_dbginit
>
> No. I just do
>
> > arm-none-linux-gnueabi-gdb
>
> with
>
> > cat .gdbinit
> echo Setting up the environment for debugging gdb.\n
>
> # This connects to OpenOcd at localhost:3333
> target remote localhost:3333
>
> # Increase the packet size to improve download speed.
> set remote memory-write-packet-size 1024
> set remote memory-write-packet-size fixed
>
> #omap3_dbginit must be run in OpenOCD after every reset
> monitor omap3_dbginit
>
monitor halt

> # Load the program executable called "LEDblink"
> load LEDblink
>
> # Load the symbols for the program.
> symbol-file LEDblink
>
> Dirk
>
Magnus

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

Reply via email to