BipBip1981

Hi @ebin-dev, @SymbiosisSystems, and everyone in this thread,
Following the recurring instability reports here and in the older topic
( https://forum.armbian.com/topic/30074-helios64-armbian-2308-bookworm-issues-solved/ ),
I've packaged your opp-microvolt workaround as an opt-in DT overlay in
the Armbian build framework. PR:
  https://github.com/armbian/build/pull/9822
— adds the overlay to both Armbian kernel trees: `rockchip64-current`
(6.18) and `rockchip64-edge` (7.0).
What you get once this lands:
  - `rockchip-rk3399-helios64-cpu-stability.dtbo` ships inside the
    regular `linux-dtb-{current,edge}-rockchip64` package. No
    hand-patching of DTBs, no separate downloads; `apt upgrade` keeps
    the overlay in sync with whatever DTB your kernel ships.
  - **Not enabled by default** — for the people whose Helios64 "just
    works", the mainline OPPs stay untouched. I don't want to push a
    tree-wide voltage bump onto every user when only some units exhibit
    the instability.
  - Activation is the standard Armbian way, either:
      armbian-config → System → Kernel →
      Manage device tree overlays → [*] rk3399-helios64-cpu-stability
      → save → reboot
    or manually, by adding the overlay name to the `overlays=` line in
    `/boot/armbianEnv.txt` (the `rockchip-` prefix is implicit, because
    `overlay_prefix=rockchip` is already set on this board):
      overlays=rk3399-helios64-cpu-stability
    Then reboot.
Voltages are exactly the ones from your post in this thread —
https://forum.armbian.com/topic/58597-helios64-armbian-trixie-with-linux-618-incl-opp-microvolt-patch/?do=findComment&comment=237456
(opp00..opp06 raised to
900 / 900 / 900 / 950 / 1025 / 1100 / 1175 mV; opp07 left at the
mainline 1.20 V; `max` everywhere kept at 1.25 V). Frequencies are not
touched.
End-to-end verified on my Helios64 with both kernels:
  - current / 6.18.30, Trixie SD-card image
  - edge    / 7.0.7,   Trixie SD-card image (locally built)
After enabling the overlay and a reboot:
  for n in 0 1 2 3 4 5 6 7; do
    od -An -tx4 --endian=big \
       /sys/firmware/devicetree/base/opp-table-1/opp0$n/opp-microvolt
  done
  opp00  000dbba0 000dbba0 001312d0
  opp01  000dbba0 000dbba0 001312d0
  opp02  000dbba0 000dbba0 001312d0
  opp03  000e7ef0 000e7ef0 001312d0
  opp04  000fa3e8 000fa3e8 001312d0
  opp05  0010c8e0 0010c8e0 001312d0
  opp06  0011edd8 0011edd8 001312d0
  opp07  00124f80 00124f80 001312d0
...which matches your table 1:1. U-boot log line on boot:
  Applying kernel provided DT overlay
  rockchip-rk3399-helios64-cpu-stability.dtbo
confirms that u-boot picks up the `.dtbo` from
`/boot/dtb/.../rockchip/overlay/` and applies it via `fdt apply` before
the kernel starts.
Ready-to-flash **current/6.18** images, built from the PR branch by the
official Armbian builder workflow:
  https://fi.mirror.armbian.de/incoming/iav/helios64/archive/
  - Armbian_26.5.0_Helios64_resolute_current_6.18.30_minimal.img.xz
  - Armbian_26.5.0_Helios64_resolute_current_6.18.30_xfce_desktop.img.xz
  - Armbian_26.5.0_Helios64_trixie_current_6.18.30_minimal.img.xz
If any of you can grab one of those (or wait for a nightly after the PR
is merged) and confirm the workaround applies cleanly through the
overlay path on your board, that would help the PR land. Bug reports
are welcome too.
Attribution lives in the overlay README block (look for the heading
`### rk3399-helios64-cpu-stability`), pointing back to forum topics
30074 and 58597, prahal and ebin-dev:
  https://github.com/armbian/build/blob/feat/helios64-cpu-stability-overlay/patch/kernel/archive/rockchip64-6.18/overlay/README.rockchip-overlays
  https://github.com/armbian/build/blob/feat/helios64-cpu-stability-overlay/patch/kernel/archive/rockchip64-7.0/overlay/README.rockchip-overlays
Thanks!

The most current download images for Helios64 are now all provided with linux 6.18.xx.
 
I downloaded a minimal image and checked the dtb: it would not appear to contain the opp-microvolt patch that made Helios64 finally stable.
 
So for the ones who have stability issues again on Helios64, I attached the patched dtb compiled for linux 6.18.xx using the exact same opp-microvolt values as in the previous dtb versions I compiled for linux 6.6 and 6.12. The current linux deb files can be downloaded from beta.armbian.com, the linux 6.18.18 deb files I used can be downloaded from here (to be installed with 'dpkg -i linux*').
 
In order to install the dtb, simply unzip it, copy it into the proper location, update initramfs and reboot:
 
# install the dtb with the opp-microvolt patch: unzip rk3399-kobol-helios64.dtb-6.18.18-opp.zip cp rk3399-kobol-helios64.dtb-6.18.18-opp /boot/dtb/rockchip/rk3399-kobol-helios64.dtb update-initramfs -u reboot rk3399-kobol-helios64.dtb-6.18.18-opp.zip

Hi, I continue to use file rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp on the last Helios64:  v25.8.1 for Helios64 running Armbian Linux 6.12.42-current-rockchip64
 
Without this file, i have crash or problem with ciffer orperation (Luks and another program...)
With this file, all it's Okok.
 
Have a good day.

Hi, 
I agree with Snakekick, the voltage patch is for me the best thing for the helios64 run stable. 
Maybe it's not a perfect solution but:
"It is better to have a good solution in time than a perfect one too late."

Hi, 
I agree with Snakekick, the voltage patch is for me the best thing for the helios64 run stable. 
Maybe it's not a perfect solution but:
"It is better to have a good solution in time than a perfect one too late."

Hi,
To my side, i have a stable system:
bulleye trunk
build from source with armbian-dev-tools
with 5.15.26 Kernel
and 400MHZ-1400MHZ schedutil.
Have a good day.

Hi,
To my side, i have a stable system:
bulleye trunk
build from source with armbian-dev-tools
with 5.15.26 Kernel
and 400MHZ-1400MHZ schedutil.
Have a good day.

Hi,
 
I try "on demand" 400-1400Mhz this week-end, seem stable.
I will waiting one week...
Next i try 400-1800Mhz.
I do all my previous test with "Conservative" on governor, maybe "on demand" is the key of stability.
 
Have a good day