Julian Oes 50d24429ec

feat(params): add board-level read-only parameter support ...

Integrators can declare read-only parameters in a per-board YAML file:
readonly_params.yaml.

There are two ways to define the read-only params:
- "block": default writable, explicitly list params to be locked
- "allow": default readonly, explicitly list params to be writable

Enforcement is activated by `param lock` in rcS after all startup
scripts have run, so board defaults and airframe scripts can still set
params during init.

The feedback via MAVLink uses the new
MAV_PARAM_ERROR_READ_ONLY as part of the PARAM_ERROR message.

2026-04-09 06:43:17 +12:00

..

cannode

config: add dynamic init file

2025-08-21 16:46:06 +02:00

performance-test

Performance & testing targets

2025-02-24 16:02:46 +01:00

px4fmu_common

feat(params): add board-level read-only parameter support

2026-04-09 06:43:17 +12:00

px4fmu_test

ROMFS: purge old mixing system

2022-09-09 09:14:09 -04:00

CMakeLists.txt

romfs: allow target level airframe selection (#25677)

2025-10-10 11:29:27 -06:00