Full SDK compilation for the A133 involves compiling the Bootloader, Kernel, and Android OS separately. The Board Support Package (BSP) often references the sun50iw10p1 platform codename.
The kernel configuration file is located at arch/arm64/configs/sun50iw10p1smp_a133_android_defconfig . Build outputs are placed in longan/out/a133/c3/android/ .
Patched unsigned boot.img for Allwinner A133 does not boot #8810 allwinner a133 firmware work
The Allwinner A133 offers a flexible yet structured firmware environment. While the boot process is multi-stage and relies on some proprietary blobs (boot0, dram parameters), the availability of FEL mode and open-source U-Boot support makes it a manageable platform for experienced embedded engineers. Understanding the interaction between BROM, boot0, and U-Boot is critical to bringing up custom boards, recovering bricked devices, and implementing secure boot.
: Most A133 devices run Android. The firmware here includes the Full SDK compilation for the A133 involves compiling
To interact with an A133 chip, you need specific software utilities designed for Allwinner's proprietary boot ROM protocol (FEL mode). PhoenixSuit
Look for .img files rather than .zip files, as Allwinner chips typically use image-based flashing tools. 2. Required Tools & Drivers Build outputs are placed in longan/out/a133/c3/android/
Allwinner SoCs are paired with specific Power Management ICs (like the AXP717). If your firmware is compiled for a different PMIC, the board will not distribute power correctly, resulting in a completely dead device or a bootloop.
The work done on Allwinner A133 firmware has a range of applications, including:
If a valid boot medium is found, the BROM loads the into a small internal SRAM (typically 48KB–64KB). The boot0 image must be signed if secure boot is enabled; otherwise, a plain binary is accepted.