Differences between revisions 4 and 6 (spanning 2 versions)
Revision 4 as of 2016-07-18 01:40:09
Size: 3413
Comment: correct "git co" to "git checkout"
Revision 6 as of 2018-01-17 09:37:17
Size: 3474
Editor: PaulWise
Comment: fix page link
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from InstallingDebianOn/CuBox
Line 17: Line 18:
This page is about the Marvell Armada 510 based Cubox (1st version), NOT about the [[ArmHardFloatPort/CuBox-i|CuBox-i]] ! This page is about the Marvell Armada 510 based Cubox (1st version), NOT about the [[nstallingDebianOn/SolidRun/CuBox-i|CuBox-i]] !

Translation(s): none

DebianOn is an effort to document how to install, configure and use Debian on some specific hardware. Therefore potential buyers would know if that hardware is supported and owners would know how get the best out of that hardware.

The purpose is not to duplicate the Debian Official Documentation, but to document how to install Debian on some specific hardware.

If you need help to get Debian running on your hardware, please have a look at our user support channels where you may find specific channels (mailing list, IRC channel) dedicated to certain types of hardware.

Models covered
Solidrun Cubox

This page is about the Marvell Armada 510 based Cubox (1st version), NOT about the ?CuBox-i !

Sub-models options : - 1GB RAM

Overall Status

Debian kernel fails to boot. The rest works fine.

Kernel

I had to compile a kernel with this .config

Dependencies:

# apt install gcc-arm-linux-gnueabihf u-boot-tools

Build:

$ cd $BUILD
$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git checkout v4.5
$ export ARCH=arm
$ export CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf-
$ make olddefconfig
$ make -j5 zImage
$ make -j5 dtbs
$ make -j5 modules
$ find . \( -name '*.ko' -o -wholename './modules.*' \) -type f | tar cvf modules.tar -T -

U-Boot

My Cubox runs a version of U-Boot forked by Solidrun in 2009. The old version of U-Boot in the Cubox doesn't support device tree, so we have to cheet it

$ cat arch/arm/boot/zImage arch/arm/boot/dts/dove-cubox.dtb > zImage.cubox
$ mkimage -A arm -O linux -C none  -T kernel -a 0x00008000 -e 0x00008000 -n 'Linux-cubox' -d zImage.cubox uImage

boot.scr:

setenv bootargs console=ttyS0,115200n8 console=tty1,115200 root=/dev/mmcblk0p1 rootfstype=ext3 rootwait video=HDMI-A-1:1920x1080-32@60
ext2load mmc 0 0x2000000 /boot/uimage
bootm 0x2000000

$ mkimage -A arm -O linux -C none  -T script -n 'Boot Linux' -d boot.txt boot.scr

Debian installation

Note: there is no installer as far as I know. You need to already have a working linux on your ?CuBox

# mkfs.ext3 /dev/sdb1
# mount /dev/sdb1 /mnt
# debootstrap --foreign --arch=armhf jessie /mnt/ http://ftp.debian.net/debian
# cp $BUILD/linux/arch/arm/boot/uImage /mnt/boot
# mkdir -p /mnt/lib/modules/4.5.0/
# cd /mnt/lib/modules/4.5.0/
# tar xvf $BUILD/linux/modules.tar
# cp $BUILD/boot.scr /mnt/
# umount /mnt

Boot your Cubox on you old system, and find a way to instert you new Micro SD on it (e.g. USB adapter). Then:

# mount /dev/mmcblk0p1 /mnt
# chroot /mnt
# /debootstrap/debootstrap --second-stage
# passwd
# echo $HOSTNAME > /etc/hostname
# echo 'T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100' >> /etc/inittab

You may also want to adapt your /etc/fstab and /etc/network/interfaces.

Then halt your cubox, remove the old system Micro SD and replace it by the new one and enjoy your new debian Jessie


?CategoryEmbeddedComputer