public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Peng Fan <peng.fan@oss.nxp.com>
Cc: u-boot@lists.denx.de, Peter Robinson <pbrobinson@gmail.com>
Subject: Re: rk3588 MNT Reform2 fails to boot from SD card
Date: Fri, 30 Jan 2026 00:16:59 -0800	[thread overview]
Message-ID: <87fr7nbjlw.fsf@wireframe> (raw)
In-Reply-To: <aXwo28QQQ0IwjIBW@shlinux89>

[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]

On 2026-01-30, Peng Fan wrote:
> On Thu, Jan 29, 2026 at 05:46:43PM -0800, Vagrant Cascadian wrote:
>>Thanks for adding support for rk3588 MNT Reform2!
>>
>>I tried using u-boot 2026.01 with the rk3588 MNT Reform2, but it only
>>gets as far as SPL, and then fails:
>>
>>  U-Boot SPL 2026.01 (Jan 01 1970 - 00:00:01 +0000)
>>  Trying to boot from MMC1
>>  mmc_load_image_raw_sector: mmc block read error
>>  Error: -38
>>  SPL: Unsupported Boot Device!
>>  SPL: failed to boot from all boot devices
>>  ### ERROR ### Please RESET the board ###
>>
>>I *think* MMC1 is eMMC, which I currently have blanked, as recovering
>>from a failed install on eMMC is trickier.
>>
>>The vendor u-boot works fine on either eMMC or SD.
>>
>>Any suggestions to get it to support booting off SD card?
>
> Please check whether you have this patch in your tree:
>
> commit c4f5b1d4b037beeb538cf6dee0a16cd196539273
> Revert "mmc: mmc-uclass: Use max-frequency from device tree with default handling"
>
> This reverts commit aebb523a23818a8ee4199c9532b51e3d4020696f.

Thanks for the suggestion! Just tested with v2026.04-rc1, which appears
to contain both if I am reading this right::

  git describe --contains c4f5b1d4b037beeb538cf6dee0a16cd196539273
  v2026.04-rc1~56^2

  git describe --contains aebb523a23818a8ee4199c9532b51e3d4020696f
  v2026.04-rc1~52^2~23^2~7

But the behavior was about the same:

  U-Boot SPL 2026.04-rc1 (Jan 01 1970 - 00:00:01 +0000)
  Trying to boot from MMC1
  mmc_load_image_raw_sector: mmc block read error
  Error: -38
  SPL: Unsupported Boot Device!
  SPL: failed to boot from all boot devices
  ### ERROR ### Please RESET the board ###

There are 63 commits since v2026.04-rc1 currently on master, but nothing
immediately leaps out as relevent to my untrained eyes... :)

I could test the initial commit it was introduced in and if it works,
bisect from there (looks to bee about 600 commits between introduction
of the platform and v2026.01)...


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2026-01-30  8:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-30  1:46 rk3588 MNT Reform2 fails to boot from SD card Vagrant Cascadian
2026-01-30  3:43 ` Peng Fan
2026-01-30  8:16   ` Vagrant Cascadian [this message]
2026-01-30  9:51 ` Quentin Schulz
2026-01-30 21:07   ` Vagrant Cascadian
2026-02-02  9:51     ` Quentin Schulz
2026-02-02 21:43       ` Vagrant Cascadian

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=87fr7nbjlw.fsf@wireframe \
    --to=vagrant@debian.org \
    --cc=pbrobinson@gmail.com \
    --cc=peng.fan@oss.nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox