Using Hard Fault
Clients
Section titled “Clients”Hard Fault works with Codex CLI and Claude Code. Install and sign in to the client you prefer, then follow Easy setup. Choose your model and account in that client. BYO does not include a model subscription.
Use byo codex firmware or byo claude firmware from your project.
The client starts the local MCP server, which handles board access.
Your project keeps its own compiler, SDK, and build commands.
The optional firmware-full launch mode gives the client unrestricted access
to your computer and requires --allow-full-access. It does not change the
board’s safety level.
Everyday tasks
Section titled “Everyday tasks”Ask for what you want in plain English:
- “Build the firmware and show any errors.”
- “Flash the application and check the UART output.”
- “Investigate this unexpected reset using the current ELF.”
- “Show this board’s safety level and available operations.”
The agent loads guidance for routine coding, debugging, and board setup. Use Manual skills for larger changes, complex fixes, downgrades, or mass erase.
A successful flash means the image was written. Ask for a test or board observation that checks whether it works.
Troubleshooting
Section titled “Troubleshooting”| Problem | Try this |
|---|---|
byo is missing |
Open a new terminal. |
| MCP server or skills are missing | Run byo doctor in the project. Run byo init if it is new, or byo workspace update to refresh it. Restart the client. |
| Client cannot sign in | Fix authentication in Codex or Claude. |
| Board is not found | Check power, USB data cable, probe wiring, and drivers. Close other programs using the probe. |
| UART is not found | Check the serial connection, driver, and baud rate. Close other programs using the port. |
| Several devices match | Choose the physical board from the agent’s list. |
| Setup cannot find the MCU | Give the exact part number and official datasheet PDF. |
| An operation is blocked | Ask the agent to explain the reason and the required fix. Full setup may need fresh validation after reconnecting. |
| Board is locked | Ask about recovery and data loss before authorizing mass erase. |
Uninstall
Section titled “Uninstall”Close client sessions using BYO. Run project commands from the project’s folder.
| Command | What it removes |
|---|---|
byo uninstall |
BYO integration from this project. Keeps board data, plans, backups, and the shared runtime. |
byo uninstall --purge |
This project’s integration and BYO data, including .firm/, .agent-workspace/, and .agent-backups/. |
byo uninstall --global |
BYO data from every registered project, plus the installed runtime, launcher, and global settings. |
Purge and global uninstall delete saved BYO data. Project source and
unrelated client settings are preserved. Each command prints what it removed
and kept. Use --project <path> to target a project from another folder.