You are currently reviewing an older revision of this page.
Welcome to the Arm Development Platforms Community wiki and thank you for purchasing a TC2 board.
We recommend all new users install the latest Linaro software deliverables on their board, which will give you a full software stack including board firmware and either an EDK2-based UEFI environment or a Linux kernel plus filesystem booted via a boot monitor wrapper.
Please follow the instructions below to install the latest deliverables.
The TC2 platform is deprecated and no longer available. However, current Linaro releases continue to update the associated software components.
The current Linaro release is 17.10; see here for release notes and binary artefact direct download links.
The Arm software images contained in this release are distributed according to the EULA.
This software release offers a number variety of software stacks:
This document describes how to:
For any problems with your TC2 please contact firstname.lastname@example.org.
These instructions assume your host PC is running Ubuntu Linux 16.04.1 LTS.Windows users may also follow these instructions but will only be able to use prebuilt configurations.
A number of prerequisite packages will need to be installed. The workspace initialization script will automatically detect and list any missing prerequisite packages.
If building from source you will need to configure git's `user.name' and `user.email' attributes:
$ git config --global user.name "John Doe"
$ git config --global user.email "email@example.com"
Create and enter a new directory that will be your workspace. The path to this directory will be referred to as `<workspace>' in these instructions.
Next download the workspace initialisation script to your workspace and run it:
$ python3 workspace_1710.py
The script will guide you through the process of initialising your workspace, automatically downloading all relevant source files and required binaries.
You can skip this section if you chose to use a prebuilt configuration when running the script.
To clean, build, and package the software:
$ ./build-scripts/build-all.sh all
You can also individually perform each of these steps:
$ ./build-scripts/build-all.sh clean
$ ./build-scripts/build-all.sh build
$ ./build-scripts/build-all.sh package
You can invoke a particular component's build script in the same way in order to build just that component rather than the whole software stack, for example `./build-scripts/build-linux.sh' targets just the Linux kernel.
If you chose to use Android or one of the OpenEmbedded filesystems, the workspace initialisation script will have placed the filesystem image in the root of `<workspace>'. You will need to write this image to a USB stick with a minimum capacity of 4GB.
Linux users can do this like so:
$ sudo dd if=<workspace>/<filesystem>.img of=/dev/sdX bs=64M
Note: Replace `/dev/sdX' with the handle corresponding to your USB stick as identified by the `lsblk' command.
Next connect both a serial cable and a USB-B cable between your host PC and the TC2 board (the top-right UART port on the back of the board), then configure a serial monitor such as `PuTTy' or `minicom' with the following settings:
Power on the board and (if prompted) press Enter to stop auto-boot. Enter the following commands on the TC2's boot monitor console:
This will delete any binaries and UEFI settings currently stored in the TC2's Flash, then mount the TC2's MMC card as an external storage device on your host PC.
From your host PC, delete all files on your TC2's mounted MMC card.
Next copy the contents of `<workspace>/vexpress-firmware/' directory onto the TC2's mounted MMC card.
Next, navigate to the subdirectory in `<workspace>/output/' corresponding to your chosen configuration.
For example for an EDK2-based UEFI environment this will be `<workspace>/output/tc2/tc2-uefi/' whereas for an Android environment it will be `<workspace>/output/tc2/tc2-android/bootmon/'.
Copy all files from that folder into the `/SOFTWARE/' folder on your TC2's mounted MMC card, overwriting any duplicate files.
Be sure to issue a `sync' command on your host PC which will guarantee that the copy has completed.
If you chose to use an Android or OpenEmbedded filesystem, insert the USB stick created above into one of the TC2's rear USB ports (not needed for BusyBox or if booting into an EDK2-based UEFI environment).
Next ensure that the left dip-switch (closest to the black RESET button and USB-B port) is in the DOWN position.
Finally, power cycle the TC2. After it has finished copying the contents of the MMC card into Flash, the board will boot up and run the new software images
If booting a Linux kernel you should eventually reach a prompt, at which point can start using the system.