Copyright (C) 2012 Alejandro Mery amery@geeks.cl
For a full list of contributors, see
this link
or use the command git shortlog -se --no-merges
.
Tools to help hacking Allwinner A10 (aka sun4i) based devices and its successors (sunxi), that's why the 'x' in the package name.
.fex
file (de)compiler
Usage: ./sunxi-fexc [-vq] [-I <infmt>] [-O <outfmt>] [<input> [<output>]]
infmt: fex, bin (default:fex)
outfmt: fex, bin (default:bin)
compatibility shortcut to call sunxi-fexc
to decompile a script.bin
blob back into .fex
format used by Allwinner's SDK to configure
the boards.
compatiblity shortcut to call sunxi-fexc
to compile a .fex
file
into the binary form used by the legacy 3.4 kernel ("linux‑sunxi").
script interface for talking to the FEL USB handler built in to the CPU. You activate FEL mode by pushing the uboot / recovery button at poweron. See http://linux-sunxi.org/FEL/USBBoot for a detailed usage guide.
Simple wrapper (script) around fel-pio
and sunxi-fel
to allow GPIO manipulations via FEL
ARM native sdcard bootloader forcing the device into FEL mode
ARM native sdcard bootloader, which is only printing a short "hello" message to the UART0 serial console. Because it relies on runtime SoC type detection, this single image is bootable on a wide range of Allwinner devices and can be used for testing. Additionally, it may serve as a template/example for developing simple bare metal code (LED blinking and other similar GPIO related things).
ARM native helper (binary) for fel-gpio
Manipulate PIO register dumps
Tool for manipulating Allwinner NAND partition tables
Tool used to create raw NAND images (including boot0 images)
ARM native boot helper to force the SD port into JTAG and then stop, to ease debugging of bootloaders.
Dump information from Allwinner boot files (boot0 / boot1)
--type=sd include SD boot info
--type=nand include NAND boot info (not implemented)
gives information about a phoenix image created by the phoenixcard utility and optionally extracts the embedded boot code & firmware file from their hidden partitions.
Tool for reading DRAM settings from registers. Compiled as a static binary for use on android and other OSes. To build this, get a toolchain and run:
make CROSS_COMPILE=arm-linux-gnueabihf- sunxi-meminfo
A simple tool, which can be executed on a rooted Android device to dump the script.bin blob from RAM via reading /dev/mem. To build this, get a toolchain and run:
make CROSS_COMPILE=arm-linux-gnueabihf- sunxi-script_extractor
Compilation requires the development version of libusb-1.0 (include header
and library) to be installed for sunxi-fel
. Unless you explicitly pass
LIBUSB_CFLAGS and LIBUSB_LIBS to the make utility, pkg-config
is also
needed.
Available build targets:
-
make tools
builds tools that are useful on the host. This is what most people will want, and our default target (when simply usingmake
). -
make target-tools
builds tools that are intended for the target (Allwinner SoC), using a cross-compiler. The toolchain prefix CROSS_COMPILE defaults toarm-none-eabi-
, adjust it if needed.
Hint: When compiling 'natively' on the target platform you may simply use an empty toolchain prefix here (make target-tools CROSS_COMPILE=
ormake all CROSS_COMPILE=
). -
make all
builds both tools and target-tools. -
make install-tools
builds tools and then copies/installs them to a filesystem location. The destination is affected by settings forDESTDIR
,PREFIX
and possiblyBINDIR
. For details, please refer to the Makefile. You may usemake install
as a shortcut for this. -
make install-target-tools
builds target-tools and then copies/installs them to a filesystem location selected byDESTDIR
,PREFIX
and possiblyBINDIR
- seemake install-tools
above. -
make install-all
builds and installs both tools and target-tools. -
make misc
builds miscellaneous (host) utilities that are not part of our 'standard' suite. Currently this meansphoenix_info
andsunxi-nand-image-builder
. -
make install-misc
builds misc and installs the resulting binaries.
This software is licensed under the terms of GPLv2+ as defined by the Free Software Foundation, details can be read in the LICENSE.md file.