…31 sensors)

…15348)

* X7Pro adds CAN driver
* UAVCAN timer selection moved to default.cmake
* Modify some details about @CUAVcaijie UAVCAN timer selection moved to default.cmake
* Put some timer parameters to micro_hal.h from board_config.h. Fix all h7 boards

Co-authored-by: honglang <[email protected]>

 - single register output is in 2's complement

All the other distance sensors have their default rotation to downwards
facing as well

It loads the battery parameters but then overwrites them
with hardcoded values and it breaks the ModuleParams
parent/child hierarchy. Both is undesired.

The subscription to parameter updates has to get
copied otherwise the change detection will not get
reset for next time.

This was not a problem before because battery.h
included the adc driver and implicitly snprintf
was defined through there.

Co-authored-by: Jonathan Hahn <[email protected]>

 - auto disarm when locked down was added in PX4#14766 to prevent user confusion in regular usage, but also breaks HITL where lockdown is enabled for safety
 - fixes PX4#15686

…state

…SB on new carrier boards)

- add console builds (cubepilot_cubeorange_console) for hardware test rack and developers

 - BOARD_DSHOT_MOTOR_ASSIGNMENT isn't needed if there's no remapping

I observed stack overflows when executing `uavcan params list`, so the
stack size probably needs to be increased.

Signed-off-by: Alex Mikhalev <[email protected]>

Regression from d2254c2, I overlooked that they were defined in
reverse order.

 - this ensures the relevant parameters are marked active immediately
before parameter sync
 - fixes PX4#15872

 - run battery_status module on adc_report publications rather than a fixed schedule

updateBatteryStatus() already publishes

Fixes param migration, e.g. if BAT_N_CELLS is set, migrates to
BAT1_N_CELLS.

Avoid a GCS showing 2 battery indicators.
Alternatively we could also check the 'connected' flag, but this is more
explicit.

The battery migration interferes with the tests.

 - ecl/EKF: Improve robustness of yaw reset to bad inertial data (PX4/PX4-ECL#914)
 - ecl/EKF: Use strength in Gauss (bug fix) (PX4/PX4-ECL#933)

Sometimes, the mission_result timestamp is the same as the
internal_state timestamp which would meant that we would not switch to
LOITER even though the takeoff is clearly done at that point.

On boot, if board_hardfault_init finds a hardfault stored in BBSRAM, it
checks if there is any data available on stdin to see if there is
somebody there to respond to a prompt. But on boards such as cubeorange
where there is not a serial console by default, the ioctl fails and
bytesWaiting is uninitialized. So it will non-deterministally hang the
boot process with no outside feedback if that value is not zero.

Signed-off-by: Alex Mikhalev <[email protected]>

 - fixes PX4#16132

 - this allows px4_fmu-v2_rover to function until we have a better mechanism for including or excluding ROMFS dependencies PX4#15711

- prioritize 42688p IMU

There is a proper fix for this already on master
but it's a rabbit hole to cherry-pick it:
-> update matrix
-> dependency on changing ecl
-> dependency on a lot of autopilot changes

 - unfortunately we can't depend on the system field due to potential
external binding and non-genuine Spektrum equipment
 - reject any DSM frame with duplicate channels
 - add 16 channel mask
 - tighten valid PWM range 990-2010us (±100% travel is 1102-1898µs)
 - update RCTest rejected frame count

- refactor FMU v6x to ModalAI FCv2 name only

… doing sensing on 3.3

- remove PWM capture, not routed

- configure old tone alarm pin for FYSNC for IMUs in the future

- update Spektrum settings to control output

- add ICM42688p driver

- disable ethmac