What I just posted has the M0 as a complete copy and paste of the M3 code, so the entire thing is duplicated. However, that was more because we wanted to test the M0 code but still be able to work with the M3. The M3 is almost a perfect super set of the M0, so I don't think it would be hard to avoid duplicating everything. However, there are a couple of parts where it would be unavoidable, specificly the Thumb assembly functions. There are also are some more sutle differences (reset handleing, registers, tracing support, interrupts) but none of them are too dramatic.
Thanks, Kevin Kiningham On Fri, Jun 10, 2011 at 4:56 PM, Øyvind Harboe <oyvind.har...@zylin.com>wrote: > What would it take to convert cortex-m3.c to cortex-m.c and avoid > code duplication like we had for cortex-a8/9.c....? > > Is there a lot of code duplication here? I haven't looked. > > -- > Øyvind Harboe > > Can Zylin Consulting help on your project? > > US toll free 1-866-980-3434 / International +47 51 87 40 27 > > http://www.zylin.com/zy1000.html > ARM7 ARM9 ARM11 XScale Cortex > JTAG debugger and flash programmer >
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
