Yocto Customizing U-Boot

Warning: This page is designed to be used with a 'release' URL parameter.

This page is using the default release RELEASE_PYRO_V1.0_VAR-SOM-MX6.
To view this page for a specific Variscite SoM and software release, please follow these steps:

1. Visit variwiki.com
2. Select your SoM
3. Select the software release

VAR-SOM-MX6 - Customizing U-Boot

Choose one of the following three methods to customize U-Boot.
After following one of the below methods you can either bitbake your complete image (e.g. fsl-image-gui) and the updated U-Boot will be used, or you can bitbake U-Boot alone by running " bitbake virtual/bootloader" (see the Build Yocto from source code page for the initial setup and for more info on using bitbake).

Add your own patches on top of our source code

Using this method Yocto will take the source code from our default remote repository, and apply your patches to it before building it:

Setup Yocto:

• Follow steps 1-3 of the Build Yocto from source code page.
• Follow the first part of step 4 of the same page, to source the setup-environment script (stop after that - don't build any image). E.g.:

$ cd ~/var-fslc-yocto
$ MACHINE=var-som-mx6 DISTRO=fslc-x11 . setup-environment build_x11

Get the source code:

$  bitbake -c unpack virtual/bootloader
$ mkdir -p ../local_repos/uboot-imx
$ cp -a tmp/work/var_som_mx6-fslc-linux-gnueabi/u-boot-variscite/<uboot version>/git/. ../local_repos/uboot-imx
$ cd ../local_repos/uboot-imx
$ git reset --hard
$ git clean -fdx

Make your changes in the source code and create a patch:
You can use either diff or patch file types.
For example:

$ cd ~/var-fslc-yocto/local_repos/uboot-imx
$ gedit board/variscite/mx6var_som/mx6var_som.c
$ gedit include/configs/mx6var_som.h
edit and save

$ git diff > my_mx6var_som_changes.diff

Update the recipes to use your patch:

Copy your patch:

$ cd ~/var-fslc-yocto/sources/meta-variscite-fslc/recipes-bsp/u-boot/
$ mkdir -p files
$ cp ~/var-fslc-yocto/local_repos/uboot-imx/my_mx6var_som_changes.diff  files/

Create a u-boot-variscite.bbappend file:

$ gedit u-boot-variscite.bbappend

and append the following line to it:

SRC_URI += "file://my_mx6var_som_changes.diff"

Also update the u-boot-fw-utils recipe:

$ cp u-boot-variscite.bbappend u-boot-fw-utils.bbappend

Use a local repository

Using this method Yocto will take the U-Boot source from a local repository instead of our remote ones on github:

Setup Yocto:

• Follow steps 1-3 of the Build Yocto from source code page.
• Follow the first part of step 4 of the same page, to source the setup-environment script (stop after that - don't build any image). E.g.:

$ cd ~/var-fslc-yocto
$ MACHINE=var-som-mx6 DISTRO=fslc-x11 . setup-environment build_x11

Get the source code:

$  bitbake -c unpack virtual/bootloader
$ mkdir -p ../local_repos/uboot-imx
$ cp -a tmp/work/var_som_mx6-fslc-linux-gnueabi/u-boot-variscite/<uboot version>/git/. ../local_repos/uboot-imx
$ cd ../local_repos/uboot-imx
$ git reset --hard
$ git clean -fdx

Make your changes in the source code and commit them:
After making changes in the source code you need to commit them.
For example:

$ cd ~/var-fslc-yocto/local_repos/uboot-imx
$ gedit board/variscite/mx6var_som/mx6var_som.c
$ gedit include/configs/mx6var_som.h
edit and save

$ git commit -a -m "my_mx6var_som_changes"

To list all of the commits:
$ git log

Get the latest commit id:
$ git rev-parse HEAD

Update the recipes to use the local repository instead of the default one:

$ cd ~/var-fslc-yocto/sources/meta-variscite-fslc/recipes-bsp/u-boot/

Create a u-boot-variscite.bbappend file:

$ gedit u-boot-variscite.bbappend

and append the following lines to it (see the previous section for listing the commits or getting the latest commit id):

UBOOT_SRC = "git://${BSPDIR}/local_repos/uboot-imx;protocol=file"
SRCBRANCH_var-som-mx6 = "imx_v2015.04_4.1.15_1.1.0_ga_var03" (or your own created branch)
SRCREV_var-som-mx6 = "The commit id you'd like to use"

Also update the u-boot-fw-utils recipe:

$ cp u-boot-variscite.bbappend u-boot-fw-utils.bbappend

For the SRCREV value you can also use "${AUTOREV}" during development to get the latest commit of the branch
(If you do so, make sure to run " bitbake -c cleansstate virtual/bootloader" before rebuilding U-Boot)

Use your own remote repository on github

Using this method Yocto will take the source code from your own remote repository on github:

Create your own github account and upload your proprietary U-Boot to a new repository:
For example, you can fork our repository to your own account by visiting the following link and clicking on "Fork" at the top right of the screen.
Alternatively, you can clone our repository to your local machine, and push it later to your own account.

https://github.com/varigit/uboot-imx/tree/imx_v2015.04_4.1.15_1.1.0_ga_var03

Update the recipes to use your remote repository instead of the default one:

$ cd ~/var-fslc-yocto/sources/meta-variscite-fslc/recipes-bsp/u-boot/

Create a u-boot-variscite.bbappend file:

$ gedit u-boot-variscite.bbappend

and append the following lines to it (see the previous section for listing the commits or getting the latest commit id):

UBOOT_SRC = "git://github.com/your_account/uboot-imx.git;protocol=git"
SRCBRANCH = "imx_v2015.04_4.1.15_1.1.0_ga_var03" (or your own created branch)
SRCREV = "The commit id you'd like to use"

Also update the u-boot-fw-utils recipe:

$ cp u-boot-variscite.bbappend u-boot-fw-utils.bbappend

For the SRCREV value you can also use "${AUTOREV}" during development to get the latest commit of the branch
(If you do so, make sure to run " bitbake -c cleansstate virtual/bootloader" before rebuilding U-Boot)