ARM Cross Compiler

To compile the Linux kernel for the GoFlex Home, you must first have an ARM cross compiler installed. I use gcc-4.7-arm-linux-gnueabi-base that comes with Ubuntu 13.04. To install the compiler run:

sudo apt-get install gcc-arm-linux-gnueabi

U-Boot mkimage

The bootloader used on the GoFlex Home is U-Boot. U-Boot has a special image format called uImage. It includes parameters such as descriptions, the machine/architecture type, compression type, load address, checksums etc. To make these images, you need to have a mkimage tool that comes part of the U-Boot distribution. Download U-Boot, make and install the U-Boot tools:

tar -xjf u-boot-latest.tar.bz2
cd into u-boot directory
make tools-only
sudo install tools/mkimage /usr/local/bin

Building the GoFlex Home Kernel

# wget
# tar -xJf linux-3.14.tar.xz
# cd linux-3.14

Make and run the configuration menu:

# make ARCH=arm kirkwood_defconfig
# make ARCH=arm menuconfig

Customise your kernel. I enable the following:

Device Drivers --> Memory Technology Devices (MTD) --> Enable UBI - Unsorted Block Images
File Systems --> Miscellaneous Filesystems --> UBIFS file system support
File Systems --> Miscellaneous Filesystems --> LZO compression support
File Systems --> Miscellaneous Filesystems --> ZLIB compression support

File Systems --> DOS/FAT/NT Filesystems --> NTFS file system support
File Systems --> DOS/FAT/NT Filesystems --> NTFS write support

Networking support -> Networking options --> The IPv6 protocol
Networking support -> Networking options --> Network packet filtering framework (Netfilter)

Device Drivers --> Block Devices --> RAM block device support (Reflashing)

Once you have finished configuring your kernel, save the config. Then build it:

# make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage dtbs -j4

Now build the modules and install them to a suitable path:

# make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules
# make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- INSTALL_MOD_PATH=/home/cpeacock/export/rootfs modules_install


To support your newer Linux Kernel with Device Tree Support, you must have an up-to-date u-Boot bootloader with Device Tree Support installed on your GoFlex Home.

Please see Upgrading uBoot with Device Tree Support for the Seagate GoFlex Home

TFTP Server

Rather than flashing your newly created kernel to find out it doesn't work or it is not quite configured correctly, a better way to load the kernel into RAM and boot it from there. U-Boot allows kernel images to be loaded via TFTP.

To speed up development, I create an 'export' directory. A TFTP server is then configured to use this directory as the TFTP root.

From the export directory, add symbolic links to the kernel images. This way, you can recompile the kernel and the new image is instantly available without having to move it.

# ln -s /path to linux/arch/arm/boot/uImage uImage-3.14
# ln -s /path to linux/arch/arm/boot/dts/kirkwood-goflexnet.dtb uImage-3.14.goflexnet.dtb

U-Boot tftpboot

To test your kernel, bring up a serial console to the Seagate GoFlex Home. First we will need to configure the IP addresses. The ipaddr variable contains the IP address for the GoFlex Home, while the serverip variable is the address of the TFTP server containing the kernel image.

setenv ipaddr
setenv serverip

These variables can be saved to non-volatile memory to speed up development.

Next load the kernel image and Device Tree BLOB into memory:

tftpboot 0x800000 uImage-3.14.goflexnet.dtb
tftpboot 0x810000 uImage-3.14

You will also require a root filesystem to do any serious testing. One option is to use the filesystem already in place (i.e. UBIFS on mtd2) as I have done below. However, it is unlikely to have your new kernel modules installed.

setenv bootargs console=ttyS0,115200 mtdparts=orion_nand:1m(uboot),6M(uImage),-(root) ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs

The preferred option is to export a root NFS filesystem with your newly installed kernel modules installed. This has the added advantage as you can compile userland binaries on your development box, install them to the NFS export and have instant access to them on your target system.

setenv bootargs console=ttyS0,115200 root=/dev/nfs rw nfsroot= ip=

Finally, you can boot the kernel from the memory:

bootm 0x810000 - 0x800000

Hopefully you should yield results similar to the following:

## Booting kernel from Legacy Image at 00810000 ...
   Image Name:   Linux-3.14.0
   Created:      2014-04-14   9:21:57 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3747576 Bytes = 3.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 00800000
   Booting using the fdt blob at 0x800000
   Loading Kernel Image ... OK
   Loading Device Tree to 07b1b000, end 07b20962 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 3.14.0 (root@ubuntu) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #1 PREEMPT Mon Apr 14 02:21:34 PDT 2014
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977

Saving Kernel to Flash

Once your new Linux kernel has been thoroughly tested, you may want to permanently save it to flash.

To flash the kernel:

setenv ipaddr
setenv serverip
tftp 0x6400000 uImage-3.14.goflexnet.dtb
tftp 0x6410000 uImage-3.14
nand erase 0x100000 0x400000
nand write.e 0x6400000 0x100000 0x400000

I've allocated the first 64Kbytes (0x10000) of the kernel space to the Flattened Device Tree blob.

I use the following environment variables to load the new flattened device tree kernel:

GoFlexHome> printenv
bootargs=console=ttyS0,115200 mtdparts=orion_nand:1m(uboot),6M(uImage),-(root) ubi.mtd=root root=ubi0:root rootfstype=ubifs ro
bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
bootcmd=${kernel}; setenv bootargs ${console} ${mtdparts} ${bootargs_root}; bootm 0x6410000 - 0x6400000;
kernel=nand read.e 0x6400000 0x100000 0x400000

Environment size: 592/131068 bytes