firmware: debug/test build profiles with real behavioural differences
This commit is contained in:
@@ -102,3 +102,26 @@ inject sleep -> heartbeat chip_mode=0, config_intact=false
|
||||
-> radio_recovery level 1 -> failed (correctly refuses)
|
||||
-> radio_recovery level 2 -> rx_restored
|
||||
```
|
||||
|
||||
## Build profiles
|
||||
|
||||
```
|
||||
./tools/build.sh test # default; the configuration all HIL numbers use
|
||||
./tools/build.sh debug # verbose diagnostics, assertions, per-TX dumps
|
||||
./tools/flash.sh [test|debug]
|
||||
```
|
||||
|
||||
Differences are behavioural, not cosmetic:
|
||||
|
||||
| | test | debug |
|
||||
|---|---|---|
|
||||
| `verbose` at boot | off | on |
|
||||
| `tx_diag` after every TX | only on failure | always |
|
||||
| raw frame hex in events | yes (HIL needs it) | yes |
|
||||
| optimisation / log level | size, warn | debug, info |
|
||||
| task watchdog | 15 s | 30 s |
|
||||
|
||||
`hil/run.sh` always builds and flashes the `test` profile, so reported
|
||||
timing is never perturbed by debug serial traffic. Build directories are
|
||||
separate (`build-test`, `build-debug`) so profiles cannot silently reuse a
|
||||
stale sdkconfig.
|
||||
|
||||
Reference in New Issue
Block a user