This PR makes all the uavcan subscribers, publishers and controllers built-time configurable via kconfig. This solves the issue: https://github.com/PX4/PX4-Autopilot/issues/21836 where the uavcan driver caused high CPU usage on one of the NXP board, and by selecting only the parts which you want to use reduce the cpu load.
The community call is almost always in my commuting time, so difficult for me to join. However I will try and see if I can make it.
I would just like to get some eyes on the PR, and get any comments on next to do’s to get this in.
This PR is about the introduction of tilting drones in the PX4 airframes. I would like to understand if all the github checks must be successful before having the opportunity to open the PR, because I think that there are some checks that can’t pass with this version (like the simulations).
I would like to have feedback about that PR.
I was seeing param resets on boot for recently calibrated drones using a custom board built from fmuv6x. Firmware is built off 1.13. Tracking the issue down, the BSON decoder would read a node value of 0xFF (indicating reading an empty sector), terminate the import and return success. To fix the problem, I now return an error and let the startup script load params from the backup file on the SD Card.
Is there a reason why when reading an empty section of the FRAM the import should return success to the startup script?