Skip to main content

Build Marvell ARMv5 toolchain with Crosstool-NG

Notes: under Ubuntu 16.04

 

0. Prepeare - install required tools



1. Install crosstool-ng

# mkdir -p scratch/ct-ng; cd scratch/ct-ng

# wget http://crosstool-ng.org/download/crosstool-ng/crosstool-ng-1.18.0.tar.bz2

# tar xf crosstool-ng-1.18.0.tar.bz2

# cd crosstool-ng-1.18.0

# ./configure --prefix=`pwd`/crosstool

# make && make install

# export PATH="${PATH}:`pwd`/crosstool/bin"

# ct-ng help

This is crosstool-NG version 1.18.0



2. Configure marvell ARMv5 toolchain


# mkdir -p ~/scratch/marvell; cd ~/scratch/marvell

# ct-ng list-samples

 [G.X]   arm-cortex_a15-linux-gnueabi
 [G..]   arm-cortex_a8-linux-gnueabi
 [G..]   arm-davinci-linux-gnueabi
 [G..]   arm-unknown-eabi
 [G..]   arm-unknown-linux-gnueabi
 [G.X]   arm-unknown-linux-uclibcgnueabi
 [G..]   x86_64-unknown-linux-gnu
 [G..]   x86_64-unknown-linux-uclibc
 [G.X]   x86_64-unknown-mingw32


# ct-ng show-arm-unknown-linux-gnueabi


    OS             : linux-3.7.3
    Companion libs : gmp-4.3.2 mpfr-2.4.2 libelf-0.8.13
    binutils       : binutils-2.19.1a
    C compiler     : gcc-4.3.2 (C,C++,Fortran,Java)
    C library      : glibc-2.9 (threads: nptl)
    Tools          : dmalloc-5.5.2 duma-2_5_15 gdb-6.8a ltrace-0.5.3 strace-4.5.19


# ct-ng arm-unknown-linux-gnueabi


 ***********************************************************
 Initially reported by: Alexander BIGGA
 URL: http://sourceware.org/ml/crossgcc/2008-06/msg00031.html
 ***********************************************************

 Now configured for "arm-unknown-linux-gnueabi"

# mkdir ~/scratch/src

# mkdir ~/scratch/x-tools

# ct-ng menuconfig

  Paths and misc options -- Local tarballs directory: ${HOME}/scratch/src
  Paths and misc options -- Prefix directory: ${HOME}/scratch/x-tools
  Target options -> Architecture level -> armv5te  # marvell 88F6282


  * Need also to update Kernel and GCC version according to target board


3. Build

# ct-ng builld

....................


 And after build completes, toolchain will be installed in ${HOME}/scratch/x-tools



Reference:
* http://shyuanliang.blogspot.ca/2013/08/crosstool-ng-toolchain.html

Popular posts from this blog

Installing Debian on QNAP HS-210, TS-21x and TS-22x devices

QNAP's original firmware has a lot of bloatware. If you want to has a lean NAS with more choices and controls on what are running inside the box, here is a webpage to install Debian, my favorite distro, into TS-212p. [https://www.cyrius.com/debian/kirkwood/qnap/ts-219/install/] Overview In a nutshell, the installation of Debian on your QNAP HS-210, TS-21x or TS-22x works like this: you use the QNAP firmware to write a Debian installer image to flash. When you restart your device, Debian installer starts and allows you to login via SSH to perform the installation. Debian will be installed to disk and a Debian kernel will be put in flash that will start Debian from disk. If you follow this procedure, Debian 9 (stretch) will be installed to your SATA disk and the QNAP firmware on disk and in flash will be replaced with Debian. Debian does not install a web interface to configure your machine, although it's possible to install such software. If this is not what you want, pleas...

Recovery mode of QNAP HS-210, TS-21x and TS-22x devices

If, somehow, hard drive becomes unreadable, use the method below to restore installation[ https://www.cyrius.com/debian/kirkwood/qnap/ts-219/recovery/] Recovery mode of QNAP HS-210, TS-21x and TS-22x devices QNAP HS-210, TS-21x and TS-22x devices have a recovery mode that can be used when there is a problem with your installation of Debian that renders your device unbootable. The system recovery mode allows you write a recovery image to flash via the network using the TFTP protocol. This pages describes how how to create recovery images and how to use the recovery mode. As an alternative to the instructions on this page, you can use a  Live CD provided by QNAP . Creating recovery images In order to create a recovery image for your QNAP TS-21x/TS-22x, you have to take an exact copy of your flash memory. That is, the recovery image consists of the following parts of your flash in this order:  mtd0 ,  mtd4 ,  mtd5 ,  mtd1 ,  mtd2 ,  mtd3 . ...