-
Commit 6d001778e43a4c5373cdbaec8e4eceea6c0f04bb breaks this library for attiny85, at328p and atmega32u4, and probably all non ESP boards.
I get the following errors
```
.piolibdeps/Manchester/Man…
-
```
Summary: when calling analogWrite() with values 0 or 255, it defaults to
analogWrite() which leaves PWM registers in the previous state, and the next
analogWrite() starts with a "glitch", very n…
-
```
Summary: when calling analogWrite() with values 0 or 255, it defaults to
analogWrite() which leaves PWM registers in the previous state, and the next
analogWrite() starts with a "glitch", very n…
-
```
Summary: when calling analogWrite() with values 0 or 255, it defaults to
analogWrite() which leaves PWM registers in the previous state, and the next
analogWrite() starts with a "glitch", very n…
-
```
Summary: when calling analogWrite() with values 0 or 255, it defaults to
analogWrite() which leaves PWM registers in the previous state, and the next
analogWrite() starts with a "glitch", very n…
-
```
the current core definitions are huge walls of code with ifdefs sprinkled in
between: very hard to follow.
I actually did this already, though I only tested that the "Fade" example
sketch compi…
-
```
the current core definitions are huge walls of code with ifdefs sprinkled in
between: very hard to follow.
I actually did this already, though I only tested that the "Fade" example
sketch compi…
-
```
the current core definitions are huge walls of code with ifdefs sprinkled in
between: very hard to follow.
I actually did this already, though I only tested that the "Fade" example
sketch compi…
-
```
the current core definitions are huge walls of code with ifdefs sprinkled in
between: very hard to follow.
I actually did this already, though I only tested that the "Fade" example
sketch compi…
-
```
the current core definitions are huge walls of code with ifdefs sprinkled in
between: very hard to follow.
I actually did this already, though I only tested that the "Fade" example
sketch compi…