See the discussion in https://forum.armbian.com/topic/30074-helios64-armbian-2308-bookworm-issues-solved/page/3/#comment-179040

Description

The Helios64-specific changes get moved to rockchip64, as https://github.com/armbian/build/blob/main/config/boards/helios64.csc#L3 says that it's not rk3399 anymore.

How Has This Been Tested?

See discussion in https://forum.armbian.com/topic/30074-helios64-armbian-2308-bookworm-issues-solved

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] Any dependent changes have been merged and published in downstream modules

View the full article

Hi @prahal,

 

I'm running Armbian_23.5.4_Helios64_bookworm_current_6.1.36 on my Helios64.

In /etc/armbian-release, BOARDFAMILY was rk3399

 

As per your post, I manually changed BOARDFAMILY to rockchip64.

$ cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=helios64
BOARD_NAME="Helios64"
BOARDFAMILY=rockchip64
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=173ed85
VERSION=23.08.0-trunk
LINUXFAMILY=rockchip64
ARCH=arm64
IMAGE_TYPE=stable
BOARD_TYPE=csc
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
FORCE_BOOTSCRIPT_UPDATE=
VENDOR=Armbian
REVISION=23.08.0-trunk
BOOTSCRIPT_FORCE_UPDATE="no"
BOOTSCRIPT_DST="boot.cmd"
BRANCH=current

 

That's dirty, but that let me have access to the newest armbian package releases.

Can you please advise whether you know a cleaner way to match to the new BOARDFAMILY for Helios64 and its rockchip processor?

deleted - offtopic

Edited April 22, 20242 yr by Deoptim