From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Maxime Ripard <mripard@redhat.com>, Nishanth Menon <nm@ti.com>
Cc: u-boot@lists.denx.de
Subject: Re: eMMC broken on SK-AM62
Date: Thu, 09 Nov 2023 11:29:17 +0100 [thread overview]
Message-ID: <871qcz9q4i.fsf@baylibre.com> (raw)
In-Reply-To: <hsk5wejuf5maoer3aodjyndmyft56gag4cepfjep7lfthmwrcy@r2yoebb7stk6>
Hi Maxime, Nishanth,
On mer., nov. 08, 2023 at 16:05, Maxime Ripard <mripard@redhat.com> wrote:
> Hi Nishanth,
>
> I've been trying for the last few days to get an SK-AM62 to boot from
> the eMMC user data area.
>
> I finally got the jumper configuration to make the CPU boot from there
> thanks to Mattijs, but it looks like the 2024.01-rc2 release doesn't
> support booting from there:
>
> U-Boot SPL 2024.01-rc2 (Nov 08 2023 - 14:11:12 +0100)
> SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.5--v09.01.05 (Kool Koala)')
> SPL initial stack usage: 13368 bytes
> Trying to boot from MMC1
> MMC Device 0 not found
> spl: could not find mmc device 0. error: -19
> SPL: failed to boot from all boot devices
> ### ERROR ### Please RESET the board ###
>
> It looks like you tried to fix it with 0f1c1e8b368b ("arm: mach-k3:
> am625: Add support for UDA FS"), but it looks like it's not enough.
I confirm I reproduce the issue on AM62x SK EVM.
Beagle play seems to boot fine:
U-Boot SPL 2024.01-rc2 (Nov 09 2023 - 11:24:04 +0100)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.1--v09.01.01 (Kool Koala)')
SPL initial stack usage: 13400 bytes
Trying to boot from MMC1
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Starting ATF on ARM64 core...
NOTICE: BL31: v2.8(release):08.06.00.007
NOTICE: BL31: Built : 11:17:33, Nov 9 2023
U-Boot SPL 2024.01-rc2 (Nov 09 2023 - 11:24:30 +0100)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.1--v09.01.01 (Kool Koala)')
SPL initial stack usage: 1888 bytes
Trying to boot from MMC1
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
U-Boot 2024.01-rc2 (Nov 09 2023 - 11:24:30 +0100)
SoC: AM62X SR1.0 GP
Model: BeagleBoard.org BeaglePlay
DRAM: 2 GiB
Core: 98 devices, 27 uclasses, devicetree: separate
MMC: mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2
Loading Environment from nowhere... OK
In: serial@2800000
Out: serial@2800000
Err: serial@2800000
Net: No ethernet found.
Press SPACE to abort autoboot in 2 seconds
=>
Note that Beagle Play does not boot tiboot3 from UDA (User Data Area)
but from mmc0boot0 so the boot flow is not exactly the same.
>
> Thanks!
> Maxime
next prev parent reply other threads:[~2023-11-09 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 15:05 eMMC broken on SK-AM62 Maxime Ripard
2023-11-09 10:29 ` Mattijs Korpershoek [this message]
2023-11-09 12:23 ` Nishanth Menon
2023-11-09 15:21 ` Maxime Ripard
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=871qcz9q4i.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=mripard@redhat.com \
--cc=nm@ti.com \
--cc=u-boot@lists.denx.de \
/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.