There has never been an unexpectedly short debugging period in the history of computers
… but the periods might have become shorter with the right tools
There has never been an unexpectedly short debugging period in the history of computers
… but the periods might have become shorter with the right tools
As mentioned in an earlier blog post this year, hardware debuggers are the premier class of embedded debugging tools. However, until today, there were only very few relatively expensive tools around supporting the debugWIRE interface that is used by the classic ATtinys and a few ATmega MCUs.
The good news is that now you can turn an Arduino UNO, Nano, or Pro Mini into a debugWIRE hardware debugger that communicates with avr-gdb
, the AVR version of the GNU project debugger.
The featured image of this post is by Albert Guillaume – Gils Blas, 24 décembre 1895, Public Domain, Link
When you develop a tool for a protocol that is undocumented, it is not surprising that you will encounter situations you will not have be anticipated. This was exactly what I experienced developing the hardware debugger dw-link, which connects debugWIRE MCUs to the GDB debugger. Although a substantial part of the debugWIRE protocol has been reverse-engineered, I encountered plenty of surprising situations: Split personality MCUs, stuck-at-one bits in program counters, secret I/O addresses, half-legal opcodes, and more.
Continue readingThe featured image of this post is is a comic from xkcd.com.
The above xkcd comic, which is titled Debugger, alludes to the concern that when you try to apply a particular method to itself, you might not get what you asked for. Turing’s Halting problem is a very famous example of this, i.e., you cannot algorithmically decide whether an algorithm terminates on an input. So, does that issue apply to debuggers as well? In particular, I asked myself whether it makes sense to debug the hardware debugger I am developing with itself.
Continue readingThe featured image of this post is based on a picture by TheDigitalArtist on Pixabay.
Link-time optimization (LTO) is a very powerful compiler-optimization technique. As I noticed, it does not go very well together with debugging object-oriented programs under GCC, at least for AVR MCUs. I noticed that in the context of debugging an Arduino program, and it took me quite a while to figure out that LTO is the culprit.
Continue readingLubarsky’s Law of Cybernetic Entomology: There’s always one more bug
(Who the hell is Lubarsky?)
The featured image of this post is by Vladimir163rus on Pixabay.
A new Arduino library has seen the light of day: SingleWireSerial
. It supports single-wire, asynchronous serial, half-duplex communication. By using the input capture feature of the AVR MCUs, it is extremely accurate and supports bit rates up to 250 kbps robustly. And contrary to its title, one can even use it in a two-wire setting.
The featured image of this post is by dooder – de.freepik.com
Serial asynchronous communication is one of the most common forms of communication between two electronic devices. Let us see, what Arduino libraries are there to support it, and let us check, how well they perform.
Continue readingThe featured image of this post is by rawpixel.com – de.freepik.com
The SoftwareSerial
class has the available()
method, which returns the number of characters that have been already received but not yet read. This is very similar to what the standard Serial.available()
method offers. There is an interesting difference, though. A call to SoftwareSerial.available()
is significantly slower than a call to Serial.available()
. We will look for the deeper reason for this strange behavior and I will show you three ways how to fix it.
EDIT: The problem will vanish with Arduino version 1.8.17
Continue readingThe featured mage of this blog post is by Gerd Altmann from Pixabay
What is the overhead imposed by the millis()
interrupt? And can we get rid of it?
Copyright © 2023 Arduino Craft Corner
Theme by Anders Noren — Up ↑