New NPi i.MX6 crashes during Kernel init

Products & Technology Single Board Computers
#1

So i just received my board and wanted to check it out but it keeps crashing on starting the kernell…
Below is the full console log.
U-Boot 2019.04-g7c1d8e17-dirty (Dec 26 2019 - 05:50:56 +0000)

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

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
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1…
switch to partitions #0, OK
mmc0 is current device
Checking for: /uEnv.txt …
1552 bytes read in 10 ms (151.4 KiB/s)
Loaded environment from /uEnv.txt
Importing environment from mmc …
Checking if uenvcmd is set …
Checking if client_ip is set …
Checking for: /boot.scr …
Checking for: /boot/boot.scr …
Checking for: /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 /vmlinuz-4.19.71-imx-r1 …
debug: [enable_uboot_overlays=1] …
debug: [uboot_base_dtb=] …
loading /dtbs/4.19.71-imx-r1/imx6ull-seeed-npi.dtb …
38661 bytes read in 12 ms (3.1 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] …
DTOVERLAY[debug]: param no:5 0x83000000 0x88000000 uEnv.txt 0x80800000

DTOVERLAY[debug]: ** uEnv.txt file length:0x610

DTOVERLAY[debug]: ** /lib/firmware/imx-fire-led-overlay.dtbo file length:0x615

loading overlay：/lib/firmware/imx-fire-led-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-lcd5-overlay.dtbo file length:0x175f

loading overlay：/lib/firmware/imx-fire-lcd5-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-sound-overlay.dtbo file length:0xd72

loading overlay：/lib/firmware/imx-fire-sound-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-key-overlay.dtbo file length:0x336

loading overlay：/lib/firmware/imx-fire-key-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-mpu6050-overlay.dtbo file length:0x34e

loading overlay：/lib/firmware/imx-fire-mpu6050-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-18b20-overlay.dtbo file length:0x30e

loading overlay：/lib/firmware/imx-fire-18b20-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-hdmi-overlay.dtbo file length:0xade

loading overlay：/lib/firmware/imx-fire-hdmi-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-dht11-overlay.dtbo file length:0x30e

loading overlay：/lib/firmware/imx-fire-dht11-overlay.dtbo
7982616 bytes read in 363 ms (21 MiB/s)
loading /initrd.img-4.19.71-imx-r1 …
4710916 bytes read in 220 ms (20.4 MiB/s)
debug: [console=ttymxc0 root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 vt.global_cursor_default=0 quiet] …
debug: [bootz 0x80800000 0x88000000:47e204 0x83000000] …
Kernel image @ 0x80800000 [ 0x000000 - 0x79ce18 ]

Flattened Device Tree blob at 83000000

Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8303cfff
Modify /soc/aips-bus@2200000/epdc@228c000:status disabled
ft_system_setup for mx6

Starting kernel …

[ 1.531554] fec 20b4000.ethernet: Invalid MAC address: 00:00:00:00:00:00
[ 1.605788] fec 2188000.ethernet: Invalid MAC address: 00:00:00:00:00:00
[ 1.848889] cpu cpu0: running cpufreq without cooling device: 0
[ 1.960697] sii902x 1-0039: Sii902x: cound not find device

U-Boot 2019.04-g7c1d8e17-dirty (Dec 26 2019 - 05:50:56 +0000)

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

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
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1…
switch to partitions #0, OK
mmc0 is current device
Checking for: /uEnv.txt …
1552 bytes read in 10 ms (151.4 KiB/s)
Loaded environment from /uEnv.txt
Importing environment from mmc …
Checking if uenvcmd is set …
Checking if client_ip is set …
Checking for: /boot.scr …
Checking for: /boot/boot.scr …
Checking for: /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 /vmlinuz-4.19.71-imx-r1 …
debug: [enable_uboot_overlays=1] …
debug: [uboot_base_dtb=] …
loading /dtbs/4.19.71-imx-r1/imx6ull-seeed-npi.dtb …
38661 bytes read in 12 ms (3.1 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] …
DTOVERLAY[debug]: param no:5 0x83000000 0x88000000 uEnv.txt 0x80800000

DTOVERLAY[debug]: ** uEnv.txt file length:0x610

DTOVERLAY[debug]: ** /lib/firmware/imx-fire-led-overlay.dtbo file length:0x615

loading overlay：/lib/firmware/imx-fire-led-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-lcd5-overlay.dtbo file length:0x175f

loading overlay：/lib/firmware/imx-fire-lcd5-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-sound-overlay.dtbo file length:0xd72

loading overlay：/lib/firmware/imx-fire-sound-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-key-overlay.dtbo file length:0x336

loading overlay：/lib/firmware/imx-fire-key-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-mpu6050-overlay.dtbo file length:0x34e

loading overlay：/lib/firmware/imx-fire-mpu6050-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-18b20-overlay.dtbo file length:0x30e

loading overlay：/lib/firmware/imx-fire-18b20-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-hdmi-overlay.dtbo file length:0xade

loading overlay：/lib/firmware/imx-fire-hdmi-overlay.dtbo
DTOVERLAY[debug]: ** /lib/firmware/imx-fire-dht11-overlay.dtbo file length:0x30e

loading overlay：/lib/firmware/imx-fire-dht11-overlay.dtbo
7982616 bytes read in 363 ms (21 MiB/s)
loading /initrd.img-4.19.71-imx-r1 …
4710916 bytes read in 219 ms (20.5 MiB/s)
debug: [console=ttymxc0 root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 vt.global_cursor_default=0 quiet] …
debug: [bootz 0x80800000 0x88000000:47e204 0x83000000] …
Kernel image @ 0x80800000 [ 0x000000 - 0x79ce18 ]

Flattened Device Tree blob at 83000000

Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8303cfff
Modify /soc/aips-bus@2200000/epdc@228c000:status disabled
ft_system_setup for mx6

Starting kernel …

[ 1.531406] fec 20b4000.ethernet: Invalid MAC address: 00:00:00:00:00:00
[ 1.605557] fec 2188000.ethernet: Invalid MAC address: 00:00:00:00:00:00
[ 1.846691] cpu cpu0: running cpufreq without cooling device: 0
[ 1.951126] sii902x 1-0039: Sii902x: cound not find device

Setting it to boot from SD card instead doesn’t help:
U-Boot 2019.04-g7c1d8e17-dirty (Jan 16 2020 - 11:30:16 +0000)

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

WARNING:init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc0 is current device
flash target is MMC:0

It probably has something to do with the bold line…
Tried reflashing the SD card with the latest image, but no difference.
But odd thing is that the console complains about missing SD card when boot is set to eMMC and no SD is present…
So maybe the jumpers aren’t read properly?

Either way, this isn’t the buildquality I’d expect from Seeed (is any Q&A done?)
There’s barely any solder on those pins (which i think are power pins)

solder
solder2195×645 308 KB

And the placement seems a little bit off (but i’m new so cant post picture).

#2

There are no notable exceptions from the way you started the log.But your board is constantly rebooting, and I suggest you use a steady power supply to test it. @Craio

#3

Well since the post i’ve kept experimenting and managed to install an image for a different board (with the same processor) so power isn’t the cause.

But i expect that the board doesn’t come with anything pre-installed on the eMMC? Furthermore, it seems likely the cause is that the current latest official build is corrupt, given that the size is <100MB and some directories are empty.

#4

Customizing the software is possible, but if you can be sure that there is no problem with the power supply and that there may be a hardware problem with the board, you are advised to contact the Seeed aftersales department.

#5

I don’t want to customize the software at this point, i just want a working image for the board.
There is no problem with the power supply if the board boots fine with an alternative image… no idea how to be sure that there might be a hardware issue.

#6

@Craio The fastest way is to use the same SD card, boot from the SD card on another board, and test it again.
You can also remove the quit word from the uEnv.txt file on the SD boot partition.Then start again to get more logs.This is a detailed log, but it does not show power-related issues.

#7

@Baozhu I agree that comparing to another board would be the quickest, but i only have one. Furthermore, given that the board doesn’t startup properly probably because the missing directory content mentioned earlier (which includes an empty boot).

#8

You need to boot from the SD card, burn the firmware to the SD card, and the boot partition will have files.

#9

Be that as it may, i’ve tried flashing with the SD image a couple of times now without succes and am still waiting for someone to say the image is actually functional… or even just give me checksum for it.

The image is called ‘imx6ull-debian-buster-console-armhf-latest-2gb’ but it is only about 350MB (extracted).

So after learning a lot and cursing even more:
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 …

But it’s not going any further than this… Any idea where to start looking?

#10

Managed to get passed it, turns out the SD card was faulty…
But either way, gave up on using that image because it runs the 4.19 kernel.

#11

The current 4.19 kernel is an LTS version with community long-term maintenance support.

#12

When I installed it, the EOL of 4.19 was december this year, this was changed in the beginning of june.
The most recent LTS is 5.4, the community yocto releases for i.MX6 boards use 5.4. (codename zeus) which i have more faith in than the Seeed releases based on beaglebone code. Given that the Kernel is built with the i.MX in mind and not the Ti processors.

Given that sysfs access to gpio is deprecated and mem is discouraged, i’d prefer to use 5.5 because in that release libgpiod is ‘completed’. But i’m still learning the ropes of Yocto.

#13

Just file system differences, Yocto is not suitable for quick evaluation.As you know, not everyone can build a Yocto development environment quickly.