Re: [meta-freescale] imx6qdl based board won't boot with kernel 4.9.x

From: "Stefan Birkholz" <birkholz@systecnet.com>
To: Cory <cory@otis8.com>,
	"meta-freescale@lists.yoctoproject.org"
	<meta-freescale@lists.yoctoproject.org>
Subject: Re: [meta-freescale] imx6qdl based board won't boot with kernel 4.9.x
Date: Wed, 11 Dec 2019 14:26:13 +0000	[thread overview]
Message-ID: <85026c56c96c4231a5baf6b42ace3b20@systecnet.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2305 bytes --]

Hi,

just a quick guess – the Load Address / Entry Point looks suspicious; for i.MX6DL I usually build the Kernel with “LOADADDR=10008000”.

Regards,
Stefan

Von: meta-freescale@lists.yoctoproject.org [mailto:meta-freescale@lists.yoctoproject.org] Im Auftrag von Cory
Gesendet: Mittwoch, 11. Dezember 2019 15:10
An: meta-freescale@lists.yoctoproject.org
Betreff: [meta-freescale] imx6qdl based board won't boot with kernel 4.9.x

Hi all,

I've been battling with upgrading the kernel our imx6qdl based custom board using Yocto Thud. We have been happily running the linux-imx 4.1-2 kernel, but it's time to push it forward to the 4.9.x versions. But it's not booting, at all. I've be poring over changes to other imxqdl based device trees and defconfigs, and nothing is making sense as to what change I may have missed (because I can't find many). We are running U-Boot 2017.11 (I know that could also be upgraded, but that shouldn't matter...unless I'm wrong).

I've stripped our kernel customizations down to nothing except for our board device tree, which works fine in kernel 4.1-X. We've never had issues like this with a kernel version bump before. After U-Boot loads the device tree and kernel, there is no output. When I check the HW, I've probed the DDR clock and it's stuck high. All 4.9+ kernels included in meta-freescale behave this same way:

## Booting kernel from Legacy Image at 10800000 ...

   Image Name:   Linux-4.9.123-imx+g6a71cbc

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    5476256 Bytes = 5.2 MiB

   Load Address: 10808000

   Entry Point:  10808000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 11000000

   Booting using the fdt blob at 0x11000000

   Loading Kernel Image ... OK

   Using Device Tree in place at 11000000, end 1100dd66

Starting kernel ...

## NOTHING AFTER THIS ##

My main question is, has anyone else successfully used the linux-imx 4.9.x kernels (4.9.11, 4.9.123, etc), on a board based on the imx6qdl, and if so, do you have any tricks I'm missing? Has something major changed  in 4.9.x that affects the imx6 that I may have missed? (except for the framebuffer, that's another issue I'll deal with later).

I appreciate any guidance!

Cheers,
Cory

[-- Attachment #2: Type: text/html, Size: 6056 bytes --]