When you are at the linux prompt, what does “fw_printenv” work? The config file is “/etc/fw_env.config”.
root@apalis-imx8:~# fw_printenv
Cannot read environment, using default
Cannot read default environment from file
root@apalis-imx8:~# cat /etc/fw_env.config
/dev/mmcblk0 0x800000 0x2000
/dev/mmcblk0 0x1000000 0x2000
I didn’t notice before, but I see that I get an error in U-boot at startup:
U-Boot 2020.04-5.3.0-devel+git.76fd4496a40b (Apr 07 2021 - 07:35:42 +0000)
CPU: NXP i.MX8QM RevB A53 at 1200 MHz
DRAM: 4 GiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment
so I did a “env default -a” at the U-boot prompt. Now it works. I don’t really understand what happened there, sorry for the panic but I thought my patch broke mender.
That’s still problematic. The environment should be set to the default when you boot the first time. That’s what the bad CRC message is indicating. I don’t know what env default -a would do differently than that. I’ll try to find some time later today or over the weekend to play with this a bit.
OK, thanks for looking into that.
BTW, I also notice an error when updating via mender. The update works fine, but I wonder if the error is expected or a mis-configuration on my part:
INFO[0000] Update Module path "/usr/share/mender/modules/v3" could not be opened (open /usr/share/mender/modules/v3: no such file or directory). Update modules will not be a
vailable
There is no folder called /usr/share/mender/module on my target
Yeah, that’s fine. That just means you have not installed any update modules.
Drew
1 Like
Hi @pgiangrossi are you still having issues with the U-Boot environment? I saw something similar and it turned out we just needed to increase the environment size. The specific commit is here.
I wrapped that up with your change for overlays as well as changing our modifications to boot.cmd.in to be applied via patch in a PR here. Can you review that, and try it to see if the overlays work for you now?
1 Like
I have not had any more problems with the U-boot env. Good to know that you may have fixed that by increasing env size.
I tested the PR and it works fine. It applies the overlays and the screen is verified to work. Below is the U-boot output. The only issue I see is the “Unknown command '0x9c000000”. Doesn’t seem to break anything, though.
Found U-Boot script /boot.scr
2691 bytes read in 19 ms (137.7 KiB/s)
## Executing script at 83100000
Unknown command '0x9c000000' - try 'help'
Loading hdp firmware from 0x000000009c000000 offset 0x0000000000002000
Loading hdp firmware Complete
Saving Environment to MMC... Writing to redundant MMC(0)... OK
Loading DeviceTree: imx8qm-apalis-v1.1-eval.dtb
166596 bytes read in 22 ms (7.2 MiB/s)
108 bytes read in 10 ms (9.8 KiB/s)
Applying Overlay: apalis-imx8_lvds_overlay.dtbo
638 bytes read in 21 ms (29.3 KiB/s)
Applying Overlay: apalis-imx8_atmel-mxt_overlay.dtbo
402 bytes read in 19 ms (20.5 KiB/s)
Applying Overlay: display-lt170410_overlay.dtbo
834 bytes read in 21 ms (38.1 KiB/s)
10260548 bytes read in 248 ms (39.5 MiB/s)
Uncompressed size: 24267264 = 0x1724A00
Bootargs: pci=nomsi root=/dev/mmcblk0p2 ro rootwait
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Loading Device Tree to 00000000fcdff000, end 00000000fce4afff ... OK
Starting kernel ...