Skip to content

Add Support Shimeta Aiot-rk3588a #8971

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
ghhccghk wants to merge 16 commits into
base: main
Choose a base branch
from
+834 −0
Draft

Add Support Shimeta Aiot-rk3588a #8971

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
162ed68
Aiot-rk3588a:Add shimeta-aiot-rk3588a board configuration
ghhccghk Nov 16, 2025
1000470
Update Aiot-rk3588a board configuration with new boot settings
ghhccghk Nov 18, 2025
9b19719
Add aiot_rk3588a_defconfig for Aiot-rk3588a board uboot configuration
ghhccghk Nov 19, 2025
4d570c4
Add device tree and update configuration for Aiot-rk3588a board
ghhccghk Nov 21, 2025
d96cb43
Add Aiot rk3588a Linux Devices Tree
ghhccghk Nov 22, 2025
fcb9cdc
Disable the DP interface in the Shimeta Aiot-rk3588a Linux device tre…
ghhccghk Nov 23, 2025
7d4f5c2
Disable PCIe interfaces in the Aiot-rk3588a device tree,Failure to sh…
ghhccghk Nov 23, 2025
34b352c
Add bootargs, LED, and MCU configuration to Aiot-rk3588a device tree
ghhccghk Nov 25, 2025
58420d3
Add ADC keys and EDP panel configuration for Aiot-rk3588a device tree
ghhccghk Nov 27, 2025
c29a447
Update Aiot-rk3588a device tree: remove unused includes, update LED G…
ghhccghk Nov 29, 2025
13dba92
Update Aiot-rk3588a device tree: add heartbeat and default-on LED con…
ghhccghk Nov 29, 2025
1124734
Update Aiot-rk3588a device tree: correct GPIO for heartbeat LED, enab…
ghhccghk Dec 2, 2025
ac1de5e
Update Aiot-rk3588a device tree: refine GPIO and I2C configurations
ghhccghk Dec 3, 2025
eba15bb
Update Aiot-rk3588a device tree: refine regulator and GPIO configurat…
ghhccghk Dec 6, 2025
b36ca7e
Update Aiot-rk3588a board config: add V2.0 and V3.1 versions, note M.…
ghhccghk Jan 6, 2026
9405f71
Add BOARD_VENDOR to Aiot-rk3588a board config
ghhccghk Jan 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions config/boards/shimeta-aiot-rk3588a.conf
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
#Rockchip RK3588 SoC octa core 4-8GB SoC 1Gbe eMMC USB3 USB2 HDMI Type-c LVDS EDP EDPx MIPI MIPI_CAN RS485 RS232 Mic Headphones,4G/5G Module,SATA，HDMI in，Ir Speaker I2C TP，TF Card，FAN
Copy link
Member

@EvilOlaf EvilOlaf Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to list every single feature. Cut this down to at least half, see other boards for examples.

#Note: Optional 2k EEPROM, PCIe switchable to M.2, speaker output (supports left/right channel output, max. dual 20W/4Ω or 10W/8Ω), eMMC supports 16–128GB. This development board has three versions: V1.1,V1.2,V1.3,V2.0,V3.1
#Note: This board supports M.2 SSD interfaces and 16GB memory under version V3.1.
BOARD_NAME="Aiot rk3588"
Copy link
Collaborator

@tabrisnet tabrisnet Nov 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should Shimeta be explicitly mentioned here? Aiot feels a hair generic.
@coderabbitai

Copy link
Contributor

@coderabbitai coderabbitai bot Nov 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check BOARD_NAME patterns in existing board configuration files
echo "=== BOARD_NAME patterns in board configs ==="
rg -n 'BOARD_NAME=' config/boards/ -A 0 | head -50

echo -e "\n=== Rockchip RK3588 board names specifically ==="
rg -n 'BOARD_NAME=' config/boards/*rk3588*.conf -A 0

echo -e "\n=== Board configs with 'aiot' or 'Aiot' in filename or BOARD_NAME ==="
fd -e conf -e csc aiot config/boards/
rg -i 'aiot' config/boards/ -n -C 1

Length of output: 3575

@tabrisnet, you're absolutely right! Looking at the naming patterns across Armbian board configurations, manufacturer/vendor names are typically included in BOARD_NAME for clear identification. Examples include:

  • "Xiaomi Elish"
  • "YouYeeToo YY3568"
  • "Turing RK1"
  • "ThinkPad X13s"
  • "Tinker Board"

"Aiot" (AI + IoT) is indeed quite generic and doesn't uniquely identify this board. Since the filename already includes shimeta, the BOARD_NAME should follow the same pattern. I'd recommend:

BOARD_NAME="Shimeta Aiot RK3588"

This would be consistent with how other vendors name their boards in the Armbian build system and makes it clear which manufacturer's board this is.

🧠 Learnings used 
Learnt from: HackingGate
Repo: armbian/build PR: 8665
File: config/boards/photonicat2.csc:4-4
Timestamp: 2025-10-26T10:41:35.118Z
Learning: In the Armbian build system, rk3576 boards consistently use BOARDFAMILY="rk35xx" for both vendor and edge kernel targets. The rk35xx family configuration sources rockchip64_common.inc, which provides edge and current kernel branch definitions, making these branches available even though they're not defined directly in rk35xx.conf.

Learnt from: EvilOlaf
Repo: armbian/build PR: 8537
File: config/boards/qcom-robotics-rb5.conf:1-1
Timestamp: 2025-09-18T03:36:17.862Z
Learning: In Armbian board configuration files (regardless of file extension), the standard pattern is to have only one line as a comment describing the board hardware specifications. This single-line description typically includes the SoC model, core count, RAM options, and key features like connectivity options, storage interfaces, and special features. The file extensions indicate board support status: .conf (standard support), .csc (community supported), .eos (end of support), .tvb (tvbox), .wip (work in progress).

Learnt from: igorpecovnik
Repo: armbian/build PR: 8789
File: config/kernel/linux-sunxi64-edge.config:839-839
Timestamp: 2025-10-22T07:51:53.015Z
Learning: In Armbian's wireless driver configuration, CONFIG_RK_WIFI_DEVICE_* options are Rockchip-specific device registration settings, while CONFIG_WLAN_UWE* are the actual cross-platform driver modules for UWE5622 wireless chips. The UWE5622 chip (manufactured by Unisoc/Spreadtrum) is used on multiple Allwinner boards including Orange Pi Zero 2/2W/3 and Orange Pi 3 LTS, so CONFIG_WLAN_UWE5621/5622 along with Unisoc infrastructure options (CONFIG_SPARD_WLAN_SUPPORT, CONFIG_SC23XX, CONFIG_UNISOC_WIFI_PS, CONFIG_WCN_BSP_DRIVER_BUILDIN) are correct in sunxi64 kernel configs.

Learnt from: igorpecovnik
Repo: armbian/build PR: 8849
File: config/boards/radxa-e54c.csc:14-28
Timestamp: 2025-11-02T20:49:56.719Z
Learning: In Armbian board configuration files (config/boards/*.conf, *.csc, etc.), do not use kernel_config_set, kernel_config_set_m, kernel_config_set_y, or custom_kernel_config__* functions to modify kernel configuration. Kernel configuration is associated with LINUXFAMILY/BOARDFAMILY, not individual BOARD. Board-specific kernel modifications cause inconsistency in kernel packages published to the apt repository because boards within a family share the same kernel packages. Kernel configuration changes must be made in the appropriate kernel config file (e.g., config/kernel/linux-*-*.config) or in family configuration files (config/sources/families/*.conf, *.inc) instead.

Learnt from: EvilOlaf
Repo: armbian/build PR: 8537
File: config/boards/qcom-robotics-rb5.conf:1-1
Timestamp: 2025-09-18T03:36:17.862Z
Learning: In Armbian board configuration files, .wip and .conf extensions require BOARD_MAINTAINER to be present and contain at least one maintainer. If no maintainer is present, the board support rules state it does not qualify for standard support and must be moved to community support (.csc extension). This is documented at https://docs.armbian.com/User-Guide_Board-Support-Rules/

Learnt from: amazingfate
Repo: armbian/build PR: 8619
File: config/sources/families/rockchip.conf:64-70
Timestamp: 2025-09-14T06:29:18.958Z
Learning: In the Armbian build system, vendor branch configurations in family files are designed to be shared across multiple SoCs within the same family that use the same vendor kernel tree. For example, rk35xx and rockchip-rk3588 families both use identical vendor branch settings (same KERNELSOURCE, KERNELBRANCH, and KERNELPATCHDIR), demonstrating that vendor branches are intentionally generic rather than SoC-specific.

Learnt from: pyavitz
Repo: armbian/build PR: 8388
File: config/boards/kickpik2b.conf:1-14
Timestamp: 2025-07-17T04:12:33.125Z
Learning: In the Armbian build system, board configuration files (*.conf) follow a project standard of not including shebang lines, even though they contain bash code and are sourced by the build system. This is an established Armbian convention that individual contributors are expected to follow, and changes to this standard would require broader project maintainer approval.

Learnt from: EvilOlaf
Repo: armbian/build PR: 8619
File: config/sources/families/rockchip.conf:64-70
Timestamp: 2025-09-14T06:10:25.610Z
Learning: In the Armbian build system, rk32xx and rk33xx Rockchip SoCs no longer have BSP-based (vendor) kernel branches. The rk3506 is the first 32-bit Rockchip SoC to use the vendor branch in the current codebase.

Learnt from: EvilOlaf
Repo: armbian/build PR: 8586
File: config/boards/nanopi-r76s.conf:15-21
Timestamp: 2025-09-07T17:39:32.272Z
Learning: In the Armbian build system, the variables $BOARD and $SDCARD are always set by the build framework, so guard checks for these variables are unnecessary in board configuration files and hook functions.

Learnt from: amazingfate
Repo: armbian/build PR: 8619
File: config/sources/families/rockchip.conf:222-230
Timestamp: 2025-09-14T06:32:29.806Z
Learning: In the Armbian build system, the write_uboot_platform() function implementations follow different patterns across Rockchip family files. The newer standard (used in rockchip64_common.inc and rk3506) includes 'status=none' parameter in dd commands, while older implementations (rk3288, rk322x) use an older pattern without this parameter. The rk3506 implementation correctly follows the current Rockchip family standard.

BOARD_VENDOR="shimeta"
BOARDFAMILY="rockchip-rk3588"
Copy link
Collaborator

@tabrisnet tabrisnet Dec 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BOARD_VENDOR was added to all of the boards recently. #9063

BOARD_MAINTAINER="ghhccghk"
BOOTCONFIG="aiot_rk3588a_defconfig"
BOOT_SOC="rk3588"
KERNEL_TARGET="vendor"
KERNEL_TEST_TARGET="vendor"
FULL_DESKTOP="yes"
BOOT_LOGO="desktop"
BOOT_FDT_FILE="rockchip/rk3588-aiot-rk3588a.dtb"
IMAGE_PARTITION_TABLE="gpt"
Loading
Loading