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 <[email protected]
<mailto:[email protected]>> 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: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-freescale/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#24162):
https://lists.yoctoproject.org/g/meta-freescale/message/24162
Mute This Topic: https://lists.yoctoproject.org/mt/68150691/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-freescale/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
