23

When one selects a board within Arduino IDE, a preprocessor definition is added to one of the behind-the-scenes files.

After a lot of hunting and some good fortune I found that the format of this definition is:

#define ARDUINO_<PROCESSOR-DESCRIPTOR>_<BOARDNAME>

Some are easy to guess (ARDUINO_AVR_UNO, for example), but others are less so. The Pro Micro has '16' or '8' appended to the definition depending on the speed. I do not know if the definition is different for 5V or 3.3V. I haven't managed to guess the definition for the Mega2560, but it isn't anything obvious.

Question 1: Is there a list in existence of the possible definitions?

Question 2: Is there any distinction, as far as compilation and preprocessor involvement is concerned, between BoardX-5V and BoardX-3.3V, and how is this distinction defined?

CharlieHanson
  • 1,430
  • 1
  • 11
  • 25

4 Answers4

17

The list of board symbols can be generated by this shell command:

$ grep board= boards.txt | cut -f2 -d= | sort -u
AVR_ADK
AVR_BT
AVR_DUEMILANOVE
AVR_ESPLORA
AVR_ETHERNET
AVR_FIO
AVR_GEMMA
AVR_LEONARDO
AVR_LILYPAD
AVR_LILYPAD_USB
AVR_MEGA
AVR_MEGA2560
AVR_MICRO
AVR_MINI
AVR_NANO
AVR_NG
AVR_PRO
AVR_ROBOT_CONTROL
AVR_ROBOT_MOTOR
AVR_UNO
AVR_YUN

The boards are defined by the "build.board" property in the boards.txt file.

mini.build.board=AVR_MINI

This property is used by the build recipe together with ARDUINO_-prefix.

-DARDUINO_{build.board}

Cheers!

Community
  • 1
Mikael Patel
  • 7,989
  • 2
  • 16
  • 21
7

Mikael has the right answer, but there are multiple boards.txt files depending on the installed boards with board manager, modifying the command to:

grep board= `find . -name boards.txt` | cut -f2 -d= | sort -u

and running it from your base Arduino directory collects the whole set.

bill
  • 71
  • 1
  • 1
3

The first blank is the platform. This is "AVR" for AVRs, "SAM" for SAM-based Arduinos, etc. This is derived from the platform directory containing the core.

The second blank is the board. This comes from the entry in boards.txt in the core itself, and is the identifier before the first period.

There is no difference between compilation processes with regards to voltages; any speed difference is given in F_CPU and the board itself should not be checked for this.

So there is no definitive list, since the list is of arbitrary size due to its source.

Ignacio Vazquez-Abrams
  • 17,733
  • 1
  • 28
  • 32
0

If you're looking for ESP32 boards this can be achieved using a similar technique to mentioned in other answers but the location of the boards.txt files is different (although using the find, or mdfind on MacOS, command to locate works on unix based systems as mentioned in @bill's answer) - the base directory will be the same but a different sub directory: Arduino15/packages/esp32

If you want a list of only the unique defines then you can use this command:

awk '/board=/ {split($0, a,"=");print a[2]}' `find ~ -path '*/esp32/*' -name boards.txt` | sort | uniq

Or on a Mac it is faster to use mdfind:

awk '/board=/ {split($0, a,"=");print a[2]}' `mdfind -name boards.txt -onlyin ~/Library/Arduino15/packages/esp32` | sort | uniq

The names of the boards can be useful so you list these with this alternate command:

grep 'board=' `find ~ -path '*/esp32/*' -name boards.txt`

Or on Mac:

grep 'board=' `mdfind -name boards.txt -onlyin ~/Library/Arduino15/packages/esp32`
Pierz
  • 109
  • 3