Closed MitchGaines closed 2 years ago
I'm actually going to close this issue I think because its a weird set of circumstances that are a bit beyond the scope of this project. Further, I was trying to hack some things together to make them function. Ultimately, I was able to move back up to u-boot 2022.01 which resolved my rauc issues.
Hi @MitchGaines,
Thank you for sharing your experience and the note about u-boot 2022.01 and congrats for figuring it out. The feedback might be useful to someone else in a similar situation using CM4.
Thanks, Leon
Hi team,
I have a bit of an issue I'm hitting encompassing u-boot, rauc, and my raspberrypi board that I was hoping someone here could potentially assist me with. I'm using meta-rauc-raspberrypi as is for the RPi Compute Module 4 running dunfell. When I run
rauc status
, I get the following:As a result, it obviously doesn't work. Not sure when this problem was introduced on my development system, so I'm having some trouble tracking it down.
Fundamentally, the issue seems to be because the
BOOT_ORDER
variable doesn't seem to be saving to myuboot.env
. When I manually set that viafw_setenv
, rauc corrects itself. But, if I reboot, that variable doesn't stick. Below is what I get when I runfw_printenv
:Here's my u-boot debug output:
A thing to note, I recently downgraded my u-boot version from 2022.01 for unrelated reasons and needed to apply a patch to uboot to support the CM4 board. Below is the patch I created.
Logically, this move seems like the smoking gun, but I'm not sure why. Not sure if anyone here has hit this error before or has some insight. It seems a little odd that the
BOOT_A_LEFT
variable would stick, but the others wouldn't. When I take a look at theuboot.env
file, it seems to be consistent with whatfw_printenv
prints out. Also, theLoading Environment from FAT... *** Warning - bad CRC, using default environment
error when u-boot loads seems to also indicate other issues with my environment.Would appreciate any help on this. Thanks