Manual build howto

This page describes the process to combine sunxi U-Boot, linux kernel and other bits together to create a useful SD-card from scratch, the basis for further hacking. You will need a Linux system running to follow this howto. If you are going to install Linux on real hardware in in a Virtual Machine it is prefereable you get a 64bit version (referred to as amd64 or x86_64) because some allwinner tools only run on 64bit systems. You may not need these tools but they may be useful for device recovery.

We of course do not build a whole distribution, we only build U-Boot, the kernel and a handful of tools, and then use an existing rootfs to get a useful system. Depending on the rootfs size, you might want to use a 2GB or larger SD Card. SD-card partitioning and formatting will be taken care of later.

= Getting a cross toolchain =

For this part, you need to refer to our toolchain page.

= Building u-boot = Please refer to U-Boot

= Building script.bin =

First, get the following repositories: git clone git://github.com/linux-sunxi/sunxi-tools.git git clone git://github.com/linux-sunxi/sunxi-boards.git

Descend into sunxi-tools and run the command 'make fex2bin'.

Then, get into the sunxi-board tree and find the fex file for your board. You also need to find out the MAC Address of Ethernet adapter, as you will need to fix the MAC in the [dynamic] section of the fex file, to match the one for your device: [dynamic] MAC = "000000000000" to, for example: [dynamic] MAC = "0123456789AB"

Note: If the [dynamic] section does not exist in your .fex file, you can just add it with your MAC address.

For more information see EMAC.

Now you can create the script.bin file: ../../../sunxi-tools/fex2bin .fex script.bin You will need this later on when finishing u-boot installation.

= Building the kernel = Please refer to our Kernel compilation guide. = Setting up the boot partition =

install bootloader and partition card
Please execute commands in Bootable_SD_card, Bootable_SD_card, Bootable_SD_card

Mount your boot or root partition again: mount /dev/${card}1 /mnt

boot.cmd
Now create boot.cmd in /mnt or /mnt/boot with the following content:

kernel arguments
For traditional layout with separate boot partition the kerenl will use the second partition (mmcblk0p2) for root: setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait panic=10 ${extra} With single partition use the first: setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p1 rootwait panic=10 ${extra} You may want to add more arguments to set up display, etc

load kernel
These commands load the script.bin and kernel from the first partition. fatload mmc 0 0x43000000 script.bin || ext2load mmc 0 0x43000000 boot/script.bin fatload mmc 0 0x48000000 uImage || ext2load mmc 0 0x48000000 uImage boot/uImage bootm 0x48000000

machine id
If you have cubieboard2 and are dealing with an obsolete kernel or u-boot built by cubietech you might need to insert one of following lines into your boot.cmd (see machine ID mismatch):

setenv machid 0x00000f35 or setenv machid 0x000010bb

boot.scr
Now you can generate boot.scr: mkimage -C none -A arm -T script -d /mnt/boot.cmd /mnt/boot.scr

cleanup
Unmount the partition again. umount /mnt

= Setting up the rootfs = Please refer to Bootable_SD_card

As a last step you need to copy the kernel modules into the newly created rootfs. Change into the top level directory of the newly created rootfs and run: mount ${cardroot} /mnt mkdir -p /mnt/lib/modules rm -rf /mnt/lib/modules/ cp -r /output/lib /mnt/ umount /mnt (Replace  with the directory you have built your kernel in as described above.)

= Boot! =

Now you should be able to unmount your SDCard filesystems, and you should be able to boot your brand new installation.