v86 arm64 Linux

Keyboard: arrows (left is Back, right is Select), or Esc, Backspace and Enter.

Keyboard (outside the console): Esc for the top left button (the menu; held, power), the left and right arrows for the bottom ones, Enter for the top right one. The console below is its serial port: Epicardium's log, and MicroPython's REPL: Ctrl-C stops the app, and Ctrl-C again once the menu's up gives the >>> prompt.

Debugging the two cores

Core 0 · Epicardium (FreeRTOS) Open in new tab

Core 1 · Pycardium (MicroPython) Open in new tab

The debuggers' Linux machine (its console)

Inside: Pycardium calling Epicardium

Core 1 (Pycardium) busy - Core 0 (Epicardium) busy - API calls -/s Interrupts -/s

Busiest calls (last second)	Calls/s	Round trip

Every API call Pycardium (MicroPython, core 1) makes, Epicardium (FreeRTOS, core 0) runs for it: core 1 takes the hardware semaphore, writes the call's number and arguments into the memory both cores share, sets its flag and wakes core 0 with an event (SEV), then waits (WFE). Core 0's dispatcher task runs the call, writes the result, and wakes core 1 again. Between the cores, each call is a bar from when core 1 made it to when it returned, a row per function (the latest calls drawn down to core 0 and back); orange arrows are interrupts core 0 raises on core 1 (through timer 5): Ctrl-C, serial input, sensor data.