# Raspberrypi cm3 zeus-test issues **URL:** \ **Category:** General Discussions\ **Created:** [May 5, 2020, 5:53pm UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881 "2020-05-05T17:53:23Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [May 5, 2020, 5:53pm UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/1 "2020-05-05T17:53:23Z")
Hi, I’m trying to test update of raspberrypi cm3 module to zeus branch. I’m hitting following issues: 1. u-boot -\> do\_configure task is in loop: ```auto make -f /home/jenkins/mender/mender-raspberrypi/build/tmp/work/raspberrypi_cm3-poky-linux-gnueabi/u-boot/1_2020.01-r0/git/scripts/Makefile.build obj=scripts/kconfig oldconfig scripts/kconfig/conf --oldconfig Kconfig .config:178:warning: symbol value '' invalid for ENV_OFFSET * * Restart config... * * * Environment * Environment is not stored (ENV_IS_NOWHERE) [N/y/?] n Environment in EEPROM (ENV_IS_IN_EEPROM) [N/y/?] n Environment is in a FAT filesystem (ENV_IS_IN_FAT) [N/y/?] n Environment is in a EXT4 filesystem (ENV_IS_IN_EXT4) [N/y/?] n Environment in flash memory (ENV_IS_IN_FLASH) [N/y/?] n Environment in an MMC device (ENV_IS_IN_MMC) [Y/n/?] y Environment in a NAND device (ENV_IS_IN_NAND) [N/y/?] n Environment in a non-volatile RAM (ENV_IS_IN_NVRAM) [N/y/?] n Environment is in OneNAND (ENV_IS_IN_ONENAND) [N/y/?] n Environment is in remote memory space (ENV_IS_IN_REMOTE) [N/y/?] n Enable redundant environment support (SYS_REDUNDAND_ENVIRONMENT) [N/y/?] n Environment offset (ENV_OFFSET) [] (NEW) Environment offset (ENV_OFFSET) [] (NEW) Environment offset (ENV_OFFSET) [] (NEW) Environment offset (ENV_OFFSET) [] (NEW) Environment offset (ENV_OFFSET) [] (NEW) Environment offset (ENV_OFFSET) [] (NEW) Environment offset (ENV_OFFSET) [] (NEW) Environment offset (ENV_OFFSET) [] (NEW) ``` 1. meta-mender-core layer are patches for u-boot-2020.01 but meta-raspberrypi use 2019.07version . When try to set this version as preferred patches cannot be applied (rpi related). I refreshed u-boot patch (will post PR when verify board booting). Comments? Thanks. marek ---
**Author:** ![oleorhagen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/oleorhagen/32/297_2.png) [@oleorhagen](https://hub.mender.io/u/oleorhagen)\ **Post date:** [May 6, 2020, 6:50am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/2 "2020-05-06T06:50:15Z")
I’m afraid I cannot help you here directly, but I know that @kacf have been working on porting the u-boot patching to zeus for us. I’m sure he will drop by shortly 🙂 ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [May 6, 2020, 6:51am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/3 "2020-05-06T06:51:34Z")
Well I find out also that with zeus u-boot u-boot doesn’t work on cm3 at all ;). Thanks. ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [May 6, 2020, 6:58am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/4 "2020-05-06T06:58:04Z")
I was just working on RPi3 myself, and this problem was fixed in these two commits: - [u-boot: Start using new CONFIG\_SYS\_REDUNDAND\_ENVIRONMENT switch.](https://github.com/mendersoftware/meta-mender/commit/e60b35006a82fc5e108b5ef974e485250f6fe462) - [MEN-3476: Fix OOM issue when configuration is missing from defconfig.](https://github.com/mendersoftware/meta-mender/commit/27f96afc2ff7c64864e67b31387f0ddf43452a12) Still there are some issues remaning on zeus, but it’s getting closer. ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [May 6, 2020, 6:59am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/5 "2020-05-06T06:59:18Z")
@kacf but why in meta-mender is added u-boot 2020.01 as raspberrypi is using in zeus 2019.07? ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [May 6, 2020, 8:21am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/6 "2020-05-06T08:21:37Z")
When I compile for Raspberry Pi it looks like it uses 2020.01, even though 2019.07 is the one available in the meta-raspberrypi layer. I suppose it just chooses the latest one, which is the one from poky. Can you confirm that the same thing happens to you? I would not expect the original error that you encountered unless 2020.01 is being used. ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [May 6, 2020, 8:31am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/7 "2020-05-06T08:31:38Z")
Yes if I don’t set preferred version to 2019.07 is use 2020.01. I’ll try your patches and let you know. Thanks. ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [May 6, 2020, 8:51am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/8 "2020-05-06T08:51:55Z")
Clearing up some confusion 🙂 > 2019.07 is the one available in the meta-raspberrypi layer meta-raspberrypi only has a `bbappend` to `2019.07` and the actual 2019.07 recipe is in `poky`. > I suppose it just chooses the latest one, which is the one from poky. It chooses the one we have in meta-mender, [https://github.com/mendersoftware/meta-mender/blob/zeus-next/meta-mender-core/recipes-bsp/u-boot/u-boot\_2020.01.bb](https://github.com/mendersoftware/meta-mender/blob/zeus-next/meta-mender-core/recipes-bsp/u-boot/u-boot_2020.01.bb) Poky on `zeus` provides U-Boot 2019.07. I know we added 2020.01 U-Boot recipe to fix U-Boot → GRUB support (Beaglebone and others) and I thought the intention was to use this as the default bootloader for other platforms that rely on upstream U-Boot as well and I have deferred to comment on this earlier. Raspberry Pi is a bit special, since it does not use the U-Boot → GRUB approach, but it is using upstream U-Boot. We could force the Raspberry Pi integration to use 2019.07, since it is a “manual integration” and not impacted by the breakage/fixes of U-Boot → GRUB. But you have already updated the patches to 2020.01 for Raspberry Pi, so might as well stick to it? ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [May 6, 2020, 11:34am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/9 "2020-05-06T11:34:37Z")
Good catch @mirzak, I had forgotten about that. I checked the dunfell branch of meta-raspberrypi, which uses U-Boot v2020.01, and it has no patches, so I assume they have all been applied to v2020.01 already. So yes, I think we should just stick to v2020.01, at least if @MarekBelisko can confirm that this works for him. ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [May 6, 2020, 11:36am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/10 "2020-05-06T11:36:12Z")
So we will have zeus-dunfell hybrid 😉 ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [May 6, 2020, 8:59pm UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/11 "2020-05-06T20:59:02Z")
OK I’ve used patches from @kacf mentioned above and build 2020.01 and have this on console: ```auto U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000) DRAM: 948 MiB RPI Compute Module 3 (0xa020a0) ``` then it stuck so I need t investigate why it hangs. But anyway good progress 👍 on zeus branch. Thanks. ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [May 13, 2020, 9:49am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/12 "2020-05-13T09:49:43Z")
I’m getting now other issue in zeus branch: ```auto 47 | # error CONFIG_ENV_OFFSET should not be defined explicitly (will be auto-configured). | ^ ~~~~ u-boot/1_2020.01-r0/git/include/config_mender.h:50:3: error: #error CONFIG_ENV_OFFSET_REDUND should not be defined explicitly (wi ll be auto-configured). ``` u-boot autoconfig is disabled and I have added `MENDER_PARTITION_ALIGNMENT = "4194304"` When removed then getting other error: ```auto ERROR: u-boot-1_2020.01-r0 do_configure: U-Boot configuration rpi_3_32b_config has setting: CONFIG_ENV_OFFSET=0x400000 CONFIG_ENV_OFFSET_REDUND=0x800000 but Mender expects: CONFIG_ENV_OFFSET=0x800000 Please fix U-Boot's configuration file. ``` I’m bit confused now ;). Any ideas? Thx. ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [May 13, 2020, 11:33am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/13 "2020-05-13T11:33:42Z")
Are you using the `meta-mender-raspberrypi` layer? I thought this was fixed in [https://github.com/mendersoftware/meta-mender/commit/e60b35006a82fc5e108b5ef974e485250f6fe462](https://github.com/mendersoftware/meta-mender/commit/e60b35006a82fc5e108b5ef974e485250f6fe462). ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [May 13, 2020, 12:53pm UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/14 "2020-05-13T12:53:16Z")
Yes. Let me inspect it if I can spot anything. Thanks. ---
**Author:** ![tlinford](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tlinford/32/657_2.png) [@tlinford](https://hub.mender.io/u/tlinford)\ **Post date:** [June 11, 2020, 2:44pm UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/15 "2020-06-11T14:44:35Z")
Hi there, also trying out upgrading to zeus on rpi4, and was having the same error in u-boot do\_configure. Got it working by manually specifying > MENDER\_UBOOT\_ENV\_STORAGE\_DEVICE\_OFFSET\_1 = “0x400000” > MENDER\_UBOOT\_ENV\_STORAGE\_DEVICE\_OFFSET\_2 = “0x800000” but I don’t know if that’s the proper way ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [June 12, 2020, 12:18pm UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/16 "2020-06-12T12:18:45Z")
There is a new tag zeus-v2020.06 out now. Can you try and see if that helps? I tried both Raspberry Pi 3 and 4, and both worked for me. ---
**Author:** ![tlinford](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tlinford/32/657_2.png) [@tlinford](https://hub.mender.io/u/tlinford)\ **Post date:** [June 15, 2020, 2:56pm UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/17 "2020-06-15T14:56:21Z")
gave a try with meta-mender on zeus-v2020.06 and still getting the same errors without settings those variables explicitly: > ERROR: u-boot-fw-utils-mender-auto-provided-1.0-r0 do\_configure: U-Boot configuration rpi\_4\_config has setting: > CONFIG\_ENV\_OFFSET=0x400000 > CONFIG\_ENV\_OFFSET\_REDUND=0x800000 > but Mender expects: > CONFIG\_ENV\_OFFSET=0x800000 > Please fix U-Boot’s configuration file. > ERROR: u-boot-fw-utils-mender-auto-provided-1.0-r0 do\_configure: Execution of ‘/mnt/yocto/yocto-mender-raspberrypi/build/tmp/work/raspberrypi4\_64-poky-linux/u-boot-fw-utils-mender-auto-provided/1.0-r0/temp/run.do\_configure.48447’ failed with exit code 1: > CONFIG\_ENV\_SIZE=0x4000 > CONFIG\_ENV\_SIZE=0x4000 > CONFIG\_ENV\_OFFSET=0x400000 > WARNING: exit code 1 from a shell command. same configuration is working without problems on warrior branch. ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [June 16, 2020, 8:35am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/18 "2020-06-16T08:35:29Z")
Can you try with this patch applied? [https://github.com/mendersoftware/meta-mender/pull/1009/files](https://github.com/mendersoftware/meta-mender/pull/1009/files) ---
**Author:** ![tlinford](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tlinford/32/657_2.png) [@tlinford](https://hub.mender.io/u/tlinford)\ **Post date:** [June 16, 2020, 1:45pm UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/19 "2020-06-16T13:45:12Z")
That fixed it, thanks kacf! guess it wasn’t picking up my `MENDER_PARTITION_ALIGNMENT = "4194304"` ---
**Author:** ![doganmurat](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/doganmurat/32/573_2.png) [@doganmurat](https://hub.mender.io/u/doganmurat)\ **Post date:** [June 19, 2020, 7:43am UTC](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881/20 "2020-06-19T07:43:08Z")
Hi @MarekBelisko , I am also stuck at this screen. ```auto U-Boot 2020.01 (May 06 2020 - 20:09:45 +0000) DRAM: 948 MiB RPI Compute Module 3 (0xa020a0) ``` Did you find a solution? I am trying current zeus branch. [Next page](https://hub.mender.io/t/raspberrypi-cm3-zeus-test-issues/1881.md?page=2)