On Thu, Nov 6, 2014 at 5:21 PM, Uwe Bonnes <
[email protected]> wrote:

>
> So probably after the detection of the CPU type, but before the callout to
> "
> -event examine-end" the communication hangs. Could the callout be made
> earlier? Or another event be sent right after detection? Or is there
> something wrong with my effort?
>
>
Success or failure will probably depend on the timing of the target
entering or leaving sleep, relative to OpenOCD's attempt to examine it.
It's not going to be robust.

The solution is to add connect_assert_srst to your reset_config, then
OpenOCD will assert reset before and during examination and you get control
with the chip halted at the reset vector.

/Andreas
------------------------------------------------------------------------------
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to