Re: Unable to boot 9.2 on SolidRun Cubox i4pro

[Nick Hudson <nick.hudson%gmx.co.uk@localhost>]

On 01/06/2021 16:36, Andrea Sormanni wrote:
> Hello,
> i'm unable to boot NetBSD 9.2 on my SolidRun Cubox i4pro, the GENERIC
> kernel loads but does not starts. After a while, a spontaneous reboot
> occurs, with same result.
>
> The board appears (or not ?) supported, among installation files on
> NetBSD site i can see several ARM kernels, including "CUBOX" and
> "CUBOX-I" variants, so i assume that the support is in place.
>
> I've downloaded the official armv7 installation image (checksum OK) in
> an x86_64 NetBSD VM running on my main workstation, then installed
> SolidRun U-Boot official version (with other versions -> black screen
> only) using loop device method:
>
> Host-001# ls
> armv7.img              spl-imx6-sdhc.bin      u-boot-imx6-sdhc.img
> Host-001# vnconfig /dev/vnd0 armv7.img
> Host-001# dd if=spl-imx6-sdhc.bin of=/dev/rvnd0 bs=1k seek=1 conv=sync
> 51+0 records in
> 51+0 records out
> 52224 bytes transferred in 0.003 secs (17408000 bytes/sec)
> Host-001# dd if=u-boot-imx6-sdhc.img  of=/dev/rvnd0 bs=1k seek=69 conv=sync
> 321+1 records in
> 322+0 records out
> 329728 bytes transferred in 0.021 secs (15701333 bytes/sec)
> Host-001# vnconfig -u /dev/vnd0
>
> Then flashed the resulting image on SD Card via BalenaEtcher, also
> trying several of them just in order to avoid a bad one, without
> errors.
>
> Here the boot log, captured via Cubox serial console:
>
> ------- cut here -------
[snip]
...

> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
> ## Starting EFI application at 12000000 ...
> WARNING: Invalid device tree, expect boot to fail

Pretty sure this is the problem

Check what dtb it's looking for via u-boot 'printenv'


> > > NetBSD/evbarm efiboot (arm), Revision 1.13 (Wed May 12 13:15:55 UTC 2021)
> Press return to boot now, any other key for boot prompt
> booting netbsd - starting in 0 seconds.
> 6744836+2068632+1388392 [403602+461280+481068]=0xb05038
>
> ------- ends here -------
>
> No other messages at all, board hangs until spontaneous reboot.

Enabling

options 	VERBOSE_INIT_ARM

and

options 	EARLYCONS=imx, CONSADDR=0x02020000
(hopefully this is right for your imx6)

will help as well.

Nick