From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: imx6qdl based board won't boot with kernel 4.9.x
To: meta-freescale@lists.yoctoproject.org
From: "Cory" <cory@otis8.com>
X-Originating-Location: Johannesburg, Gauteng, ZA (105.184.14.176)
X-Originating-Platform: Mac Chrome 78
User-Agent: GROUPS.IO Web Poster
MIME-Version: 1.0
Date: Wed, 11 Dec 2019 06:10:23 -0800
Message-ID: <epf0.1576073423341825154.02Nz@lists.yoctoproject.org>
Content-Type: multipart/alternative; boundary="mMkz8Etv5CLgo1Yf8Tis"

--mMkz8Etv5CLgo1Yf8Tis
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi all,

I've been battling with upgrading the kernel our imx6qdl based custom boar=
d 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 boot=
ing, 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 m=
issed (because I can't find many). We are running U-Boot 2017.11 (I know th=
at 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 boa=
rd device tree, which works fine in kernel 4.1-X. We've never had issues li=
ke this with a kernel version bump before. After U-Boot loads the device tr=
ee 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 beh=
ave this same way:

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

Image Name:=C2=A0 =C2=A0Linux-4.9.123-imx+g6a71cbc

Image Type:=C2=A0 =C2=A0ARM Linux Kernel Image (uncompressed)

Data Size:=C2=A0 =C2=A0 5476256 Bytes =3D 5.2 MiB

Load Address: 10808000

Entry Point:=C2=A0 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=C2=A0 in =
4.9.x that affects the imx6 that I may have missed? (except for the framebu=
ffer, that's another issue I'll deal with later).

I appreciate any guidance!

Cheers,
Cory

--mMkz8Etv5CLgo1Yf8Tis
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<p>Hi all,<br /><br />I've been battling with upgrading the kernel our imx6=
qdl based custom board using Yocto Thud. We have been happily running the l=
inux-imx 4.1-2 kernel, but it's time to push it forward to the 4.9.x versio=
ns. But it's not booting, at all. I've be poring over changes to other imxq=
dl based device trees and defconfigs, and nothing is making sense as to wha=
t change I may have missed (because I can't find many). We are running U-Bo=
ot 2017.11 (I know that could also be upgraded, but that shouldn't matter..=
.unless I'm wrong).<br /><br />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. Af=
ter U-Boot loads the device tree and kernel, there is no output. When I che=
ck 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:<br /><br /></p>
<p>## Booting kernel from Legacy Image at 10800000 ...</p>
<p>&nbsp; &nbsp;Image Name:&nbsp; &nbsp;Linux-4.9.123-imx+g6a71cbc</p>
<p>&nbsp; &nbsp;Image Type:&nbsp; &nbsp;ARM Linux Kernel Image (uncompress=
ed)</p>
<p>&nbsp; &nbsp;Data Size:&nbsp; &nbsp; 5476256 Bytes =3D 5.2 MiB</p>
<p>&nbsp; &nbsp;Load Address: 10808000</p>
<p>&nbsp; &nbsp;Entry Point:&nbsp; 10808000</p>
<p>&nbsp; &nbsp;Verifying Checksum ... OK</p>
<p>## Flattened Device Tree blob at 11000000</p>
<p>&nbsp; &nbsp;Booting using the fdt blob at 0x11000000</p>
<p>&nbsp; &nbsp;Loading Kernel Image ... OK</p>
<p>&nbsp; &nbsp;Using Device Tree in place at 11000000, end 1100dd66</p>
<p>Starting kernel ...<br /><br />## NOTHING AFTER THIS ##<br /><br />My m=
ain question is, has anyone else successfully used the linux-imx 4.9.x kern=
els (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&nbsp; 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).<br /><br />I appreciate any gu=
idance!<br /><br />Cheers,<br />Cory</p>

--mMkz8Etv5CLgo1Yf8Tis--