iMX95 - swupdate/fw_printenv problem

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

iMX95 - swupdate/fw_printenv problem

Jump to solution
1,714 Views
sicScar1
Contributor III

 

Hi there,

I’m trying to integrate SWUpdate (by sbabic) inside my Yocto distro, using the NXP guides, which use the meta-swupdate-imx and swupdate-scripts repos as a reference.
I tried to make a port to Scarthgap (last branch for meta-swupdate-imx is Mickledore) and add config files for imx95 (last is imx93).

I should be at a good point of the integration, but I noticed that the tool fw_printenv can’t access U-Boot env variables. Log:

~# fw_printenv
Cannot read environment, using default
Cannot read default environment from file

At the moment, the file /etc/fw_env.config is:

/dev/mmcblk0 0x700000 0x4000
/dev/mmcblk0 0x704000 0x4000

That’s because in the uboot defconfig (in my case, I'm using iMX95 Verdin from Toradex, but the config is basically the same for imx95evk except for dtbs) configs/imx95_19x19_verdin_defconfig I have:

CONFIG_ENV_SIZE=0x4000
CONFIG_ENV_OFFSET=0x700000

and the NXP patches also include:

+CONFIG_SYS_REDUNDAND_ENVIRONMENT=y
+CONFIG_ENV_OFFSET_REDUND=0x704000

But it’s not working… Does someone know how to deal with it?
Thank you 

Tags (2)
0 Kudos
Reply
1 Solution
1,677 Views
sicScar1
Contributor III

(AUTO)SOLVED:

~# fw_printenv
Cannot read environment, using default
Cannot read default environment from file

That error simply means that you MUST execute the command “saveenv” in U-Boot at least once after flashing the board. The offsets I posted are correct.

View solution in original post

Tags (2)
0 Kudos
Reply
1 Reply
1,678 Views
sicScar1
Contributor III

(AUTO)SOLVED:

~# fw_printenv
Cannot read environment, using default
Cannot read default environment from file

That error simply means that you MUST execute the command “saveenv” in U-Boot at least once after flashing the board. The offsets I posted are correct.

Tags (2)
0 Kudos
Reply