...
- Compiler: GCC ARM
- A compiler builds human readable source code into a machine readable target language, usually a machine executable or binary for a specific architecture. GCC ARM compilers compiles C code into machine readable .elf, .hex or .bin files which can be flashed onto the MCU. GCC ARM is the standard open source compiler for ARM architecture. Compilers are powerful and often catch typos, errors, and warnings; they also optimize code for efficiency or size. The compiler flags set these behaviors of the compiler.
- Build Tools: GNU Make and GNU Linker aka ld
- Build tools usually instruct the compiler on where the source files it is building are located and which files to look at in order to build the target program. Often a Linker will be used with a Makefile to build a collection of C and header files into a standard library which can be included in your program. GNU Make and Linker are long-standing open source standard build tools used by many developers, although many alternatives do exist.
- Linter: cpplint
- A linter is a program that checks the style of source code for errors. Some linters also perform static analysis, ours does not, which look to catch programming errors before the code is executed. cpplint is Google's open source linter for C/C++ programs, note that our Coding Standards closely follow Google's and as a result, this linter works well for us. It will often be more pedantic than we need but it is a good tool to use.
- Flasher: st-link/GDB or OpenOCD
- A flasher will transfer firmware (our compiled program) onto the MCU. Typically, this is done with a special cable or by a chip on the PCB and requires flashing software to transfer the contents of the source code into the memory of the MCU. For our purposes, we will be using st-link with GDB for debug which is the chip manufacturer supported method or OpenOCD the open source version.
- IDEs: Eclipse or any text editor (Core members like: Vim, Sublime Text and Visual Studio Code)
- Anyone just starting out and especially those using Windows are strongly encouraged to use the Eclipse IDE which is one of the few ways to get a working Toolchain on a Windows machine. Note that we will not be supporting any issues you may encounter using other methods on Windows although, we will also support a Linux VM if you want to do that a VM or dual boot but you will need to figure out the install on your own.
- Source Control: GitHub
- We use GitHub for our source and versioning control. In order to contribute to the codebase, you will also need to start using GitHub. If you are new to GitHub you may want to check out these guides. We have tight controls on out git repositories and require all commits to come from pull requests and that they are squashed prior to submitting.
...