AP_HAL_ChibiOS: add hwdef files for NarinFC-H7

[vololand]

AP_HAL_ChibiOS: add hwdef files for NarinFC-H7
(ArduPilot/ardupilot:master <--- vololand/ardupilot:NarinFC-H7)

[vololand]

Is there a description of "New Board Support" and "Wiki Need"?

[Hwurzburg]

just labels for our dev team use to track PRs...

[vololand]

Thank you for the explanation.
Labels understood.
Where can I find a description for writing wiki?

[Hwurzburg]

@vololand

1. Since this is an exact clone of the CUAV X7 you will need to do the following:
   • submit a separate PR for an assignment of a board id in the Tools/AP_Bootloader/build_types.txt file for your own board id. perhaps AP_HW_NarinH7 1183 as the next available. It can be merged as soon as you post it to reserve the bd id.
   • be sure to include the CUAV copyright notice on any source code copied (hwdef.dat,etc.) per their LICENSE (https://github.com/ArduPilot/Schematics/blob/master/CUAV/LICENSE)
2. You will need to create a bootloader for this PR.
3. For the wiki, I use the readme file included here to create a wiki page
   Once the first two items above are done , myself and others will review (I know I will ask for more details on the readme in order for me to ba able eventually create the wiki page) and once you have prototypes and have tested them, we will submit to the dev team for final review and merge into the database.

[vololand]

@vololand

1. Since this is an exact clone of the CUAV X7 you will need to do the following:

   • submit a separate PR for an assignment of a board id in the Tools/AP_Bootloader/build_types.txt file for your own board id. perhaps AP_HW_NarinH7 1183 as the next available. It can be merged as soon as you post it to reserve the bd id.
   • be sure to include the CUAV copyright notice on any source code copied (hwdef.dat,etc.) per their LICENSE (https://github.com/ArduPilot/Schematics/blob/master/CUAV/LICENSE)

2. You will need to create a bootloader for this PR.

3. For the wiki, I use the readme file included here to create a wiki page
   Once the first two items above are done , myself and others will review (I know I will ask for more details on the readme in order for me to ba able eventually create the wiki page) and once you have prototypes and have tested them, we will submit to the dev team for final review and merge into the database.

@Hwurzburg

There is no tool/AP_Bootloader/build_types.txt file in the path you were told.
There is a tool/AP_Bootloader/board_types.txt file in the path you told me, do you want me to write AP_HW_NarinH7 1183 here and create PR?

[Hwurzburg]

Since you are a bit confused, I created the PR for you #29124
use AP_HW_NarinH7 for the APJ_BOARD_ID instead of a number in both hwdefs....create a bootloader .bin with this number and include it in Tools/bootloaders folder and commit in this PR

[vololand]

Since you are a bit confused, I created the PR for you #29124 use AP_HW_NarinH7 for the APJ_BOARD_ID instead of a number in both hwdefs....create a bootloader .bin with this number and include it in Tools/bootloaders folder and commit in this PR

@Hwurzburg
Thank you.
Renamed from AP_HW_NarinH7 to AP_HW_NarinFC-H7.

[Hwurzburg]

you need to be sure the bootloaders have this new id and squash all commits and then split using "Tools/gittools/git-subsystems-split" to sort into library commits

[vololand]

you need to be sure the bootloaders have this new id and squash all commits and then split using "Tools/gittools/git-subsystems-split" to sort into library commits

@Hwurzburg
I worked on it as you commented.
Please check.

[Hwurzburg]

1. The tone alarm change is extraneous, remove it. Submit a separate PR (which I don't think would be approved for changing the existing startup tone for everyone)
2. you did not squash the commits and library split. There should be only the Tools:add NarinFC-H7 commit and a hwdef:add NarinFC-H7 commit. I can do this for one later this week if you wish