To the Radxa Engineering / Technical Support Team,
I am writing to provide detailed technical feedback regarding my experience with the Radxa Cubie A7A (Allwinner A733 SoC). As a developer building an embedded automotive dashboard project, I have attempted to deploy this on the Radxa platform, but I have encountered critical and persistent blockers regarding the graphics stack that render the board unsuitable for professional-grade embedded UI deployment in its current state.
I have performed a deep-dive audit of the software stack to ensure this was not a simple configuration error. Below is my Technical War Journal summarizing the stress-test results:
TECHNICAL WAR JOURNAL: Compatibility & Stability Stress-Test Report
Platform: Radxa Cubie A7A (Allwinner A733)
Duration: 30 Days of Continuous Deployment/Testing
Objective: Deploying Headless-to-GUI Automotive Dashboard (Qt/QML)
- OS & Image Permutations (Tested & Verified)
radxa-a733_bullseye_cli_r2.output_512.img: Failed - Graphics stack mismatch.
radxa-a733_bullseye_cli_r6.output_512.img: Failed - Kernel/Compositor instability.
radxa-a733_trixie_cli_t4.output_512.img: Failed - Library dependency hell.
- Graphics Stack & Compositor Stress-Testing
Wayland/Weston: System consistently fails to handshake with the GPU driver, resulting in Failed to create wl_display.
EGLFS/OpenGL: Attempted direct hardware acceleration usage but yielded fatal error: This plugin does not support createPlatformOpenGLContext! (This confirms a breakdown in the EGL/OpenGLES driver interface).
LinuxFB (Framebuffer): Attempted bypass via raw framebuffer (/dev/fb0). While technically functional for basic outputs, the lack of hardware acceleration causes CPU utilization to spike >150% during simple QML/UI redraws.
- Summary of Findings
I have performed a full audit of the software stack. The current OS images provide no path for reliable GPU-accelerated UI deployment. The system consistently fails at the interface level between the Application (Qt) and the Hardware (PowerVR BXM-4-64), regardless of the OS version or compositor configuration.
I hope the engineering team can address these driver stability issues or provide clearer documentation/patches for stable UI deployment. I believe this hardware has great potential, but it is currently hindered by the lack of a stable software graphics stack. If there are known patches or specific configuration methods for stable Kiosk/UI deployment on this SoC, I would appreciate any guidance.
Regards,
Firmansyah