Menu
Compile and run the PhoenixSketch unit tests under code/test using CMake + Google Test. Use when the user asks to run, build, or check the unit tests / ctest / Google Test suite for the radio firmware.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Compile the PhoenixSketch production firmware and flash it to the Teensy 4.1 radio over USB. Use when the user asks to build, compile, upload, flash, deploy, or program the radio / Teensy / Phoenix firmware.
Compile and flash the PhoenixSketch firmware to the T41 radio (Teensy 4.1). Use when the user wants to build, compile, upload, or flash the production firmware to the radio. Requires the radio connected via USB at /dev/ttyACM0.
Measure execution time of functions or code regions in the PhoenixSketch firmware by instrumenting the source with Flag() calls and capturing the resulting pin transitions on an Analog Discovery 2. Use when the user wants to profile, time, benchmark, or characterize how long a piece of radio code takes to run.
Run the PTT signal integrity test on the radio transmitter hardware. Use when the user asks to test the transmitter, run a PTT test, check I/Q outputs, or verify transmit signal quality. Requires an Analog Discovery 2 connected to the radio.
| name | run-tests |
| description | Compile and run the PhoenixSketch unit tests under code/test using CMake + Google Test. Use when the user asks to run, build, or check the unit tests / ctest / Google Test suite for the radio firmware. |
Builds and runs the host-side unit tests in code/test/ using CMake and ctest. The tests use mocked Arduino/hardware interfaces and run on the development machine — they do not touch the Teensy.
| Setting | Value |
|---|---|
| Source dir | code/test/ |
| Build dir | code/test/build/ |
| Test runner | ctest (Google Test discovered via CMake) |
Ensure the build directory exists. If code/test/build/ is missing, create it. If the user passed clean, remove it first and recreate.
mkdir -p code/test/build
Configure (if needed). From code/test/build/, run cmake. CMake re-configures itself on subsequent runs as needed, so it's safe to run unconditionally:
cmake ..
Build. From code/test/build/:
make
Builds can take a while on a clean tree; use a generous Bash timeout (e.g. 600000 ms). If the build fails, surface the first error and stop — do not run tests on a broken build.
Run tests. From code/test/build/:
ctest --output-on-failure
Add -R <pattern> if the user passed a filter arg, and -V if they passed verbose.
Report. Summarise in 1–2 lines: how many tests passed/failed, and the names of any failing tests. If a specific filter was used, mention what it matched.
clean — wipe code/test/build/ and reconfigure from scratch before building. Use when CMake state seems stale or the user explicitly asks for a clean build.verbose — pass -V to ctest so individual test output is shown even on success.-R regex filter (e.g. RFBoard runs ctest -R RFBoard --output-on-failure). Multiple words can be combined into one regex with |.clean and verbose may be combined with a filter arg.
code/test/build/ once it exists — relative paths in CMakeLists.txt assume that.flash-radio skill instead.code/test/build/; the firmware build artifacts (code/build/, ArduinoOutput/) are unrelated and should not be touched here.