[BUG] Raxda Rock Pi 4A serial console output stops prematurely
Anand Moon
linux.amoon at gmail.com
Sun Nov 30 08:27:46 CET 2025
Hi FUKAUMI
On Sat, 29 Nov 2025 at 15:22, FUKAUMI Naoki <naoki at radxa.com> wrote:
>
> Hi Anand,
>
> On 11/29/25 16:25, Anand Moon wrote:
> > Hi FUKAUMI,
> >
> > On Sat, 29 Nov 2025 at 10:09, FUKAUMI Naoki <naoki at radxa.com> wrote:
> >>
> >> Hi Anand,
> >>
> >> On 11/28/25 14:50, Anand Moon wrote:
> >>> Hi Heinrich,
> >>>
> >>>>> 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.
> >>>>>
> >>>>> 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
> >>>>>
> >>>>> 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.
> >>>>
> >>>>
> >>>> https://wiki2.radxa.com/Rockpi4/dev/usb-install
> >>>> has some guidance how to avoid booting from SPI NOR flash.
> >>>>
> >>> Thanks for your tip.
> >>>
> >>> I've attempted this method, but it hasn't worked for me.
> >>> Could you provide the SPI details for this board so I can map it in driver code
> >>> and from userspace and then attempt to erase or reflash the image?
> >>>
> >>> on my board
> >>> [ 1.282609] mmcblk0boot0: mmc0:0001 SLD64G 4.00 MiB
> >>> [ 1.285862] spi-nor spi1.0: unrecognized JEDEC id bytes: ff ff ff ff ff ff
> >>
> >> Are you using dts with "audio-supply = <&vcc_3v0>;"? It should fix SPI too.
> >>
> > Thanks for your tip.
> >
> > I have applied the patch from FUKAUMI, and now my console output has
> > started working
> >
> >> 1. Make u-boot-rockchip.bin with "audio-supply = <&vcc_3v0>;"
> >> 2. Write it to microSD card
> >> 3. Insert it
> >> 4. Kill SPI flash
> >> 5. Boot U-Boot from SD card
> >> 6. Revert 4.
> >> 7. Try "sf probe" "sf erase"
> >>
> > Yes, I have tried these steps (4 Kill SPI flash) ->
> > I have shortened the SPI1_CLK and GNG in the GPIO header
> > But this board first boots from SPI flash, I don't know the reason.
> >
> > I noticed your patch references the W25Q128.
> > Did you get this device detection in userspace?
> >
> > This output is from your patch.
> > => led blue:status off
> > => sf probe
> > SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
> > => led blue:status on
> > => sf probe
> > jedec_spi_nor flash at 0: unrecognized JEDEC id bytes: ff, ff, ff
> > Failed to initialize SPI flash at 1:0 (error -2)
> >
> > Could this explain why I’m unable to detect the device from userspace?
>
> What happens if you lower the SPI clock?
> e.g.
> spi-max-frequency = <10000000>;
>
Thanks for your input, but I have a bad old U-Boot in my SPI chip,
which blocks the UART. I need to erase the SPI chip externally
or erase the chip from user space.
> Best regards,
>
> --
> FUKAUMI Naoki
> Radxa Computer (Shenzhen) Co., Ltd.
>
Thanks
-Anand
More information about the U-Boot
mailing list