[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openembedded-core
Subject:    [OE-core] Building firmware recipe with different toolchain
From:       raj.khem () gmail ! com (Khem Raj)
Date:       2015-10-30 0:45:01
Message-ID: CAMKF1so8xvvEYkOhgcgepnN06uSRDAjcCwwj=HyAvrVvSK0m5A () mail ! gmail ! com
[Download RAW message or body]

On Thu, Oct 29, 2015 at 3:19 PM, Logan Buchy <logan.buchy at gmail.com> wrote:
> Hi guys,
>
> I have a board which has both a Cortex-A9 and a Cortex-m0+,  The Cortex-A9
> is running the main application with the Linux kernel while the cortex-m0+
> is present to handle some real-time control tasks.
>
> Currently, I am building the cortex-m0+ firmware separately and saving the
> artifacts to an ftp server.  A bb recipe grabs the correct binary from the
> server and incorporates it into the rootfs of the cortex-a9 image.
>
> This works for now, however it makes it a bit more difficult to do
> development on the cortex-m0+ firmware.  I am looking at augmenting the
> recipe so that it will pull the source and build the firmware.  The
> complication is that since it is a completely different architecture, I will
> need to use a different toolchain, CFLAGS and complier options.  I am not
> even sure if this is possible or where to start.
>
> Anyone have any ideas?
>

look into baremetal toolchain in latest OE may be that can help.

> Thanks
> Logan
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[prev in list] [next in list] [prev in thread] [next in thread]