On Fri, Dec 28, 2012 at 11:00:23AM +0100, Josef Holzmayr wrote:
> From: Thomas Petazzoni <[email protected]>
> > So again, unless you need to make modifications to the firmware, I
> > would probably recommend to go with a pre-built version.
>
> Yes, I would strongly recommend exactly the same.
> On the other hand, I am thinking at the moment about a constellation
> where I have a cortex a9 and a cortex m3 in AMP configuration, and the m3
> firmware is also "under development" or project specific as you put it, and
> not some
> binary blob. So what might be suggestions here?
>
> So far I've come up with
> a) two separate build processes / ptxdist projects
> b) make the m3 build configurable through .in file options and then build by
> Makefile
> c) ???
>
> A penny for your thoughts ;)
See rules/sw-ek-lm3s3748.{in,make} and rules/bare_metal.in for a similar
case with cortex-m3. If you put a DFU firmware loader into the M3 and
connect it via USB, you can even load the firmware in-system.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
[email protected]
