Skip to content

S1 in the app: open a board, see its model and problems, validate and generate - #10

Merged
teo1747 merged 1 commit into
mainfrom
app/s1-board
Nov 12, 2026
Merged

teo1747 merged 1 commit into
mainfrom
app/s1-board

Conversation

@teo1747

@teo1747 teo1747 commented Nov 12, 2026

Copy link
Copy Markdown
Member

The desktop side of S1. With #9, S1 is done.

What the person can do

  • File › Open Board… (⌘O) opens a board of an EmbLinkRTOS checkout, such as ~/EmbLinkRTOS/boards/st/nucleo_f446re. Open Recent remembers the last 8, and --open <board> does the same from the command line. The stage bar shows the board's id.
  • Board shows the generator's model: the chip, the board (console, LEDs, buttons, debug probe), the clocks, memory regions and partitions, the pins in use and the devices. Every value is the core's; the view only formats them (180 MHz, 512 KB) in the interface's language.
  • Problems lists every diagnostic, errors first, each with its file, line and YAML path. A double-click opens the file in your editor (EmbLink Studio's own editor comes in S8).
  • Board › Validate and Generate (⌥⌘G). The first time, the app asks to trust the checkout, since the generator is code from it (spec §9). Trust is remembered.
  • A trusted board is validated as soon as it opens. If the core restarts, the board opens again.

Translations: all 100 texts are in French and Simplified Chinese, including plurals ("1 erreur / 2 erreurs", "2 个错误").

Development: the build now runs the core with core/.venv's Python when it exists, so PyYAML is there for the generator. docs/development.md explains it.

Tests: the new tst_session drives the real core against a checkout whose generator is the core's test stand-in. It checks opening, the trust step, generating then showing the model in the Board view, errors reaching the Problems view with their place, reopening after a core restart, and refusals reaching the person. 7 of 7 suites pass locally, and clang-format 18 is clean.

Screenshots of the real NUCLEO-F446RE (English) and Pico 2 W (Chinese) are in progress-screenshots/ locally.

…d generate

The desktop side of S1. Session holds the open board as the core knows it;
the views show what the core answered, and nothing is computed in the GUI.

- File > Open Board (Cmd+O, Ctrl+O) opens a board directory of an EmbLinkRTOS
  checkout, with Open Recent; --open <board> does it from the command line. The
  stage bar shows the board's id.
- Board shows the generator's model: the chip, the board's console, LEDs,
  buttons and debug probe, the clocks, memory regions and partitions, the pins in
  use and the devices, as settings-style groups.
- Problems lists every diagnostic, errors first, with its file, line and path in
  the YAML; a double-click opens the file. Validate asks the generator again.
- The Board menu validates and generates (Opt+Cmd+G). When the core answers
  untrusted, the window asks once to trust the checkout, then runs the action.
- A trusted board is validated as soon as it opens, and opens again after the
  core restarts.
- Every new text is in French and Simplified Chinese, plural forms included.
- The build runs the core with core/.venv's Python when it exists, so the core
  has its dependencies (PyYAML for the generator).
- The layout version is 2: Board and Problems join the views.

tst_session drives the real core against a checkout whose generator is the core's
test stand-in. S1 is done in the specification.

Signed-off-by: teo1747 <148846371+teo1747@users.noreply.github.com>
@teo1747
teo1747 merged commit 17040ac into main Nov 12, 2026
11 checks passed
@teo1747
teo1747 deleted the app/s1-board branch November 12, 2026 23:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant