R@M Wiki

Setting up an Embedded Development Environment: Difference between revisions

Page Discussion

Setting up an Embedded Development Environment (edit)

Revision as of 14:30, 6 July 2024

774 bytes added ,  6 July 2024
no edit summary
VisualWikitext
No edit summary
No edit summary
When writing code on a PC intended to be run on a PC, the compilation-into-executable process is really straightforward. There might be some hiccups when it comes to writing software for Windows versus Linux versus macOS for example, but that is just a matter of library usage (when building for Linux your program would link to Linux system libraries, as the exercise in the previous lesson indicates; building for Windows is just a matter of linking a Windows library in its place). It gets a little more complicated when it comes to computer architecture differences however, which has become more evident recently with Apple switching their Macs to Arm processors instead of Intel x86 ones.
 
==== PickingCompiling thea RightDesktop CompilerProgram ====
The compiler is the program is responsible for translating the source code to the correct assembly language, so it's a good idea to start here. Using the GNU compiler toolchain as an example, when you run <code>gcc</code> on a Linux machine with an x86_64, what is actually being run is x86_64-none-linux-gcc (in a sense, that's why it's not in the monospaced font, because this isn't ''actually'' what happens). For GNU, compiler toolchains roughly follow this naming convention: <code>target_architecture-vendor-ABI</code>, where <code>target_architecture</code> means the architecture you are compiling for (where the compiled code is going to be executed on), <code>vendor</code> is the distributor of the compiler (this part isn't super important, for our purposes this is almost always "none"), and <code>ABI</code> is the '''Application Binary Interface''' of your target.
 
==== Application Binary Interface ====
The Application Binary Interface (ABI) is similar to an API in the sense that it provides a common executable binary interface for programs to use. One part of an ABI that you might be familiar with is the function calling convention. This is what determines the instructions that appear in a function's prologue and epilogue to ensure that no data gets lost when calling a function. The ABI also dictates how the stack behaves. Different operating systems use different ABIs, so you can imagine that it is important to specify this when generating assembly code at compile-time.
 
==== Compiling Our Embedded Program ====
As of time of writing, we use two MCUs: an STM32G0B1RE, and an STM32G431CB. Both of them use a 32-bit ARM CPU, so that is our target architecture. Arm and other companies use a standardized ABI for their embedded processors, called the '''Embedded ABI''' (EABI), and that is the ABI we use. Thus, the name of our compiler is <code>arm-none-eabi-gcc</code> (and now you know where the name comes from).
=== Downloads for Our Board ===
As of time of writing, we use two MCUs: an STM32G0B1RE, and an STM32G431CB. Both of them use a 32-bit ARM CPU, so that is our target architecture.
Ayelovic
34

edits

Retrieved from "https://ramwiki.jeg.fish/index.php/Special:MobileDiff/146"