yocto SDK for imx6 sabrelite board. (armel vs armhf)

yocto SDK for imx6 sabrelite board. (armel vs armhf)

[ssinfod ssinfod]

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

Hello,

I just built an image with SDK for the imx6 sabrelite.  (ie: MACHINE ??=
'imx6qsabrelite')
Command: bitbake core-image-full-cmdline -c populate_sdk

I noticed that the SDK toolchain is based on "gnueabi" instead of
"gnueabihf".

Here is the list from the opt directory:
dev@dev-i3:/opt/poky/1.6+snapshot$ ls
environment-setup-cortexa9hf-vfp-neon-poky-linux-gnueabi
site-config-cortexa9hf-vfp-neon-poky-linux-gnueabi
sysroots
version-cortexa9hf-vfp-neon-poky-linux-gnueabi
dev@dev-i3:/opt/poky/1.6+snapshot$
version-cortexa9hf-vfp-neon-poky-linux-gnueabi

I thought that the imx6 was a armhf device.
Why is the default toolchain using "gnueabi" and not "gnueabihf" for the
sabrelite target ?

Is there a way to change the SDK to use gnueabihf ?

In fact, I find it scary that the default toolchain is not armhf. What is
the reason behind that ?
Is it because of the video (GPU/VPU) driver ?

Thanks,
ssinfod

[-- Attachment #2: Type: text/html, Size: 1294 bytes --]

Re: yocto SDK for imx6 sabrelite board. (armel vs armhf)

[ss infod]

[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]

Does anyone have any input on this ?

Thanks
ssinfod


On Tue, Aug 12, 2014 at 8:02 AM, ssinfod ssinfod <ssinfod@gmail.com> wrote:

> Hello,
>
> I just built an image with SDK for the imx6 sabrelite.  (ie: MACHINE ??=
> 'imx6qsabrelite')
> Command: bitbake core-image-full-cmdline -c populate_sdk
>
> I noticed that the SDK toolchain is based on "gnueabi" instead of
> "gnueabihf".
>
> Here is the list from the opt directory:
> dev@dev-i3:/opt/poky/1.6+snapshot$ ls
> environment-setup-cortexa9hf-vfp-neon-poky-linux-gnueabi
> site-config-cortexa9hf-vfp-neon-poky-linux-gnueabi
> sysroots
> version-cortexa9hf-vfp-neon-poky-linux-gnueabi
> dev@dev-i3:/opt/poky/1.6+snapshot$
> version-cortexa9hf-vfp-neon-poky-linux-gnueabi
>
> I thought that the imx6 was a armhf device.
> Why is the default toolchain using "gnueabi" and not "gnueabihf" for the
> sabrelite target ?
>
> Is there a way to change the SDK to use gnueabihf ?
>
> In fact, I find it scary that the default toolchain is not armhf. What is
> the reason behind that ?
> Is it because of the video (GPU/VPU) driver ?
>
> Thanks,
> ssinfod
>
>

[-- Attachment #2: Type: text/html, Size: 1767 bytes --]

Re: yocto SDK for imx6 sabrelite board. (armel vs armhf)

[Gary Thomas]

On 2014-08-13 08:15, ss infod wrote:
> Does anyone have any input on this ?
>
> Thanks
> ssinfod
>
>
> On Tue, Aug 12, 2014 at 8:02 AM, ssinfod ssinfod <ssinfod@gmail.com <mailto:ssinfod@gmail.com>> wrote:
>
>     Hello,
>
>     I just built an image with SDK for the imx6 sabrelite.  (ie: MACHINE ??= 'imx6qsabrelite')
>     Command: bitbake core-image-full-cmdline -c populate_sdk
>
>     I noticed that the SDK toolchain is based on "gnueabi" instead of "gnueabihf".
>
>     Here is the list from the opt directory:
>     dev@dev-i3:/opt/poky/1.6+snapshot$ ls
>     environment-setup-cortexa9hf-vfp-neon-poky-linux-gnueabi
>     site-config-cortexa9hf-vfp-neon-poky-linux-gnueabi
>     sysroots
>     version-cortexa9hf-vfp-neon-poky-linux-gnueabi
>     dev@dev-i3:/opt/poky/1.6+snapshot$ version-cortexa9hf-vfp-neon-poky-linux-gnueabi
>
>     I thought that the imx6 was a armhf device.
>     Why is the default toolchain using "gnueabi" and not "gnueabihf" for the sabrelite target ?
>
>     Is there a way to change the SDK to use gnueabihf ?
>
>     In fact, I find it scary that the default toolchain is not armhf. What is the reason behind that ?
>     Is it because of the video (GPU/VPU) driver ?

What makes you think it's not HF already?  (hint - the hf is
part of the CPU model cortexa9hf)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: yocto SDK for imx6 sabrelite board. (armel vs armhf)

[David Chirgwin]

----- Original Message -----
> From: "Gary Thomas" <gary@mlbassoc.com>
> To: meta-freescale@yoctoproject.org
> Sent: Wednesday, 13 August, 2014 3:22:24 PM
> Subject: Re: [meta-freescale] yocto SDK for imx6 sabrelite board. (armel vs armhf)
> 
> On 2014-08-13 08:15, ss infod wrote:
> > Does anyone have any input on this ?
> >
> > Thanks
> > ssinfod
> >
> >
> > On Tue, Aug 12, 2014 at 8:02 AM, ssinfod ssinfod <ssinfod@gmail.com
> > <mailto:ssinfod@gmail.com>> wrote:
> >
> >     Hello,
> >
> >     I just built an image with SDK for the imx6 sabrelite.  (ie:
> >     MACHINE ??= 'imx6qsabrelite')
> >     Command: bitbake core-image-full-cmdline -c populate_sdk
> >
> >     I noticed that the SDK toolchain is based on "gnueabi" instead
> >     of "gnueabihf".
> >
> >     Here is the list from the opt directory:
> >     dev@dev-i3:/opt/poky/1.6+snapshot$ ls
> >     environment-setup-cortexa9hf-vfp-neon-poky-linux-gnueabi
> >     site-config-cortexa9hf-vfp-neon-poky-linux-gnueabi
> >     sysroots
> >     version-cortexa9hf-vfp-neon-poky-linux-gnueabi
> >     dev@dev-i3:/opt/poky/1.6+snapshot$
> >     version-cortexa9hf-vfp-neon-poky-linux-gnueabi
> >
> >     I thought that the imx6 was a armhf device.
> >     Why is the default toolchain using "gnueabi" and not
> >     "gnueabihf" for the sabrelite target ?
> >
> >     Is there a way to change the SDK to use gnueabihf ?
> >
> >     In fact, I find it scary that the default toolchain is not
> >     armhf. What is the reason behind that ?
> >     Is it because of the video (GPU/VPU) driver ?
> 
> What makes you think it's not HF already?  (hint - the hf is
> part of the CPU model cortexa9hf)
> 
You can try this test if you are unsure:
  readelf -A /proc/self/exe

If the text "Tag_ABI_VFP_args" is present, then the system is using ARMHF. Otherwise it will be ARMEL.

Dave C
> --
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
> 
Blue Chip Technology Limited. Chowley Oak Lane, Tattenhall, Chester, Cheshire CH3 9EX Tel: 01829 772000 Registered in England 3110403 Vat No: GB 618 374134