Debug Arm Zena CSS Reference Software Stack with Arm Development Studio
Introduction
Getting started
Launch the FVP
Configure the model
Create debug connections
Debug RSE from reset
Debug Safety Island code
Debug primary compute and Linux
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  1 hr
Last updated:  26 Jun 2026
Skill level:
  Introductory
Reading time:
  1 hr
Last updated:
  26 Jun 2026
Author:Ronan Synnott, Arm
Arm IP:Cortex-A Cortex-R
Tags: Performance and Architecture Linux Arm Development Studio Arm Zena CSS FVP
Author:
  • Ronan Synnott, Arm
Arm IP:
Cortex-A Cortex-R
Tags:
Performance and Architecture Linux Arm Development Studio Arm Zena CSS FVP

Who is this for?

This introductory topic is for software developers who want to use Arm Development Studio to explore and debug the Arm Zena Compute Subsystem (CSS) Reference Software Stack on a Fixed Virtual Platform (FVP).

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Set up and save a debug configuration for the Arm Zena CSS FVP
  • Start Runtime Security Engine (RSE) debug at reset and step through early boot
  • Attach to and debug Safety Island (SI) firmware
  • Attach to the Linux kernel on the primary compute cores and debug user space processes

Prerequisites

Before starting, you will need the following:

  • Ubuntu 22.04 host machine
  • Arm Development Studio 2024.1 or later with a valid license - for support see the Install Guide for Arm DS
  • Basic understanding of the Arm Zena CSS software stack, Armv8-A/Armv9-A cores, and Linux

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll debug the Arm Zena Compute Subsystem (CSS) reference software stack on a Fixed Virtual Platform using Arm Development Studio. First, you’ll launch the FVP with the Iris debug server enabled, then create and save a custom Arm DS configuration. You’ll establish connections to each heterogeneous component within Zena CSS to debug the Linux kernel and user processes. By the end, you’ll create reusable .launch files, step through early RSE boot, and attach to Safety Island and Linux targets to inspect execution across the system.

Frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
Which FVP launch method should I use for debugging?
Use the launch invocation that enables the Iris debug server. The default build-environment command runs the stack but does not enable Iris, so Arm Development Studio cannot connect.
How should I organize and save my debug connections in Arm Development Studio?
Create a General Project to store the connection files and save each connection as a .launch file. This makes it easy to reuse and enhance configurations for each subsystem.
What is the expected workflow to debug the RSE from reset?
Start the FVP with Iris enabled and hold the model at reset, then connect from Arm Development Studio. Load Trusted Firmware‑M symbols and step through the early boot code.
Can I connect to all Zena CSS processors at the same time?
Yes. Arm Development Studio supports heterogeneous systems, so you can connect to the RSE, Safety Island, and primary compute cores simultaneously, though you might prefer to set up one connection fully before adding others.
Why isn’t there a predefined Zena CSS target in Arm Development Studio?
As of Arm Development Studio 2025.0, there is no out-of-the-box configuration for the Zena CSS FVP. Create one using the Iris interface as shown in the Learning Path.
Next