Bug 259438 - 12.3-BETA1 SD image does not boot on Raspberry Pi 3B+
Summary: 12.3-BETA1 SD image does not boot on Raspberry Pi 3B+
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: arm (show other bugs)
Version: 12.3-RELEASE
Hardware: arm64 Any
: Normal Affects Many People
Assignee: freebsd-arm (Nobody)
URL:
Keywords: needs-patch, needs-qa
Depends on:
Blocks:
 
Reported: 2021-10-25 14:51 UTC by Mike Karels
Modified: 2023-05-02 18:30 UTC (History)
4 users (show)

See Also:
koobs: maintainer-feedback? (re)
koobs: mfc-stable13?
koobs: mfc-stable12?


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Karels freebsd_committer freebsd_triage 2021-10-25 14:51:36 UTC
The 12.3-BETA1 image does not boot on Raspberry Pi 3B+ on SD card.  The firmware doesn't seem to see the card, and tries to netboot.  The problem is with u-boot.bin; replacing it with the version from 13.0-RELEASE makes it boot and install.  The problem is apparently with the numbering of the MMC interfaces.
Comment 1 Emmanuel Vadot freebsd_committer freebsd_triage 2021-10-25 15:03:42 UTC
It's related to our overlay usage and u-boot.
Since we're using mmc.dtbo the mmc devices are re-ordered and the sdcard device isn't in the list of bootable devices that will be probed by u-boot.
See https://lists.freebsd.org/archives/freebsd-arm/2021-August/000417.html and https://lists.freebsd.org/archives/freebsd-arm/2021-August/000421.html
I've asked that the patch is submitted upstream as we don't allow patches in the u-boot ports anymore (the only remaining ones are for rpi already and nobody is taking care of upstreaming them ...).
Comment 2 Mike Karels freebsd_committer freebsd_triage 2021-10-25 15:58:15 UTC
Can we use an older version of u-boot or overlay on RPI3 until this is resolved?
Comment 3 Emmanuel Vadot freebsd_committer freebsd_triage 2021-10-25 16:42:19 UTC
(In reply to Mike Karels from comment #2)

Overlay won't change a thing.
Using older version of u-boot will work but I fear that if we start doing that nobody will fix the issue upstream, we will never update u-boot for rpi again and at one point we will need a newer u-boot for some newer revision or variation and we will be blocked again.
So if you care about RPI support send the patch upstream and after that we can use the patchwork patch ID to add it in the ports while waiting for the newer u-boot release with it included.
Comment 4 Mike Karels freebsd_committer freebsd_triage 2023-05-01 18:30:40 UTC
Looks like this patch made it into upstream; 12.4, 13.2, and the 20230427 14-current snapshot all work.  I think the bug can be closed; should it be "Fixed" or "Overcome by events"?
Comment 5 Ed Maste freebsd_committer freebsd_triage 2023-05-02 17:33:36 UTC
(In reply to Mike Karels from comment #4)
Good question - I can see arguments both ways, but if there's a change that went into src I'd think fixed is correct (and paste the commit message(s) as a comment perhaps).
Comment 6 Mike Karels freebsd_committer freebsd_triage 2023-05-02 18:04:38 UTC
There was a change, but it was made upstream in u-boot (if I recall correctly).  I'm not sure how to find the commit message there.  In our source, it would just be one of the imports from upstream.  btw, Glen suggested OBE; that's what I'm leaning toward.
Comment 7 Ed Maste freebsd_committer freebsd_triage 2023-05-02 18:28:31 UTC
Ah, I thought this was referring to a change that went into src. For a uboot change I think OBE is fine
Comment 8 Mike Karels freebsd_committer freebsd_triage 2023-05-02 18:30:28 UTC
Closing, as change has come in from upstream and is in all current releases.