All of lore.kernel.org
 help / color / mirror / Atom feed
From: marc@cpdesign.com.au
To: barebox@lists.infradead.org
Subject: Troubles booting kernel with new imx8 board
Date: Fri, 26 May 2023 20:46:40 +1000	[thread overview]
Message-ID: <10297393.nUPlyArG6x@dev8> (raw)

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).

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.

Any hints or suggestions are very welcome! (I can give more info but didn't 
want to dump everything straight away)

- board is based on an imx8mp module from solidrun
- boots kernel ok using u-boot (u-boot version provided by solidrun, based on 
NXP versions)
- I used the same ddr timings from u-boot
- also using same versions of firmware-imx (8.16) and ATF (2.8)

Cheers
Marc








             reply	other threads:[~2023-05-26 10:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-26 10:46 marc [this message]
2023-05-26 11:30 ` Troubles booting kernel with new imx8 board Sascha Hauer
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=10297393.nUPlyArG6x@dev8 \
    --to=marc@cpdesign.com.au \
    --cc=barebox@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.