Dear all,

 

I'm just trying to get a HummingBoard-Edge (i.MX6 Quad, 2GB) working with Armbian_5.20_Cubox-i_Ubuntu_xenial_4.7.3. Unfortunately, the board is recognized as CuBox-i, U-Boot loads the wrong dtb file (imx6q-cubox-i.dtb) and I have no access to the internal eMMC card (mmcblk1). By the way, it's the same issue with ArchLinuxArm.

 

Do I have to somehow modify the U-Boot environment variables to get the board being recognized as Hummingoard2? Do you have any other ideas?

 

Thank you very much for your help!

 

Best regards

Andreas

 

 

U-Boot 2013.10-rc4 (Aug 31 2016 - 17:35:12)

CPU:   Freescale i.MX6Q rev1.5 at 792 MHz
Reset cause: WDOG
Board: MX6-CuBox-i
DRAM:  2 GiB
MMC:   FSL_SDHC: 0
In:    serial
Out:   serial
Err:   serial
Net:   FEC [PRIME]
Hit any key to stop autoboot:  0

 

Unfortunately, the board is recognized as CuBox-i, U-Boot loads the wrong dtb file (imx6q-cubox-i.dtb)

 

Did you try the 'setenv fdtfile' approach as outlined here already?

We all rely on correct board recognition which was done by Solidrun. You can either dig into their u-boot and fix this, report the issue there or set correct fdtfile manually in boot script as Thomas suggested.

@tkaiser: Thank you for the hint. boot.cmd now reads as follows. I compiled it via mkimage.

 

 

setenv fdtfile imx6q-hummingboard2.dtb
#run autodetectfdt
setenv ramdisk_addr 0x14800000
setenv bootargs "root=/dev/mmcblk0p1 rootfstype=ext4 rootwait console=ttymxc0,1$
ext2load mmc 0 ${fdt_addr} /boot/dtb/${fdt_file} || fatload mmc 0 ${fdt_addr} /$
ext2load mmc 0 ${ramdisk_addr} /boot/uInitrd || fatload mmc 0 ${ramdisk_addr} u$
ext2load mmc 0 ${loadaddr} /boot/zImage || fatload mmc 0 ${loadaddr} zImage || $
bootz ${loadaddr} ${ramdisk_addr} ${fdt_addr}
# Recompile with:
# mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

 

The device is still recognized as SolidRun Cubox-i Dual/Quad. Parts of the boot log:

 

 

U-Boot 2013.10-rc4 (Aug 31 2016 - 17:35:12)

CPU:   Freescale i.MX6Q rev1.5 at 792 MHz
Reset cause: WDOG
Board: MX6-CuBox-i
DRAM:  2 GiB
MMC:   FSL_SDHC: 0
In:    serial
Out:   serial
Err:   serial
Net:   FEC [PRIME]
Hit any key to stop autoboot:  0

 

 

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 4.7.3-cubox (root@xenial) (gcc version 4.9.4 20151028 (prerelease) (Linaro GCC 4.9-2016.02) ) #27 SMP Wed Sep 14 23:06:12 CEST 2016
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=50c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: SolidRun Cubox-i Dual/Quad

 

mmc0 = SD card functional.

 

 

mmc0: host does not support reading read-only switch, assuming write-enable
mmc0: new high speed SDHC card at address aaaa
mmcblk0: mmc0:aaaa SL08G 7.40 GiB
 mmcblk0: p1

 

mmc1 = eMMC (?) shows up in the log but not availabe under /dev/disks

 

 

sdhci-esdhc-imx 2190000.usdhc: allocated mmc-pwrseq
mmc1: SDHCI controller on 2190000.usdhc [2190000.usdhc] using ADMA
mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
mmc1: new high speed SDIO card at address 0001
 

 

@Igor: I will report the issue in the SR forum.

You made a typo:

fdt_file not fdtfile

That's why there was no change. And those:

mmc1: queuing unknown CIS tuple 0x80 (2 bytes)

in log are due too default enabled eMMC for all boards. If you board does not have it you will see this ... it must be fixed in u-boot. 

Thank you, Igor, that fixed it!

 

 

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 4.7.3-cubox (root@xenial) (gcc version 4.9.4 20151028 (prerelease) (Linaro GCC 4.9-2016.02) ) #27 SMP Wed Sep 14 23:06:12 CEST 2016
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=50c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: SolidRun HummingBoard2 Dual/Quad

eMMC is now accessible:

 

mmc1: new DDR MMC card at address 0001
mmcblk1: mmc1:0001 4FPD3R 3.64 GiB
mmcblk1boot0: mmc1:0001 4FPD3R partition 1 4.00 MiB
mmcblk1boot1: mmc1:0001 4FPD3R partition 2 4.00 MiB
Key type encrypted registered
mmcblk1rpmb: mmc1:0001 4FPD3R partition 3 512 KiB