AP_HAL_ChibiOS: Added support for ZeroOne_Air flight controller

[ZeroOne-Aero]

AP_HAL_ChibiOS: Added support for our new ZeroOne_Air flight controller

[andyp1per]

LGTM

[peterbarker]

Commit list needs cleaning up before merge.

[ZeroOne-Aero]

We've changed the content, please help us review it again, thanks

[Hwurzburg]

The pinout diagram has many errors:

1. no debug port shown or labelled
2. TELEM1: TX1 should be TX7, etc.
3. GPS2/I2C: should be TX8/RX8
4. GPS1/Safety: should be TX1/RX1
5. UART4: should be TX4/RX6
6. should label the boot button

[Hwurzburg]

Suggested change

	| SERIAL6 | UART4 | UART4 |DMA Enabled |
	| SERIAL6 | User | UART4 |DMA Enabled |
	| SERIAL7 | Debug | UART3 |DMA Enabled |

[Hwurzburg]

note: debug port is not shown on ports image....where is it?

[Hwurzburg]

still have question on where debug port is located

[ZeroOne-Aero]

Hello, the content has been modified according to your requirements, please confirm again.

[Hwurzburg]

aside from the debug port location question...looks good...needs squashing, see https://youtu.be/iMUWQUD_Rsg

[ZeroOne-Aero]

I've tried to squashing using the method in your video, but I haven't used it before, so it's not very successful, can I merge it in the form of a new PR

[Hwurzburg]

I can do it for you this weekend...what about my debug port question?

[Hwurzburg]

the problem is you kept merging master into this branch.....in the future don't do that....you can update your local master branch to the ArduPilot upstream, and then do a git rebase master on the PR branch if you want it rebased on things that have been added to the master...but don't merge them....I had to remove ~20 master branch commits interspersed between your commits...then do a squash and library split....it good now

[ZeroOne-Aero]

Thanks, I see, I'll pay attention next time about this issue. Regarding the problem of debug interface, I need to explain to you that our series of controllers are small in size, the size of an egg, so we reserve a debug test point at the bottom of the flight controller, and we have designed a programming tooling separately for programming and testing.

[ZeroOne-Aero]