> > > > 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 vsprog and openocd when doing flash operation. Vsprog uses a parallel operation which can download data to SRAM while the kernel is writing data to flash. ADIv5 framework is almost the same.
ADIv5 works fine with CortexM0 as I test, only necessary change is that tar_autoincr_block should be 1K instead of 4K. Remove 32-bit instruction in flash loader, use 16-bit ones. Then it simply works, tested on SRAM reading and writing. 2010/6/2 David Brownell <davi...@pacbell.net> > > > 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 (ARM v7m), while > the M0 is ARM v6m -- a subset. I expect > the initial quick hack for M0 support will > be to treat it as an M3 ... according to the > v[67]m arch specs, it looks like that will > work OK from the debug perspective. > > From the programming perspective, the most > obvious difference is that M0 basically uses > the Thumb-1 instruction set not Thumb-2 ... > so there aren't as many usable registers (the > "upper" 8 registers are very limited), and code > generation needs more instructions, often using > two 16-bit opcodes instead of one 32-bit opcode. > > The big similarity between the 11xx and 13xx > chips is that they don't support JTAG: SWD-only. > So OpenOCD support for both is on hold until the > SWD patches are more complete. > > > > > > > > If anyone tries to add it to OpenOCD, he can test these differences. > > Yep, this is absolutely on the agenda for the > SWD patches I'm working on. 13xx will work first, > since it's "just" another Cortex-M3 chip. > > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > -- Best Regards, SimonQian http://www.SimonQian.com <http://www.simonqian.com/>
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
