Arm Corstone-1000/Arm Corstone-1000-A320 Fixed Virtual Platform

Arm Corstone-1000 Fixed Virtual Platform

Overview

This board configuration uses the Arm Corstone-1000 Fixed Virtual Platform (FVP) to emulate an Arm Corstone-1000 reference design with Cortex-A320 or Cortex-A35 host as the processor.

The Corstone-1000 is an Arm reference design for secure IoT systems, featuring:

  • Host processor subsystem (Cortex-A320 or Cortex-A35)

  • Secure Enclave (Cortex-M0+) running TF-M

  • Ethos-U85 NPU (Neural Processing Unit) or External System (Cortex-M3) subsystem

  • CryptoCell-312 hardware accelerator

  • System-level security with MCUboot verified boot

Zephyr board options

Zephyr runs on the Cortex-A320 host processor of the Corstone-1000-A320 FVP.

The Cortex-A320 configuration provides support for:

  • Cortex-A320 CPU (Armv9.2-A architecture)

  • GICv3 interrupt controller (GIC-600)

  • Arm Generic Timer

  • PL011 UART controller

  • SVE2 (Scalable Vector Extension 2)

Boot Architecture:
  • The Cortex-A320 host uses a multi-stage boot process involving two processors:

    Secure Enclave (M0+):  BL1_1 -> BL1_2 -> BL2/MCUboot -> TF-M SPE -.
                                                                         |
    Host CPU (A320):                                TF-A BL2 -> BL31 -> Zephyr (BL33)
    

    Secure Enclave (Cortex-M0+):

    1. BL1_1 (ROM) — hardware init, key provisioning

    2. BL1_2 (OTP) — verified by BL1_1

    3. BL2 (MCUboot) — parses GPT, loads and ECDSA-verifies TF-M and TF-A images

    4. TF-M Runtime — initializes ITS/PS/Crypto partitions, powers on host CPU via DSU-120T PPU

    Host CPU (Cortex-A320):

    1. TF-A BL2 — loaded by MCUboot, parses FIP, loads BL31 and BL33

    2. TF-A BL31 — EL3 runtime (PSCI, GIC init), ERETs to NS-EL1

    3. BL33 (Zephyr) — non-secure application at EL1

    Note

    The FVP provisioning cycle requires two full SE boot iterations before the real boot. This is normal — the first boot provisions dummy keys and reboots.

    Note

    The Ethos-U85 NPU is present in the Corstone-1000-A320 FVP but is not currently supported by this board configuration.

Hardware

Supported Features

The fvp_corstone1000 board supports the hardware features listed below.

on-chip / on-board
Feature integrated in the SoC / present on the board.
2 / 2
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files.
vnd,foo
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.
fvp_corstone1000/a320 target

On-target memory for this board target: 2 GiB of RAM, N/A of Flash.

Type

Location

Description

Compatible

CPU

on-board

Arm Cortex-A320 CPU4

arm,cortex-a320

Clock control

on-board

Generic fixed-rate clock provider1

fixed-clock

Interrupt controller

on-board

ARM Generic Interrupt Controller v31

arm,gic-v3

Power management CPU operations

on-board

Power State Coordination Interface (PSCI) version 0.21

arm,psci-0.2

Serial controller

on-board

ARM PL011 UART1

arm,pl011

Timer

on-board

per-core ARM architected timer1

arm,armv8-timer

fvp_corstone1000/corstone1000/a35 target

On-target memory for this board target: 2 GiB of RAM, N/A of Flash.

Type

Location

Description

Compatible

CPU

on-board

Arm Cortex-A35 CPU1

arm,cortex-a35

Clock control

on-board

Generic fixed-rate clock provider2

fixed-clock

Interrupt controller

on-board

ARM Generic Interrupt Controller v21

arm,gic-v2

Power management CPU operations

on-board

Power State Coordination Interface (PSCI) version 0.21

arm,psci-0.2

Serial controller

on-board

ARM PL011 UART1

arm,pl011

Timer

on-board

per-core ARM architected timer1

arm,armv8-timer

fvp_corstone1000/corstone1000/extsys target

On-target memory for this board target: 32 KiB of RAM, 256 KiB of Flash.

Type

Location

Description

Compatible

CPU

on-board

ARM Cortex-M3 CPU1

arm,cortex-m3

Clock control

on-board

Generic fixed-rate clock provider2

fixed-clock

Counter

on-board

ARM CMSDK timer2

arm,cmsdk-timer

Interrupt controller

on-chip

ARMv7-M NVIC (Nested Vectored Interrupt Controller)1

arm,v7m-nvic

Serial controller

on-board

ARM PL011 UART1

arm,pl011

SRAM

on-board

Generic on-chip SRAM2

mmio-sram

Timer

on-chip

ARMv7-M System Tick1

arm,armv7m-systick

Watchdog

on-board

ARM CMSDK watchdog1

arm,cmsdk-watchdog

Board Variants

The following board targets are available:

  • fvp_corstone1000/a320 - single-core ARMv9.2-A with Cortex-A320 CPU

  • fvp_corstone1000/a320/smp - quad-core SMP with all 4 Cortex-A320 CPUs

  • fvp_corstone1000/corstone1000/a35 - single-core Armv8-A with Cortex-A35 CPU

  • fvp_corstone1000/corstone1000/extsys - Cortex-M3 External System

Programming and Debugging

Prerequisites

  1. Zephyr SDK (recommended) — provides both arm-zephyr-eabi for TF-M and the Cortex-M3 application, and aarch64-zephyr-elf for the Cortex-A35/Cortex-A320 applications and TF-A, plus dtc for TF-A device tree compilation.

  2. Install the FVP corresponding to the selected board target from Arm Ecosystem FVPs:

    • fvp_corstone1000/a320 and fvp_corstone1000/a320/smp require FVP_Corstone-1000-A320

    • fvp_corstone1000/corstone1000/a35 and fvp_corstone1000/corstone1000/extsys require FVP_Corstone-1000

    Set the ARMFVP_BIN_PATH environment variable to the directory containing the selected FVP binary. For the Cortex-A320 targets, for example:

    export ARMFVP_BIN_PATH=~/FVP_Corstone_1000-A320/models/Linux64_GCC-9.3
    

    For the Cortex-A35 and External System targets, point ARMFVP_BIN_PATH to the directory containing FVP_Corstone-1000 instead.

  3. All targets require sgdisk to create the GPT partition table. Install it from the gdisk package:

    # Fedora / RHEL
    sudo dnf install gdisk
    
    # Ubuntu / Debian
    sudo apt install gdisk
    

Building

The Cortex-A320, Cortex-A35, and External System targets require TF-M and TF-A modules with support for the selected Corstone-1000 variant. After cloning the repository, update the modules:

west update

All targets require Sysbuild (System build) to automatically build TF-M (Secure Enclave) and TF-A (Host firmware) alongside Zephyr.

For Cortex-A320:

west build -b fvp_corstone1000/a320 samples/hello_world --sysbuild

Use fvp_corstone1000/a320/smp to build for all four Cortex-A320 CPUs.

For Cortex-A35:

west build -b fvp_corstone1000/corstone1000/a35 samples/hello_world --sysbuild

For the Cortex-M3 External System:

west build -b fvp_corstone1000/corstone1000/extsys samples/hello_world --sysbuild

The selected application runs on the Cortex-M3. Sysbuild also builds samples/hello_world for fvp_corstone1000/corstone1000/a35 as the hello_world_a35 image, which TF-A uses as BL33. TF-M BL1 and TF-A BL2/BL31 are built alongside these applications to complete the platform boot flow.

Tip

To avoid passing --sysbuild every time, set it as the default:

west config build.sysbuild true

For all targets, the build creates the following files in build/firmware/:

  • bl1.bin — Secure Enclave ROM (BL1_1 + provisioning bundle)

  • cs1000.bin — 32 MB GPT flash image containing signed TF-M, signed TF-A BL2, BL31, and Zephyr in a FIP

The Hello World build for the External System also produces:

  • build/hello_world/zephyr/zephyr.bin — Cortex-M3 application loaded by the FVP External System flash loader.

  • build/hello_world_a35/zephyr/zephyr.bin — Cortex-A35 Hello World application packaged as BL33 in build/firmware/cs1000.bin

Running

After building any target, start its corresponding FVP with:

west build -t run

To set a simulated time limit or other FVP options, set ARMFVP_EXTRA_FLAGS at configure time:

ARMFVP_EXTRA_FLAGS="--simlimit 120" west build -b fvp_corstone1000/a320 \
    samples/hello_world --sysbuild
west build -t run

Expected output after the platform provisioning cycle:

*** Booting Zephyr OS build v4.3.0-... ***
Hello World! fvp_corstone1000/<a320,a320/smp,corstone1000/a35,corstone1000/extsys>

Debugging

Refer to the detailed overview about Application Debugging.

The FVP supports connection via Arm Development Studio or other debuggers using the Iris debug interface.

Tip

For early boot debugging before the UART is available, semihosting can be used by enabling CONFIG_SEMIHOST and CONFIG_SEMIHOST_CONSOLE, and disabling CONFIG_UART_CONSOLE. The FVP has semihosting enabled by default.

Known Limitations

  • Linux/Unix host only - the sysbuild integration uses POSIX shell utilities (sh, dd, sgdisk) to assemble the Secure Enclave flash image and is not currently supported on Windows hosts.

  • Ethos-U85 NPU — the NPU is present in the Corstone-1000-A320 FVP model but is not currently supported by Zephyr.

  • mmap overlap warning — mmap_add_region_check() failed. error -22 appears in TF-A BL2/BL31. This is a non-fatal Ethos-U85 memory map overlap in release mode, also present in the Yocto reference build.

References