/etc/fw_env.conf refers to non-existent device

Technical Support
, , ,
1

The /etc/fw_env.conf file on TorizonCore has the following:

# emmc-boot0 is symlink to the mmcblkXboot0

# Block device name     Device offset   Env. size
/dev/emmc-boot0         -0x2200         0x2000

however this device / symlink does not exist and hence fw_printenv also fails. If I replace this with the actual device /dev/mmcblk0boot0 then fw_printenv works. This is in the TorizonCore distro and also my local image built from dunfell-5.x.y.

In the Reference Image (Apalis-iMX8_Reference-Minimal-Image-Tezi_5.0.0+build.3.zip) from the artifact server, this is working as the file has /dev/mmcblk0boot0

2

Greetings @gregb,

Thank you for reporting this. I was able to recreate this on the i.MX8 as well as other supported platforms. This isn’t an issue in our 5.0 BSP nor was it an issue in Torizon 4.0. So this certainly narrows what change could have caused this problem.

I’ve made bug report to the team so they can investigate further and create a fix.

Best Regards,
Jeremias