Brand new cubox-i4x4 won't boot Debian_Stretch_next

Recommended Posts



I have a brand new cubox-i4x4 and am attempting to install 

Armbian Stretch 
mainline kernel 4.15.y

I downloaded the image from used keka and etch to extract and write image to the SD card. After installing the SD card in the cubox and powering on, it gets stuck at:

U-Boot SPL 2017.11-armbian (Jan 24 2018 - 22:39:16)
Trying to boot from MMC1

U-Boot 2017.11-armbian (Jan 24 2018 - 22:39:16 +0100)

CPU:   Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz)
CPU:   Extended Commercial temperature grade (-20C to 105C) at 24C
Reset cause: POR
Board: MX6 Cubox-i
DRAM:  2 GiB
*** Warning - bad CRC, using default environment

No panel detected: default to HDMI
Display: HDMI (1024x768)
In:    serial
Out:   serial
Err:   serial
Net:   FEC
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
1816 bytes read in 104 ms (16.6 KiB/s)
## Executing script at 12000000
0 bytes read in 67 ms (0 Bytes/s)
113 bytes read in 83 ms (1000 Bytes/s)
38007 bytes read in 221 ms (167 KiB/s)
4824515 bytes read in 365 ms (12.6 MiB/s)
5546904 bytes read in 407 ms (13 MiB/s)
## Loading init Ramdisk from Legacy Image at 14800000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4824451 Bytes = 4.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800c476

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


I have tried setting the fdt_file parameter in /boot/armbianEnv.txt file and tried all the available variant of imx6q-cubix-i*.dtb files but get the same result. 


The cubox boots ok from Solid-run's ignition image, but I want to install armbian. Any advice would be greatly apprciated.


Link to post
Share on other sites
Donate and support the project!

This topic is now closed to further replies.