RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
"Kernel and rdkb rootfs will be generated as part BPIR4 build instructions"
...
Used below mentioned git repo for generating bl2.img and fip.bin file.
1) https://github.com/frank-w/u-boot/tree/2024-04-bpi → for generating uboot.bin files .
2) https://github.com/frank-w/u-boot/tree/mtk-atf → for generating atf flow bootloader files (bl2.img and fip.bin)
At initial cloned mentioned git code "https://github.com/frank-w/u-boot/tree/2024-04-bpi" , and made below mentioned changes in u-boot env file to make boot-loader compatible in loading kernel and rdkb os at initial boot-up itself.
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
repo init -u https://code.rdkcentral.com/r/manifests -b kirkstone -m rdkb-bpi-extsrc.xml repo sync -j `nproc` --no-clone-bundle --no-tags #Include mentioned PR changes to meta-cmf-bananapi for the inclusion of bl2.img and fip.bin. PR: "https://github.com/rdkcentral/meta-cmf-bananapi/pull/27" MACHINE=bananapi4-rdk-broadband source meta-cmf-bananapi/setup-environment-refboard-rdkb #After giving machine command select the option based of your flashing mode. # Option 1 to generate sdcard image. jenkins@build-yocto-persistent-rdkm-hkumar343:~/jenkinsroot/workspace/Heam/BPIR4_SD$ MACHINE=bananapi4-rdk-broadband source meta-cmf-bananapi/setup-environment-refboard-rdkb You had no conf/local.conf file. This configuration file has therefore been created for you from /home/jenkins/jenkinsroot/workspace/Heam/BPIR4_SD/meta-rdk/conf/local.conf.sample You may wish to edit it to, for example, select a different MACHINE (target hardware). See conf/local.conf for more information as common configuration options are commented. You had no conf/bblayers.conf file. This configuration file has therefore been created for you from /home/jenkins/jenkinsroot/workspace/Heam/BPIR4_SD/meta-rdk/conf/bblayers.conf.sample To add additional metadata layers into your configuration please add entries to conf/bblayers.conf. The Yocto Project has extensive documentation about OE including a reference manual which can be found at: https://docs.yoctoproject.org For more information about OpenEmbedded see the website: https://www.openembedded.org/ Common targets are: core-image-minimal rdk-oss-image rdk-generic-hybrid-image rdk-generic-mediaclient-image rdk-generic-broadband-image rdk-generic-camera-image rdk-generic-broadband-tdk-image rdk-generic-broadband-dev-image rdk-generic-hybrid-dev-image rdk-generic-mediaclient-dev-image You can also run generated qemu images with a command like 'runqemu qemuarm' Configuration files have been created for the following configuration: DISTRO: rdkb MACHINE: bananapi4-rdk-broadband Manifest Name = rdkb-bpi-extsrc.xml kirkstone tune-cortexa53.inc kirkstone whitelist.inc ######################################################### ### Which Format image you want to generate for BPIR4 ### ######################################################### 1) SD 2) EMMC 3) NOR Choose image format(1-SD, 2-EMMC, 3-NOR): 1 bitbake rdk-generic-broadband-image |
Image generating steps for BPIR4.
After completion of build go to deploy folder and execute "bpir4_sd_image_creater.sh" script file, to generate final sdcard image.
...