System Manager Application

Description

The System Manager application demonstrates platform initialization and boot flow management on the supported boards for this application. It performs comprehensive system management including core service initialization, boot source detection, and boot path routing to ensure reliable system startup and operation.

The sample includes multiple system management operations:

• Platform initialization: Initialize core platform services including UART, timer, XSPI, and logger.

• Boot source detection: Detect and identify the current boot source (XSPI, eMMC, or USB).

• Boot path routing: Route boot handling to appropriate boot paths based on detected source.

• A55 handoff preparation: Prepare the system for A55 boot handoff with proper configuration.

• USB boot services: Support USB boot operations including eMMC flashing and A-core image execution.

• System manager task: Create and manage system manager task for runtime operations.

• Runtime logging: Provide comprehensive logs for bring-up verification and debugging.

During each run, the app logs initialization status, boot source detection results, boot flow decisions, and handoff preparation status. This makes it easy for end users to confirm that system management operations are working as expected.

The latest example structure uses a common application source tree with board-specific hardware setup kept under hw/<BOARD>/. For this app:

• Common application sources such as main.c and boot-related files stay in the app root.

• Application defconfigs are stored under configs/.

• Board and hardware-specific setup is selected from hw/<BOARD>/, for example hw/SL2610_RDK/.

The application can also be exported and built as a standalone app repository. In that flow, keep this app in its own directory, point SRSDK_DIR to the SDK root, and build from the app directory itself. For the full application workflow model, see Astra MCU SDK User Guide.

Supported Boards

This application supports:

• SL2610_RDK

Select the defconfig that matches your target board, and the build system will pick the corresponding board-specific hardware setup from hw/<BOARD>/.

Prerequisites

• Choose one setup path:

  • CLI: Setup and Install SDK using CLI

  • VS Code: Setup and Install SDK using VS Code

Test Case Selection

Before building, choose the testcase defconfig that matches your target board.

You can:

• Select the required defconfig directly from the application’s configs/ directory.

• Run make list_defconfigs from the application directory to list all supported defconfigs.

Available defconfigs:

• sl2610_rdk_system_manager_ddr3_defconfig

• sl2610_rdk_system_manager_ddr4_1x16_defconfig

• sl2610_rdk_system_manager_defconfig

• sl2610_rdk_system_manager_lpddr4_defconfig

For this app, the default defconfig is:

• sl2610_rdk_system_manager_defconfig

Building and Flashing the Example using VS Code and CLI

Use the VS Code flow described in the SL2610 guides and VS Code Extension guide:

• SL2610 Platform Guide

• Astra MCU SDK VS Code Extension User Guide

Build (VS Code):

1. Open Build and Deploy -> Build Configurations.

2. Select one system manager project configuration in the Project Configuration dropdown:

   • sl2610_rdk_system_manager

   • sl2610_rdk_system_manager_ddr3

   • sl2610_rdk_system_manager_lpddr4

   • sl2610_rdk_system_manager_ddr4_1x16

3. Build with Build (SDK+Project) for the first build, or Build (Project) for rebuilds.

Build (CLI):

1. Build from the application directory itself:

   cd <sdk-root>/examples/system_manager
   export SRSDK_DIR=<sdk-root>
   make <app_defconfig> BUILD=SRSDK
   

2. For faster rebuilds when only app code changes, reuse the app-local installed SDK package:

   cd <sdk-root>/examples/system_manager
   export SRSDK_DIR=<sdk-root>
   make build
   

3. If this app has been exported to its own repository, use the same commands from that exported app directory after setting SRSDK_DIR to the SDK root.

Build outputs (CLI):

• Application binary: <app-dir>/out/<target>/release/<target>.elf

• App-local SDK package: <app-dir>/install/<BOARD>/<BUILD_TYPE>/

Flash/Image Generation (VS Code):

1. Build the SL2610 bootloader image and generate the required output binaries.

2. Use the SL2610 image-generation flow in the VS Code extension to create the required sub-image.

3. Open Image Flashing (SL2610).

4. Select Flash Target as M52 Image.

5. In Image Path, browse to and select the generated sub-image file, such as sysmgr.subimg.gz.

6. Start the flashing operation to program the image to the target.

Flash/Image Generation (CLI):

Note: SL2610 image generation is not supported on native Windows. Use WSL for image generation. In WSL, ensure required tools are installed: Python, make, and Arm GNU toolchain. You can use the VS Code extension’s Tools Installer in WSL, or follow Linux Environment guide for CLI setup.

1. Build the SL2610 bootloader from SDK root:

   make sl2610_bootloader_rdk_defconfig BOARD=SL2610_RDK
   make
   

2. Generate binaries:

   cd <sdk-root>/examples/system_manager
   export SRSDK_DIR=<sdk-root>
   make imagegen
   

3. Copy generated binaries to VSSDK:

   • sl2610_bootloader_extras.bin

   • sl2610_bootloader_output.bin

   • sl2610_cm52_fw_extras.bin

   • sl2610_cm52_fw_output.bin

4. Generate system sub-image in VSSDK.

   • Refer: SL2610 Platform Guide - Image Generation

5. Flash/download image to target.

   • Refer: SL2610 Platform Guide - Image Flashing

---

Running the Application using VS Code Extension

1. Power the board and press RESET after flashing.

2. For logging output, click SERIAL MONITOR and connect to the DAP logger port on J14.

   • To make it easier to identify, ensure only J14 is plugged in (not J13).

   • The logger port is not guaranteed to be consistent across OSes. As a starting point:

     • Windows: try the lower-numbered J14 COM port first.

     • Linux/macOS: try the higher-numbered J14 port first.

   • If you do not see logs after a reset, switch to the other J14 port.

3. System manager logs appear in the logger window.

Expected Logs

before lock sts: 0x20

 LCS OTP: 0xaead0303
after lock sts: 0x21

synaprot a0 spk: release id 0xfc9b8b5, commit time Mon Oct 13 19:27:42 2025 -0700
synaprot a0 hal : release id 0xf24e4cf, commit time Mon Oct 13 01:32:40 2025 -0700
Cold Boot...
speed_up clock_freq...
conf flightcontrol...
fc: reset0_faultasso0_FAULT: 0xf80000f8
fc: reset0_faultasso1_FAULT: 0xe0000007
Waiting command...
read msg data is 0x5b
read msg data is 0x5a
read msg data is 0x33
read msg data is 0x4
read msg data is 0xd4
read msg data is 0x33
read msg data is 0x1
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
read msg data is 0x0
download bl image

u32_num_bytes is 0x133d4, img_dwnld_addr=0x30002000
opcode download bl image
verify bl
image_buf: 0x30002000
bl header type: 0x00000011
image dest addr: 0x30020000, body_size: 0x00013160
clear BL !
save m52 entry: 0x30020000
save magic: 0x574d424c

 send rx msg: 0x5b 0x5a 0x33 0x4 0x0 0x0 0x0 0x0
relocate vector table...
Vector table is 128-byte aligned.
release M52...
BL: MCU Init...command...
Init DDR4 @ 3200
DHL:v0p40 PT:v0p40 ID:0x21010000
USB MOUNTED
0000000000:[0][WRN][LOGR]:Changing logger interface to LOGGER_IF_UART_0
0000000000:[0][INF][SYS ]:------------------------------------------
0000000000:[0][INF][SYS ]:            Hello  ASTRA
0000000000:[0][INF][SYS ]:------------------------------------------
0000000000:[0][INF][SYS ]:System initialization done
0000000000:[0][INF][SYS ]:M52:: Build Date 19-01-2026 Time 15:57:15 Commit unknown
0000000000:[0][INF][SYS ]:sl2610 SDK version 1.3.0
0000000000:[0][INF][USB ]:USB device unmounted
0000000004:[0][INF][HAPI]:Active interface is USB
0000000110:[0][INF][SYS ]:VCORE 800 mV
0000000322:[0][INF][USB ]:USB device mounted
0000001928:[0][INF][HAPI]:Requested Service ID: 13 and Opcode: 15
0000002055:[0][INF][HAPI]:Requested Service ID: 13 and Opcode: 15
0000002158:[0][INF][HAPI]:Requested Service ID: 13 and Opcode: 18
0000002196:[0][INF][HAPI]:Requested Service ID: 13 and Opcode: 15
0000002297:[0][INF][HAPI]:Requested Service ID: 13 and Opcode: 15
0000002407:[0][INF][HAPI]:Requested Service ID: 13 and Opcode: 15
0000000000:[0][WRN][LOGR]:Changing logger interface to LOGGER_IF_UART_0
0000000000:[0][INF][SYS ]:M52:: Build Date 22-01-2026 Time 18:02:38 Commit unknown
0000000000:[0][INF][SYS ]:sl2610 SDK version 1.3.0
0000000102:[0][INF][SYS ]:VCORE 800 mV
0000000106:[0][INF][SYS ]:eMMC: Boot A55
0000000176:[0][INF][SYS ]:Loading bl_a
0000000269:[0][INF][SYS ]:Loading tzk_a
NOTICE:  BL31: v2.7(release):v2.7.0-18-g483e9cedcf-dirty
NOTICE:  BL31: Built : 15:02:46, Jun  1 2022

After the above sequence, the System Manager hands off control and boots the A-core (A55).