On Tue, Mar 24, 2015 at 12:16:43PM +0100, SevenW wrote:
> The hla newtap stuff was a mix-up from my side. Corrected it in the blog.
> Thanks for pointing it out. I will answer the other questions after a
> bit of testing.

I would appreciate it if you help making upstream lpc8xx.cfg config
directly usable.

Regarding your adapter_khz notes, the usual advice for target config
authors is:

1. add a minimal adapter_khz command, it should be slow enough to
connect to a target running in a typical low-power mode or a target
that was just released from power-on-reset;

2. add a reset-init handler that should manipulate target's PLL in a
way to configure higher core clock based on internal oscillator; after
that an appropriate adapter_khz command is issued;

3. add a reset-start handler with adapter_khz suitable for usage right
after reset.

Both "program" command and default hooks for gdb "load" issue "reset
init" before flashing, so the programming speed with a proper target
config is supposed to be optimal. gdb "load" also leads to "reset
halt" just after flashing to bring the target to a clean initial
state before debugging, of course the adapter_khz needs to be reverted
to a slow value by reset-start. If it's not enough for debugging, add
a breakpoint in GDB that would trigger after your target firmware
configures clocks and issue "mon adapter_khz N, continue" when it's
hit (see "Breakpoint Command Lists").

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to