Digi ConnectCore 6 doesn't generate sdimg file

Board Integrations
, ,
1

Hi,

Happy New Year!

I’m trying to add Mender support for the Digi ConnectCore 6 board (NXP i.MX6 Cortex A9 SoM - ConnectCore 6N - Linux, Android and Windows Embedded SOM | Digi International) using Yocto.

I had to hack up a few of the classes in the meta-digi layer to get it to play nicely with meta-mender after adding the requisite parameters in my conf/local.conf as outlined in your documentation.

However, after executing bitbake dey-image-qt which is the final Yocto image, I don’t see a .sdimg file. These are the final image files that are generated:

[build-digi-cc6]$ ls -lh tmp/deploy/images/ccimx6sbc/ | grep img
-rw-r--r-- 1 mab mab  16M Jan  1 10:43 dey-image-qt-xwayland-ccimx6sbc-20250101154246.bootimg
-rw-r--r-- 1 mab mab 128M Jan  1 10:43 dey-image-qt-xwayland-ccimx6sbc-20250101154246.dataimg
-rw-r--r-- 1 mab mab 3.6G Jan  1 10:44 dey-image-qt-xwayland-ccimx6sbc-20250101154246.uefiimg
-rw-r--r-- 1 mab mab 5.7K Jan  1 10:44 dey-image-qt-xwayland-ccimx6sbc-20250101154246.uefiimg.bmap
-rw-r--r-- 1 mab mab 264M Jan  1 10:44 dey-image-qt-xwayland-ccimx6sbc-20250101154246.uefiimg.bz

I don’t see an sdimg file and it looks like the uefiimg file matches the expected file size, but clearly a UEFI image isn’t what I want.

Can you help me understand what I’m doing wrong.

2

Hi @mabembedded,

Glad to have you around!

Probably you don’t have the Mender feature mender-image-sd enabled. Add such do your local.conf:

MENDER_FEATURES_ENABLE:append = " mender-image-sd "

Hope this helps, let me know if you have more questions.

Greetz,
Josef

3

Thanks @TheYoctoJester , that helped. I do see an .sdimg. However, after flashing this to the SD card, the boot partition doesn’t look correct:

[yocto-clean]$ ls -l /media/mab/boot/
total 6
drwxr-xr-x 2 mab mab 2048 Apr  5  2011 dtb
drwxr-xr-x 3 mab mab 2048 Apr  5  2011 EFI
drwxr-xr-x 4 mab mab 2048 Apr  5  2011 grub-mender-grubenv

On a few positive notes, the RFS looks correct and the boot partition is a FAT partition:

Device     Boot   Start     End Sectors  Size Id Type
/dev/sda1  *      16384   49151   32768   16M  c W95 FAT32 (LBA)
/dev/sda2         49152 3653631 3604480  1.7G 83 Linux
/dev/sda3       3653632 7258111 3604480  1.7G 83 Linux
/dev/sda4       7258112 7520255  262144  128M 83 Linux

Any thoughts on why Grub was selected as the bootloader, instead of U-Boot?

4

Hi @mabembedded,

Probably you are also missing the other feature settings. For an SD-card based board running on u-boot, this usually is

MENDER_FEATURES_ENABLE:append = " mender-uboot mender-image-sd"
MENDER_FEATURES_DISABLE:append = " mender-grub mender-image-uefi"

See also meta-mender-community/kas/include/nxp.yml at scarthgap · mendersoftware/meta-mender-community · GitHub, for example.

Greetz,
Josef