Troubleshooting
Common issues with the dashboard, the fwm CLI, and generated firmware — and how to fix them.
Dashboard issues
Document generation hangs or fails
Long-running document generators (especially Code Scaffold and Firmware Architecture) can take 30–90 seconds. If a job appears stuck for more than five minutes, check Dashboard → Jobs for the current status.
If the job failed, you'll see the error there. You can re-run it from the same page — context is preserved.
Download ZIP is empty
This usually means no documents have been generated yet for the project. Generate at least one document, then download.
If you've generated documents but the ZIP is still empty, contact us via the Contact form with your project name.
fwm CLI issues
fwm: command not found
The install script adds ~/.fwm/bin (or %USERPROFILE%\.fwm\bin on
Windows) to your PATH. Restart your terminal so the change takes
effect, or source your shell profile manually.
Authentication failed
Your API token may have expired or been revoked. Run fwm login again
with a fresh token from Dashboard → Settings → API Tokens.
REPL hangs after a prompt
The agent may be waiting on a long generation. Press Ctrl+C to cancel
it without exiting the REPL.
Generated code doesn't compile
This is rare but possible — usually the cause is an SDK version
mismatch. Make sure your nRF Connect SDK version matches the west.yml
in the generated scaffold (or update one to match the other).
If the error persists, run fwm /analyze for a diagnostic pass, or
switch to /mode debug and paste the build output.
Build & runtime issues
Cannot find symbol … at link time
Almost always a missing Kconfig — the relevant subsystem is referenced
in source but not enabled in prj.conf. Run fwm /validate to surface
missing Kconfig dependencies.
Peripheral doesn't respond
Check device_is_ready() is called before any peripheral operation,
and that the peripheral is enabled in your Device Tree overlay
(status = "okay").
BLE timing or connection drops
Check that you're using the LFXO (low-frequency crystal oscillator) and not the LFRC (RC oscillator). The LFRC has too much drift for stable BLE connections in most cases.
Still stuck?
Get in touch — include your project name, the relevant generated files, and any logs. We typically respond within 1–2 business days.