Allwinner A133 Firmware Work [hot] -

Allwinner A133 Firmware Work

The Allwinner A133 is an ARM-based SoC used in entry-level tablets and SBCs. This post covers practical steps and considerations for working with A133 firmware—whether you’re updating, extracting, modifying, or building firmware images.

4. How to Flash A133 Firmware

Allwinner provides several flashing methods:

4. Building components

1. U-Boot (SPL + main):
   • Clone sunxi U-Boot branch compatible with your device.
   • Configure with the board defconfig (or a close SoC board) then make CROSS_COMPILE set.
   • Example:

     export CROSS_COMPILE=aarch64-linux-gnu-
     make <board_defconfig>
     make -j$(nproc)
     

2. Kernel & Device Tree:
   • Use a kernel version supported by required drivers; many A133 boards use a 5.x or 6.x mainline or vendor kernel.
   • Build kernel with CONFIG options for DRM, DRM drivers for GPU (if supported), NAND/eMMC, MMC, Ethernet, Wi-Fi.
   • Create/adjust DTB for board-specific pinmux, regulators, and peripherals.
3. Boot scripts & uEnv/boot.scr:
   • Create boot scripts or env that point to kernel and rootfs locations, initramfs, and kernel cmdline.
4. Root filesystem:
   • Use ext4, f2fs, or squashfs depending on device and storage. Armbian/rootfs tarballs are common starting points.

5.2 Modifying U-Boot Environment

Interrupt boot (press any key on UART console), then: allwinner a133 firmware work

setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p7 rw
saveenv

4.3 SD Card Boot

Write a133_xxx.img directly to SD card:

sudo dd if=a133_firmware.img of=/dev/sdX bs=1M status=progress

5.1 Changing Boot Logo

Replace logo image in logo.bmp or logo.jpg inside the boot partition. For Android, also update logo.bin via pack -l. Allwinner A133 Firmware Work The Allwinner A133 is

Task 1: Unbricking via FEL Mode

The A133 has a built-in “FEL” mode (Factory Emergency Loader). Short the NAND/eMMC data pin (or hold the FEL button on devkits) while powering on. The SoC will wait for a USB command.

Use sunxi-fel (Linux) or LiveSuit (Windows) to upload a new firmware: U-Boot (SPL + main):

sudo sunxi-fel version  # Check connection
sudo sunxi-fel write 0x2000 u-boot-sunxi-with-spl.bin

FEL Mode: The Debug and Recovery Gateway

One of the most valuable features for firmware engineers is FEL (Forced Entry Level) mode. Triggered by holding a specific button (usually the "VOL+" or "FEL" pin) during power-on or by sending a USB reset command, FEL halts the BROM and exposes a USB bulk endpoint.

In FEL mode, the SoC does not execute any external bootloader. Instead, it waits for commands over USB. This allows:

• Flashing bootloaders and firmware to empty or corrupted storage
• Booting a full system over USB for testing (via sunxi-fel tool)
• Debugging early boot failures without JTAG
• Bypassing signature checks during development (if secure boot is disabled)

The sunxi-fel utility is the primary tool for interacting with FEL mode. For example:

sunxi-fel ver          # Read chip ID and BROM version
sunxi-fel write 0x2000 u-boot-sunxi-with-spl.bin
sunxi-fel exec 0x2000 # Execute custom code