imx6UL evk with kernel 4.1

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

imx6UL evk with kernel 4.1

Jump to solution
4,818 Views
matt67
Contributor III


Hello all,

I'm testing the imx6UL evk with yocto and I'm wondering if it is easy to change the kernel provider to build 4.1 kernel.

Currently with jethro, the machine conf of imx6UL evk uses the linux-imx (which is 3.14) and I would like to switch to 4.1 kernel.

What do you think about that ? and what's the easiest way to do it (changing virtual/kernel provider to linux-flsc) ?

Regards,

Matt

Labels (2)
Tags (3)
1 Solution
13 Replies
2,195 Views
qinghuazhu
Contributor III

Now you can download new version yocto from http://freescale.github.io/

0 Kudos
Reply
2,195 Views
matt67
Contributor III

Hello Fabio,

Thanks for your support, I created a custom recipes with this version of the kernel and it worked !

2,195 Views
yichen
Contributor I

Hello Matt,

I have the same problem

Do you change setting like

repo init -u git://git.freescale.com/imx/fsl-arm-yocto-bsp.git -b imx-4.1.15-1.0.0_ga

I use these setting

but my kernel is 3.0.35

0 Kudos
Reply
2,195 Views
matt67
Contributor III

Hey,

Here is the the content of my manifest.xml

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

  <default sync-j="2"/>

  <remote fetch="git://git.freescale.com/imx" name="fsl-release" />

  <remote fetch="git://git.yoctoproject.org" name="yocto"/>

  <remote fetch="git://github.com/Freescale" name="freescale"/>

  <remote fetch="git://git.openembedded.org" name="oe"/>

  <remote fetch="git://github.com/OSSystems" name="OSSystems"/>

  <remote fetch="git://github.com/meta-qt5"  name="QT5"/>

  <project remote="yocto" revision="dd0ba9ea4a11ab15348d4fe3574e4b28784db82f" name="poky" path="sources/poky"/>

  <project remote="yocto" revision="35b8b9bd9863de208ab60e33b55f10ee43e2619b" name="meta-fsl-arm" path="sources/meta-fsl-arm"/>

  <project remote="oe" revision="ad6133a2e95f4b83b6b3ea413598e2cd5fb3fd90" name="meta-openembedded" path="sources/meta-openembedded"/>

  <project remote="freescale" revision="3a9c59399dbcf4790578125f016c6e86aff43367" name="fsl-community-bsp-base" path="sources/base">

        <copyfile dest="README" src="README"/>

        <copyfile dest="setup-environment" src="setup-environment"/>

  </project>

  <project remote="freescale" revision="e200df91b70da254461c59082ddd5db0a3c415a2" name="meta-fsl-arm-extra" path="sources/meta-fsl-arm-extra"/>

  <project remote="freescale" revision="2231e946e7a94d096394f2b2477e8184c9bbde7b" name="meta-fsl-demos" path="sources/meta-fsl-demos"/>

  <project remote="OSSystems" revision="b6d46d69a261fe6bd7c1e9811dc2a9bbd0b79aeb" name="meta-browser" path="sources/meta-browser" />

  <project remote="QT5" revision="d5536e34ec985c82b621448ab4325e5cbba38560" name="meta-qt5" path="sources/meta-qt5" />

  <project remote="fsl-release" name="meta-fsl-bsp-release" path="sources/meta-fsl-bsp-release" revision="jethro_4.1.15-1.0.0_ga" >

     <copyfile src="imx/tools/fsl-setup-release.sh" dest="fsl-setup-release.sh"/>

  </project>

</manifest>

You better should use a new repo like I did with imx-4.1.15-1.0.0_ga.

But the way to change the kernel provider also worked for me.

0 Kudos
Reply
2,195 Views
yichen
Contributor I

Hi Matt

Find out my problem was based on my target board.

It can not boot from sd card

Thanks for your help!

0 Kudos
Reply
2,195 Views
matt67
Contributor III

Good to read that you find what was the issue :smileywink:

0 Kudos
Reply
2,195 Views
yichen
Contributor I

@@Hi Matt!

Thanks for your reply.

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

  <default sync-j="2"/>

  <remote fetch="git://git.freescale.com/imx" name="fsl-release" />

  <remote fetch="git://git.yoctoproject.org" name="yocto"/>

  <remote fetch="git://github.com/Freescale" name="freescale"/>

  <remote fetch="git://git.openembedded.org" name="oe"/>

  <remote fetch="git://github.com/OSSystems" name="OSSystems"/>

  <remote fetch="git://github.com/meta-qt5"  name="QT5"/>

  <project remote="yocto" revision="dd0ba9ea4a11ab15348d4fe3574e4b28784db82f" name="poky" path="sources/poky"/>

  <project remote="yocto" revision="35b8b9bd9863de208ab60e33b55f10ee43e2619b" name="meta-fsl-arm" path="sources/meta-fsl-arm"/>

  <project remote="oe" revision="ad6133a2e95f4b83b6b3ea413598e2cd5fb3fd90" name="meta-openembedded" path="sources/meta-openembedded"/>

  <project remote="freescale" revision="3a9c59399dbcf4790578125f016c6e86aff43367" name="fsl-community-bsp-base" path="sources/base">

        <copyfile dest="README" src="README"/>

        <copyfile dest="setup-environment" src="setup-environment"/>

  </project>

  <project remote="freescale" revision="e200df91b70da254461c59082ddd5db0a3c415a2" name="meta-fsl-arm-extra" path="sources/meta-fsl-arm-extra"/>

  <project remote="freescale" revision="2231e946e7a94d096394f2b2477e8184c9bbde7b" name="meta-fsl-demos" path="sources/meta-fsl-demos"/>

  <project remote="OSSystems" revision="b6d46d69a261fe6bd7c1e9811dc2a9bbd0b79aeb" name="meta-browser" path="sources/meta-browser" />

  <project remote="QT5" revision="d5536e34ec985c82b621448ab4325e5cbba38560" name="meta-qt5" path="sources/meta-qt5" />

  <project remote="fsl-release" name="meta-fsl-bsp-release" path="sources/meta-fsl-bsp-release" revision="jethro_4.1.15-1.0.0_ga" >

     <copyfile src="imx/tools/fsl-setup-release.sh" dest="fsl-setup-release.sh"/>

     <copyfile src="imx/README" dest="README-IMXBSP"/>

  </project>

</manifest>

0 Kudos
Reply
2,195 Views
yichen
Contributor I

Hi Matt

We have the same manifest.xml.

But I don't know why I use uname -a command shows up like these?

uname.jpg

0 Kudos
Reply
2,195 Views
Yuri
NXP Employee
NXP Employee

Hello,

Pleae try using clean build (separate directory) for the BSP.

Regards

Yuri

0 Kudos
Reply
2,195 Views
yichen
Contributor I

Hi Yuri,

I don't know how to use clean build as you said.

0 Kudos
Reply
2,195 Views
Yuri
NXP Employee
NXP Employee

  To buid Your system, please follow "Freescale_Yocto_Project_User's_Guide.pdf",

section 3 (Host Setup) and 4 (Yocto Project Setup), assuming there is no "fsl-release-bsp"

directory on Your home folder.

Regards,

Yuri.

0 Kudos
Reply
2,196 Views
fabio_estevam
NXP Employee
NXP Employee
2,195 Views
gusarambula
NXP TechSupport
NXP TechSupport

Thank you, Fabio!

0 Kudos
Reply