August 17, 2026
Where I continue to discus how to debug code on the ATtiny13A on a Linux computer using the Microchip Snap, bloom, avr-gdb and gdb-dashboard. This entry goes into a detail as to how I like to use avr-gdb, Bloom and a customized window from gdb-dashboard to debug the ATtiny13A.
The code for this article and other articles on the ATtiny13A can be found in the ATtiny13A repository. Additional detail and files for implementing this aproach can be found ATtiny/docs/gdb_dashboard.
June 16, 2026
Where I continue to discus how to debug code on the ATtiny13A on a Linux computer using the Microchip Snap, bloom and avr-gdb. This entry goes into a little more detail as to how to use gdb along with Bloom to debug the ATtiny13A.
The code for this article and other articles on the ATtiny13A can be found in the ATtiny13A repository.
avr-gdb ──► Bloom ──► SNAP ──► ATtiny13A
(TUI in a (debugWire ↔ (debugWire over RESET)
terminal) GDB server,
Linux only)The recommended front end is avr-gdb’s built-in terminal TUI, optionally alongside Bloom’s Insight GUI for registers/peripherals/memory. Two heavier frontends — gdbgui (browser) and Sublime + DAP — were explored and rejected; see Explored and rejected for why, so the dead ends aren’t re-walked.
June 11, 2026
Where I describe the process of developing serial communications for the Microchip ATtiny13A.
Even with a microcontroller with limited capabilities as the ATtiny13A, it is desirable to have the ability to communicate via the serial port. The ATmega328P and others have a UART built-in which makes it much easier to integrate serial communications. With the ATtiny13A, serial communications must be performed completely in software and using assembly language makes it possible and reliable.
June 11, 2026
Where I describe the process of writing and debugging a multitasking program for the Microchip ATtiny13A.
To get the most of any microcontroller, its best to have a framework for multitasking and to ensure it will be as efficient as possible, write it in assembly code. The second aspect to developing the code is debugging it. Which can be problematic, particularly on a chip with limited resources such as the ATtiny13A. This post covers both the code for multitasking and a clever way to determine which tasks are running and for how long.
June 7, 2026
Where I illustrate how to develop and debug code on the ATtiny13A on a Linux computer (Raspberry Pi) using the Microchip Snap, bloom and avr-gdb.
The code for this article and other articles on the ATtiny13A can be found in the ATtiny13A repository.
As mentioned previously, I’ve moved from a multi-platform approach to using a Raspberry Pi (RPi) for my development system. I use it as a headless system, meaning, I connect to the RPi using ethernet or wireless from my Mac. All code editing occurs in VS Code on my Mac, while all debugging is performed via the terminal. Both VS Code and the terminal are connected via SSH to the RPi.
May 30, 2026
Where I describe the differences between the industry standard AVR microcontroller (ATmega328P), star of the Arduino Uno R3 and a minimal version of an AVR microcontroller, the Microchip ATtiny13A.
Why is this comparison important?
It is helpful to understand that this chip is significantly less capable than the chip used by the Uno. That said, it perfect for projects which need a “little bit of intelligence”, and only, three inputs and three outputs.
May 28, 2026
Where I describe the process of developing code for the Microchip ATtiny13A, starting at the chip level.
This is a series of posts describing how to develop at the chip level using both, assembly language and C. In this series, I’ll be using a Microchip ATtiny13A, which is a minimal (tiny!) version of an ATmega328P, the microcontroller used in the Arduino Uno R3.
The code for this article and other articles on the ATtiny13A can be found in the ATtiny13A repository.