A tutorial on 'Freescale Yocto Project'. Source code is located here
NOTE: When doing 'repo init -u .... -b <LATEST_STABLE_BRANCH_NAME>', make sure you are using the latest stable branch (dora is the latest when writing this note)
I've followed the guide, but when running bitbake it seems it picks the wrong path... that is it ommits ../fsl-community-bsp/.. from the path and so it fails because it doesn't find layer.conf
did you run the setup-environment script? After its executing, the prompt is now under the build folder, and in that folder the correct layers paths are on conf/bblayers.conf. Make sure the setup script is running fine and the bblayers.conf has correct paths.
We are having problems with HDMI resolution on a Sabrelite board. Looking for information about the kernel graphic driver I came to your tutorial. The chapter about "Building the kernel manually" take my attention.
I clonegited the linux and then looked for the file mxc_hdmi.c (I saw a reference on another page) ... and I did not find it. Then i looked for it at our yoctodylan directory (I already did not remenber why I clonedgited before I look here) and I found it at:
If build/tmp/work/imx6qsabrelite-poky-linux-gnueabi/linux-boundary/3.0.35-r0/git seems to be the complete linux Yocto is using, why is necessary to download another copy?
On your cloned Linux kernel, did you move to the correct branch? You can compile either in the Yocto or your clone kernel folder, both are clones from the same source. In the other hand, the Yocto kernel may have some patches on top (look at the recipe), and the one you clone don't.
Unfortunately fetch issues are common. It may be the case that either the site is down temporally so you may try later. One way to overcome this problem is find the tarball somewhere and place it on the 'downloads' folder. I know, it is ugly but you do not stuck.
Just a heads up but the curl path you have in your document (i.e. https://dl-ssl.google.com/dl/googlesource/git-repo) is no longer valid... I just tried today and I get an Error 404 in the resulting "repo" file.
Secondly, I tried to find repo and when I googled it I found repo 1.19...however this version when doing the repo init... generates the following "could not verify the tag 'v1.12.7'". When I investigated this error I found others had this issue and they ended up getting repo from "http://commondatastorage.googleapis.com/git-repo-downloads/repo". So the resulting command I used was:
The document is great! However, I have some questions, as follows:
On page 1, under "Build's local configuration file..." the first line says "MACHINE ??= 'wandboard-dual'. However, on page 3 at the bottom, the document says "Machine configuration file: meta-fsl-arm/conf/imx6qsabresd.conf" I am using a wandboard-quad. Should the page 1 statement be MACHINE ??='wandboard-quad' and the page 3 line be Machine configuration file: meta-fsl-arm-extra/conf/machine/wandboard-quad.conf"?
On page 4, the document refers to
"KERNEL_DEVICE_TREE = "${S}/arch/arm/boot/dts/imx6q-sabresd.dts". Should this be changed to reflect the wandboard-quad?
UBOOT_MACHINE = "mx6qsabresd_config". Should this be changed to reflect the wandboard-quad?
Where would I tell the Yocto system that the machine configuration file is "meta-fsl-arm-extra/conf/machine/wandboard-quad.conf"?
I am used to the ./configure, make linux, make linux_install method of building an embedded kernel and similarly for applications. I am finding the whole recipes thing quite confusing although I can see its merits. Are there any other clear, current, step-by-step guides to help me?
Adding few notes regarding "Building the Kernel Manually" after review and test on my platform (DECEMBER 2015/MCIMX6UL-EVK)
I am working with the i.MX6 UL EVK board (MCIMX6UL-EVK), my local BRANCH is imx_3.14.38_6ul_ga. The defconfig used for my setup is: imx_v7_defconfig (the configuration is stored in the kernel source code under arch/arm/configs).
To be able to run make menuconfig properly on my Ubuntu host machine (Linux 3.13.x), I had to "apt-get install" the package called:libcurses5-dev.
The SD card requires a zImage, so I just called "make zImage" to get the new image built.
