AnsweredAssumed Answered

i.MX6ULL board stuck at Starting kernel

Question asked by Michiel TJampens on May 28, 2020
Latest reply on May 29, 2020 by Michiel TJampens

So i bought a Seeed I.MX6ULL board to gain experience with I.MX processors but the official image causes the board to go crash on starting the kernel. Then i managed to install an EVK image using uuu and that boots to log in (on console only) so i tried making my own image based on these (using 5.7 kernel) steps and after a lot cursing and learning new things i managed to get to a point where the board gets to 'Starting kernel' but then nothing happens.

 

 

U-Boot 2019.04-00676-gd447c486 (May 27 2020 - 05:26:26 +0000)

CPU: Freescale i.MX6ULL rev1.1 792 MHz (running at 396 MHz)
CPU: Industrial temperature grade (-40C to 105C) at 49C
Reset cause: POR
Model: Freescale i.MX6 ULL 14x14 EVK Board
Board: MX6ULL 14x14 EVK
DRAM: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

Display: TFT43AB (480x272)
Video: 480x272x24
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc1(part 0) is current device
flash target is MMC:1
Net:
Error: ethernet@020b4000 address not set.

Error: ethernet@020b4000 address not set.

Error: ethernet@02188000 address not set.
eth-1: ethernet@020b4000
Error: ethernet@02188000 address not set.
, eth-1: ethernet@02188000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
switch to partitions #0, OK
mmc1(part 0) is current device
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
1587 bytes read in 9 ms (171.9 KiB/s)
Loaded environment from /boot/uEnv.txt
debug: [dtb=imx6ull-seeed-npi.dtb] ...
Using: dtb=imx6ull-seeed-npi.dtb ...
Checking if uname_r is set in /boot/uEnv.txt...
Running uname_boot ...
loading /boot/vmlinuz-5.7.0-rc6-armv7-x5 ...
10250152 bytes read in 456 ms (21.4 MiB/s)
debug: [enable_uboot_overlays=1] ...
debug: [uboot_base_dtb=] ...
loading /boot/dtbs/5.7.0-rc6-armv7-x5/imx6ull-seeed-npi.dtb ...
38661 bytes read in 14 ms (2.6 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] ...
debug: [console=ttymxc0,115200n8 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 vt.global_cursor_default=0 quiet] ...
debug: [bootz 0x80800000 - 0x83000000] ...
Kernel image @ 0x80800000 [ 0x000000 - 0x9c67a8 ]
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8300c704
Modify /soc/aips-bus@2200000/epdc@228c000:status disabled
ft_system_setup for mx6

Starting kernel ...

 

Any tips on where to start looking? I found a page that said that it might actually keep going but just the console port being wrong. But it's the same as for the EVK image and that works fine...

I tried rebuilding the kernel to output more info but if it's not starting...

Or point me towards a different howto?

Outcomes