From: Denis Benato <benato.denis96@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Cannot boot imx8mm symphony board
Date: Tue, 29 Apr 2025 21:51:12 +0200 [thread overview]
Message-ID: <c84e8246-8104-4409-8d95-389d61bc07af@gmail.com> (raw)
Hello,
I write this to ask for help in booting linux on a slight variation of the development board imx8mm-var-symphony.
At the moment I am using an u-boot version that can boot a linux 6.6 kernel and a 5.15.60 that I have
adapted to my custom board: https://github.com/NeroReflex/linux-imx/tree/old
I can boot that without any problem: the gpu works as well as networking, backlight, RTC and every other device on the board; however I want to use either 6.14.4 or linux-next.
On that version I can see a device tree arch/arm64/boot/dts/freescale/imx8mm-var-som-symphony.dts
that, from my understanding, is supposed to at least arrive at the point of printing something from the debug serial, where I can actually pick up and start figuring out what's missing/wrong.
My problem is that u-boot (the same u-boot version that can boot v6.6 just fine) works flawlessly, the fdt is
loaded into memory as well as the kernel, but then I have no output on the debug serial, no backlight is turned on (I tried adding my screen to the device tree) and the ethernet controller on my board does not reset as
it usually does when a working kernel is booted: this lead me into thinking there is a problem somewhere in
the early boot sequence.
Therefore I attempted to use the previously working device tree, the one from 5.15, but to no avail.
At this time I think my problem can only be either one of these:
- u-boot I am using is not suitable to boot kernels past 6.6
- I have a problem in my config
I also tried using the following patch as it appears to be relevant for this hardware:
https://lore.kernel.org/all/20250311-wip-obbardc-qcom-defconfig-interconnects-builtin-v1-1-675b6bc57176@linaro.org
but again to no avail.
Can someone please point me in the right direction? What config am I supposed to be using to boot that board?
What version of u-boot (and configuration) should I be using?
Thanks in advice,
Denis
reply other threads:[~2025-04-29 19:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c84e8246-8104-4409-8d95-389d61bc07af@gmail.com \
--to=benato.denis96@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®