In many sources I have ‘inactive’ code: source code which is disabled by some macros or defines. Eclipse is great to ‘gray’ out the inactive parts using its Indexer, but they still need screen real estate:
Don’t get me wrong. I love a good slow-smoked and true BBQ pulled pork shoulder just as probably everyone else out there. And I love the babysitting (aka beer drinking 🙂 ) while the shoulder gets that incredible taste inside the smoker. But my workload for this weekend is insane high with all the university exam and grading work. My family loves that pulled pork too, and I knew upfront that I would not have the time to check and handle the smoking process for 12-18 hours (see “Easter Weekend Apple Juice Brined Pulled Pork Smoked on Beech Wood“). So I decided to prepare pulled pork the ‘easy’ way: Using a Sous Vide cooker and then use a normal oven to finish it. So it was an experiment, and the result is interesting:
I like to have as many lines of source code visible on my notebook or desktop monitor. And I think I have found a good balance between font size and readability.
On the other side: I’m getting older and my eyes are not getting any better. At the same time I noticed that students start using these ‘high-resolution-retina-displays’. They are great, but result in tiny default system fonts, so I have a hard time to read the source code on their machines.
Another challenge I noticed are the high-resolution projectors in class rooms or conferences. They are not well suited to show source code or text files because of the tiny fonts. Starting with Eclipse Neon there is an awesome feature which I can use to dynamically increase and decrease the font size which solves that problem:
For a research project, we are going to send a satellite with an embedded ARM Cortex microcontroller into space early next year. Naturally, it has to work the first time. As part of all the ESA paperwork, we have to prove that we tested the hardware and software thoroughly. One pice of the that is to collect and give test coverage evidence. And there is no need for expensive tools: Free-of-charge Eclipse and GNU tools can do the job for a space mission 🙂
To celebrate the end of that sunny weekend, we smoked tuna and salmon with a simple soy-based brine:
The GNU tools include powerful utilities to collect coverage information. With coverage I know which lines of my code have been executed, which is a very useful test metric. The GNU coverage tools are commonly used for Linux applications. But to my surprise not much for embedded application development, mostly because it requires a few extra steps to have it available? Why not using free and powerful tools for improving software quality? This article explains how to install the GNU gcov tools into the Eclipse IDE.
BLE (Bluetooth Low Energy) sensor devices like the Hexiwear are great, but they cannot store a large amount of data. For a research project I have to collect data from many BLE devices for later processing. What I’m using is a Python script running on the Raspberry Pi which collects the data and stores it on a file:
For many projects it would be cool to build a custom USB Joystick device, either as custom game controller for Windows or any USB host which can be used with a USB Joystick. Instead buying one, why not build my version? All what I need is a USB capable board, some kind of input (potentiometer, push buttons) and some software, and I have my USB Joystick:
In “Cycle Counting on ARM Cortex-M with DWT” I have used the ARM DWT register to count the executed cycles. With the MCUXpresso IDE comes with a very useful feature: it can capture the ARM SWO (Single Wire Output) trace data. One special kind of trace data is the ‘cycle counter’ information which is sent through SWO.