As outlined in my earlier post about hiding the toolbar: it is important to me that I have a flexible way to use my screen real estate. There is another thing I need frequently: I’m using a small Eclipse window like this one:
Screen real estate is important to me. Especially working on a small notebook screen I want to get the most out of it. And I know: all the cool (and fancy) UI items in Eclipse have a price.
So how to get more space for important things like my source files? Eclipse has feature to hide the toolbar completely. For this I simply use the context menu and select ‘Hide Toolbar’: Continue reading
Typically a Processor Expert component creates two files: a header file and a source file. That’s fine for normal drivers. But this does not work well for more complicated things like an RTOS or communication stacks: these are built from a whole set of source files. So how can I generate multiple files with a Processor Expert Component?
Exactly the thing I was looking for! A small and affordable 32bit board with easily accessible microcontroller signals. The Freescale Tower boards are great, but the PCI Express connectors are not that ideal. I love that normal Berg connectors 🙂
When I added ‘support for ARM/Kinetis‘ to my bucket list in my Percepio+Trace post, I knew it will not be straight forward. But it was a lot harder than I thought. I had to burn many week-end hours. But finally I have Percepio Trace with FreeRTOS up and running for Kinetis and ARM Cortex-M4 with CodeWarrior for MCU10.2 :-).
As promised back in Percepio, I want to have it ported and working with the Freescale Cortex-M4/Kinetis in CodeWarrior. That’s what I’m working on now, deep into the night. While doing this, I had to generate a lot of trace data, and I used the script I presented in that earlier post: Setting a breakpoint in the trace buffer wrapper event and then export the data. But there has to be an even better way, and indeed there is one: Breakpoints with Special Effects!
I have received a new touchscreen, and all what I want to do with it in the next weeks is to get it up and running with one of my Tower modules. Touchscreens are such a great thing, not only because of Apple, iPad and all the other tablet providers. It is such a great and intuitive way to communicate with machines. And here is a great article I got forwarded at the University right on that subject:
Apes with Apps: IEEE Spectrum Article
Apes with Apps is about how Apes (Bonobos, to be exact) are great communicators with tablets and touch screens. Worth reading.
Happy Touching 🙂
I’m chasing down a weird include problems in my project: Somehow it looks like the compiler is including the wrong file, causing strange compiler errors. I admit: the include order with all the #defines is pretty complicated, most of it I have inherited from an open source project. How to know who is including what, which files is included by whom? what is included directly, and what is included indirectly?
Writing Processor Expert components is not always completely independent of the compiler and underlying microcontroller. In many cases I need to know the compiler for which the source code is generated. Or I need to know on which CPU architecture the code shall run. For this I need to know the compiler and the CPU family.
If I’m debugging my application in Eclipse or CodeWarrior, it shows in the Variables view the local and global variables of the current Thread and stack frame only:
Debug View with Variables View
This makes sense as this is usually where my focus is. And this is good from a performance point of view: The debugger does not need to read a lot of other variables from the target which I’m not interested in. But the question is: how to show the variables which are in other files if I really need to look at them?
MCU on Eclipse 