> >
> > This is why people often put a small reset delay in the
> startup file
> > for the
> > str7 to compensate for this.
>
> Last I checked there was a str710.cfg file which we use. How
> do you set his "small reset delay" you speak of? Would this
> be jtag_n[st]rst_delay? Should this be in str710.cfg?
>
No this reset delay is in your str7 startup code, eg.
.macro StartupDelay delay_value
ldr R1, =\delay_value
ldr R2, =0
__StartDelay:
sub R1, R1, #1
cmp R1, R2
bhi __StartDelay
.endm
#*************************************************************************
# Reset Handler Entry Point
#*************************************************************************
_start:
StartupDelay 500000
.....
Another way is to put a while(1) at the reset vector. As soon as the device
is halted
set the pc to the next instruction.
The problem with letting a small amount of code run is that some peripherals
may get configured.
Even a soft_reset_halt will not help here, but the above delay will
guarantee that none of your
code is executed until the debugger has caught up.
Cheers
Spen
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
