arduino

ArduinoCore-avr

C2019–2023

arduino / ArduinoCore-avr

ArduinoCore-avr

The Official Arduino AVR core

Hardware & Embedded

Explore on GitHub Read Hacker News discussions

7Distinct people

7Mentions

0Explicit recommenders

1.5KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

The Official Arduino AVR core

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

espressif/arduino-esp32 · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2019-12-09 19:46:58 UTC to 2023-06-28 00:31:41 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	1	1
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	0	0
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	3	3
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	2	2
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	1

What Hacker News says

7 sources

meatmanek·Jun 28, 2023

They've done a good job of hiding the RTOS from you and making most sketches run fine without porting, but you're still running as a task under the RTOS, yielding between loop() calls[1]. This leads to mysterious timing issues if you aren't aware of it[2] It doesn't appear that the Arduino core for the Renesas chip is using the RTOS, at least by default -- its main loop is literally doing while (1) { loop(); }, similar to how the AVR core works. [3, 4] 1. https://github.com/espressif/arduino-esp32/blob/72c41d09538663ebef80d29eb986cd5bc3… 2. https://www.reddit.com/r/esp32/comments/t9aqr6/what_on_earth_is_my_esp32_doing_bet… 3. https://github.com/arduino/ArduinoCore-renesas/blob/149f78b6490ccbafeb420f68919c38… 4. https://github.com/arduino/ArduinoCore-avr/b

Read the rest

lob/eabd762a1edcf076877b7bec28b7f99099141473/cores/arduino/main.cpp#L46

In Arduino Uno R4 WiFi

turbinerneiter·Jun 8, 2022

You don't have to use `setup` and `loop` tough. We use Arduino as a library in C++ using PlatformIO as tooling. Best of both worlds. The thing you are hating on is pretty much this file: https://github.com/arduino/ArduinoCore-avr/blob/master/cores... Arduino is C++ with some boilerplate and a library.

In MicroPython – Python for Microcontrollers

josephcsible·May 30, 2022

Maybe you should go the path that the Arduino UNO and Mega use, and use an ATmega16U2 programmed to do just that. The code they use lives here: https://github.com/arduino/ArduinoCore-avr/tree/master/firmw...

In Really Prolific?

kaszanka·Sep 12, 2021

Yes, Arduino is the library that defines these macros: https://github.com/arduino/ArduinoCore-avr/blob/8f8df161ebf3...

In Using a laser pointer and a matrix LED as a two-dimensional input device (2010)

useryman·May 12, 2021

On Arduinos, it's actually "for (;;)", which surprised me. https://github.com/arduino/ArduinoCore-avr/blob/master/cores...

In Exploring the software that flies SpaceX rockets and starships

Measter·Mar 14, 2021

> You should contribute these improvements upstream then. You honestly think they'd accept changes that would break literally every single library using these functions? Somehow I find that hard to believe. > The Arudino developers are not trying to write slow code on purpose. Of course they didn't. No reasonable person goes out of their way to make a terrible API. That's why I'm confused and irritated about how they managed to do such a bad job. All the inputs are bare integers, pins and mode/state, so you get no warning whatsoever when you get it wrong. I've seen posts from people confused because they tried to digitalWrite pins A6 or A7 on a Nano which is accepted by the compiler and runs, but doesn't work correctly because those pins aren't on a digital port. The other analog pins are on a digital port, so work fine. It gets better. L

Read the rest

et's say I digitalWrite with a pin number higher than 19 on a Nano, what happens? Well, it will start off by doing lookups in its pin tables [0]. How does it do the lookup? It just adds the user's value to the lookup tables' addresses [1], and reads that address. On the Nano, these tables are 20 items long [3]. It's going to read god knows what from your flash, and use whatever gibberish it received to decide what to do! And, because of the need to use inline assembly for the lookups, the compiler can't reason about the data in the tables, and so can't optimize out the lookups, nor can it properly optimize code that relies on those lookups. So the result is it ends up needlessly consuming your limited flash space. And this is an API that's supposed to be used by beginners! Beginners are the ones most likely to get it wrong because they don't know better. They're using a C++ compiler in C++11 mode, they're not stuck in the dark ages! Why use a bare integer to represent the pin, a pin's IO mode, or the pin state, or the analog reference voltage source (which, by the way, also makes no attempt to ensure it's a valid value [4])? At the very least they could have used enum classes instead of bare integers so users get a compiler error when they fuck up. [0] https://github.com/arduino/ArduinoCore-avr/blob/master/cores... [1] https://github.com/arduino/ArduinoCore-avr/blob/master/cores... [2] [2] Because of the separate memory spaces, it has to use inline assembly to do this. The pgm_read_byte macro from the AVR header is what does that here. [3] https://github.com/arduino/ArduinoCore-avr/blob/master/varia... [4] https://github.com/arduino/ArduinoCore-avr/blob/master/cores...

In I Don’t ‘Do’ Arduino

bxparks·Dec 9, 2019

Arduino boards (the ones based on AVR chips) use the GCC C++ compiler adapted for the AVR. The current IDE version 1.8.10 uses avr-gcc-7.3.0 (https://github.com/arduino/Arduino/blob/master/hardware/pack...). The previous IDE version 1.8.9 used avr-gcc-5.4.0. The compiler is configured to follow the -std=gnu++11 variant. Here are the flags: https://github.com/arduino/ArduinoCore-avr/blob/master/platf... If you use other Arduino-compatible boards (e.g. ARM chips, ESP8266 or ESP32), they will use a different C++ compiler and different settings. See for example: * SAMD uses 'arm-none-eabi-g++' (https://github.com/arduino/ArduinoCore-sam/blob/master/platf...) * ESP8266 uses xtensa-lx106-elf-gcc (https://github.com/arduino/esp8266/blob/master/platform.txt) * ESP32 uses xtensa-esp32-elf-gcc (https://github.com/espressif/arduino-esp32/blob/master

Read the rest

/platf...) So Arduino programming is "just" C++ with additional libraries and an IDE. Though I wrote "just" in quotes because they've done a lot of work to make things easier and approachable for beginners, so I don't want to diminish their work.

In Some things every C programmer should know about C (2002)