Overclocking Rock Pi 4B+ OP1

I’ve been looking into overclocking the Rock Pi 4B+ OP1 to use the full 2GHz that it is supposed to have instead of the default 1,8Ghz I’m getting.

Currently stuck at trying to configure rsetup overlays but overclocking or changing frequency simply doesn’t show up.
originally was looking at the wiki but it appears this has long been outdated. So configuration file like hw_intfc.conf have been retired and say to use rsetup instead.
rsetup does allow for device overlay configuration but is missing a cpu frequency overlay.Screenshot%202025-05-19%20154535
In /boot/dtbo can find overlays that look like they could be what i’m looking for but they don’t appear in rsetup overlays:

rk3399-opp-2000.dtbo.disabled
rk3399-opp-2200.dtbo.disabled

Any idea why there are no overlay entries for it or perhaps another approach entirely?

Armbian has 2GHz opp overlay on rock 4 series, it worked on earlier build for sure.
RK3399 has promised vendor kernel upgrade, but it was already delayed and nobody knows when we can expect anything regarding this :frowning:

Checkout this dtso: https://github.com/radxa/kernel/blob/1bb08d49cc405e188d9291ff1f46f9cb15c157ea/arch/arm64/boot/dts/rockchip/overlay/cpufreq.dts
Not sure if it applies to your dtb in use, but its a good starting point to write your own dts/dtso.
Tested it on my 4B+ and it seems to work:

# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
1512000
# cat /sys/devices/system/cpu/cpu4/cpufreq/cpuinfo_max_freq
2016000

however my system becomes unstable, but thats most likely due to the limited power supply my board has (5V, 3A).

best

does it reboot?

Nope, no reboots, but rather random Illegal instruction.

Also have to say, I run this board from an NVMe, and I have clocked it to PCIE 2.0 speeds, so maybe something goes wrong on that end. There needs to be some reason in stock config PCIE is limited to 1.0 speeds.
However, with clock speeds limited to 1416000 / 1800000, the system runs fine at PCIE 2.0.

BSP image or mainline?
Maybe worth to try second one with that

Usually where there is no enough power it just reboots, this seems to be something related to kernel.

We use BSP kernel (5.10) on 4B+ and it automatically works at 2 GHz (two big cores) / 1.5 GHz (four small cores) without any additional overlays.

But if I remember correctly some earlier builds incorrectly loaded 4B device tree on 4B+.