Upgraded to Win10 digispark not compiling

Using Arduino IDE 1.x
1

Using board 'digispark-tiny' from platform in folder: C:\Users\Daniel\AppData\Local\Arduino15\packages\digistump\hardware\avr\1.6.7
Using core 'tiny' from platform in folder: C:\Users\Daniel\AppData\Local\Arduino15\packages\digistump\hardware\avr\1.6.7
Detecting libraries used...
"C:\Users\Daniel\AppData\Local\Arduino15\packages\arduino\tools\avr-gcc\4.8.1-arduino5/bin/avr-g++" -c -g -Os -w -fno-exceptions -ffunction-sections -fdata-sections -w -x c++ -E -CC -mmcu=attiny85 -DF_CPU=16500000L -DARDUINO=10607 -DARDUINO_AVR_DIGISPARK -DARDUINO_ARCH_AVR "-IC:\Users\Daniel\AppData\Local\Arduino15\packages\digistump\hardware\avr\1.6.7\cores\tiny" "-IC:\Users\Daniel\AppData\Local\Arduino15\packages\digistump\hardware\avr\1.6.7\variants\digispark" "C:\Users\Daniel\AppData\Local\Temp\arduino-sketch-248AB8D9132DD55E0266B4FC71735C08\sketch\DigisparkRGB.ino.cpp" -o nul
In file included from C:\Users\Daniel\AppData\Local\Arduino15\packages\digistump\hardware\avr\1.6.7\cores\tiny/Arduino.h:4:0,
from C:\Users\Daniel\AppData\Local\Temp\arduino-sketch-248AB8D9132DD55E0266B4FC71735C08\sketch\DigisparkRGB.ino.cpp:1:
C:\Users\Daniel\AppData\Local\Arduino15\packages\digistump\hardware\avr\1.6.7\cores\tiny/WProgram.h:8:27: fatal error: avr/interrupt.h: No such file or directory
#include <avr/interrupt.h>
^
compilation terminated.
Alternatives for avr/interrupt.h: []
ResolveLibrary(avr/interrupt.h)
-> candidates: []

exit status 1

Compilation error: exit status 1

2

Do you need the core for digispark-tiny (via Boards Manager >> enter digispark-tiny >> install)?

3

I do not understand

4

That's okay, I will explain.

Each board needs a "core" (read about cores later). Your board is Digispark-Tiny (first line of text). To find the core for your board, open the TOOLS >> BOARDS MANAGER (IDE 2.0.3 - click the BOARDS icon on the left). After the Boards Manager opens, type "digispark-tiny" in the search bar. You will see a "core" written by Konde Spence (or Spence Konde). Click the "install" button in the description. CLOSE then OPEN your IDE. Open your sketch and compile it.

5

@xfpd the "core" (the correct term is actually "platform", but everyone uses "core" instead) that provides support for the DigiSpark board is named "ATTinyCore".

From the output @dandav shared, I can tell they are using the platform from DigiStump, the manufacturer of the DigiSpark board:

6

Okay. I have the wrong understanding of platform. Would that be the mcu (for the ATtinycore)? Other? I will search platform v core. If you have a favorite, i would like to read it. Did Konde write that (after Drazzy?) Thank you.

[late edit here]
I struggle with not calling these things "cores" when "core" is in their names and descriptions... but I will adapt.
[End edit]

7

Documentation of cores here:

https://arduino.github.io/arduino-cli/latest/platform-specification/#cores

As an example, this folder contains the ATTinyCore platform's core:

https://github.com/SpenceKonde/ATTinyCore/tree/v2.0.0-devThis-is-the-head-submit-PRs-against-this/avr/cores/tiny

And this folder contains the "core variants":

https://github.com/SpenceKonde/ATTinyCore/tree/v2.0.0-devThis-is-the-head-submit-PRs-against-this/avr/variants

The "core" is only one of several components of a "platform", so even though a platform contains a "core", calling a platform a "core" is confusing because a strict interpretation would indicate the specific component of the platform is being referred to, but we might infer from the context of the discussion that it is really referring to the entire platform.

The other components of a platform:

A boards.txt file where the boards are defined.

Documentation: https://arduino.github.io/arduino-cli/latest/platform-specification/#boardstxt
Example: https://github.com/SpenceKonde/ATTinyCore/blob/v2.0.0-devThis-is-the-head-submit-PRs-against-this/avr/boards.txt

A programmers.txt file where the programmers are defined.

Documentation: https://arduino.github.io/arduino-cli/latest/platform-specification/#programmerstxt
Example: https://github.com/SpenceKonde/ATTinyCore/blob/v2.0.0-devThis-is-the-head-submit-PRs-against-this/avr/programmers.txt

A platform.txt file where the compilation, upload, and burn bootloader commands are configured.

Documentation: https://arduino.github.io/arduino-cli/latest/platform-specification/#platformtxt
Example: https://github.com/SpenceKonde/ATTinyCore/blob/v2.0.0-devThis-is-the-head-submit-PRs-against-this/avr/platform.txt

"Platform bundled" libraries.

Documentation: https://arduino.github.io/arduino-cli/latest/platform-specification/#platform-bundled-libraries
Example: https://github.com/SpenceKonde/ATTinyCore/tree/v2.0.0-devThis-is-the-head-submit-PRs-against-this/avr/libraries

Bootloader binaries: https://github.com/SpenceKonde/ATTinyCore/tree/v2.0.0-devThis-is-the-head-submit-PRs-against-this/avr/bootloaders

To make matters even more confusing, a platform can reference components from other platforms, including the core:

https://arduino.github.io/arduino-cli/latest/platform-specification/#referencing-another-core-variant-or-tool

So many platforms don't even contain a core, yet they are still referred to as a "core". Arduino is just as bad about this incorrect use of terminology as the community. You will find the incorrect use of "core" throughout much of the official documentation. It is really sad because this is a very complex subject matter regardless, but this ambiguity makes matters even worse.

8

Thank you,
Your information WORKED.... :smiley:

Very much appreciated...

9

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.