Re: VisionFive 2 eMMC boot issues.

Yao Zi <[email protected]>
Newsgroups org.u-boot-project.lists.u-boot
Message-ID <am2ukr9PzNtDUrp2@pie>
On Fri, Jul 31, 2026 at 06:38:38PM +0200, Milad wrote:
> Quick update, i also tested v2026.04 as well, and it also boots the SD card
> correctly with the same clean pattern as v2025.10/v2026.01, straight
> through to GRUB and Debian, no cluster read errors. Log below.
> 
> So the regression is most likely somewhere between v2026.04 and v2026.07.

Thanks for the information. I'll take a look later this day.

Best regards,
Yao Zi

> Also worth mentioning, someone else in a community also reported having the
> exact same errors on v2026.07 (SD/EFI boot failure), and mentioned v2026.04
> worked for them too which is why i tried it so this isn't isolated to my
> board specifically.
> 
> --- v2026.04 log ---
> U-Boot SPL 2026.04 (Jul 31 2026 - 18:19:25 +0200)
> DDR version: dc2e84f0.
> Trying to boot from SPI
> 
> 
> U-Boot 2026.04 (Jul 31 2026 - 18:19:25 +0200)
> 
> CPU: sifive,u74-mc
> Model: StarFive VisionFive 2 v1.3B
> DRAM: 8 GiB
> Core: 159 devices, 30 uclasses, devicetree: board
> WDT: Not starting watchdog@13070000
> MMC: mmc@16010000: 0, mmc@16020000: 1
> Loading Environment from SPIFlash... SF: Detected gd25lq128 with page size
> 256 Bytes, erase size 4 KiB, total 16 MiB
> OK
> StarFive EEPROM format v2
> 
> --------EEPROM INFO--------
> Vendor : StarFive Technology Co., Ltd.
> Product full SN: VF7110B1-2318-D008E000-18005137
> data version: 0x2
> PCB revision: 0xb2
> BOM revision: A
> Ethernet MAC0 address: 6c:cf:39:00:ba:b0
> Ethernet MAC1 address: 6c:cf:39:00:ba:b1
> --------EEPROM INFO--------
> 
> In: serial@10000000
> Out: serial@10000000
> Err: serial@10000000
> Net: eth0: ethernet@16030000, eth1: ethernet@16040000
> starting USB...
> USB XHCI 1.00
> Bus xhci_pci: 2 USB Device(s) found
>        scanning usb for storage devices... 0 Storage Device(s) found
> Working FDT set to ff6fab80
> Hit any key to stop autoboot: 0
> Card did not respond to voltage select! : -110
> ** Booting bootflow '<NULL>' with efi_mgr
> Booting: Label: mmc 1 Device path:
> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,0000000000000000)/VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b,7200000000000000)/SD(1)/SD(1)
> ...
> Loading Linux 6.12.96+deb13-riscv64 ...
> Loading initial ramdisk ...
> /dev/mmcblk1p2: clean, 61400/7364608 files, 4698361/29427968 blocks
> Debian GNU/Linux 13 visionfive-2 ttyS0
> visionfive-2 login:
> 
> Happy to keep looking into it this if useful, please let me know if there's
> a specific commit or intermediate version i might need to test.
> 
> 
> On Tue, 28 Jul 2026, 18:28 Yao Zi, <[email protected]> wrote:
> 
> > On Tue, Jul 28, 2026 at 04:42:03PM +0200, Milad wrote:
> > > Hello everyone,
> > >
> > > Little reminder on this thread regarding my VisionFive 2 MMC boot issue.
> > >
> > > Archive link:
> > > https://lists.u-boot-project.org/pipermail/u-boot/2026-July/624724.html
> >
> > The last time I tried upstream U-Boot with SD cards is about v2025.10 -
> > v2026.01 and it works fine on my side. Could you try these two versions,
> > too, so we know whether it's a new regression or just a bug yet to be
> > discovered?
> >
> > Thanks,
> > Yao Zi
> >
> > > Just following up to see if anyone has had a chance to look at the
> > details
> > > in my original message on the link.
> > >
> > > Thanks!
> >
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.