OPI 4A - Allwinner T527

[JuanEsf]

@re.ADW You can generate and share the "SHA256" hash of the image that was used on your board, please...

[re.ADW]

@JuanEsf Yep, here it is a080ed7128c898bec1cad6ec68c57bae159169d2fa06fb18008100ad63e4445c

[Randy Joshua Simorangkir]

i used OPi4a then using image, but no one USB sound card working, lsusb found the device but not registered as sound device, alsamixer,pulse audio does not detect device.
how to fix ?

 

i'm using image : Orangepi4a_1.0.4_ubuntu_jammy_desktop_gnome_linux5.15.147

frome here : Gdrive

[Werner]

56 minutes ago, Randy Joshua Simorangkir said:

Orangepi4a_1.0.4_ubuntu_jammy_desktop_gnome_linux5.15.147

This is not an Armbian image. We do not support 3rd party images.

[Randy Joshua Simorangkir]

ah i see, sorry.

is there armbian OS for Opi4A?
i didnt found yet, on official page armbian, only for OPI4 and OPI4 LTs.

thank you in advance

[Werner]

No, this board isn't supported. However anyone from the community can step up and add support for it.

Found an attempt on Github:https://github.com/juanesf/build/pull/1 

[cvxx]

@JuanEsf in case you need testing - I own both OrangePi 4A and Radxa Cubie A5E.

So far I tried to build the image from your repo (https://github.com/juanesf/build) - neither board boots for me.

[ioncube]

I think this OS for T527 Allwinner should work on 4A. Official 4A releases are stuck at jammy while this has Noble

https://github.com/AvaotaSBC/AvaotaOS/releases

 

If you observe the contents inside `linux-dtb-sun55i-t527-bsp_0.3.0.4_arm64.deb` you will realise it's doesn't have 4A `dtb` So after burning image copy `dtb` File from jammy. Kernel is same so I belive it should work

 

 

 

 

[ioncube]

Regarding the VPU under jammy I have compiled a guide here 

https://github.com/defencedog/orangepi4A/tree/main/GPU_VPU

 

Gstreamer players like clapper do use HW acceleration for H264 & H265 (however 10bit HEVC) are not working ad per my tests

 

Version 1.0 of `libcedarc` is used. In v2.0 HEVC 10bit support is added. If anyone can provide git links & some help to compile I am ready to spend time on it

 

In whole internet I only got x1 git for this

https://gitlab.com/tina5.0_aiot/media/cedarc-release/libcedarc_v2.0

[ioncube]

I further expanded kernel because VPN clients like twingate needed a module `tun` more on this here https://github.com/defencedog/orangepi4A/tree/main/kernels#update-2

[BillyBlaze]

None of the images are no longer working for me, no matter which recent image I take, the A5E board just remains stuck with a solid blue light (with some green light flickering).

I even tried compiling armbian myself, but that also didn't work.

The only image working for me is the 25.02 version from earlier this year.

I am using the Radxa A5E v1.2 version with 4gb ram.

 

I also mounted the SD card to a linux machine and looked into /var/log for a boot file or reading the journal but I don't see any logs written.

Have somebody stumbled unto a solution or does somebody have advice me how I can get the logs to find the culprit?

Edited Sunday at 10:06 AM by BillyBlaze

[BillyBlaze]

I was able to find a UART module to read out the boot.

See the file attached of the full log I was able to capture.

 

It seems to fail on this part:

Starting kernel ...

done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  UUID=0a0755af-1936-4167-9d26-9ca9a87a9103 does not exist.  Dropping to a shell!

 

U-Boot SPL 2025.10-rc3-armbian-2025.txt