From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Ra C <rcrichlow9000@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] stm32mp1 kernel won't boot on custom board
Date: Sat, 28 Jan 2023 22:21:02 +0100 [thread overview]
Message-ID: <20230128222102.2de52447@windsurf> (raw)
In-Reply-To: <CACHw65JhmQX27SkN0jSMAD-P=UuwOizZc+sG+WatprbH_PFFyQ@mail.gmail.com>
On Sat, 28 Jan 2023 14:52:12 -0600
Ra C <rcrichlow9000@gmail.com> wrote:
> I have a custom stm32mp157a board which runs OK with a modified 5.4 kernel.
> I want to migrate to the latest stm supported kernel.
> I built a stm32mp157a_dk1 target using the BR2_EXTERNAL feature described
> here: https://github.com/bootlin/buildroot-external-st which builds a 5.15
> kernel.
>
> Using the same dtb , the 5.15 kernel fails to mount the root device (a
What do you mean by "using the same DTB" ?
Make sure to use the DTB that matches the kernel version you're using.
Even though DTBs are in theory kernel-version independent, there are
quite frequently some subtle changes that causes a DTB written for
kernel version X to not work with kernel version Y.
Also, make sure to pass "rootwait" in your kernel command line, to tell
the kernel to wait for the root device to appear. As SD/MMC devices are
detected asynchronously, sometimes they are detected too late compared
to the point where the kernel attempts to mount the rootfs.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-01-28 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 20:52 [Buildroot] stm32mp1 kernel won't boot on custom board Ra C
2023-01-28 21:21 ` Thomas Petazzoni via buildroot [this message]
2023-01-28 22:52 ` Ra C
2023-01-30 14:54 ` Simon Doppler
2023-02-08 16:30 ` Ramon Crichlow
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=20230128222102.2de52447@windsurf \
--to=buildroot@buildroot.org \
--cc=rcrichlow9000@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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