AVR Datasheet Note: Blink

Calendar September 13, 2021
C, ATmega328, Arduino

Where I use a detailed analysis of the ATmega328P datasheet to develop C code using the C toolchain. Yes, another look at the blink program!

Sources#

Introduction#

You’ve installed the tool chain, you’ve tested it and added automation. This means you are now ready to begin the process of learning how to program an embedded microcontroller! You might have thought, that was what you were doing with the Arduino. Not quite, you were programming a specific embedded microcontroller board with a specific programming framework.

Developing in C for the ATmega328P: Commentary

Calendar September 11, 2021
C, ATmega328, Arduino

Where I discuss the process of developing in Standard C (and only C) on the Arduino Uno (also known as the ATmega328P).

Introduction#

This series is designed to help someone who has been using the Arduino framework, however, desires to use only the C Language. It covers adding the toolchain to your system of choice, executing the toolchain on examples and (possibly) advancing the ability to debug using a hardware debugging tool. Or stated more formally:

Developing in C on the RP2040: First

Calendar September 1, 2021
C, RP2040, Pico

Where I explain the issues which impact developing C/C++ code on the RP2040.

Sources#

Introduction#

There are three fundamental steps one must take to fully develop C/C++ code on the RP2040. Both the Raspberry Pi “Getting Started with Pico” known as the Guide from here on and this blog utilize this approach:

  1. Install the tool chain necessary to cross-compile C/C++ and link code for the RP2040 on the platform of choice.
  2. Test #1 using the Raspberry Pi Pico Github code using the pico-sdk and pico-examples.
  3. Advance the ability to debug by adding a hardware debugger in the form of the Picoprobe and gdb.

For each of the platforms, there is a level of complexity to accomplish each step. Its important to understand that the tools that exist to accomplish cross-compiling and linking C/C++ for an embedded microcontroller are designed for Linux. Therefore, the closer a system “looks like Linux”, the easier it is to follow the three steps. This isn’t a problem. It is simply something to understand and account for. Specifically, the level of difficulty of the three steps in each operating system is:

Developing in C on the RP2040: Windows

Calendar August 31, 2021
C, RP2040, Pico

Where I begin to develop code in C on the RP2040 in the Windows environment.

Sources#

Download Sources#

Introduction#

If you haven’t read it, please read Read This First… before you continue.

As I have said before, I do not like to use VS Code, nor do I believe that it is a good tool for students beginning to learn how to develop embedded C. My approach will be to follow that of Shawn Hymel’s without the VSCode part as well as what has already been published via the Guide. In the place of VS Code, we will use Notepad++.

Developing in C on the RP2040: New Project

Calendar August 25, 2021
C, RP2040, Pico

Where I demonstrate bringing up a new project in C on the PR2040 including embedding project information in the binary.

Sources#

Introduction#

You have played with the examples the Raspberry Foundation has thoughtfully provided. Now you want to create something on your own! I like the information provided by the Foundation as to how to create a project and how to add easily binary information to the binary code of project. This means you can build a project, write pin information to the binary and then pick up the board weeks(months?) later and determine what is on the board and how to use it.

Debugging in C Code on the RP2040: Using gdb - Hints

Calendar August 22, 2021
C, RP2040, Pico, Gdb

Where I provide hints on using gdb to debug code on the RP2040 (Pi Pico board).

Sources#

gdb Hints#

  1. gdb recommended in its screen feedback to use “target extended-remote :3333” instead of the Guide’s “target remote localhost:3333”. I found that this seemed to solve some of these inconsistencies, so I updated my instructions. After a bit of reading “extended-remote” does seem to be the right instruction. Note: If using Bloom and avr-gdb, extended doesn’t serve a purpose, use target remote:1442.
  2. If you find your self executing a lengthy command quite a bit (such as “monitor reset init”), use “define” to create a shorter command for it. If you put it into the .gdbinit file (as I have), it will remember from session to session.
  3. gdb can be incredibly easy to use. Norman Matloff’s tutorial is great for illustrating the commands needed. I recommend reading and practicing with it, its well worth it!
  4. Start with using gdb to replace printf statements. Run code, have it stop by using a “breakpoint function name” or “breakpoint line number”, then use “print” or “display” to get the values of variables. This will work the same as inserting print statements, however, it doesn’t affect your code.
  5. It took me less time to learn gdb, and write these two tutorials than the time I spent attempting to debug Visual Studio Code. Your mileage may vary, however, a simple gdb/code editor setup is fast and easy to learn and use.
  6. If your code ends, you will see “exit(status=0)….”. To restart the program, simply issue a “mri” (a command from .gdbinit) which will reset the processor. Press “c” and the program will begin running again.
  7. gdb operates in at least two modes:
    • command, indicated by (gdb) prompt. This is where you will enter all of the commands to interact with gdb
    • execution, indicated by a lack of a (gdb) prompt. This means the program is running and hitting a breakpoint or watchpoint will return you back to command mode. Or you can hit Ctrl-C which will interrupt the process and put into command mode.
  8. Enter the command layout src or start by using gdb –tui and the window will divide into two horizontal windows. The top window will show 20 lines of source and the bottom window will continue to be the command window. This is a great way to view a breakpoint. For example, set a breakpoint on a function name, then “n(ext)” through the code to view execution. Once you have entered “n”, you can simply hit the return key and it will advance using the next command.
  9. Note found elsewhere, I’ll link to it when I find it: “remember to use -g only for the image you pass to gdb, not the firmware you load into the device (if it can grok elf). Also another very critical prerequisite for C programs is -O0 (which is usually default). But if you use -Os or something, you can get very unpredictable debugging results. This btw. makes debugging some code on avrs for example almost impossible, as they often rely on -Os to fit the image in there. But.. it is very possible and comfy to debug simple optimized C programs in assembly, if you know roughly what to expect. Use objdump -dS on the optimized .elf file with debugging info and you’ll roughly see what assembly code was produced for what C code.”

Debugging in C Code on the RP2040: Using gdb - Setup

Calendar August 21, 2021
C, RP2040, Pico, Gdb

Where I show a simple method of using gdb to debug code on the RP2040 (Pi Pico board).

Sources#

Setup .gdbinit#

The Guide recommends at the very least, add “target remote localhost:3333” to your .gdbinit file. To make our edit/compile/link/load round trip easy, I recommend the following for your .gdbinit:

Developing in C on the RP2040: Linux

Calendar August 20, 2021
C, RP2040, Pico

Where I begin to develop code in C on the RP2040.

Sources#

Introduction#

I like using Forth to develop code on embedded microcontrollers, however at times, I’ll have a project that requires a more supportive framework. In this case, C is a superior choice if I need the execution speed of Forth and the framework of microPython. This requires a significant investment in building the tools required and skills to use those tools, to develop in C.

gdb Resources

Calendar March 20, 2021
C, RP2040, Pico, Gdb

All of the resources found related to gdb (particularly, related to the RP2040) and how to use it.

GNU gdb documentation#

gdb Tutorials#

Cheat Sheets#

Tools to enhance gdb#

AVR gdb#

AVR gdb Notes#

  1. Check the version number on avr-gdb as of December 2021, it is 11.1. On Ubuntu, the latest version is 8.1 from 2018 which had quite a few bugs. Attempted to build it manually (which failed), so I spun up a Manjaro (Arch Linux) instance to get the latest. Crazy, I know.
  2. Start avarice in a separate window using, then launch gdb in another window: 
    avarice -g -w -d -P atmega328p :3333 	# window 1
avr-gdb -tui							# window 2
  3. If avarice crashes on startup, cycle power on both the debugger (Dragon) and the target (Uno)

Pico (RP2040) gdb#

Developing in C on the AVR ATmega328P

Calendar March 4, 2021
Arduino, ATmega328, C, Content

Introduction#

While the Arduino tool set, (both the Arduino IDE and Arduino software framework) are outstanding for quickly developing a working prototype, they do so with a combination of a graphical-user-interface (GUI), the C++ language and Arduino-only classes. This in itself, isn’t a problem, one can be quite efficient and productive using this approach.

This approach is an issue if you are at a university or job which expects a standards-based C language proficiency. It is also an issue, if your class or job, requires understanding how to use command-line-interface (CLI)-based tools. The C language, and not C++, is the basis of a significant number of embedded systems development.

Wellys Dev - Lief Koepsel