Dear All,
Thanks for your all support till yet!
I am working on following:
1. Board : RPICM4
2. Yocto: Krikstone
3. Initramfs image: Core-Image-minimal
4. OS Image: core-image-sato
5. Bootloader : Broadcom bootloader (default given by yocto)
6. Rootfs type: ext4
7. Busybox : V1.35
Activity: I am trying to re-flash emmc0p2 i.e. root partition completely during booting and restarting the system with new rootfs i.e. new.rootfs.
Booting difference === > partitioning between uboot and Broadcom Bootloader
uboot : PBL -> uboot -> initramfs -> kernel - > rootfs -> init -> Prompt ==> boot partition : uboot + kernel + initramfs root partition : + rootfs + init
Broadcom Bootloader: PBL -> Broadcom Bootloader -> Kernel -> initramfs -> rootfs -> init -> prompt === > boot partition : Broadcom Bootloader + Kernel + initramfs root partition : rootfs + init
Major Difference: In case of uboot loads initramfs which in turn load kernel and initramfs, while in case of broadcom bootloder, broadcom bootloader kernel which in turn loads initramfs and kernel. The segmentation of Broadcom
Bootloader during booting prevent to initialize full storage stack which typically involving DTS, Device Drive , Filesystem Driver and other related kernel module involved into storage subsystem of kernel.
At the time of booting via initramfs on the runtime re-flashing the rootfs partition i.e. emmcblk0p2 will show the inconsistent behavior which in turn I observed during my exercise to do this i.e
I was able to re-flash emmcblk0p2 with several random behavior like :
Mounting / Unmounting issues
Flashing verification issues
Major issue or switch_root
Additionally
Busybox limitations like switch_root not all option not available.
Broadcom Bootloader do not support pivot_root.
Kindly advice best possible solution on above issue i.e. unstable Mounting / Unmounting, Flashing verification issues and at end major roadblock switching to the root of newly flashed rootfs.
Kindly advice on above accordingly.
Regards.
Ankur
Thanks for your all support till yet!
I am working on following:
1. Board : RPICM4
2. Yocto: Krikstone
3. Initramfs image: Core-Image-minimal
4. OS Image: core-image-sato
5. Bootloader : Broadcom bootloader (default given by yocto)
6. Rootfs type: ext4
7. Busybox : V1.35
Activity: I am trying to re-flash emmc0p2 i.e. root partition completely during booting and restarting the system with new rootfs i.e. new.rootfs.
Booting difference === > partitioning between uboot and Broadcom Bootloader
uboot : PBL -> uboot -> initramfs -> kernel - > rootfs -> init -> Prompt ==> boot partition : uboot + kernel + initramfs root partition : + rootfs + init
Broadcom Bootloader: PBL -> Broadcom Bootloader -> Kernel -> initramfs -> rootfs -> init -> prompt === > boot partition : Broadcom Bootloader + Kernel + initramfs root partition : rootfs + init
Major Difference: In case of uboot loads initramfs which in turn load kernel and initramfs, while in case of broadcom bootloder, broadcom bootloader kernel which in turn loads initramfs and kernel. The segmentation of Broadcom
Bootloader during booting prevent to initialize full storage stack which typically involving DTS, Device Drive , Filesystem Driver and other related kernel module involved into storage subsystem of kernel.
At the time of booting via initramfs on the runtime re-flashing the rootfs partition i.e. emmcblk0p2 will show the inconsistent behavior which in turn I observed during my exercise to do this i.e
I was able to re-flash emmcblk0p2 with several random behavior like :
Mounting / Unmounting issues
Flashing verification issues
Major issue or switch_root
Additionally
Busybox limitations like switch_root not all option not available.
Broadcom Bootloader do not support pivot_root.
Kindly advice best possible solution on above issue i.e. unstable Mounting / Unmounting, Flashing verification issues and at end major roadblock switching to the root of newly flashed rootfs.
Kindly advice on above accordingly.
Regards.
Ankur
Statistics: Posted by ankur_r — Sun Nov 10, 2024 6:04 pm