Version 46 (modified by Ryan Erbstoesser, 17 months ago) ( diff )

update openwrt

Newport Board Support Package (BSP)

Gateworks provides a Board Support Package for Newport which provides source code and an easy mechanism to build different images, including Ubuntu and OpenWrt.

Gateworks uses the term 'BSP' to describe one 'image' file, that contains everything, including all boot firmware, operating system (rootfs and kernel).

The Gateworks BSP is the easiest comprehensive software process because it contains everything. If a deep dive, expert path is desired, each piece of the BSP (boot firmware, rootfs, kernel) can all be built separately.

BSP Pre-Built Firmware Images

Pre-built firmware images can be found on

A sampling includes:

  • Entire Board Software (recommended), including boot firmware, bootloader, OS, kernel, etc:
    • Newport Images - Compressed Disk Image containing Firmware and kernel and OS ( .img.gz files )
      • Ubuntu version details are available here
      • OpenWrt
  • Newport GSC
  • Only Boot Firmware
  • Only Newport Kernel

Installation instructions are at the following URL: Newport Flashing Instructions

BSP Source Code

Newport Source code for the firmware, bootloader and kernel are hosted at GitHub. We highly recommend you create a GitHub account and 'Watch' these repositories to keep abreast of important feature additions, bugfixes, and firmware-releases. You can configure your GitHub account to e-mail you when changes are made to repositories here.

The following GitHub repos are used for Newport:

Building the BSP from source

Below are instructions for building the entire BSP, which includes all of the bootloader components and Linux kernel and Ubuntu or OpenWrt. Pre-built images are available above.

The Gateworks Venice Board Support Package uses the Google git-repo tool to manage multiple code repositories.

The following pre-requisites are needed to build the Newport BSP:

  • Linux Development host (desktop or laptop computer) (Ubuntu 16.04 is used by Gateworks and tested)
  • Python 2.x (required by the 'repo' tool and imaging tools)
  • Git (used for source code repositories)
  • repo (used to manage multiple git repos)
  • libssl-dev (used for signing images)

NOTE: Building images requires root privileges

Installing pre-requisites:

# install packages
sudo apt-get install build-essential git python2 python3 python-is-python3 python3-setuptools python3-distutils python3-dev swig libssl-dev ncurses-dev kmod bison flex device-tree-compiler wget cpio unzip rsync bc fdisk file -y
# configure git
git config --global ""
git config --global "Your Name"
git config --global color.ui true

Install the latest version of repo (Do not rely on Ubuntu apt package being up to date):

sudo wget -O /usr/local/bin/repo
sudo chmod a+rx /usr/local/bin/repo

To obtain the code:

  1. Initialize repo (fetch the repo manifest)
    mkdir $HOME/newport
    cd $HOME/newport
    repo init -u
  2. Sync repositories (repeat this when you want to fetch the latest code updates)
    repo sync --fail-fast -v
    • This will fetch/update the source repos described above. The first time it can take several minutes depending on your Internet connection and will take approximately ~2.5GB of disk space
  3. Setup build environment (*repeat this each time you open shell*)
    source newport/setup-environment
  4. Build the BDK (this only needs to be done once).
    make bdk
  5. Build desired software target as defined below. For example:
    make -j8 ubuntu-image

The build targets supported by the Newport BSP include:

  • ubuntu-image - builds ubuntu-newport.img.gz: A Compressed Disk Image which includes the 16MB Boot Firmware (BDK/ATF/U-Boot and Device-Tree images) as well as the Kernel and Ubuntu root filesystem.
  • openwrt-image - build openwrt from the git repo, using instructions here: OpenWrt/building
  • firmware-image - builds 'firmware-newport.img': 16MB Boot Firmware which includes the BDK/ATF/U-Boot and Device-Tree images - (takes about 2 mins on a modern development system).
  • kernel_image - builds linux-newport.tar.xz - A compressed tarball of the kernel (boot/Image) and kernel modules (lib/modules/*) which can be used on top of any compatible root filesystem

General installation instructions:

Working with the repo tool

The repo tool unifies Git repositories into a single project by specifying Git repos and directories they exist in. The tool was created for the Android project as Android is comprised of hundreds of repos however it has since been used by many projects that benefit from its git repo management tool.


Updating to the latest code

When working with the repo tool you can update to the latest code using the repo sync command:

$ repo sync
Fetching: 100% (8/8), done in 5.258s
Garbage collecting: 100% (8/8), done in 0.188s
repo sync has finished successfully.

The repo tool works off of a manifest file in .repo/manifests/default.xml which specifies the various projects, what repo they are in, and where they are checked out in your directory structure. If a branch has changed, a project added, or a project removed the manifest file will be updated when you run repo sync then it will update the various project repos. If a branch has changed to something new you can encounter an error such as:

$ repo sync
remote: Enumerating objects: 5, done.
remote: Counting objects: 100% (5/5), done.
remote: Compressing objects: 100% (1/1), done.
remote: Total 3 (delta 1), reused 3 (delta 1), pack-reused 0
Unpacking objects: 100% (3/3), done.
project .repo/manifests/
Updating 5c981dac1797..0b0055e7445e

error: in `sync`: revision v5.10.76-venice in Gateworks/linux-venice not found

This specific error is saying that the 'v5.10.76-venice' revision (or branch) is not in the current working copy of the repo. To resolve this you need to do a git remote update for that project. You can also use repo foreach to update all projects:

repo forall -c git remote update # update all projects
git -C linux remote update # update just the project in the linux path

Showing diffs for all projects (repo diff)

You can show all the diffs for each project using repo diff

Using the latest version

The repo tool is updated frequently. While it is rarely necessary to have the latest version it will inform you if there is an update and how to install that update in the current working directory:

$ repo sync

... A new version of repo (2.17) is available.
... You should upgrade soon:
    cp /usr/src/venice/bsp/.repo/repo/repo /home/user/bin/repo

To update the repo tool just copy the file as mentioned above:

cp .repo/repo/repo $HOME/bin/repo

Modifying the stand-alone Linux Kernel (ie for Ubuntu)

The Gateworks Newport BSP instructions above create an environment for building the Linux kernel among other targets.

Some additional instructions for common actions (make sure you have already installed the BSP and setup your shell environment as specified above):

  • Make standard Gateworks Newport kernel with Gateworks newport_defconfig
    make linux # first build the kernel with the standard newport_defconfig
  • Modify Kernel configuration (enabling modules etc):
    make -C linux menuconfig # make your changes
    make -C linux savedefconfig # once satisfied create a defconfig
    cp linux/defconfig linux/arch/arm64/configs/newport_defconfig # and copy it to the newport_defconfig
  • Build kernel tarball:
    make kernel_image # builds the kernel and modules and tarball
  • Build new disk image using the updated kernel tarball:
    make ubuntu-image

Modifying OpenWrt (toolchain, apps, kernel, filesystem)

The OpenWrt build system includes building its own toolchain and kernel (so the kernel and toolchain directories in the bsp directory are not used)

Modifying OpenWrt toolchain, installed applications, and general configuration:

make -C openwrt menuconfig # configure toolchain, installed applications and general configuration
  • this results in a custom .config file in the openwrt directory which you may want to save away

Modifying OpenWrt kernel:

make -C openwrt kernel_menuconfig
  • this results in modifying target/linux/octeontx/config-* in the openwrt directory which you may want to save away
  • Note that some kernel configurations get over-written by OpenWrt despite what you may select here

Build/rebuild OpenWrt (with your customizations):

make openwrt
  • results in build artifacts in {{openwrt/bin/targets/octeontx/generic/}}} including rootfs tarball, linux kernel, and squashfs filesystem

If you would like to change the filesystem size for the image being created you will need to edit

The path to this configuration script is established here:


Marvell toolchain

The Newport BSP uses a Marvell toolchain to build the kernel and boot firmware based on gcc v7.3.0.

The specific details can be shown by running 'gcc -v' for example:

user@host:/usr/src/newport/bsp$ . ./setup-environment # configure PATH and CROSS_COMPILER env vars
user@host:/usr/src/newport/bsp$ ${CROSS_COMPILE}gcc -v
Using built-in specs.
Target: aarch64-marvell-linux-gnu
Configured with: /home/jenkins/workspace/BuildToolchainAARCH64_Marvell7/toolchain/scripts/../src/configure --disable-fixed-point --without-ppl --without-python --disable-werror --enable-plugins --with-lto-plugin-source=/home/jenkins/workspace/BuildToolchainAARCH64_Marvell7/toolchain/scripts/../gits/gcc/lto-plugin --with-system-zlib --enable-initfini-array --with-sysroot --with-local-prefix=/home/jenkins/workspace/BuildToolchainAARCH64_Marvell7/toolchain/scripts/../marvell-tools/aarch64-marvell-linux-gnu/sys-root --disable-sim --enable-symvers=gnu --enable-__cxa_atexit --enable-symvers=gnu --enable-__cxa_atexit --disable-sim --with-multilib-list=lp64,ilp32 --enable-gnu-indirect-function --target=aarch64-marvell-linux-gnu --enable-languages=c,c++,fortran --prefix=/home/jenkins/workspace/BuildToolchainAARCH64_Marvell7/toolchain/scripts/../marvell-tools --with-pkgversion='Marvell Inc. Version: Marvell GCC7 build 238.0' --with-bugurl= --with-libexpat-prefix=/home/jenkins/workspace/BuildToolchainAARCH64_Marvell7/toolchain/scripts/../libs
Thread model: posix
gcc version 7.3.0 (Marvell Inc. Version: Marvell GCC7 build 238.0) 

The buildroot based toolchain is used by virtue of sourcing the setup-environment file which adds to your PATH and sets the CROSS_COMPILE variable.

Cross compile examples

Examples of cross-compiling using the buildroot toolchain

  • ANSI-C hello world:
    cat << EOF > helloworld.c
    #include <stdio.h>
    #include <stdlib.h>
    int main(int argc, char **argv)
            printf("hello world!\n");
            return 0;
    . ./setup-environment # setup environment for buildroot toolchain
    ${CROSS_COMPILE}gcc helloworld.c -o helloworld
  • C++ hello world:
    cat << EOF > helloworld.cpp
    #include <iostream>
    using namespace std;
    int main() {
            cout << "Hello World!";
            return 0;
    . ./setup-environment # setup environment for buildroot toolchain
    ${CROSS_COMPILE}gcc helloworld.cpp -lstdc++ -o helloworld
  • kernel module:
    . ./setup-environment # setup environment for buildroot toolchain
    make kernel_image # first build the kernel
    make -C linux M=$PWD/my-module modules
    • Note that some out-of-tree kernel modules do not follow the suggested Makefile standards and may need to be modified to use the CROSS_COMPILE prefix and/or specify the kernel directory (as opposed to the above example where you do a make in the linux dir and set M to the path of your module)
Note: See TracWiki for help on using the wiki.