[BACKPORT] px4_fmu-v6c:Add Mini & fix Rev 1

[davids5]

No description provided.

[davids5]

@mrpollo @vincentpoont2 will test this in the AM tomorrow. Then it can be merged

[vincentpoont2]

Tested on

• Pixhawk 6C (VER0 REV 0)
• Pixhawk 6C (VER0 REV 1)
• Pixhawk 6C Mini (VER2, REV1)

The sensor calibration, receiver, and LOG functions are all normal

Boot Logs
6c-mini_boot-print.txt
Pixhawk 6C_REV0_20230301 release1.13-pr-backport-HB-6C-Mini0.txt
Pixhawk 6C_REV1_20230301 release1.13-pr-backport-HB-6C-Mini0.txt

[junwoo091400]

@davids5 note, if you create a branch in release/* format, it automatically triggers the metadata deployment to S3 webserver:

PX4-Autopilot/.github/workflows/deploy_all.yml

Line 7 in 7edce94

- 'release/*'

Therefore, it will modify the target metadata before even it gets merged. Could you not use the release/* format for the branch name?

Note: left a comment in discord as well: https://discord.com/channels/1022170275984457759/1045343300850290778/1081108778956619847

[davids5]

@davids5 note, if you create a branch in release/* format, it automatically triggers the metadata deployment to S3 webserver:

PX4-Autopilot/.github/workflows/deploy_all.yml

Line 7 in 7edce94

- 'release/*'

Therefore, it will modify the target metadata before even it gets merged. Could you not use the release/* format for the branch name?

Note: left a comment in discord as well: https://discord.com/channels/1022170275984457759/1045343300850290778/1081108778956619847

@junwoo091400 Good to know - thank you. with the exception of main I use the base name in my branches to keep rebasing and PR on the correct target. I am curious how others keep it straight. How do you do it.

[mrpollo]

Thanks @davids5