From: Sascha Hauer <sha@pengutronix.de>
To: marc@cpdesign.com.au
Cc: barebox@lists.infradead.org
Subject: Re: Troubles booting kernel with new imx8 board
Date: Fri, 26 May 2023 13:30:25 +0200 [thread overview]
Message-ID: <20230526113025.GT17518@pengutronix.de> (raw)
In-Reply-To: <10297393.nUPlyArG6x@dev8>
On Fri, May 26, 2023 at 08:46:40PM +1000, marc@cpdesign.com.au wrote:
> Hi all,
>
> I'm trying to get barebox going for a new imx8mp based board. I can
> successfully power on and get to a barebox prompt etc and fiddle with gpios,
> files on sd, memtest etc, but when booting to kernel it will hang. Note though
> that the board boots ok with u-boot (using exact same kernel image).
Do you have an example crash dump? Does the kernel crash reproducibly or
randomly?
>
> I'm trying to figure out what is different between booting via uboot and
> barebox, I'm new to imx8 so have been going down a few rabbit holes...
>
> Disabling various drivers (eg imx-cpufreq-dt) in the kernel will get past the
> hang, but result in a crash later on in the boot sequence. Disabling that may
> get further but will result in a crash somewhere else.
> My instinct is that its something to do with sdma, but a lot of this is still
> a black box to me.
SDMA is only used in few devices like UART, I2C, SPI and sound. Apart from
sound all devices should work without SDMA, so you could disable the
driver.
>
> Any hints or suggestions are very welcome! (I can give more info but didn't
> want to dump everything straight away)
PMIC comes to my mind. Does it need some configuration?
Is the amount of memory detected correctly by barebox?
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2023-05-26 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 10:46 marc
2023-05-26 11:30 ` Sascha Hauer [this message]
2023-05-27 5:35 ` marc
2023-05-31 5:50 ` Ahmad Fatoum
2023-06-02 5:33 ` marc
2023-05-26 11:44 ` Ahmad Fatoum
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=20230526113025.GT17518@pengutronix.de \
--to=sha@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=marc@cpdesign.com.au \
/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