On Tuesday 24 November 2009, Zach Welch wrote: > I think the subject of "Embeddeding Open" > needs to be addressed more comprehensively in its own section.
I'm not disagreeing ... but what would be in that section? Some of the folk who've done some of this should chime in... Just for kicks, I started a cross-compile for a Cortex-M3, and got this error from configure: configure: error: C compiler cannot create executables Hrm, OK, I'll try some different flags then, this was just for test building, but ... maybe stuff like that should be covered. I suspect for "real embedded" targets, which is to say not just hosted on an embedded Linux, there will need to be build environment tweaks like: - Letting some other component finish linking the flash image. - Selective build/link for cpu, flash, and jtag drivers. A Thumb2 build for Cortex-A8 (not M3!) involved over half a meg of code, which is way too huge to fit into its portion of a 128 KB flash. - Facilitating custom JTAG (mini?) drivers. - Disabling filesystem-dependent commands, since there is no file system! - Allowing different ways to provide image data, like through USB endpoints or TCP sockets That's for starters. I suppose another thing to address is what is meant by an "embedded host". - Dave _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
