`usb start` freezes friendlyelec CM3588 Plus NAS board
Krumelmonster
krumelmonster at zoho.com
Sun Nov 16 18:51:11 CET 2025
Hello Jonas,
On 15/11/2025 22.22, Jonas Karlman wrote:
> On 11/15/2025 5:30 PM, Krumelmonster wrote:
>> Using the cm3588-nas-rk355_defconfig, running `usb start` in u-boot
>> freezes my cm3588 nas in all commits I checked:
>> v2024.10, v2025.10, v2026.01-rc, and the current `rockchip` branch
>> (commit a81c91446a1) on collaboras rk3588 repo at
>> https://gitlab.collabora.com/hardware-enablement/rockchip-3588/u-boot
>>
>> It doesn't freeze if I disable PHY_ROCKCHIP_INNO_USB2.
>>
>> This is the 32GB RAM, 64GB eMMC variant of the CM3588 Plus NAS Kit as
>> sold by friendlyelec.
>>
>> I don't intend to use usb support there, just happened to stumble upon
>> this. USB gadget and host are supposedly working on the CM3588 according
>> to commit 5bc8209e1ba ("board: rockchip: Add FriendlyElec CM3588 NAS").
>>
>> => usb start
>> starting USB...
>> USB EHCI 1.00
>>
>> No further output follows.
>
> I am not able to reproduce this issue on a CM3588 NAS Kit, and looking
> at the schematics the only diff seem to be LPDDR4X vs LPDDR5.
>
> DDR b8ce94f14b cym 25/08/25-14:29:26,fwver: v1.20
> ...
> LPDDR4X, 1848MHz
> ...
> out
>
> U-Boot SPL 2026.01-rc2 (Nov 15 2025 - 20:57:41 +0000)
> Trying to boot from MMC2
> ## 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
> INFO: Preloader serial: 2
> NOTICE: BL31: v2.3():v2.3-942-g98eaeb2f3:derrick.huang, fwver: v1.53
> NOTICE: BL31: Built : 12:10:56, Aug 25 2025
> INFO: spec: 0x1
> INFO: code: 0x88
> INFO: customer demand: 0x0
> INFO: ext 32k is not valid
> INFO: ddr: stride-en 4CH
> INFO: GICv3 without legacy support detected.
> INFO: ARM GICv3 driver initialized in EL3
> INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
> INFO: l3 cache partition cfg-0
> INFO: system boots from cpu-hwid-0
> INFO: disable memory repair
> INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
> INFO: dfs DDR fsp_params[0].freq_mhz= 1848MHz
> INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz
> INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz
> INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz
> INFO: BL31: Initialising Exception Handling Framework
> INFO: BL31: Initializing runtime services
> WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
> ERROR: Error initializing runtime service opteed_fast
> INFO: BL31: Preparing for EL3 exit to normal world
> INFO: Entry point address = 0xa00000
> INFO: SPSR = 0x3c9
>
>
> U-Boot 2026.01-rc2 (Nov 15 2025 - 20:57:41 +0000)
>
> Model: FriendlyElec CM3588 NAS
> SoC: RK3588
> DRAM: 8 GiB
> PMIC: RK806 (on=0x10, off=0x00)
> Core: 422 devices, 34 uclasses, devicetree: separate
> MMC: mmc at fe2c0000: 1, mmc at fe2e0000: 0
> Loading Environment from nowhere... OK
> In: serial at feb50000
> Out: serial at feb50000
> Err: serial at feb50000
> Model: FriendlyElec CM3588 NAS
> SoC: RK3588
> Net: No ethernet found.
> Hit any key to stop autoboot: 0
> => usb start
> starting USB...
> USB EHCI 1.00
> USB OHCI 1.0
> USB EHCI 1.00
> USB OHCI 1.0
> Register 2000140 NbrPorts 2
> Starting the controller
> USB XHCI 1.10
> Register 2000140 NbrPorts 2
> Starting the controller
> USB XHCI 1.10
> cannot reset port 1!?
> Bus usb at fc800000: 1 USB Device(s) found
> Bus usb at fc840000: 1 USB Device(s) found
> Bus usb at fc880000: 1 USB Device(s) found
> Bus usb at fc8c0000: 1 USB Device(s) found
> Bus usb at fcd00000: 2 USB Device(s) found
> Bus usb at fc400000: 1 USB Device(s) found
> scanning usb for storage devices... 1 Storage Device(s) found
> => usb tree
> USB device tree:
> 1 Hub (480 Mb/s, 0mA)
> u-boot EHCI Host Controller
>
> 1 Hub (12 Mb/s, 0mA)
> U-Boot Root Hub
>
> 1 Hub (480 Mb/s, 0mA)
> u-boot EHCI Host Controller
>
> 1 Hub (12 Mb/s, 0mA)
> U-Boot Root Hub
>
> 1 Hub (5 Gb/s, 0mA)
> | U-Boot XHCI Host Controller
> |
> +-2 Mass Storage (5 Gb/s, 126mA)
> Corsair Voyager VEGA 070894224D1DDF08
>
> 1 Hub (5 Gb/s, 0mA)
> U-Boot XHCI Host Controller
>
> =>
>
> Above is from using tag v2026.01-rc2 with only a single USB stick
> connected to one of the 3 USB-A ports on the board, using the reset
> button between each test to ensure a clean state.
>
>> I will happily provide further information upon request.
>
> Do you have any other peripherals attached to your board when you test?
> E.g. PCIe/NVMe, HDMI, Ethernet or similar?
I've always been testing on Micro-SD, with ethernet, uart and 12V 5A
supply connected, I reset by switching off power supply.
When systematically testing the mentioned revisions, two M.2 SSDs where
connected but I've observed the same behavior without anything in the
M.2 slots.
When systematically testing revisions nothing was connected to USB, only
when I tested for kconfig options that influence the issue I connected
an USB keyboard to different USB-A slots (and that didn't change the
symptomatic).
> For my test run above I only had 12V power-in, SD-card (with u-boot) and
> Debug UART connected to my CM3588 NAS Kit board.
>
> Also what DDR-init fwver and TF-A (BL31) are you using?
bl31.elf from arm trusted firmware 2.13.0 f3db1dea4fde771fab3e3bae3b117a43
from
https://kojipkgs.fedoraproject.org/packages/arm-trusted-firmware/2.13.0/4.fc43/noarch/arm-trusted-firmware-armv8-2.13.0-4.fc43.noarch.rpm
rk3588_ddr_lp4_2112MHz_lp5_2400MHz_v1.19.bin
1fdd2039c042b04415c0085b85bd5300 from
https://github.com/rockchip-linux/rkbin/blob/master/bin/rk35/rk3588_ddr_lp4_2112MHz_lp5_2400MHz_v1.19.bin
I don't suspect this to be the reason as I've observed the same issue
with armbian's u-boot build for the cm3588 nas.
Regards,
Krumelmonster
More information about the U-Boot
mailing list