课程详情

Embedded C Development and the need for an IDEEmbedded C Programming consists of writing C based codes and software but for embedded systems and devices, and this requires low level knowledge on how the hardware is working and this low level knowledge must be reflected into our software written code.The problem with such written project is that we need to program, compile then load the binary into the embedded device then finally having live debugging of the executed program.This whole process can be done via some scripts and even very basic command line, but to reach that level we need to have some advanced experience and to have good awareness about all the tools and packages for each of the stages, therefore using User friendly based IDE will allow to abstract all those stages via some simple push buttons to minimize the complexity of building/loading and debugging the embedded C based project.Embedded Systems Based IDEs ExamplesIn term of IDE we are having big variety of them within the market, however some of them requires some ,licensing and some are open sources but requires much more manual configurations and settings to get it to work.IDE with Licenses:Keil-mdk from ARM: has all in one single ide, you can create your project, load binary into target microcontroller and start debug session and even gather code coverage based traces , but the issue the student version of this IDE which can be used without license can handle only 32 KB image size, if you want to load program binary bigger than 32 kb or debug it then it will not work, also the compilers parts of the keil-mdk package (armcc, armclang..) requires licenses as well, plus of course this works only with ARM micro-processors.IAR-workbench: similar to keil-mdk, IAR-Workbench has all in one (project creation, loading, debugging) and can works actually with different processor architecture (not like keil-mdk) , however this is not for free and requires some paid licensing as well.Trace32 from Lauterbach: contrarily to IAR and Keil , trace32 is mainly for debugging and code coverage analysis not for project development, so Lauterbach has chosen totally different path in respect to other competitors, but due to their advanced debugging/coverage features their licensing is quiet expensive and must renewed based on the version of trace32 you are using.OpenSource IDE:MCU Eclipse: MCU Eclipse is used originally to create embedded C/C++ based projects from scratch then having some fancy features to edit your code, format it with different styles..., however to be able to use for loading the generated program into target device and debug what has been compiled then we need first certain Eclipse plugin like OpenOCD, PyOCD, Segger Jlink GDB server.(this is what is so called GDB Server) to interact and initiate different debug commands to target device , then we need a GDB client part of the compiler toolchain itself to provide the list of processor supported features like registers naming, type of breakpoint to be used, some more formatted debug command from user perspective and standardized somehow regardless of the processor in use. But as you can see this is adding extra complexity to setup the whole environment with MCU Eclipse to get it working all in one single IDE.What you learn in this Course?You will get to know the whole flow in term of tooling/packages to compile/load and debug your program in MCU Eclipse.You will get as part of the Course a basic embedded C based makefile project.You will learn how to import your makefile project into eclipse, and expose makefile commands to eclipse.You will be able to setup your fully open source debug configuration using OpenOcd and arm-none-eabi-gdb client in MCU Eclipse.Finally you will be able to load your program into STM32L4 microcontroller, Debug it in Eclipse as well as exploring different hardware resources.So Let's start our new debugging experience with Eclipse!

课程标签

0人关注该课程

主题相关的课程