Eclipse as IDE takes care about compiling and building all my source files. But in an automated build system I would like to build it from the command line too. While using make files (see “Tutorial: Makefile Projects with Eclipse“) is an option, there is another easy way to build Eclipse projects from the command line:
Building MCUXpresso IDE from Command Line
This hike has been on my ‘must-hike’ list since last summer, and when I saw Urška writing about recently, it got definitely on my top list of things. The Oeschinen Lake (German: Oeschinensee) is a beautiful lake in the Bernese Overland, Switzerland, east of Kandersteg, and is a UNESCO World Heritage Site:
Oeschinensee view from Heuberg
Last month (June 2017), the latest version of Eclipse “Oxygen” has been released, and I have successfully used it in several embedded projects. Time to write a tutorial how to use it to build a custom Do-It-Yourself IDE for ARM Cortex-M development: simple, easy, unlimited and free of charge. While the DIY approach takes a few minutes more to install, it has the advantage that I have full control and I actually know what I have.
Eclipse Oxygen
Sometimes it happens that arm-none-eabi-gdb complains about “no source file named” in the GDB console view in Eclipse when I debug a project with GDB:
No Source File Named in GDB Console
I love 3D printing as it enables me to create custom enclosures for all kind of projects. The NXP LPC-Link2 probe is great, but it lacks a protective enclosure. So I decided to create a custom enclosure. And as 3D filaments are available in different colors, I experimented with red and black and custom painting:
lpc-link2 enclosure
FreeRTOS seems to get more and more popular, and I think as well because more and more debugger and Eclipse IDE vendors add dedicated debugging support for it.
FreeRTOS Threads in Eclipse
Good news! There is an updated version of the EmbSysRegView v0.2.6 available which works now for Eclipse Neon and Oxygen :-).
EmbSys
So we prepared a hiking trip the day before. The weather forecast said “mostly sunny”. Only to find out that the weather was not that great in the morning. Yes, true: Technically the sun is shining, at least above the clouds:
Mostly Sunny? A good day for a hiking tour!
By default, the GNU Linker expects a very special naming scheme for the libraries: the library name has to be surrounded by “lib” and the “.a” extension:
lib<NAME>.a
But what if the library I want to use does not conform to that naming standard?
Non-conforming Library Naming
The benefit of an IDE like Eclipse is: it makes working with projects very easy, as generates make files and it takes and automatically manages the make file(s). But sometimes this might not be what I want because I need greater flexibility and control, or I want to use the same make files for my continues integration and automated testing system. In that case a hand crafted make file is the way to go.
One thing does not exclude the other: This article explains how to use make files with Eclipse with similar comfort as the managed build system in Eclipse, but with the unlimited power of make files:
Makefile Project with Eclipse
MCU on Eclipse 