3.4 KiB
#Using docker to set up build enviorement
1.Installing Docker
Ex Ubuntu: https://docs.docker.com/v17.09/engine/installation/linux/docker-ce/ubuntu/#install-docker-ce
for any other OS folow instruction on docker.com
2.Building image
cd DIY-LAPTOP/SOFTWARE/A64-TERES/
docker build - < Dockerfile
if build is successful,you can list you image with
docker image list
3.Running image
Run :
docker build -q - < Dockerfile
you will recieve as ouptur docker image id, to run it :
cd ../../
docker run -it --rm -v "$(pwd):$(pwd)" -w "$(pwd)" id_from_previous_command
Now you can follow instructions in README, just skip toolchain installation step:
Linux
cd SOFTWARE/A64-TERES/linux-a64
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- olimex_teres1_defconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- LOCALVERSION= clean
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j`nproc` LOCALVERSION= Image
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j`nproc` LOCALVERSION= modules
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j`nproc` LOCALVERSION= modules_install INSTALL_MOD_PATH=out INSTALL_MOD_STRIP=1
Allwinner Pack Tools
cd ../
make -C sunxi-pack-tools
U-Boot
cd scripts/
./build_uboot.sh #A64-Teres
or
./build_uboot_a64.sh #A64-OLinuXino
4. Helper Scripts
Ramdisk
Either make one with the steps below or download one from some other place.
Make sure the initrd is for aarch64
.
Get Busybox tree
cd ../
git clone --depth 1 --branch 1_24_stable --single-branch git://git.busybox.net/busybox busybox
Configure and build Busybox
Build a static busybox for aarch64. Start by copying the blobs/a64_config_busybox
file to .config
of your Busybox folder.
cp blobs/a64_config_busybox busybox/.config
cd busybox
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j`nproc` oldconfig
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j`nproc`
Make initrd.gz
Use the make_initrd.sh
script to create a simple initrd based on the busybox binary previously compiled.
cd ../scripts
./make_initrd.sh
Create bootable image
Scripts that create bootable image are using privilege escallation in Docker, so we recommend to close Docker container, and run them on host machine :
Close Docker and navigate to scripts directory:
exit #from Docker container
cd SOFTWARE/A64-TERES/scripts
sudo apt install kpartx bsdtar mtools dos2unix device-tree-compiler
Create kernel tarball :
./make_kernel_tarball.sh . ../linux-a64 #This will produce file named linux-a64-xx.yy.zz.tar.xz
Create simple image structure:
sudo ./make_simpleimage.sh teres.img 1000 ./linux-a64-3.10.104-1.tar.xz
sudo xz teres.img
Build a bootable image:
sudo ./build_image.sh teres.img.xz ./linux-a64-3.10.104-1.tar.xz xenial
If successfully completed, this command will create file named xenial-teres-bspkernel-<date>.img
.
Use dd
to write this image to an SD Card:
dd if=xenial-teres-bspkernel-<date>.img of=/dev/sdX bs=1M status=progress
Use these credentials to log in after first boot:
- User:
olimex
- Password:
olimex
Connection to the internet can be enabled via command-line by running:
sudo nmtui
Feel free to install everything you want, e.g., a graphical desktop environment:
sudo install_desktop.sh mate # installs mate desktop