On my platform, the u-boot environment variables can always be modified. Currently, I'm changing the value of `force_ro` to '1', which sets the permission mode to read-only. This change is reflected in the output of the `lsblk` command. However, even after rebooting my device, I can still write values to my boot partition, and the changes persist.
Here are the results of my test:
$ cat /sys/block/mmcblk0boot1/force_ro
1
$ fw_setenv primary 2
$ fw_printenv primary
2
Here are some details about my platform:
Hardware details:
Could anyone suggest a solution to make my boot partition read-only based on the value of `force_ro`?
Solved! Go to Solution.
@Sanket_Parekh Yes you are right about the libubootenv , which bypasses the force_ro write protection by the mentioned commit. So for my platform, I have to modify the source code
Thanks for your quick replay and valid root cause trace