From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail2.skidata.com (mail2.skidata.com [91.230.2.91]) by mx.groups.io with SMTP id smtpd.web09.4630.1576077042170199287 for ; Wed, 11 Dec 2019 07:10:43 -0800 Authentication-Results: mx.groups.io; dkim=fail reason="signature has expired" header.i=@skidata.com header.s=selector1 header.b=Vz2TBM6i; spf=pass (domain: skidata.com, ip: 91.230.2.91, mailfrom: prvs=2416d3f76=richard.leitner@skidata.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=skidata.com; i=@skidata.com; q=dns/txt; s=selector1; t=1576077042; x=1607613042; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=esLgxvZBpWwjz+jtGz1Oyi+dn6f0EBrIkkWqeOwoni4=; b=Vz2TBM6iaN9aA2TbyE/UqCYzbXi6USbg8JtPEO0WAVleSaNGedhsiEuE OY7tGxDR2sHJuBA1UQUdDGHx2X4JeW4ojdNrGQyh54HFRNrWcYJx/YsFa jJslJAg2ynEHnDENtFQfXTlc8IhEDpytmjuHdQqVlzApskWX1IzSf+iEY ljE9nOND5n1vm3pXeONBR4gqabhaimCFJWxld2ComjDI9KRh3iqyPgwrZ SQDaavHhSfHnp04BCo3Rmzf2Pt5t+sZWdnd86V+RTbALUjEBo2WQEKX6j MSsdWv1VUXSyx3pNpu5znw/Br/W4UTpQraWTfeOWq7B+YJBA/xvx4WXBa g==; IronPort-SDR: BZolLWGpIM3GX6/sVoqe8IrMI/eR1mIUf1Oi7SIWIA5+3Xu3ZSkb1AchrcL0iAbMGzWo1zaTMA /YYZ8uBJ82woHOSzqiyzcbnSR+gKkWoHA3duBC5+b/kuySzzJ0ZOY5p/IGOUcJfL0tt7Fy0ol/ xZT6ZhFc5Pnyxjgit7A+m4/UMAhHg01/M6NGa/X85j86C+Txtka/r9RrWVH5toC/+ciouMydzn +YUAGFWtipArKnvbSJou6UmNtUiJjSM2Oo/6v3u2lAOXNR+OOG/QVjBlUivSmVV/46qXF5kMCb 1D0= X-IronPort-AV: E=Sophos;i="5.69,301,1571695200"; d="scan'208";a="2457295" Subject: Re: [meta-freescale] imx6qdl based board won't boot with kernel 4.9.x To: References: From: "Richard Leitner" Message-ID: Date: Wed, 11 Dec 2019 16:10:38 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: Return-Path: richard.leitner@skidata.com X-Originating-IP: [192.168.111.252] X-ClientProxiedBy: sdex5srv.skidata.net (192.168.111.83) To sdex5srv.skidata.net (192.168.111.83) Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Hi, some things I would try/check: * is the kernel not booting or just failing to output to the serial? to check this you may for example add a heartbeat LED... * enable debug-ll, earlyprintk and similar stuff and see if you get more output * use a real debugger (if you have one) hope that helps. regards;richard.l On 11/12/2019 16:05, Marc Ferland wrote: > 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 > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#24160): https://lists.yoctoproject.org/g/meta-freescale/message/24160 > Mute This Topic: https://lists.yoctoproject.org/mt/68150691/3617580 > Group Owner: meta-freescale+owner@lists.yoctoproject.org > Unsubscribe: https://lists.yoctoproject.org/g/meta-freescale/unsub [richard.leitner@skidata.com] > -=-=-=-=-=-=-=-=-=-=-=- >