• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 243 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM625: Yocto Boot Partition

Nate Drude
Prodigy 180 points
Part Number: AM625

Why is the boot partition so large in the wks file: https://git.ti.com/cgit/arago-project/meta-ti/tree/wic/sdimage-2part.wks?h=dunfell&id=a83fb916dcfcad3028256ba8ff7d0626cf475cc5#n5

The actual content is only ~2.1M:

-rwxrwx--- 1 root disk 292K Jun 15 15:07 tiboot3.bin
-rwxrwx--- 1 root disk 938K Jun 15 15:07 tispl.bin
-rwxrwx--- 1 root disk 880K Jun 15 15:07 u-boot.img
-rwxrwx--- 1 root disk 574 Jun 15 15:07 uEnv.txt

Is there any risk if we reduce the boot partition to 32M using the following wks:

part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 1024 --fixed-size 32M --use-uuid
part / --source rootfs --ondisk mmcblk0 --fstype=ext4 --label root --align 1024 --use-uuid --offset 40M

Thanks,

Nate

  • +1
    TI__Guru 69707 points
    Nate Drude said:
    Why is the boot partition so large in the wks file: https://git.ti.com/cgit/arago-project/meta-ti/tree/wic/sdimage-2part.wks?h=dunfell&id=a83fb916dcfcad3028256ba8ff7d0626cf475cc5#n5

    For evaluation/experimentation it can be beneficial to have more space available in the boot partition for example to store ram disk images (initramfs) and Kernel images (which can be quite large on aarch64), so I suppose this is the reason behind this. Also note that the same wks file is used for the different TI platforms, and (esp. some older ones) have a different boot architecture, and may even requiring those artifacts to be there. The wks file is not meant to be seen as "this is how it must be done for AM625 specifically". This being said, feel free to re-size the partitions as per your needs, also keeping in mind potential extensions/future plans you may have for that partition.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 180 points

    Thanks, mainly I wanted to confirm:

    1. There were no future plans by TI for the AM6 family that would require the boot partition to be this size

    2. There are no limitations of the bootrom requiring the boot partition to be this size

  • 0 in reply to Nate Drude
    TI__Guru 69707 points

    Hi Nate,

    Nate Drude said:
    1. There were no future plans by TI for the AM6 family that would require the boot partition to be this size

    I discussed some more with the R&D/SDK team, and the only thing really on the radar screen that would use some more space are some R5 SPL-based early boot splash screen features part of the upcoming SDKv9.x, which would need some added storage space for the image file (compressed BMP image file), which should be in the 10's...100's of KB max. I suppose. So with you wanting to go to 32MB I don't have any concerns.

    Nate Drude said:
    2. There are no limitations of the bootrom requiring the boot partition to be this size

    Obviously you want to build a test image and see if it boots. If it does - then you'll be fine, such image with that specific partition map and partition types will then always work. And following the guidance from the TRM should always get you something that boots.

    Regards, Andreas