rusefi
/
rusefi_documentation
mirror of https://github.com/rusefi/rusefi_documentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

merge rusEFI wiki

This commit is contained in:
GitHub Action 2021-11-19 20:01:58 +00:00
parent 7ab7d40c1c 1104daa27e
commit eeab4e5477
1 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
Developing-On-Linux.md
View File

@ -6,6 +6,26 @@ These can be extracted under your home directory; just add the `bin` directory t
TODO: You probably need to install additional packages but I don't remember what they are.
Then to compile the firmware,
```
cd firmware
make PROJECT_BOARD=nucleo_h743 PROJECT_CPU=ARCH_STM32H7 -j4
```
Edit according to your environment.
To compile the simulator,
```
cd simulator
./compile.sh
```
To compile the unit tests,
```
cd unit_tests
make -j4
```
# Working with STM32 Dev/Nucleo boards
These boards are convenient as they include an ST-Link onboard which aids debugging. I believe the main difference is a Development board includes a bunch of peripherals that you may or may not care about, while a Nucleo board is much more stripped down. Some (all?) boards will be powered when you connect to the ST-Link USB board. The ST-Link will include, among other things, a virtual com port, which can be used to run either the console or TunerStudio. However, by default the ports are not accessible by regular users. You can solve this with: