Arm Community
Arm Community
  • Site
  • User
  • Site
  • Search
  • User
  • Groups
    • Research Collaboration and Enablement
    • DesignStart
    • Education Hub
    • Innovation
    • Open Source Software and Platforms
  • Forums
    • AI and ML forum
    • Architectures and Processors forum
    • Arm Development Platforms forum
    • Arm Development Studio forum
    • Arm Virtual Hardware forum
    • Automotive forum
    • Compilers and Libraries forum
    • Graphics, Gaming, and VR forum
    • High Performance Computing (HPC) forum
    • Infrastructure Solutions forum
    • Internet of Things (IoT) forum
    • Keil forum
    • Morello Forum
    • Operating Systems forum
    • SoC Design and Simulation forum
    • 中文社区论区
  • Blogs
    • AI and ML blog
    • Announcements
    • Architectures and Processors blog
    • Automotive blog
    • Graphics, Gaming, and VR blog
    • High Performance Computing (HPC) blog
    • Infrastructure Solutions blog
    • Innovation blog
    • Internet of Things (IoT) blog
    • Operating Systems blog
    • Research Articles
    • SoC Design and Simulation blog
    • Smart Homes
    • Tools, Software and IDEs blog
    • Works on Arm blog
    • 中文社区博客
  • Support
    • Arm Support Services
    • Documentation
    • Downloads
    • Training
    • Arm Approved program
    • Arm Design Reviews
  • Community Help
  • More
  • Cancel
Open Source Software and Platforms
Open Source Software and Platforms
Wiki Run the Arm Platforms deliverables on TC2
  • Help
  • Jump...
  • Cancel
  • About this wiki
  • Supported platforms
  • Obtaining support
  • +Arm Reference Platforms deliverables
  • -A-class platforms
    • +Juno
    • +FVPs
    • +System Guidance for Infrastructure (SGI)
    • +System Guidance for Mobile (SGM)
    • Corstone-500
    • Cortex-A5 DesignStart
    • +Neoverse N1 SDP
    • Neoverse Reference Designs
    • -Legacy platforms
      • Armv7-A FVPs
      • -TC2
        • Run the Arm Platforms deliverables on TC2
  • +M-class platforms
  • +R-class platforms
  • +FPGA prototyping boards
  • +Open source software

Run the Arm Platforms deliverables on TC2

NOTICE: The Arm Reference Platforms are now hosted on this git repository.

The instructions on this page assume you have followed the instructions in the user guide to fetch, build, and package the deliverables for TC2.

 

Running the deliverables on TC2

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:

$ lsblk
$ sudo dd if=<workspace>/<filesystem>.img of=/dev/sdX bs=64M
$ sync

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:

  • 38400 baud
  • 8-bit word length
  • No parity
  • 1 stop bit
  • No flow control

Power on the board and (if prompted) press Enter to stop auto-boot. Enter the following commands on the TC2's boot monitor console:

Cmd> flash
Flash> eraseall
Flash> quit
Cmd> usb_on

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.

  • Share
  • History
  • More
  • Cancel
Related
Recommended