Mender for CM3 64 bits ()

[David Bensoussan]

Hello,

I'm trying to make mender work on the rpi3-64 target using a compute module instead. I think the issue comes from using the newest u-boot version

Setup:

* sumo branches of every layer 

* my own layer with u-boot2017.08 recipe (required otherwise the CM3 doesn't boot at all with uboot provided by sumo u-boot2018.01)

* master branch for mender (because it contains patches that can patch the new u-boot version)

Mender configuration: (works perfectly on rpi3-64 target on a non compute module board with uboot 2018.01)

IMAGE_OVERHEAD_FACTOR = "1.1"

IMAGE_ROOTFS_MAXSIZE = "20000000"

MENDER_STORAGE_TOTAL_SIZE_MB = "3720"

IMAGE_ROOTFS_EXTRA_SPACE = "0"

MENDER_BOOT_PART_SIZE_MB = "40"

MENDER_DATA_PART_SIZE_MB = "900"

When following those steps, I can build the image but booting fails with a kernel panic, see cc image.

Thanks

[Drew Moseley]

Hi David,

I don't know how solid the support is for the RPI3-64/CM stuff in the upstream. Are you able to boot this build without Mender enabled? It's possible that upstream U-Boot simply doesn't have support for that particular variant yet.

Drew

--
You received this message because you are subscribed to the Google Groups "Mender List mender.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mender+un...@lists.mender.io.
To post to this group, send email to men...@lists.mender.io.
Visit this group at https://groups.google.com/a/lists.mender.io/group/mender/.

--
Drew Moseley | Technical Solutions Architect | (+1) 480-797-0552 | https://mender.io

Northern.tech AS | @northerntechHQ | @drewmoseley

[Belisko Marek]

Hi, I have mender running on CM3 but I need to use u-boot 2018.03 (when booting works fine). IIRC in sumo there is 2018.01 and with this one I have some issues.

I can share patches if necessary.

BR,

marek

as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com

[David Bensoussan]

This is actually my fault, I had some mender variable setup that disabled a patch. sorry for the inconvenience

[Belisko Marek]

Patch is simple just update recipe for u-boot to 2018.03 and device
should boot. If you don't know how to do it I can share gzipped
directory

BR,

marek
On Tue, Oct 9, 2018 at 12:01 PM David Bensoussan
<dbens...@synapticon.com> wrote:
>
> I spoke too fast. Uboot starts but gets stuck at Starting kernel ... This is a u-boot issue. Not related to mender. @Belisko, do you have your patches in some repos?

[David Bensoussan]

I tested 2018.07 and 2018.03. Without mender, I can boot (even though UART seems broken). With mender (on the 2 u-boot versions), u-boot starts normally, next screen shows 4 raspberrypis and a black screen.
Are you using sumo for all layers and master for mender too?

[Belisko Marek]

I'm using rocko release not sumo. Do you have enable_uart=1 in
config.txt to capture u-boot messages? Can you share it pls. Thanks.
Regards

[Belisko Marek]

I can test with my cm3 on sumo but it will take some time though
(probably this week if it's OK with you)

[Kristian Amlie]

On 08/10/18 19:19, David Bensoussan wrote:
> When following those steps, I can build the image but booting fails with
> a kernel panic, see cc image.

Messages including "mount_root" in the stack trace are almost always
because the "root=/dev/..." argument given to the kernel is wrong. What
kind of storage does it have? And what is MENDER_STORAGE_DEVICE set to?

--
Kristian

[David Bensoussan]

I'm actually now building with rocko, I'll update you asap :)

[Belisko Marek]

Hi David,

I have build mender in sumo branch and it boots fine:

bootlog:

U-Boot 2018.07 (Sep 18 2018 - 13:03:21 +0000)

DRAM: 948 MiB
RPI Compute Module 3 (0xa020a0)
MMC: mmc@7e202000: 0, sdhci@7e300000: 1
Loading Environment from FAT... WARNING at
/home/marek/projects/sportcaster/yocto/build-veo-cm3/tmp/work/raspberrypi_cm3-poky-linux-gnueabi/u-boot/1_2018.07-r0/git/drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()!
WARNING at /home/marek/projects/sportcaster/yocto/build-veo-cm3/tmp/work/raspberrypi_cm3-poky-linux-gnueabi/u-boot/1_2018.07-r0/git/drivers/mmc/bcm2835_sdhost.c:408/bcm2835_send_command()!
*** Warning - bad CRC, using default environment

Failed (-5)
Loading Environment from MMC... OK
In: serial
Out: vidconsole
Err: vidconsole
Net: No ethernet found.
starting USB...
USB0: scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
U-Boot>

U-Boot 2018.01 (Oct 10 2018 - 07:36:45 +0000)

DRAM: 948 MiB
RPI: Board rev 0xa unknown
RPI Unknown model (0xa020a0)
MMC: sdhci@7e300000: 0
*** Warning - bad CRC, using default environment

In: serial
Out: vidconsole
Err: vidconsole
Net: No ethernet found.
starting USB...
USB0: Core Release: 2.80a
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
reading /boot.scr
300 bytes read in 9 ms (32.2 KiB/s)
## Executing script at 02000000
switch to partitions #0, OK
mmc0(part 0) is current device
4924624 bytes read in 761 ms (6.2 MiB/s)
## Booting kernel from Legacy Image at 01000000 ...
Image Name: Linux-4.14.68
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4924560 Bytes = 4.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 2eff9e00
Booting using the fdt blob at 0x2eff9e00
Loading Kernel Image ... OK
reserving fdt memory region: addr=0 size=1000
Using Device Tree in place at 2eff9e00, end 2f002f87

Starting kernel ...


Poky (Yocto Project Reference Distro) 2.5.1 raspberrypi-cm3 ttyAMA0

raspberrypi-cm3 login: root
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~#
root@raspberrypi-cm3:~# fdisk -l
Disk /dev/mmcblk0: 3728 MB, 3909091328 bytes, 7634944 sectors
59648 cylinders, 4 heads, 32 sectors/track
Units: cylinders of 128 * 512 = 65536 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA
Sectors Size Id Type
/dev/mmcblk0p1 * 192,0,1 831,3,32 24576 106495
81920 40.0M c Win95 FAT32 (LBA)
/dev/mmcblk0p2 832,0,1 1023,3,32 106496 532479
425984 208M 83 Linux
/dev/mmcblk0p3 1023,3,32 1023,3,32 532480 958463
425984 208M 83 Linux
/dev/mmcblk0p4 1023,3,32 1023,3,32 958464 1220607
262144 128M 83 Linux
Disk /dev/mmcblk0boot1: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: cylinders of 64 * 512 = 32768 bytes

Disk /dev/mmcblk0boot1 doesn't contain a valid partition table
Disk /dev/mmcblk0boot0: 4 MB, 4194304 bytes, 8192 sectors
128 cylinders, 4 heads, 16 sectors/track
Units: cylinders of 64 * 512 = 32768 bytes

Disk /dev/mmcblk0boot0 doesn't contain a valid partition table
root@raspberrypi-cm3:~#

mender is up & running. I didn't try update though.

BR,

marek

On Tue, Oct 9, 2018 at 4:58 PM David Bensoussan
<dbens...@synapticon.com> wrote:
>
> I'm actually now building with rocko, I'll update you asap :)
>

[Mirza Krak]

There is two U-boot boots in the log, is that a copy/paste error or does it actually boot U-boot twice? It also seems to be different versions. 

/ Mirza 

[Belisko Marek]

Ups yes first one was some test version. Boot starts from 2008.01. I
didn't test if mender update can be done (I'm using CM3 in IO module)
and the is no ethernet but I'll find next week usb->eth dongle and
will give a try. Thanks.

BR,

marek