Debugging non-booting Mainline Linux Kernel for Colibri T30

Technical Support
, , ,
1

Dear Forum,
dear Mr. Ziswiler,

We did compile the linux kernel 4.13 and the device tree (outside our oe environment) with the following command:

make clean
make colibri_t30_defconfig
LOADADDR=0x80008000 make -j3 uImage 2>&1 | tee build.log

after flashing it to our T30 board (Version E) we get the following output on the serial console:

U-Boot 2016.11-2.7.4+g1b121c6 (Oct 05 2017 - 04:24:38 +0000)

TEGRA30
DRAM:  1 GiB
MMC:   Tegra SD/MMC: 0, Tegra SD/MMC: 1
In:    serial
Out:   vidconsole
Err:   vidconsole
Model: Toradex Colibri T30 1GB V1.1E, Serial# 02923461
Net:   No ethernet found.
Hit any key to stop autoboot:  0
Booting from internal eMMC chip...
reading tegra30-colibri-eval-v3.dtb
27055 bytes read in 17 ms (1.5 MiB/s)
reading uImage
5223400 bytes read in 141 ms (35.3 MiB/s)
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-4.13.11-dirty
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5223336 Bytes = 5 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 82000000
   Booting using the fdt blob at 0x82000000
   Loading Kernel Image ... OK
   Using Device Tree in place at 82000000, end 820099ae

Starting kernel ...

What would be the next steps to debug our problem further?

2

There is no colibri_t30_defconfig in mainline kernel, where did you got it from? have you tried tegra_defconfig?

3

Mr. Sliwa. Thank you. That was it!

4

You might be better off trying LTS 4.14 with some of the patches as noted here plus maybe some stuff just recently submitted for inclusion.