Dear Community,
I would like to know if there's simple wait to change the fdtfile variable from user-space, please ? My user-case is that I would like to switch the dtb for the selected camera sensor without entering u-Boot's prompt.
I saw the method of using fw_printenv/fw_setenv and it seems that one needs to append the u-boot-fw-utils into image's rootfs :
IMAGE_INSTALL_append += " u-boot-fw-utils"
Is that the correct and enough way?
Thanks in advance and best regards,
Khang
Solved! Go to Solution.
Hi @chinnnu ,
Thanks for your answers. In fact, I am able to change u-Boot's variable from Linux user-space with the adding of u-boot-fw-utils to make appear fw_printenv/fw_setenv in the rootfs as in my initial post.
Regards,
K.
Hi @chinnnu ,
Thanks for your answers. In fact, I am able to change u-Boot's variable from Linux user-space with the adding of u-boot-fw-utils to make appear fw_printenv/fw_setenv in the rootfs as in my initial post.
Regards,
K.
Hello.... In order to modify the uboot environment variables from user space we will need a program called fw_setenv, we can compile this program ourselves from the u-boot sources, follow the instructions in this wiki page and then proceed to compile with (don't modify the .h file as it says in the tools/env/README file): regards mrtv technical team.
make env
cp fw_printenv fw_setenv
The next thing we will need is the fw_env.config file with the appropiate settings for our board. Here comes the confusion In this file you have to specify: MTD device name Device Offset Environment Size Flash sector size Number of sectors (ignored in NOR)
Hello.... In order to modify the uboot environment variables from user space we will need a program called fw_setenv, we can compile this program ourselves from the u-boot sources, follow the instructions in this wiki page and then proceed to compile with (don't modify the .h file as it says in the tools/env/README file):