>> >> The overrun appears to happen after I call resume. > > > So what does the code you're resuming do? It's expected for the debugger to > lose debug connectivity if the code puts the core into sleep mode. Or > disable JTAG pins for that matter. Try stepping instead of resuming and see > how far you get. >
Turns out the problem is that the ARM code changes it's clock frequency. In my case - the ARM code needs to change the clock to some high speed. But when it comes out of reset the chip will be running at some low speed. What is the best way to handle this? The openocd manual suggests using a reset handler or other tcl code to change the clock. But in my case I need ARM code to do that. Is there some other way? The manual does mention using adaptive clocking - for ARM devices is this the main solution? -Ram ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
