[meta-ti] boot fail in omap3 evm

[deepak vijay]

Hi Denys,
I tried the lower version of yocto (1.2 denzil) but it was its not
supporting the meta-ti layer which contains omap3evm support. It was
throwing some un known error and os incompatibility error also. So I
dropped  the idea of using lower versions.
So I was planing to move to next suggested option and I find out that only
2.6.x kernel recipe (linux-omap_2.6.37.bb) support omap3evm. Not the higher
versions.
Please help me to resolve this problem.
How to add support for omap3evm to the higher kernel recipes in meta-ti
layer.

All the responses are appreciated.

Regards,
Deepak


On Fri, May 16, 2014 at 11:15 PM, Denys Dmytriyenko <denys at ti.com> wrote:

> On Fri, May 16, 2014 at 12:33:31PM +0530, deepak vijay wrote:
> > Hi all,
> > I am new to yocto project .
> > I have downloaded the beaglebone-daisy-11.0.0 and add meta-ti layer
> whith a
> > commit id of 4e5bcb5712bf2f0587ceff908d75177e410de48f.
> > And when I build it for omap3evm and boot the images of the build I am
> > getting the following dump logs when I enable earlyprintk without
> changing
> > any other configurations.
> >
> > And one of the member suggested me that use lower version of gcc like gcc
> > 4.3. But I didn't find any way to use it. Because only gcc 4.8.2 recipe
> is
> > there in the layer.
>
> You can grab one of the older Yocto releases, e.g. 1.2 denzil has gcc-4.6
> Otherwise there were/are some layers still with gcc-4.5 support, at least
> in
> the external toolchain form...
>
> On the other hand, may I ask why do you want to build such an old kernel
> with
> the latest Yocto setup and the toolchain? Can you just use one of the
> recent
> 3.x kernels?
>
> --
> Denys
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20140519/79481f4b/attachment.html>