Steps to build and flash Yocto Image on Beaglebone black

-
Step1: Create a folder for Yocto source code:
$ mkdir beagblebone_yocto && cd beagblebone_yocto

 Step2: Clone the poky source code:
$ git clone -b thud git://git.yoctoproject.org/poky.git

Step3: Run the environment script to setup the Yocto Environment and create build directory
$ source poky/oe-init-build-env build

Step4: Set the MACHINE variable to 'beaglebone-yocto'
$ echo 'MACHINE = "beaglebone-yocto"' > conf/local.conf

Step5: Build the core-image-minimal image
$ bitbake core-image-minimal

After a few hours, you will find the images will be present in beaglebone_yocto/build/tmp/deploy/images/beaglebone-yocto folder

Step6: Take memory card and make two partitions using gparted:
Partition1 : Size 100 MB, fat16 (boot flag)
Partition2: Size > 2GB , ext4

Step7: Copy the files in the required partition.
$ cd beaglebone_yocto/build/tmp/deploy/images/beaglebone-yocto 
$ cp MLO-beaglebone-yocto /media/jamal/boot/MLO
$ cp u-boot.img /media/jamal/boot/u-boot.img
$ sudo tar -xf core-image-minimal-beaglebone-yocto.tar.bz2 -C /media/jamal/rootfs

Step8: Connect the Micro SD Card to the beaglebone black and to boot from MicroSD press the User Button(S2) While applying power. 

Step9: Connect the Serial cable at J1 Header for accessing Linux



Comments

  1. Munish Bhardwaj11 April 2019 at 11:13

    Great

    Am also working on beaglebon black .

    Have you used gstreamer for videos streaming ?

    ReplyDelete
    Replies
    1. Embedded Guru11 April 2019 at 19:19

      Yes, I have used it on some other project. Not on this

      Delete
  2. David29 September 2019 at 22:09

    Hi,
    I use Yocto to create image and boot beaglebone green wireless. like this introdctuion,
    After flash process, board turn down, but it's still old image. Please help thank in advance.

    ReplyDelete
  3. SAGAR8 March 2021 at 05:12

    hi
    i am working on yocto for beaglebone black,image is also build but that image is not boot in the my beagelbone. please can you help me ,i am following the same steps for image building.

    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

make config vs oldconfig vs defconfig vs menuconfig vs savedefconfig

-
Image
Building the Linux Kernel is a two-step process: Configuring the Kernel options Building the Kernel with those options. There are many methods available for configuring the kernel. make config: Text-based Configuration.  Options are prompted one after another. All options need to be answered Access to former options is not possible make menuconfig: Menu-driven user interface Allows to navigate forwards and backward directly between features Allows to load and save files with filenames different from ".config" Provides search feature It uses ncurses library for GUI. If the ncurses library is not installed, make menuconfig option fails. To install ncurses library on Ubuntu: sudo apt-get install libncurses5-dev make defconfig: Creates a ".config" file with default options from the ARCH supplied defconfig Configurations are generally stored in the directory: arch/$(ARCH)/configs $ ls arch/x86/configs/ i386_defconfi
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