Menu
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.
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 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.
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.
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 | flash-radio |
| description | 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. |
Compiles code/src/PhoenixSketch/PhoenixSketch.ino with arduino-cli and uploads the resulting .hex to the connected Teensy 4.1.
The build settings come from code/.vscode/arduino.json and must stay in sync with it:
| Setting | Value |
|---|---|
| Board (FQBN base) | teensy:avr:teensy41 |
| FQBN options | usb=serial2,speed=600,opt=o1lto,keys=en-us |
| Sketch | src/PhoenixSketch/PhoenixSketch.ino (relative to code/) |
| Output dir | ../ArduinoOutput (relative to code/) |
| Default port | /dev/ttyACM0 |
If those values diverge from code/.vscode/arduino.json, prefer the file and tell the user.
Check the board is connected. Run arduino-cli board list and confirm a Teensy is present (it usually appears as /dev/ttyACM0, FQBN teensy:avr:teensy41). If no Teensy is listed, stop and tell the user to connect/power the radio — do not try to flash a missing device.
Compile. From the code/ directory:
arduino-cli compile \
--fqbn "teensy:avr:teensy41:usb=serial2,speed=600,opt=o1lto,keys=en-us" \
--output-dir ../ArduinoOutput \
src/PhoenixSketch/PhoenixSketch.ino
Compiles take a while; run with a generous Bash timeout (e.g. 600000 ms / 10 min). If compilation fails, surface the first error and stop — do not flash a broken build.
Flash. If the port discovered in step 1 differs from /dev/ttyACM0, use that one. From the code/ directory:
arduino-cli upload \
-p /dev/ttyACM0 \
--fqbn "teensy:avr:teensy41:usb=serial2,speed=600,opt=o1lto,keys=en-us" \
--input-dir ../ArduinoOutput \
src/PhoenixSketch/PhoenixSketch.ino
The Teensy loader may prompt the user to press the physical button on the board — mention this if upload appears to hang.
Report. Summarise in 1–2 lines: whether compile succeeded, whether upload succeeded, and any notable warnings.
compile-only — run step 2 only; skip the flash step. Useful when no board is connected or the user just wants to verify the build.flash-only — skip compile and re-flash whatever is already in ../ArduinoOutput. Only valid if that directory contains a recent build for this sketch; otherwise fall back to the full compile+flash.code/ so the relative paths in arduino.json resolve correctly.code/test/build/ and are a separate workflow.code/build/ directory is the CMake test build; the firmware artifacts go in ArduinoOutput/ at the repo root.