Your message dated Thu, 22 Jun 2023 23:54:39 -0700
with message-id <87jzvu3byo.fsf@wireframe>
and subject line Re: Bug#1033845: u-boot fails to boot on pinebook pro if
installed on internal emmc
has caused the Debian Bug report #1033845,
regarding u-boot fails to boot on pinebook pro if installed on internal emmc
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1033845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033845
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: u-boot-rockchip
Version: 2023.01+dfsg-2
Severity: serious
Tags: patch
X-Debbugs-Cc: [email protected]
If the u-boot is installed on the internal emmc then u-boot is failing as
follows:
U-Boot SPL 2023.01+dfsg-2 (Jan 18 2023 - 01:57:16 +0000)
Trying to boot from MMC1
mmc fail to send stop cmd
mmc_load_image_raw_sector: mmc block read error
Trying to boot from MMC1
mmc_load_image_raw_sector: mmc block read error
Trying to boot from SPI
Trying to boot from MMC2
Card did not respond to voltage select! : -110
spl: mmc init failed with error: -95
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
The following patch in the configuration will fix that:
pinebook-pro-rk3399_defconfig:
--- pinebook-pro-rk3399_defconfig 2023-03-22 11:09:33.987508968 +0100
+++ pinebook-pro-rk3399_defconfig 2023-03-22 12:56:41.773648426 +0100
@@ -32,6 +32,7 @@ CONFIG_SPL_BSS_MAX_SIZE=0x2000
CONFIG_SPL_STACK=0x400000
CONFIG_SPL_STACK_R=y
CONFIG_SPL_STACK_R_MALLOC_SIMPLE_LEN=0x10000
+CONFIG_SPL_MTD_SUPPORT=y
CONFIG_SPL_SPI_LOAD=y
CONFIG_TPL=y
CONFIG_CMD_BOOTZ=y
@@ -56,6 +57,8 @@ CONFIG_LED=y
CONFIG_LED_GPIO=y
CONFIG_MISC=y
CONFIG_ROCKCHIP_EFUSE=y
+CONFIG_MMC_HS200_SUPPORT=y
+CONFIG_SPL_MMC_HS200_SUPPORT=y
CONFIG_MMC_DW=y
CONFIG_MMC_DW_ROCKCHIP=y
CONFIG_MMC_SDHCI=y
-- System Information:
Debian Release: 12.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: arm64 (aarch64)
Kernel: Linux 6.1.0-6-arm64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
u-boot-rockchip depends on no packages.
Versions of packages u-boot-rockchip recommends:
ii python3 3.11.2-1
ii u-boot-tools 2023.01+dfsg-2
Versions of packages u-boot-rockchip suggests:
ii arm-trusted-firmware 2.8.0+dfsg-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2023.07~rc4+dfsg-1
On 2023-06-23, Wolfgang Zarre wrote:
> Hmmm, I can see it at least in branch master:
> commit 63a49240d47e34a9a85091f3ab0841cafd22426a
Thanks, not sure how I missed it...
git describe --contains 63a49240d47e34a9a85091f3ab0841cafd22426a
v2023.07-rc3~3^2~2
Well, I guess we've released a fix in experimental, at least! :)
live well,
vagrant
signature.asc
Description: PGP signature
--- End Message ---
