Building Yocto Image for Raspberry Pi

-
The current stable branch of Yocto is Thud. Following are the steps for generating image for Raspberry Pi3 for Thud Branch.

Step1: Clone the Poky Layer (Thud branch)
$ git clone -b thud git://git.yoctoproject.org/poky.git

Step2: Clone the meta-openembedded Layer (Thud branch), as it is one of the dependencies mentioned in https://git.yoctoproject.org/cgit.cgi/meta-raspberrypi/about/
$ git clone -b thud git://git.openembedded.org/meta-openembedded

Step3: Clone the Raspberry-Pi BSP Layer: meta-raspberrypi (Thud branch)
$ git clone -b thud git://git.yoctoproject.org/meta-raspberrypi

Step4: Once you complete cloning, there should be three folders: poky, meta-openembedded, meta-raspberrypi

Step5: Run the environment script to setup the Yocto Environment and create build directory ("raspi-build")
$ source poky/oe-init-build-env raspi-build

Step6: Add meta-openembedded layers ( meta-oe, meta-multimedia, meta-networking, meta-python) and meta-raspberrypi layer to bblayers.conf

Step7: Set the MACHINE in local.conf to "raspberrypi3".
$ echo 'MACHINE = "raspberrypi3"' >> conf/local.conf

Step 8:
Final step is to build the image. To find out the available images:
$ ls ../meta-raspberrypi/recipes-*/images/


Step9: Let's build the "rpi-basic-image" by running "bitbake rpi-basic-image" command


Step 10: Write the image on to the sd card using the following command:

$ sudo dd if=tmp/deploy/images/raspberrypi3/rpi-basic-image-raspberrypi3.rpi-sdimg of=/dev/sdb bs=4M


You will see Yocto logo when you power up RPI with this image.


Comments

  1. Airheadbit25 January 2020 at 21:39

    This comment has been removed by the author.

    ReplyDelete
  2. Anonymous9 May 2023 at 03:18

    This comment has been removed by the author.

    ReplyDelete

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

PR, PN and PV Variable in Yocto

-
PN : Represents the name of the recipe. The name is usually extracted from the recipe file name. PR:  Represents the revision of the recipe. Default value for this revision is "r0". Subsequent revisions of the recipe conventionally will have "r1", "r2" and so on. PV:  Represents the version of the recipe. Normally extracted from the recipe file name. For example: ffmpeg_3.4.2.bb recipe. ${PN} : ffmpeg ${PV} : 3.4.2
Read more