-
Radxa Cubie A7A/A7Z - Allwinner a733
@deva67 Thanks a lot for building and testing! The SSH behaviour is by design: there is no default password, the first login has to happen on the screen or the serial console (README, “First login”). Your log is from commit c7d921e; current main uses the mainline DT name. Two questions, what was plugged into the USB port? a keyboard? the log shows “ohci-platform 4101400.usb: HC died”, which we have not seen yet. And is your switch 100 Mbit? Ethernet came up at 100 Mbps.
-
Are there any plans to create an Armbian image for the Radxa Cubie A7S? It's a really cute single-board computer with a powerful Allwinner A733 SoC.
From the community side: there is now a public build recipe for the A7S (mainline 6.18 plus an A733 patch series, Debian 13): https://github.com/DockSeed/a7s-build I have offered the patches in the A733 thread, one topic at a time: https://forum.armbian.com/topic/56130-radxa-cubie-a7aa7z-allwinner-a733/
-
Radxa Cubie A7A/A7Z - Allwinner a733
@deva67 Yes, I run a Radxa Cubie A7S on mainline 6.18 (now 6.18.54) with an A733 patch series on top. No BSP kernel; a few drivers are ported from Allwinner's BSP and say so in their headers. All of it is public as a build recipe: https://github.com/DockSeed/a7s-build One ./build.sh builds the boot chain, the kernel and a Debian 13 image in a container. The patches are single files with their origin in the header (kernel/6.18/patches/). Vendor binaries (boot0 with the DRAM init, GPU and WLAN firmware) are downloaded at build time, not shipped. What I have measured on the A7S: - eMMC at HS400 (200 MHz, 8 bit, 1.8 V): about 290 MB/s sequential read at 64 KiB requests, md5-equal data, same result across cold starts. - SD card at SDR104, 20 of 20 cold starts, about 91 MB/s sequential read. I am not a kernel developer. The measurements come from my board; the analysis and code were done with the help of an AI assistant (Claude). @Nick A @alexc I can offer the patches one topic at a time, eMMC first, since eMMC on the A7A/A7S still looked open here. Where should they go: into your 6.18 kernel, or onto the mainline work in PR #10712? I will prepare them for whichever you prefer.
normanherms
Members
-
Joined
-
Last visited