Git is now my favorite version control system. Git and GitHub are very powerful, it has (nearly) all features I can think about, and best of all: As a distributed version control system, I can work with it, even if disconnected from the network :-).
There are many standalone and IDE integration available for Git. Beside of using TortoiseGit, I’m using the eGit Eclipse integration. This post is about how to install eGit in Eclipse, particularly in CodeWarrior for MCU10.4.
So far I have covered in this tutorial series how to install ARM GNU gcc, adding Eclipse, followed by adding GNU GDB debugger, and then adding Processor Expert. I’m using FreeRTOS a lot in my projects, and luckily there is a Kernel Awareness Plugin available for FreeRTOS for GDB in Eclipse. This tutorial is about how to install and use it.
I covered in a previous tutorial how add ARM gcc to Kepler Eclipse to build a DYI toolchain. I’m using Processor Expert a *lot* in my project, because it simplifies and speeds up the development of my embedded applications. What is missing so far is how Processor Expert can be added to Eclipse. As Kepler is as of this writing the latest Eclipse version, this tutorial is using that version.
I love to have my sources ‘warning free’, so I spend an extra effort to have things clean and the way the compilers like it. In a similar way, I want to have my source comments spell-error free :-). For this, I love the Eclipse spell checker (see this post) which offers to add unknown words to the dictionary:
Add word to dictionary
But what if that ‘Add’ action is missing? How to re-enable it?
This is the third part of a tutorial series how to ‘do-it-yourself’ a tool chain for the Freescale Kinetis microcontroller, with the FRDM-KL25Z as example. The tool chain is using GNU ARM gcc plus Eclipse Kepler release. So far I have the following parts:
So far things are very generic. But with debugging it means different hardware, and different hardware connections. And for this connection we need a GDB Server.
Eclipse CDT features a GNU Debugger (GDB), and this is what I want to use here: debugging my microcontroller with GDB inside Eclipse. In order to debug the microcontroller, I need two other things: a GDB Server and a Debug Probe.
After my first post using a Bluetooth module, things have evolved a bit. The challenge with these Bluetooth modules is: they look the same, but having different firmware. I did not fully realize that until I have ordered another bluetooth module from dx.com:
DX.com Bluetooth Module (HC-06)
That module comes already on a carrier, so I assumed I can use the same driver as for my other module. I was wrong :-(.
Having many projects open the same time, and working on them in parallel is a challenge. Ok, the human brain is not built for multitasking, but I still try ;-). What I typically I end up in my Eclipse Problems View to have entries from multiple projects mixed up:
Problems View with Entries for multiple Projects
How to show it that I can fix the problems for ony project only, and not showing all problems from all projects?
I stumbled now twice over a problem, and only after a lot of head scratching (you should see my head now ) I have found the cause (and solution) for it. In the hope that I can save the readers of this blog some time, here is what happened.
If you are following my recent posts, then you know I started using USBDM on OpenSDA as an alternative run control solution. Now with the advent of MCU10.4, the question is: how to use USBDM with it, because the USBDM installer obviously only knows the version up to MCU10.3?
Freescale has released this week an updated version of CodeWarrior: version 10.4. I’m usually not switching a tools version in the middle of a university semester. Unless I see a real benefit, and the risk is low. Well, I have used it now for a few days, and I have decided to move my projects from 10.3 to 10.4. Why? Read on…