Peter Barker

Made the changes requested at DevCall - did away with the mapping from weird string to board ID for Pixhawk6C, and just modified the board type. I created a PR...

I've again confirmed there's no change to the build products for the IOMCUs.

configure-all still passes everything when I rebase this on master. Merging as agreed at DevCall.

@AlSharji0 this bug causes a bunch of CI tests to fail, which is very annoying. Are you still chasing this?

For a simple up-and-down flight, setting log_disarmed first: ``` pbarker@fx:~/rc/ardupilot(pr/ap-bitmask-stop-it)$ ./Tools/scripts/du32_change.py logs/00000033.BIN 1728616069: Creating connection Original armed_with_airmode_switch: 0 Original auto_armed: 0 Original compass_mot: 0 Original gps_glitching: 0 Original in_arming_delay: 0...

... and the same thing but arming the vehicle with an airmode switch (aux function 154) ``` pbarker@fx:~/rc/ardupilot(pr/ap-bitmask-stop-it)$ ./Tools/scripts/du32_change.py logs/00000034.BIN 1728616318: Creating connection Original armed_with_airmode_switch: 1 Original auto_armed: 1 Original...

.... rebased it in the hopes that CI passes

Dies due to the tool being old, I think?

I've pushed up another patch here to install the generator from source, which should get CI to pass.

OK, sorry, I wasn't away you'd linked the MAVProxy Wiki there. So someone wants to develop ArduPilot will get MAVProxy as part of the environment install script - but not...