* feat(mavlink): make the MAV_x instance count a per-board Kconfig option
MAV_x_* params and rc.serial were fixed at 3, though up to 6 MAVLink
instances can run. CONFIG_MAVLINK_NUM_CONFIG_INSTANCES (default 3) sets it;
extra instances take instance 2's defaults.
Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
* feat(boards/agam): enable 5 MAVLink instances on the v6X-RT
Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
* docs(releases): add per-board MAVLink instance count to main release notes
Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
* fix(mavlink): share main's --board-config in the instance count generators
main already passes the boardconfig as --board-config to generate_params.py,
so the duplicate option failed every build after a rebase. Both generators now
read it through the shared load_board_config. Kconfig caps the count at 5,
or 3 on constrained-memory boards, leaving a channel for USB, and list
defaults keep their length check unless the count comes from Kconfig.
Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
---------
Signed-off-by: abhijithcv <abhijithcv1212@gmail.com>
The output-group parser reads timer_config.cpp as text. A board that
guards timer or channel entries with #if defined(CONFIG_...) now gets
those guards evaluated against the board's Kconfig output, passed as
--board-config by the parameter and actuator metadata generators, so
the PWM_MAIN parameters and the actuator metadata match the channels
the firmware actually has.
Co-authored-by: Andre Heinemans <andre.heinemans@nxp.com>
Add the PX4 arch layer for the i.MX9 family: ADC, HRT on LPTMR with
LPIT deadlines, TPM io timers, pin interrupts, LPSPI with chip selects
for all eight instances, critmon on the DWT cycle counter, a tone alarm
on a TPM channel, version reporting with the 128-bit ECID read from the
Fuse Status Block as the UUID, the board reset entry point, plus the
i.MX95 chip include set, the chip mapping in px4_impl_os.cmake and the
PX4_SOC_ARCH_ID_IMX95 id. DShot uses the shared NXP FlexIO driver with
the i.MX9 FlexIO base, offsets, IRQ, clock root and pad hooks.
Not implemented yet: reset of the M7 through the System Manager, LED
PWM and PWM input capture.
i.MX9 timer configs name their timers Timer::TPMn and mark DShot
capable ones with initIOTimerDshot(), so teach
output_groups_from_timer_config.py both forms.
Co-authored-by: Andre Heinemans <andre.heinemans@nxp.com>
The generator copied the yaml value into the tag, so false became
"@reboot_required False", and the metadata parsers treat any value as
set. QGC prompted for a reboot after changes to 35 parameters that
apply live, among them the gyro filters, log rotation and ADSB squawk.
Emit flag tags only when true. volatile had the same flaw, though no
parameter sets it false yet.
Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Jacob Dahl <dahl.jakejacob@gmail.com>
- migrate_c_params.py: preserve newlines and paragraph breaks in long
descriptions, use YAML block scalars for multi-line strings
- generate_params.py: support @value tags on float type parameters
(fixes RC*_REV enum values being lost during yaml generation)
Add PWM_*_CENTERx for each servo.
Use a bilinear transform to map actuator_servos to PWM signals.
This solution only works for PWM based servos. Other types of servos are not affected.
* PWM: Add servo trim option
* PWM: Improve documentation of PWM trim feature
* PWM: cleaner clamping and docs typo
* update documentation & safety
* add migration formula
* rename param from trim to center
* docs with center instead of trim
* move clamping and reorder values
* improve documentation
* adress failing range check
* improve documentation
* CA: add event for setting CENTER with TRIM
Signed-off-by: Silvan <silvan@auterion.com>
---------
Signed-off-by: Silvan <silvan@auterion.com>
Co-authored-by: Silvan <silvan@auterion.com>
and remove the possibility to set min > max to reverse.
Initially the idea was to add the checkbox on the UI side, to avoid adding
another param, but I don't think I'll go through the extra effort on the
QGC side.
The implementation assumed timers are defined in the same order as used
in the channels. This could lead to a mismatch between TIMx param and
actual timer config.
Now we use the actual array index, same as in the code.