Supported Devices

Cubieboard2

Introduction

The Cubieboard2 is an low cost, high performance open ARM box based on Allwinner A20 (Cortex A7 Dual-Core) which can be used in many fields.

CPU Information Processor : ARMv7 Processor rev 4 (v7l) processor : 0 BogoMIPS : 1915.28 processor : 1 BogoMIPS : 1915.28 Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 4 Hardware : sun7i Revision : 0000 Serial : 0000000000000000 boot.log

Installation

Booting CRUX-ARM from uSD

This info is based on http://linux-sunxi.org/Bootable_SD_card and u-boot.bin and SPL are built from git://github.com/hno/u-boot branch wip/a20
To install the current release we need to setup an uSD card with 2 partitions after cluster 2048 (see http://linux-sunxi.org/Bootable_SD_card#Partitioning for details). The first partition must be vfat formated, required for bootloader's stuff and the second one must be ext2, ext3 or ext4 formated and will contain the files from the release and current kernel modules.

• First to activate the bootloader we need to write directly to the card with 'dd' command (sdX directly without specifying the partition):
  • sunxi-spl.bin
  • u-boot.bin

dd if=sunxi-spl.bin of=/dev/sdX bs=1024 seek=8
dd if=u-boot.bin of=/dev/sdX bs=1024 seek=32

• Then on the first partition we must put these files:
  • uImage-3.4.43-cubieboard2_20130827 After download rename it to uImage which is used in boot.scr
  • boot-mmc.scr and rename it to boot.scr
    • boot-mmc-serial.scr and rename it to boot.scr if you will user serial output
  • script.bin
• For the second partition, download and place contents from these files:
  • crux-arm-rootfs-3.5-cubieboard2.tar.xz
  • modules-3.4.43-cubieboard2_20130827.tar.xz (kernel modules)

Configuration

We should setup all the important files: pkgmk.conf, prt-get.conf, inittab, fstab, rc.conf, net ...

Serial Console

To obtain serial access we need to make some modifications to this file:

• Uncommenting and changing the line in /etc/inittab:

s1:2:respawn:/sbin/agetty 115200 ttyS0 vt100

• In the client side (using minicom here) it's needed to disable hardware flow control to get input events working.

Udev Rules

• Add these values to /etc/udev/rules.d/50-mali.rules

KERNEL=="mali", MODE="0660", GROUP="video"
KERNEL=="ump", MODE="0660", GROUP="video"