Oberon RTK

Astrobe Configuration Files

Layout and naming convention for the .ini configuration files in <repo>/config/

Overview

The Oberon RTK repository ships pre-made Astrobe .ini configuration files under <repo>/config/. Unless your installation of Astrobe and the Oberon RTK framework matches the one used in the repository (see Astrobe IDE & Tools and Framework Installation), you will need to adapt the settings – in particular paths – to your set-up.

This page describes the directory and filename layout so you can find or adapt the right file.

Directory and Filename Layout

The directory path and the filename together encode four axes:

  • Astrobe IDE/tools: astrobe-rp2040 or astrobe-rp2350 – which Astrobe install builds the program.
  • Board (with its MCU): pico-rp2040, pico2-rp2350, u585i-iot, … – the target board.
  • Library version: v31, v30, v21, … – the version of the Oberon RTK library the program is built against.
  • Variants: k1, k3, k4, imagedef, plib, t2, … – kernel choice and other build flags.

Top-level Directories

  • <repo>/config/astrobe-rp2040/:

    • for Astrobe for RP2040
    • builds programs for:
      • MCU = RP2040, board = Pico

  • <repo>/config/astrobe-rp2350/:

    • for Astrobe for RP2350
    • builds programs for:
      • MCU = RP2350, board = Pico2
      • MCU = STM32H573II, board = STM32H573I-DK
      • MCU = STM32U585AI, board = B-U585I-IOT02A
      • MCU = MCXA346, board = FRDM-MCXA346
      • MCU = MCXN947, board = FRDM-MCXN947

Note: support for the NXP MCUs is not included in lib/v3.1 or later. This may change going forward, but don't hold your breath.

Per-Board, Per-Lib-Version Sub-directories

Within each top-level directory, .ini files are grouped by board and library version, eg.:

<repo>/config/astrobe-rp2040/
   pico-rp2040-v31/
   pico-rp2040-v30/
   pico-rp2040-v21/
   ...

<repo>/config/astrobe-rp2350/
   pico2-rp2350-v31/
   pico2-rp2350-v30/
   pico2-rp2350-v21/
   ...

The lib-version split (one sub-directory per v31, v30, …) keeps the active set of .ini files visible in Astrobe's IDE configuration menu (which limits how many entries it displays at once) and lets older library versions sit alongside the current one without crowding the menu.

Filename Convention

The files follow a systematic-ish naming convention.

For example:

v20-rp2040-pico-k1.ini
  • v20: library version (lib/v2.0)
  • rp2040: MCU
  • pico: target board
  • k1: variant suffix (here: kernel-v1)

There can be additional variant suffixes:

v21-rp2040-pico-k1-plib.ini

v21-rp2350-pico2-k1-t2.ini
  • t2: generate Thumb2 code (Astrobe option Thumb Code unchecked)
v31-rp2350-pico2-k1-imagedef.ini
  • imagedef: code base is 10000000H, for use with Astrobe's ImageDef module (see IMAGE_DEF).

No Kernel Used

If your program doesn't use a kernel, pick the -k1 variant – it covers both kernel-v1 programs and programs without a kernel.

Project-Specific Configurations

There can also be config files specific to a single project, placed directly in the project directory alongside the source code (eg. for a custom SRAM-split between the cores). These take precedence over the central <repo>/config/ files for that project.

Last updated: 21 May 2026