How to avoid the need to run 'env default' command on modified env variable

[Quentin Schulz]

Hi Mirceam

On 8/11/25 6:30 AM, Mircea Carausu wrote:
> [You don't often get email from mcarausu at gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> Hi All,
> apologies in advance if my question is trivial:
> 
> I am changing some critical variables in the read-only / compiled-in
> section of u-boot env variables via CFG_EXTRA_ENV_SETTINGS in
> include/configs/<my_board.h>
> All I want is to have them take effect automatically (i.e. without having
> the need to stop in u-boot console and issue the env default command).
> I see the new values if I use the env default command.
> Since I am applying the new config via a RAUC bundle and some systems are
> using automated testing it is not practical to issue env default on each
> board.
> Is there a way of telling u-boot to load / use the read-only / built-in
> values instead of the ones stored in env storage?

Build U-Boot without external environment support?

E.g. with only ENV_IS_NOWHERE?

You can also entirely and permanently erase the stored environment with 
`env erase` if you have CONFIG_CMD_ERASEENV enabled.

If that's not fitting your use-case can you provide more information please?

Cheers,
Quentin