SWO (Serial Wire Output) is a cool feature defined by ARM as part of the CoreSight debug block. However, not every debug connection supports SWO, as it requries extra pins routed from the microcontroller to the debug JTAG/SWD header.
If I’m using the Segger J-Link, and if my hardware does not support SWO, I will get a dialog telling me “The connected emulator does not support serial wire output (SWO).”
The connected emulator does not support serial wire output (SWO)
In “tinyK20 Open Source ARM Debug/Universal Board – First Prototypes” I talked about using a USB thumb drive enclosure for the board, so here is the idea:
Thumb Case for tinyK20
In case you face problems with launching GDB: Then I have a quick solution (well: workaround): kill the GDB server and or client process. The problem can show up in many way, but in general gdb is stuck or does not respond:
GDB stuck?
But it could be an error message like this too:
Error in services launch sequence Starting J-Link GDB Server timed out.
Students worked hard implementing their robots for the coming Sumo battles. Amazing looking Sumo Robots are the result :-). Have a look yourself:
Fat Bastard
Happy Sumoing 🙂
After the proof of concept phase (see “Proof of Concept: Open Source ARM SWD Debug and General Purpose Board“), the first prototypes are ready:
Two tinyK20 Boards
Tired of my tech articles? Too much geeky Eclipse stuff? Well, then I have something completely different for you: Smoking Baby Back Ribs! No electronics, no microcontroller, no software: only heavy metal, fire wood, meat and beer :-).
❗ WARNING: this post shows raw meat and alcoholic beverages! You are only allowed to continue reading if you are 18 years or older 😉
BBQ Ribs
Wondering why the Eclipse Project view might not show all files in the Project Explorer view? For example it shows this:
Eclipse Project Explorer View
But on disk I have more files? Where are they?
The FRDM-K64F board as other Freescale Freedom board have an onboard debugging device. For everyone who wants to debug the FRDM-K64F board with say a P&E Universal Multilink, here is my setup in case you do not get it working out of the box:
FRDM-K64F with P&E Multilink (click to enlarge)
I very much liked the CodeRed Eclipse based IDE (see “Red Suite 5: Eclipse Juno, Processor Expert and unlimited FRDM-KL25Z“). But back in May 2013 CodeRed was acquired by NXP. I have not used much NXP devices for my projects, and as CodeRed was focusing on the NXP parts, CodeRed was not running daily on my desk any more :-(. Well, things might make a full back circle, as NXP announced back March 1st 2015 to acquire Freescale :-). And maybe as a taste how things might come out, the GNU ARM Eclipse plugin release from March 22nd 2015 includes a CodeRed debug view 🙂 🙂
CodeRed Debug Perspective in KDS
That debug perspective mimics a CodeRed debug perspective. The advantage of this Eclipse perspective is that it works very well with small screens. This post is about adding this perspective to the recently release Kinetis Design Studio v3.0.0.
What I love with Eclipse: it has lots of small and useful features, either built-in or available as plug-in. Recently I started to use a feature which is present in Eclipse for some time: the ability to save screen real estate during debugging with the ‘breadcrumb’ view option:
Expanded Breadcrumb View
MCU on Eclipse 