Hi Quentin, Thanks for your input
> > Thanks. I am having the same issue with my Radxa Rock Pi 4 B Plus. > > > > But I am booting from SPI flash, so I cannot stop this board in the > > U-Boot prompt. > > > > Not sure why booting from SPI flash means you cannot stop the board in > U-Boot? > The board stop at U-Boot SPL 2025.10-1 (Oct 31 2025 - 11:12:15 +0000) Trying to boot from MMC1 ## Checking hash(es) for config config-1 ... OK ## Checking hash(es) for Image atf-1 ... sha256+ OK ## Checking hash(es) for Image u-boot ... sha256+ OK ## Checking hash(es) for Image fdt-1 ... sha256+ OK ## Checking hash(es) for Image atf-2 ... sha256+ OK ## Checking hash(es) for Image atf-3 ... sha256+ OK ## Checking hash(es) for Image atf-4 ... sha256+ OK load_simple_fit: Skip load 'atf-5': image size is 0! U-Boot 2025.10-1 (Oct 31 2025 - 11:12:15 +0000) SoC: Rockchip rk3399 Reset cause: POR Model: Radxa ROCK Pi 4A DRAM: 4 GiB (total 3.9 GiB) PMIC: RK808 Here, I cannot enter into U-Boot prompt. > > Is there any other way to flash the SPI flash u-boot-rockchip-spi.bin image > > in the user space to spi flash? using dd coammnd > > flashcp u-boot-rockchip-spi.bin /dev/mtdX > Thanks, I will give this a try. Once I get the SPI flash detected > I believe? > > > > > From the schematics, it has W25Q64FWZPIG > > > > [1] > > https://dl.radxa.com/rockpi4/docs/hw/rockpi4/rockpi4_v13_sch_20181112.pdf > > > > I have tried to enable SPI flash, but it is not getting detected on > > the board in userspace. > > Are you sure you have the driver for the SPI controller, MTD, > MTD_SPI_NOR, ... available? > Yes, it's enabled, but it's not getting detected in userspace. [ 0.997896] mmcblk0boot1: mmc0:0001 SLD64G 4.00 MiB [ 0.999656] spi-nor spi1.0: unrecognized JEDEC id bytes: ff ff ff ff ff ff [ 1.000975] mmcblk0rpmb: mmc0:0001 SLD64G 4.00 MiB, chardev (240:0) Datasheet for the Winbond W25Q64FW SPI flash [1] https://www.winbond.com/resource-files/w25q64fw%20revn%2005182017%20sfdp.pdf Should we add a dedicated entry for the W25Q64FW in the driver’s device table to ensure the flash is properly recognised? > You can check from a running system by looking at /proc/config or > /proc/config.gz > > (you can grep in config.gz with zgrep) > > > > > $ git diff arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4b-plus.dts > > diff --git a/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4b-plus.dts > > b/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4b-plus.dts > > index 9c741d1a3047..d18b59ddaa1d 100644 > > --- a/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4b-plus.dts > > +++ b/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4b-plus.dts > > @@ -42,6 +42,16 @@ &sound { > > hp-det-gpios = <&gpio1 RK_PA0 GPIO_ACTIVE_HIGH>; > > }; > > > > +&spi1 { > > + status = "okay"; > > + > > + flash@0 { > > + compatible = "winbond,w25q64", "jedec,spi-nor"; > > + reg = <0>; > > + spi-max-frequency = <108000000>; > > + }; > > +}; > > + > > &uart0 { > > status = "okay"; > > > > Can you share some input on how to resolve this issue? > > > > Looks ok to me. > > Cheers, > Quentin Thanks -Anand
