From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f173.google.com (mail-oi1-f173.google.com [209.85.167.173]) by mx.groups.io with SMTP id smtpd.web09.4544.1576076712175782426 for ; Wed, 11 Dec 2019 07:05:12 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Yd0IEiAO; spf=pass (domain: gmail.com, ip: 209.85.167.173, mailfrom: marc.ferland@gmail.com) Received: by mail-oi1-f173.google.com with SMTP id d62so13435623oia.11 for ; Wed, 11 Dec 2019 07:05:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zxRys/LicZ/o6AC9WHj7XhO+rvYqnrio7Qto0td0jLU=; b=Yd0IEiAOVOpSd/8j8qCe2xFiPW2A2fN7voYs6C6ElnMj+J7z0QODcQBQMw4w1/x50p X2yau5LtS+oCU6Eh7qBGbYOGPaAagiamYFqiiqPO4B1/zsiYYcbyzn5hA9EmhKVVxonj wKfV+ZJtntS547TsL81ydl4EZTUAYJBGUTd+y4CopCZYaWRi+l9Y37OAjnX4DIMGgM/g O5qqXa/ixfxVG7BFqoKzUzkqaFJmFkNcUb3+Rt/UnDf6f+yIetHxcwhmakkvB2JF9joG G9ovFrgy3Kbs70nU7YFaP9GtzQ6uhFLXCuFpSUPP9gz+TXOaEQGiUn27fLZV8MxUYG87 RHyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zxRys/LicZ/o6AC9WHj7XhO+rvYqnrio7Qto0td0jLU=; b=jVS4/BFHOXWKV4QSkncP6xArJUGX9WF5IIE89xUaJv5Xk6xz7xjuM74yJq/D0xj9Ns GNV1b+h9prqDBRcDhcuJnU/Gi60WWeMN5FpoqaJ+2lt+nIyAfzXq26hzwoKawrghDrrL 8jQNPRZRqFzi/0RuxSq6hDmiwMx1B9e7rS4F08nIp5vugbpoUIDl3MYs34ClmiBODnZY 5MZBjVji39oT2M7CY9g9fhaGJuFAFjTMiyPF3uvd1fL7qdGZMUAUqV8V/BYqwceRvkri GA66S4309yWWdELR5sbEo29rvQrzF5Ib3pmAmqrtDgadgrPikR/bGxxSyyT+MuXkYGzF Rn4A== X-Gm-Message-State: APjAAAX69BWwmEtxtLX5JmlCZBBSKizmmeNPwlXaK5HxG/Lxa/EIFK0c Nr7xvhtvzfE0pkx/mL0KTmQjjVTUuHEz5KLJfj4= X-Google-Smtp-Source: APXvYqwUgqWwh3qxnznU7emZWQmESjaNFR9SD4B4zEwf/sRlRRfUPlmKsXtF1BWKY0eiOOFV1C7vaqJz9BJEYKsB0NQ= X-Received: by 2002:aca:5143:: with SMTP id f64mr3050835oib.66.1576076711317; Wed, 11 Dec 2019 07:05:11 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: "Marc Ferland" Date: Wed, 11 Dec 2019 10:05:00 -0500 Message-ID: Subject: Re: [meta-freescale] imx6qdl based board won't boot with kernel 4.9.x To: Cory Cc: meta-freescale@lists.yoctoproject.org Content-Type: multipart/alternative; boundary="0000000000008454d005996ef428" --0000000000008454d005996ef428 Content-Type: text/plain; charset="UTF-8" On Wed, Dec 11, 2019 at 9:10 AM Cory wrote: > 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). > > Happens to me from time to time. Generally it is something with the kernel configuration (try deactivating stuff in the kernel until you get something that boots) or the device tree (again try commenting stuff out until you see a change, I've seen DTBs working with old kernel and breaking with recent ones). Hope that helps, Marc --0000000000008454d005996ef428 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Dec 11, 2019 at 9:10 AM Cory <cory@otis8.com> wrote:

Hi all,

I've been batt= ling with upgrading the kernel our imx6qdl based custom board using Yocto T= hud. 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 an= d defconfigs, and nothing is making sense as to what change I may have miss= ed (because I can't find many). We are running U-Boot 2017.11 (I know t= hat 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-Bo= ot loads the device tree and kernel, there is no output. When I check the H= W, 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 ...

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

=C2=A0 =C2=A0Image Type:=C2=A0 =C2=A0ARM Linux Kernel Image (uncompresse= d)

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

=C2=A0 =C2=A0Load Address: 10808000

=C2=A0 =C2=A0Entry Point:=C2=A0 10808000

=C2=A0 =C2=A0Verifying Checksum ... OK

## Flattened Device Tree blob at 11000000

=C2=A0 =C2=A0Booting using the fdt blob at 0x11000000

=C2=A0 =C2=A0Loading Kernel Image ... OK

=C2=A0 =C2=A0Using Device Tree in place at 11000000, end 1100dd66

Starting kernel ...

## NOTHING AFTER THIS ##

My main quest= ion 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 framebuffer, that= 's another issue I'll deal with later).

Happens to me from time to time. Generally it is something with the kerne= l configuration (try deactivating stuff in the kernel until you get somethi= ng that boots) or the device tree (again try commenting stuff out until you= see a change, I've seen DTBs working with old kernel and breaking with= recent ones).

Hope that helps,

=
Marc
--0000000000008454d005996ef428--