On Tue, 2009-11-24 at 13:21 -0800, David Brownell wrote: > 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...
For the record, I think it becomes important to distinguish between "light" and "heavy" embedded. Right now, we can support the later by way of embedded ARM (uC)Linux or eCos. The former requires addressing the points you list below. Each requires its own type of documentation. For now, $SUBJECT relates to the heavier platforms. > 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". Yup. There is a lot of work to do to provide these things in the general case, and these are worthy goals to consider. Today, we have the ZY1000's eCos-related support, but we should be considering other use cases with even less resources. Personally, I think strategic documentation will be pivotal to executing such a project, as the issues merit full enumeration and prioritizing... outside of the style guide or this thread. For now, feel free to add a section to the TODO list with your points, as I do not recall the above existing there with such specificity. Cheers, Zach _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
