Sample Demo Application

Description

The Sample Demo application is a FreeRTOS task-creation and scheduling reference for SR110.

This app initializes platform services, creates an application task, and then creates two static demo tasks (vTaskDemo1 and vTaskDemo2). The two tasks run continuously and print periodic logger messages at different intervals.

What this sample demonstrates:

Static task creation using xTaskCreateStatic
Task priority/stack configuration for user tasks
Periodic task execution with vTaskDelay
Basic logger output from multiple concurrent tasks

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, sample_demo_app.c, and sample_demo_app.h stay in the app root.
Application defconfigs are stored under configs/.
Board and hardware-specific setup is selected from hw/<BOARD>/, for example hw/SR110_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:

SR110_RDK

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

Hardware Requirements

Astra Machina Micro Kit (SR110)
USB cable for flashing and logging

Prerequisites

Choose one setup path:
- CLI: Setup and Install SDK using CLI
- VS Code: Setup and Install SDK using VS Code

Optional Configuration

You can tune demo behavior in sample_demo_app.c:

IDLE_TASK_DEMO1_DELAY_MS (default 500 ms)
IDLE_TASK_DEMO2_DELAY_MS (default 1000 ms)
SAMPLE_APP_TASK_PRIORITY
SAMPLE_APP_STACK_DEPTH

Test Case Selection

Before building, choose the testcase defconfig that matches both your target board and the transfer mode you want to validate.

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:

sr110_rdk_cm55_demo_sample_app_defconfig

Building and Flashing the Example using VS Code and CLI

Use the VS Code flow described in the SR110 guide and the VS Code Extension guide:

Build (VS Code):

Open Build and Deploy -> Build Configurations.
Select the sample_demo_app project configuration in the Project Configuration dropdown.
Build with Build (SDK+Project) for the first build, or Build (Project) for rebuilds.

Build (CLI):

Build from the application directory itself:

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

For faster rebuilds when only app code changes, reuse the app-local installed SDK package:
```
cd <sdk-root>/examples/sample_demo_app
export SRSDK_DIR=<sdk-root>
make build
```
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 (CLI):

Activate the SDK venv (required for image generation tools):

# Linux/macOS
source <sdk-root>/.venv/bin/activate
# Windows PowerShell
.\.venv\Scripts\Activate.ps1

Generate the flash image:

cd <sdk-root>/tools/srsdk_image_generator
python srsdk_image_generator.py \
  -B0 \
  -flash_image \
  -sdk_secured \
  -spk "<sdk-root>/tools/srsdk_image_generator/Inputs/spk_rc4_1_0_secure_otpk.bin" \
  -apbl "<sdk-root>/tools/srsdk_image_generator/Inputs/sr100_b0_bootloader_ver_0x012F_ASIC.axf" \
  -m55_image "<sdk-root>/examples/sample_demo_app/out/sr110_cm55_fw/release/sr110_cm55_fw.elf" \
  -flash_type "GD25LE128" \
  -flash_freq "67"

Flash the firmware image:

cd <sdk-root>
python tools/openocd/scripts/flash_xspi_tcl.py \
  --cfg_path tools/openocd/configs/sr110_m55.cfg \
  --image tools/srsdk_image_generator/Output/B0_Flash/B0_flash_full_image_GD25LE128_67Mhz_secured.bin \
  --erase-all

Running the Application using VS Code Extension

Press RESET on the board after flashing.
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.
Observe periodic task logs in the logger window.

Expected Logs

0000000023:[0][INF][SYS ]:Application drivers initialization complete without errors.
0000004210:[0][INF][SYS ]:sr110 SDK version 1.3.0
0000107685:[0][INF][SYS ]:Task vTaskDemo1
0000611706:[0][INF][SYS ]:Task vTaskDemo1
0001007723:[0][INF][SYS ]:Task vTaskDemo2
0001115727:[0][INF][SYS ]:Task vTaskDemo1
0001619748:[0][INF][SYS ]:Task vTaskDemo1
0002011765:[0][INF][SYS ]:Task vTaskDemo2
0002123769:[0][INF][SYS ]:Task vTaskDemo1