Guation

Hello everyone I noticed that the mainline has updated the u-boot version of the RADXA Cubie A5E to v2026.07, but all the u-boot patches for this board are still retained at version v2026.01 and have not been enabled. I am now unsure where to place the patches for the 1GB memory version.

Hi, @karavan Thank you for helping with the testing. It seems that the DRAM parameters of the 1G version and the 4G version cannot be mixed. I will try to enable U-BOOT to perform dynamic identification at startup. The content of the /sys/devices/system/cpu/cpufreq directory is empty. It appears that this issue has been present in the mainline version, and is not caused by the U-BOOT modifications I made. I checked it on the official Radxa system and it looks like this: root@radxa-cubie-a5e:~# uname -a Linux radxa-cubie-a5e 5.15.147-10-aw2501 #10 SMP PREEMPT Mon Sep 8 07:12:29 UTC 2025 aarch64 GNU/Linux root@radxa-cubie-a5e:~# ls -l /sys/devices/system/cpu/cpu*/cpufreq lrwxrwxrwx 1 root root 0 Aug 31 02:49 /sys/devices/system/cpu/cpu0/cpufreq -> ../cpufreq/policy0 lrwxrwxrwx 1 root root 0 Aug 31 02:53 /sys/devices/system/cpu/cpu1/cpufreq -> ../cpufreq/policy0 lrwxrwxrwx 1 root root 0 Aug 31 02:53 /sys/devices/system/cpu/cpu2/cpufreq -> ../cpufreq/policy0 lrwxrwxrwx 1 root root 0 Aug 31 02:53 /sys/devices/system/cpu/cpu3/cpufreq -> ../cpufreq/policy0 lrwxrwxrwx 1 root root 0 Aug 31 02:53 /sys/devices/system/cpu/cpu4/cpufreq -> ../cpufreq/policy4 lrwxrwxrwx 1 root root 0 Aug 31 02:53 /sys/devices/system/cpu/cpu5/cpufreq -> ../cpufreq/policy4 lrwxrwxrwx 1 root root 0 Aug 31 02:53 /sys/devices/system/cpu/cpu6/cpufreq -> ../cpufreq/policy4 lrwxrwxrwx 1 root root 0 Aug 31 02:53 /sys/devices/system/cpu/cpu7/cpufreq -> ../cpufreq/policy4

Hi, @karavan You only need to write this image to the TF card and check if it can be booted: Releases · Guation/radxa-cubie-a5e-armbian-build Additionally, please check if the mainline version has a /sys/devices/system/cpu/cpu*/cpufreq directory for @xaja34. Thank you for your help.

Hi @zmxyz I prefer to first verify on the 2GB/4GB version whether the parameters can be unified, in order to avoid splitting it into two versions as much as possible. 我倾向于先在2GB/4GB版本上验证是否能统一参数，尽量避免它分裂为两个版本。 I need someone who has this version to help verify it. 需要一个拥有该版本的人帮忙验证。 So it hasn't been submitted to the upstream yet. 所以至今还没有提交到上游。 Of course, dynamic recognition is also feasible, but the changes will be slightly larger. 当然做动态识别也是可行的，改动会稍微大一点。 Guation

Hi domillo, I remember that when you first start the image, it will ask you to create a user and set its password. So the password 1234 for root may not be usable. Perhaps the repeated startup caused the initialization process to be missed. Guation

Hi domillo, If the green light has started flashing, it may indicate that the system has been started, but at this point, we cannot determine the IP address of the Cubie a5e. Once you have a UART adapter, please try to capture the DRAM parameters of the Cubie a5e according to this document: radxa-cubie-a5e-u-boot/README.md Guation

Hi xaja34, The patches and all code modifications used to build the 1 GB Cubie A5E images are already present in my repository. I pushed the complete Git commits alongside the prebuilt images that I published in the Releases section. You can find the changes here: radxa-cubie-a5e-armbian-build@202f1bf Best regards, Guation

I found that this is related to the DRAM parameters in u-boot. I modified these parameters and now it can boot on my RADXA Cubie A5E v1.2 with 1GB RAM. However, I am not sure if these parameters are valid for the 2GB/4GB version that uses 0.6V. This is the image with the parameters I modified: radxa-cubie-a5e-armbian-build This is the tool I use to obtain parameters: radxa-cubie-a5e-u-boot