Dirk Behme wrote:
> David Brownell wrote:
>
>> Update the DaVinci target configs so they have JTAG post-reset
>> event handlers which:
>>
>> - run the 100 JTAG clocks ICEpick wants
>> - ensure the ARM (and ETB) taps are enabled
>> ---
>> The OMAP3 post-reset handlers should probably do something
>> similar, doing the (updated) omap3_dbginit stuff so that it
>> no longer needs to be done by hand.
>>
>
> Most probably, I miss the obvious ;)
>
> But in omap3530.cfg doing something like
>
> jtag configure $_CHIPNAME.jrc -event post-reset \
> "runtest 100; omap3_dbginit"
>
> obviously fails due to 'reset' command in omap3_dbginit with
>
> Runtime error, file "lib/openocd//target/omap3530.cfg", line 0:
>
> 'reset' can not be invoked recursively
>
> with omap3_dbginit being:
>
> proc omap3_dbginit { } {
> poll off
> reset
> sleep 100
>
> jtag tapenable omap3530.dap
> targets
> # General Cortex A8 debug initialisation
> cortex_a8 dbginit
> # Enable DBGU singal for OMAP353x
> omap3.cpu mww 0x5401d030 0x00002000
> poll on
> }
>
> Seems that we need some clever order of reset/omap3_dbginit/-event
> post-reset I don't see at the moment :(
>
> Best regards
>
> Dirk
>
>
> _______________________________________________
> Openocd-development mailing list
> [email protected]
> https://lists.berlios.de/mailman/listinfo/openocd-development
>
I think the obvious solution would be to remove the reset call from
omap3_dbginit
Regards
Magnus
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
