Mirror/betaflight
1
0
Fork 0
mirror of https://github.com/betaflight/betaflight.git synced 2025-07-16 12:55:19 +03:00
Code Issues Wiki Activity

Update Development.md (#12017)

Browse source 
Adding details on how to use the board scratch space for developers.
This commit is contained in:
J Blackman 2022-11-24 11:03:23 +11:00 • committed by GitHub
parent 4fb122250e
commit 090d522e35
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 27 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

27
docs/development/Development.md
View file

@ -127,3 +127,30 @@ For Linux/BSD/OSX: `git config --global core.excludesfile '~/.gitignore'`
For Windows: `git config --global core.excludesfile '%USERPROFILE%\.gitignore'`
When you `git config --global --get core.excludesfile` a second time, you should get a file location back.
### Custom Defaults - for developers
As all targets are now MCU based (and cloud built), this poses a problem for developers in flashing and running a fully baked "hex" using the standard debugger. The board scratch space (located at the /src/main/board directory) allows developers to setup their environment like they were running a fully baked unified target.
Once setup, you can simply execute make with `make BOARD=XXX` where XXX is the sub directory name under /src/main/board.
Example board.c (so that custom defaults are placed in the resultant build file):
```
#include "board.h"
const char __attribute__ ((section(".custom_defaults"), used, aligned(4))) customDefaults[] =
"# Betaflight\n"
"board_name NERO\n"
"\0";
```
board.h allows for any defines that you are working on as developers rather than specify via command line in EXTRA_FLAGS (as the cloud build system does).
board.mk allows for any additional source files, and to specify the target.
e.g.
```
TARGET := STM32F7X2
```