Control: severity 1033845 important Given that this only affects a single platform, and there are other tested working boot options for this platform, I am downgrading the severity to important.
On 2023-04-02, Wolf wrote: > 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 ### So far I have only ever tested booting from microSD... Did this work on previous versions? Does it work on the version in experimental (currently 2023.04~rc5*)? > 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 Would you consider submitting a patch upstream? live well, vagrant
signature.asc
Description: PGP signature
