> > > > I tried to add support to LPC11XX in vsprog.
> > > > LPC11XX is CortexM0 from NXP.
> > We want "OpenOCD" support, not "vsprog" support,
> > for such things ... :)
SWD is tested working in vsprog, so it's easier to add the
support in vsprog. Actually there is not much difference
between vspr
> > I tried to add support to LPC11XX in vsprog.
> > LPC11XX is CortexM0 from NXP.
We want "OpenOCD" support, not "vsprog" support,
for such things ... :)
> Aha! I think that's exciting! I am most interested in
> LPC13xx, but I
> assume there may be some things in common.
Yes. 13xx is Cortex-M3
I first implement it in vsprog, but more test should be done.
memap access is tested OK by my side, SWD dongle is Versaloon.
IAP call is success including get IDs, prepare/erase/program sectors.
But it seems that the first 1K is not blank after erase.
Write data to first 4K of flash will fail.
I w
simon qian wrote:
> I tried to add support to LPC11XX in vsprog.
> LPC11XX is CortexM0 from NXP.
Aha! I think that's exciting! I am most interested in LPC13xx, but I
assume there may be some things in common.
> If anyone tries to add it to OpenOCD, he can test these differences.
Is your OpenOCD
I tried to add support to LPC11XX in vsprog.
LPC11XX is CortexM0 from NXP.
There is the differences:
1. different ID (of course)
2. tar_autoincr_block is 1K instead of CortexM3's 4K
3. fewer asm code can be used in flash loader
Thumb2 of CortexM0 is subset of thumb2 of CortexM3.
If anyone tries to
