It happens to me many times: I’m stepping with the debugger through my code, and ups! I made one step too far!
What now? Restart the whole debugging session?
Actually, there is a way to go ‘backwards’
I’m using Version Control Systems like Git and SVN on a daily base. Because this gives me the opportunity to revert my changes and go back in time in my project. A VCS is incredible useful as well if I have deleted files or settings: restoring it is just a matter of a few mouse clicks.
But even without using a VCS, Eclipse has a built-in simple version control system: the Local History.
If you are a frequent reader of this blog, then you know: I’m a big fan of Processor Expert components. While there are many Processor Expert components delivered with CodeWarrior, it lacks many components and device drivers beside of the normal on-chip peripherals. But value gets added to an embedded project with all the external devices, sensors and actuators. That’s why I have created many more components which are available on my GitHub site. Readers of this blog have asked several times to create a tutorial on how to create a Processor Expert component. So why not working on that on a long Easter weekend full of cold rain and snow?
Many times I have Processor Expert components carefully configured in one project, and then I want to have the same thing in another project. There is actually an easy way to carry out this: to copy components from one project to another.
Using a version control system for software development is a standard procedure today. While things are pretty clear for ‘standard’ Eclipse projects, it is not that easy for Processor Expert projects. I’m using Processor Expert projects with Git and SVN (Subversion). I want to share here tips how to use Processor Expert projects with a version control system. Screenshots and vocabulary are for TortoiseGit and Git, but applicable to any other VCS (Version Control System).
Maybe this article gets the attention of a local optometrist or eye shop: I have a business opportunity for you! .
I ran into a weird problem: I received an ARM GNU gcc project which failed during the generation of the S19 file in strange way:
'Executing target #80 Freedom_Zumo.siz' 'Invoking: ARM Ltd Windows GNU Create Flash Image' “C:/Freescale/CW MCU v10.3\eclipse\../Cross_Tools/arm-none-eabi-gcc-4_7_3/bin/arm-none-eabi-objcopy” -O srec Freedom_Zumo.elf "Freedom_Zumo.hex" ' ' Der Befehl "“C:" ist entweder falsch geschrieben oder konnte nicht gefunden werden. mingw32-make: *** [Freedom_Zumo.hex] Error 1
Probably I need to add 3rd monitor to my laptop system, or maybe I’m not organized enough. But as a matter of fact: I want to have as many source files as possible open in Eclipse. But there is simply not enough screen real estate to show them all:
With that many source files open, I need an effective way to switch between the files.
Sometimes I’m looking for a functionality, and I cannot find it. But this does not mean that it does not exist .
The Eclipse preference pages have a great filter text field: If I want to change a setting which has something to do with ‘color’, I can enter that text and it will show me all setting pages having something to do with ‘color’:
The challenge with small microcontroller like the ARM-Cortex-M0+ is that they have very limited debugging resources. As such, the number of hardware break points is very limited (see this post). For example for the KL25Z on the Freedom board, I only have 2 break points available if I want to do stepping: