[230526] System Release Notice for ROCK 5B

I have installed rock-5b_debian_bullseye_cli_b33.img.xz:

  • If a UHD monitor was connected with the reboot, the system did not start or it was in a loop. Without a monitor connected the reboot always goes. After the reboot I can connect the monitor. Got the official power supply from ALLNET China.
  • The Rock Pi 5B runs slowly. See Geekbench 5 - slow Another Rock Pi 5B (rock-5b 5.10.110-36-rockchip-gba392dc725fa) in my possession runs almost twice as fast, see Geekbench 5 - normal.

What is wrong here? Thanks for your help.

Can you post the link? The only official power supply for ROCK 5B is Radxa PD30.

From the look of it I see the base frequency is missing. So probably related to the same issue mentioned by @s-ikeda.

Hello Yuntian,
ALLNET.CHINA is not likely to offer the official power supply for Europe (EU), but for the EU PD 65W POWER SUPPLY WITH USB-C CONNECTOR. This is shown under the “Customers frequently buy with this product” section for the Rock Pi 5B. Apparently the EU version of RADXA Power PD 30W does not exist or is sold out.

1 Like

Is this one ok? I’m a newbie and I have many problems to start it. I’m italian, sorry for my bad english. Thanks and regards

Hey, no need to apologize for language. It was unnecessary and you sounded totally OK. I’m personally pretty bad at past tenses and 3rd person pronouns, because Chinese is an analytic language that doesn’t have those concepts. They are instead inferred from contexts and other particles. However, if you know the evolvement of English, you know it is also becoming more analytic as it progresses. So I take no shame at accelerating this trend :smile:

I’d suggest our PD 30 which is guaranteed to work (I have one on my desk).

EU plug is now out of stock, but with a locally sourced adapter it should still be cheaper than the one you posted.

Regarding missing cpufreq, a temporary workaround is to run following commands:

echo rockchip-cpufreq | sudo tee -a /etc/modules && sudo update-initramfs -u && sudo reboot

We will fix this in the next release.

1 Like

Also updated the workaround for When multiple displays are connected, there is a chance that the display manager will fail to show desktop. in OP.

1 Like

Thank you very much but the power supply would be ok

OKdo listed 5B under Questo prodotto è compatibile con altri computer a scheda singola?, so I think it should be alright.

Hello everyone,

I recently acquired a ROCK5B SBC and I’m currently working on establishing communication on the CAN bus using an MCP2515 module. However, I encountered some difficulties in enabling the SPI interface on the SBC. I attempted to follow the WiringX tutorial, but unfortunately, it didn’t yield the desired results. Additionally, I also tried using rsetup to activate SPI, but encountered further issues.

I would greatly appreciate any assistance or guidance you can provide me with.

Thank you in advance!

1 Like

Try enabling this overlay in rsetup.

The wiringX tutorial is described in the ReadMe file here : GitHub -https://github.com/radxa/wiringX. When trying to build and generate the deb package (make command) I got errors.
The error message is described here : ROCK5B + wiringX.

Thank you for the fast reply. It may be a stupid question but how can I enable an overlay in rsetup ?

Thank you very much

Hi all, could you please tell me what is the max CPU freq on this system?

It is 2.4Ghz, just off memory some cores are 1.8 and others 2.4

I’ve installed rock-5b_debian_bullseye_kde_b33.img.xz to an nvme ssd with xzcat rock-5b_debian_bullseye_kde_b33.img.xz | sudo dd status=progress of=/dev/nvme0n1 but the image will not boot.

The following is outputted over the serial connection:

U-Boot 2017.09-g77a5f377ab-230203-dirty # (May 10 2023 - 19:09:20 +0000)

Model: Radxa ROCK 5B
PreSerial: 2, raw, 0xfeb50000
DRAM: 15.7 GiB
Sysmem: init
Relocation Offset: eda43000
Relocation fdt: eb9f94c0 - eb9fecb8
Using default environment

SF: Detected sfc_nor with page size 256 Bytes, erase size 4 KiB, total 16 MiB
Bootdev(atags): mtd 2

Unknown partition table type 0

DM: v2
No misc partition
boot mode: None
FIT: No boot partition
No resource partition
No resource partition
Failed to load DTB, ret=-19
No find valid DTB, ret=-22
Failed to get kernel dtb, ret=-22
In: serial
Out: serial
Err: serial
Model: Radxa ROCK 5B
rockchip_set_ethaddr: vendor_storage_write failed -5
rockchip_set_serialno: could not find efuse/otp device
CLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A)
b0pll 24000 KHz
b1pll 24000 KHz
lpll 24000 KHz
v0pll 24000 KHz
aupll 24000 KHz
cpll 1500000 KHz
gpll 1188000 KHz
npll 24000 KHz
ppll 1100000 KHz
aclk_center_root 702000 KHz
pclk_center_root 100000 KHz
hclk_center_root 396000 KHz
aclk_center_low_root 500000 KHz
aclk_top_root 750000 KHz
pclk_top_root 100000 KHz
aclk_low_top_root 396000 KHz
Net: No ethernet found.
Hit key to stop autoboot(‘CTRL+C’): 0
pcie@fe150000: PCIe Linking… LTSSM is 0x1
pcie@fe150000: PCIe Linking… LTSSM is 0x210022
pcie@fe150000: PCIe Linking… LTSSM is 0x210022
pcie@fe150000: PCIe Linking… LTSSM is 0x210023
pcie@fe150000: PCIe Link up, LTSSM is 0x230011
pcie@fe150000: PCIE-0: Link up (Gen3-x4, Bus0)
pcie@fe150000: invalid flags type!

Device 0: Vendor: 0x144d Rev: 5B2QGXA7 Prod: S69ENX0T905294H
Type: Hard Disk
Capacity: 1907729.0 MB = 1863.0 GB (3907029168 x 512)
… is now current device
Scanning nvme 0:2…
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
fs_devread read outside partition 7971496441811425088
Failed to mount ext2 filesystem…
** Unrecognized filesystem type **
Error reading config file
SCRIPT FAILED: continuing…
no mmc device at slot 1
no mmc device at slot 0

Device 2: Vendor: 0x2207 Rev: V1.00 Prod: sfc_nor
Type: Hard Disk
Capacity: 16.0 MB = 0.0 GB (32768 x 512)
… is now current device
** No partition table - mtd 2 **

Device 1:
Device 0: unknown device
starting USB…
No working controllers found
USB is stopped. Please issue ‘usb start’ first.
starting USB…
No working controllers found
No ethernet found.
missing environment variable: pxeuuid
Retrieving file: /boot/extlinux/pxelinux.cfg/00000000
No ethernet found.
Retrieving file: /boot/extlinux/pxelinux.cfg/0000000
No ethernet found.
Retrieving file: /boot/extlinux/pxelinux.cfg/000000
No ethernet found.
Retrieving file: /boot/extlinux/pxelinux.cfg/00000
No ethernet found.
Retrieving file: /boot/extlinux/pxelinux.cfg/0000
No ethernet found.
Retrieving file: /boot/extlinux/pxelinux.cfg/000
No ethernet found.
Retrieving file: /boot/extlinux/pxelinux.cfg/00
No ethernet found.
Retrieving file: /boot/extlinux/pxelinux.cfg/0
No ethernet found.
Retrieving file: /boot/extlinux/pxelinux.cfg/default-arm-rockchip
No ethernet found.
Retrieving file: /boot/extlinux/pxelinux.cfg/default-arm
No ethernet found.
Retrieving file: /boot/extlinux/pxelinux.cfg/default
No ethernet found.
Config file not found
starting USB…
No working controllers found
No ethernet found.
Could not get mtd 0

Booting FIT Image FIT: No boot partition

FIT: No fit blob
FIT: No FIT image

What must I do to actually boot with this image?

Failed to mount ext2 filesystem…

So it’s better to have fat32 boot partition.

I dd the image to the disk. Why are the image boot files under an ext4 partition? The boot partition of the image file is too small to simple move them there. How was this image supposed to be booted? Since I didn’t create it I’m asking here :slight_smile: