[FMUv6s] Communicate the correct board id version #25708
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
niklaut
force-pushed
the
fix/fmuv6s_board_id
branch
2 times, most recently
from
bbb9188 to
5321c1a
Compare
alexVinarskis-auterion
approved these changes
Oct 7, 2025
|
FMUv6x at 100.01% flash, even though I didn't change anything for it |
alexcekay
approved these changes
Oct 7, 2025
niklaut
force-pushed
the
fix/fmuv6s_board_id
branch
from
5321c1a to
d91c3fd
Compare
niklaut
force-pushed
the
fix/fmuv6s_board_id
branch
from
d91c3fd to
d9d594e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solved Problem
We found that the
MAVLINK_MSG_ID_AUTOPILOT_VERSIONmessage would return 0 for the board id on FMUv6s.The implementation calls
https://github.com/Auterion/PX4_firmware_private/blob/a60aa1d9887cb7e7ffd926908d0ef7ec5053ce0c/src/lib/version/version.c#L292-L299
which depends on
CONFIG_CDCACM_PRODUCTIDbeing defined.Since the board doesn't have a USB, the entire CONFIG_CDCACM module was removed and all it's config too.
Whoops.
Solution
Define
CONFIG_CDCACM_PRODUCTIDmanually in theboard_config.h. It doesn't work to just define it in the KConfig as the entire CDCACM driver is not enabled, thus the config options are not generated.Changelog Entry
For release notes:
Alternatives
We could also use the bootloader id instead (as one would expect).
Test coverage