Changelog

This page documents (nearly) all bugfixes and enhancements that produce visible changes in behavior throughout the history of megaTinyCore. Note that this document is maintained by a human, who is - by nature - imperfect (this is also why there are so many bugs to fix); sometimes the changelog may not be updated at the same time as the changes go in, and occasionally a change is missed entirely in the changelog, though this is rare. Change descriptions may be incomplete or unclear; this is not meant to be an indepth reference.

Changes not yet in release

Changes listed here are checked in to GitHub ("master" branch unless specifically noted; this is only done when a change involves a large amount of work and breaks the core in the interim, or where the change is considered very high risk, and needs testing by others prior to merging the changes with master). These changes are not yet in any "release" nor can they be installed through board manager, only downloading latest code from github will work. These changes will be included in the listed version, though planned version numbers may change without notice - critical fixes may be inserted before a planned release and the planned release bumped up a version, or versions may go from patch to minor version depending on the scale of changes.

Planned 2.5.x

Ongoing

Port enhanced documentation from DxCore.

2.5.5

Critical Bugfix to correct issue with uploading via optiboot.
Document my butchering of the board manager json and how to correct issues caused by it. (sorry!)
Housekeeping in UART.h and UART.cpp

Released Versions

2.5.4

CRITICAL BUGFIX. Prior critical bugfix was unsuccessful because the flashsize test was comparing it to the wrong value. Additionally, the branch before a jmp, with it's offset specified numerically, needs to match the size of the rjmp or jmp instruction; This corrects that.

2.5.3

CRITICAL BUGFIX Serial-using sketches wouldfail to compile if they were large enough.
Make software serial suck somewhat less by performing a single bitwise-and to calculate the result of the modulo operator, instead of dividing a 2-byte signed value which we know will never be larger than twice the buffer size (of 64) and hence fits in a single unsigned byte.

2.5.2

CRITICAL BUGFIX - burn bootloader was broken on most parts.

2.5.1

Added support for serial buffer sizes of 256.
Added test for defined(USE_ASM_TXC), USE_ASM_RXC, and USE_ASM_DRE in UART.h so that variants and board definitions can now turn this off.
Attempting to use illegal options, like buffer sizes that aren't powers of 2, now errors out.
CRITICAL BUGFIX for issue introduced in 2.5.0 which could COMPLETELY BREAK SERIAL if the sketch used >8192b of flash, with obtuse and uninformative error messages

2.5.0

New I2C/TWI implementation (I2C and TWI refer to the same interface, the one provided by Wire.h; don't get me started about how these and the library are named).
- Support for acting as both master and slave (on the same pins); this configuration, sometimes known as "multi-master", includes not only the simple case of multiple masters and slaves on an I2C bus, each of which is always exclusively either a master or a slave, but also the more complicated case, which has been a frequent request: For the AVR device to act as both master AND slave. It can both initiate transactions with slaves, or respond to transactions initiated by other masters.
- New tools menu option to select whether to support only being a master or a slave, as we do now (default) or to support acting as both master and slave (new functionality).
- Support for Dual Mode (one instance of TWI acting as master on one pair of pins and slave on another) on parts that support it (there are no current or announced tinyAVR parts with dual mode support.
- Significantly reduced flash usage under all circumstances (even master+slave mode should use less flash than old master or slave mode - the cost of supporting master-and-slave mode is RAM for a second buffer. There is an implementation included that can use the same memory for both buffers, however, it is not currently exposed via an option due to the risk of breakage if you receive while preparing to send something.
- Failed attempts will timeout instead of hanging indefinitely.
- Support for slave counting the bytes read by the master, and for slave to check whether it's in the middle of a transaction (for example, before sleeping)
Recent change to C++17 required additions to new.cpp and new.h, including sized deallocation (delete) and alignment-aware new and delete operators. The sized deallocation operator is called when existing code that worked before is compiled to the C++ 17 standard; since free() doesn't care about the size, implementation was straightforward. Discussion is ongoing about the aligned new and delete operators, which are also new in this version of the standards. It is likely that we will not support them, since other Arduino cores aren't even building to C++ 17 standard, so if your code needs aligned new/delete, it also won't work anywhere else in Arduino-land. While we are not shy about adding features, we do so only to support hardware features. If conditions change we will revisit this matter.
Using millis or micros (or rather attempting to) when they are unavailable due to millis being disabled, or in the case of micros, RTC used as millis time source, give better errors.
Clarified licence (for one thing, renamed to a .md so people can read it more easily, and know that it's readable if they're on windows) for tinyNeoPixel.
Improved docs for tinyNeoPixel. The two libraries each have a README.md linking to a greatly expanded library document.
Document use of WDT for it's original purpose, to protect against hangs!
Actually prevent disabling warnings - -Wall for all! You should not be compiling code with warnings disabled, the vast majority of the time, they're pointing to problems, and in the cases that aren't bugs, they're still a weak point that future bugs could come from (and that people will comment on when you post the code on forums to ask for help). I thought I'd done this a long time ago. Also pull in some warning-related flags from DxCore, including making implicit function declarations error, since the implied declarations when this happens are basically never result in working code, but it occasionally compiles and malfunctions.
Fix timekeeping on clock speeds only supported with external clocks or tuning when a TCA or TCB is used for millis (it's still busted with the TCD)
Correct SYSCFG0 fuse settings when burning bootloader for 2-series parts - they default the reserved bits to 1 not 0, and worse still, setting them to 0 enables a mode we probably don't want.
Stop clearing fuse 4 by writing the default values for TCD0 on a 1-series. Now, with great difficulty, we only set that on parts that actually have the type D timer in order to keep our promise of burn bootloader restoring the chip to a fully known state. (well, except for the user row, and EEPROM if you've got it set to retain).
Fix theoretical EEPROM.h bug inherited from avr-libc, and keep millis() from losing time when writing more than one byte at a time; update and harmonize with DxCore.
Harmonize Comparator.h with DxCore.
Fix 402 with bad signature support.
Fix names of .lst and .map
Add avrdude.conf for the 32k 2-series parts which are now becoming available.
Fix bug with disabled millis on tinyNeoPixel libraries not working. Again.
Correctly comment out leftover debugging prints that would be called when using tone() (megaTinyCore #550).
Adjust serial buffer size 512b and 1k parts by adding an intermediate 32b serial buffer size.
- Parts with 512b are changed - from 16->32 for RX, TX unchanged at 16 (32->48 for each port used).
- Parts with 1k are changed - from 64 to 32 for TX, RX unchanged at 64 (128->96 for each port used).
- Smaller and larger parts are unchanged. This mostly helps to smooth out the RAM usage curve as you change flash size - going from 256 to 512 didn't previously change the allocation, while the jump from 512b to 1k was alarmingly large. The fact that the 8k 2-series have poirts each makes this more noticeable. This combined with another breakpoint led me to think that something else was broken.
Officially deprecate jtag2updi.
Port micros and delay-microseconds improvements from DxCore.
Add a set of compatibility defines to make life easier for people porting non-Event-library event-using code to 0/1-series.
SerialUPDI reference now links to it's actual location.
Port Serial changes here from DxCore. The reduced flash use I had hoped for did not materialize, unfortunately, I'm still working on it. There's a whole bunch more functionality though!
Improved event library with more functionality for writing libraries and portable code.
Port new attach interrupt from DxCore.
Port new printf option from DxCore.
Update callbacks to match DxCore 1.4.0, most notably the init_reset_flags(). It will automatically clear reset flags if not overridden, stashing them in GPIOR0 (chosen because has lower overhead than a variable)
Platform.txt organization and commenting. Fix issues where defines were missing from lib-discovery phase.
Reduce flash footprint of pinMode.
Improve methods used to block attempts to use "upload using programmer" when an optiboot board is selected. That confiuration is guaranteed not to work, and we should not do things that we know 100% will not work. We would need a merged output file for this, but the IDE doesn;t make those for us here. (only over on attinycore, where they're not usable and we must go out of our way to delete the damned things)
Timers.h shared with DxCore.

2.4.2

Correct bug with openDrainFast(pin,CHANGE); This was a really nasty one, albeit for a rare corner case. Using CHANGE on a pin that was not on PORTA would alter other settings for other pins seemingly at random instead due to a missing '0x' in a memory offset.
Add a whole bunch of missing devices to SerialUPDI.
Fix a few examples so they dont throw warnings or demonstrate the wrong way to do things.
Instruct linker to use rcall and rjmp when possible (-mrelax). This should always have been the case, and it's absence had significant negative impact that had until now gone unnoticed.
Fix burn bootloader with SerialUPDI (#506)
Spelling and grammar corrections - thanks! (#508)
Fix issue with lowByte() macro and add test sketch to exercise all macros. (#515)
Fix issue with some macros caused by switch to C++17 standard. Typeof being an extension, it must be __typeof__ if compiled with standard C++ 17.

2.4.1

Bad release. Use 2.4.2

2.4.0

Finally port Event.h to tinyAVR. The event system they shipped on the 0/1-series is, to use a technical term, a shitshow. Users planning projects which depend heavily on the event system are urged to use a 2-series part unless the project also requires a type D timer, but the AVR DD-series is for some reason not an acceptable alternative.
Better TWI Baud formula (#422 - thanks @rneurink!!) - actually works more or less how it's supposed to now, rather than using baud buckets to simplify.
Support use of Tuned Internal oscillator to operate at 12 MHz, 16 MHz, 20 MHz, 24 MHz, 25 MHz, 30 MHz (20 MHz base only, may be unstable, particularly on 0/1-series) or even 32 MHz (2-series @ 20 MHz base only, may be unstable). For many specimens, 32 MHz is just too fast, but I suspect 24 and 25 will work with all or nearly all parts under favorable conditions. You must run the tuning sketch connected to a 500 Hz squarewave (A tuning sketch that works by tuning with a classic AVR like a 328p or anything shaped like one is included (You must use one WITH A CRYSTAL OR EXTERNAL CLOCK if you want accurate tuning!); Tuning values are written to the USERROW (last 12 bytes). Once tuning is completed, it is recommended to repeat for the other base oscillator (ie, 16 and 20 MHz). Yes in tuned configuration, you can run at 20 if OSCCFG fuse is pointing at 16 MHz and vice versa. If you try to use an untuned chip, we'll guess, but we could be off far enough that UART won't even work - but so far it's guesses are spookily good on the 2-series.
Add some sketches to assist in aforementioned tuning feature, see megaTinyTuner (runs on chip being tuned) and TuningSource (runs on chip - hopefully one with a crystal - being used to tune) as well as megaTinyDeTune which erases them and documented them in Tuning.md
New version of SerialUPDI to fix issues some experienced at speeds above SLOW - those should now be fixed at 230400 baud. All speeds are a bit slower now with the CH340 adapter most severely impacted (this is what I use, so I am reminded of how serious this issue is every time I upload anything) Turbo does NOT have this change, and it is not compatible with all serial adapters. This is expected.
Correct tone() issues and improve efficiency of tone while catching out several corner cases that could malfunction. That file now includes a discussion in comments that should be helpful to someone who wants a way to output multiple tones at once.
clockcycle <-> microsecond macros were unavailable with millis off. Nevermind the fact that with millis disabled, that's the only timebase you have. I just sorta grouped all the timing stuff together and disabled it without realizing some were used elsewhere, that is no longer the case. (#496, also found internally)
Correct issue with SPI.setClockDivider(). (#458)
Correct issue with Serial1.swap(1) swapping Serial instead of Serial onth TinyAVR 2-series. (#470)
Further corrections to Wire library behavior and documentation mirroring DxCore. No multi-master (ie, master/slave support) yet - needs too mcuh test for this timeframe.
Removed menu options for converting UPDI pin to something else (except alt reset pin on 2-series) on non-optiboot boards. Expert users who have the necessary exotic programming tools can reenabling it by uncommenting lines in boards.txt (to get it to apply after every programming, part of your workflow if you use one device to do the HV reset, and a normal programmer to program it subsequently - not sure how common this is - I know less common than classic AVRs). This was never supposed to be an option.
Dead code removal and cleanup of main.cpp
Fixes to Print api missing a few standard api functions (#485)
Fix bug with new/new.h - it was missing a method and the dummy file to allow including it like #include <new> - which is as far as I'm concerned perverse and wrong, but the C standard guys seem to feel otherwise.
Enable C++ 17.
Add more markdown linting to the CI checks. CI now runs for most boards with meaningful options selected.
Add a few test sketches to verify compilation works for API functions not covered by the examples, these are not included in board manager distributions as they are not educational samples.
Major doc improvements which I spent far too long writing.
Expand interrupt vector name document with general interrupt information
Massive improvements to part-specific docs
Fixed pinout charts (#442)
Installation now covers toolchain upgrade needed for manual installation.
PlatformIO docs moved to Extras.
New instructions for use with Arduino-cli
Important info links to almost all important info.
Readme covers watchdog timer more thoroughly, including how to reset it.
Added page from which you can view the io headers from the github documentation, because it's a pain to dig for them on your local machine, and you'll inevitably want to have them at the ready.
Errata section updated with recently discovered bugs. Changed my asssment of the severity of a number of the bugs (for example, the RTC bugs are much higher severity now, because I have watched someone trying to figurte out how the hell the RTC worked; it wasn't pretty.)
Correct bug when compiling tinyNeoPixel when no micros function is available.. as the compile warning says, you are responsible for giving the LEDs enough time to update in those cases. since we cannot ensure it without millis it. Previously this worked with the RTC options, but a typo prevented it from working with millis disabled entirely.
add digitalPinToTimerNow() to match DxCore; this is like digitalPinToTimer() only it will return NOT_ON_TIMER if you have used the timer takeover functions to assume full responsibility for management of a timer. Tie up some loose ends around the millis timer related defines when RTC with external source is in use.
Add support for using a pre-compiled library (that is, one distributed with .a files in place of the interesting parts of source code, typically as part of a proprietary license)
Correct bug in restart_millis() when a TCA is used for millis timekeeping.
Add human readable macros for the options passed to ADCPowerOptions() which provides control over some power management functionality of the 2-series parts.
Add openDrain(), openDrainFast() and pinConfigure() for advanced digital IO functionality.

2.3.2

Expand Keywords.txt to include register names! (#386)
Add @MCUDude's Flash.h library (not the same as the DxCore library of same name and big-picture function) (#159)
Correct issue with compilation when using TCB0 as millis timing source on parts without TCB1 (#394)
Correct huge bug in tinyAVR 2-series analogReadEnh which adverselty impacted accuracy of readings by inadvertantkly setting CLK_ADC to F_CPU/2, which exceeds the spec by 33-233%.
add analogClockSpeed(int16_t frequency = 0, uint8_t options = 0). Call with no arguments or 0, and it will just return the current CLK_ADC speed. -1 will set it to the core defaults, and a number will set it to the fastest speed that does not exceed the supplied value. Speed is expressed as kHz. Set analogReference first, as this impacts the maximum and minimum ADC clock (0.55V reference requires much slower clock). This will respect the minimum and maximum clock speeds stated in the datasheet, and if you request something outside that range, it will not set it. unless the lowest bit in options is set (that is cuerrently the only option).
Add bootloaders for 2-series parts. Correct a weakness in optiboot's implementation of the prime directive ("The application code shall not impact operation of the bootloader"). Poorly written code which jumped to the bootloader directly (or which malfunctioned and wound up running off the end of the flash or otherwise ending up with the program counter at 0x0000 without a reset) could, if it left peripheral registers in an adverse state, interfere with the operation of Optiboot; thus it is theoretically possible that if entry on POR was not enabled, and the app did this quickly enough, and the specifics of the adverse peripheral configuration also resulted in a hang or non-entry condition, the part could only be reprogrammed via UPDI. Now, very early in the initialization process, we check reset cause and if it's 0 (no reset since we cleared it before jumping to app after previous boot), we trigger a software reset, which is always an entry condition.
Add boards.txt entries for 2-series optiboot boards.
MASSIVE formatting overhaul in boards.txt - big headings that can be seen in the miniature view used to scroll on many editors. Everything is in the same order for all boards so I can add and remove lines with regexes.
Removed the board definitions for specific Microchip boards. These will be reimplemented as specific options in the other groups (eg, Curiosity1627 will show up wherever the 1627 is listed; difference will be that it will alwayus use the onboard debugger to upload (for non-bootloader configurations) and that LED_BUILTIN will match that hardware.
Remove 8-pin alternate serial pin bootloaders. That configuration does not require a separate bootloader - they were binary identical to the 14-24 pin alternate serial pins version.
Revise Logic library docs, add quick pin reference table to the readme.
Correct Wire library clock generation (#400). Enhance and correct Wire.pins() and Wire.swap() to work with new hardware and reject constant invalid arguments.
Also create memory map when doing export compiled binary
Massive improvement to speed of serial-updi (like, 8-20x faster, programming time under 5 sec is normal). Three speed options are available normal, a SLOW version that runs at 1/4 of normal (57600 baud), and a TURBO, at 460800 baud (double speed); TURBO should only be used when Vcc > 4.5V.
Disable Verbose serial-updi output. It would generate output about 4 times the size of the file being uploaded, and it was so detailed that almost nobody could decipher it. It was also incredibly repetitive; so much so that zipping it compressed it over 100:1. Since that was not useful, and without a way to get something in the middle, I just don't request verbose output, regardless of what is checked in the options. The verbose output was really only useful when modifying the upload tool.
Correct issue when the two pins controlled by TCD were written to in rapid succession (#414)

2.3.1

Rerelease to address toolchain bug. No code changes.

2.3.0

Port analogWrite() to the ADC on the 2-series parts.
Implement analogReadEnh(), for both tiny 0/1-series (suitable for porting to DxCore) and 2-series (suitable for porting to future EA-series core)
Implement analogReadDiff() for 2-series (suitable for porting to future EA-series core)
Implement configuration functions for new ADC functionality: ADCPowerOptions() for tinyAVR 2-series, analogSampleDuration() for both tiny 0/1-series and 2-series (separate implementations)
Implement ADC error return codes.
Document new features. Huge number of tweaks and improvements to the documentation, including large section on the new ADC-related functions. Please read it if you are using the ADC on a 2-series part or want more out of the ADC on a 0/1-series part.
Adjust variant pin definitions to account for the 2-series (One added USART, 4 more analog inputs on 20/24 pin parts). Correct several long-standing and unnoticed bugs. Does anyone use digitalPinHasPWM()? If so, they don't use the 24-pin 0/1-series parts....
Port the Comparator library. (#208)
Add capability for Comparator.stop() to restore digital input on the pins it disabled when it was started.
Move a bunch of hardware-related macros from Arduino.h the new core_parts.h. These are things that individual users are unlikely to need to reference, (certainly not as likely as anything that's in Arduino.h - which is where people generally know to look for core-related "stuff"
Correct large number of tone() bugs. Tone could leave the pin high. A high pitch and long duration could result in much shorter tones than intended. Frequency of 0 would leave the timer running and generating interrupts in the background for the requested duration (now it stops output if it's on the current pin, otherwise does nothing). while doing nothing. No attempt was made to handle invalid pins: it would get null pointer to port struct.... and proceed to use it without testing if it was valid, or if the bitmask was valid. Now we test for valid bitmask before requesting the port struct. Frequencies over 32768 would overflow an intermediate when called with duration and the duration would be very short. Long durations can also overflow the intermediate. The intermediate is found as 2 * frequency * duration and both multiplications can overflow (first one is as unsigned int, second as signed long.) Since the result is divided by 1000, remove 2* and change to /500 doubled the limit and removed the problem above 32768 Hz. If SUPPORT_LONG_TONES is defined as 1, then we will take additional steps to support tones longer than a minute; otherwise, when (frequency * duration) > 2^32, it'll overflow, and duration will be way short. If not specified as 0 or 1 (no existing board definition does), this defaults to 1 for any part with more than 8k of flash, as it adds 106 bytes to compiled binary and very few people want to make use of that.
Update pymcuprog bridge tool.
Converge on uniform convention for specifying analog channels vs digital pins as a uint8_t (high bit = analog channel), add ADC_CH() macro. Because the An constants are just digital pin numbers, this should mean very little to most users, but keeping this the same in all the cores I maintain will improve interoperability and make my life easier.
Add warnings for #define being used on things that aren't macros, and hence likely generating unexpected behavior. Refuse to compile with implicit definitions, as 99 times out of 10, this is a bug, and it's a waste of time to upload it.
delayMicroseconds should now be more accurate at low clock speeds, short delays, and cases where the delay is known at compile time. Particularly noticeable is the case of things like delayMicroseconds(1) at 1 MHz, (for example) where the delay wound wind up being more like 16 us before.
delay() on parts with 4k+ of flash will now work with any argument that fits in an unsigned long. Previously when passed a value greater than 4.295 million, an internal calculation would overflow and the delay would return much faster. I felt that the 24 bytes was a justified price to pay where one has 4k or more flash. While very long delays are generally poor programming practice, this is Arduino - if there's one assumption we can rely on, it is that poor programming practices are highly likely to be encountered in the field, so we should try to support them.
delay() on parts with 2k of flash will retain the old implementation in the name of saving a bit of flash. 2k is not enough flash for anyone, especially on modern AVR where the I/O space is not used for peripheral registers (don't underestimate the magnitude of this effect - many register writes are twice the size that they were on classic AVR, and with more options on the peripherals, there are often more of them). Will now error if called with a compile time known value higher than 4.294 million (as in, "I want 2 hour delay so delay(2UL*60*60*1000))
Wire buffer with 256b total ram now matches classic Uno/etc and the rest of the parts supported by this core at 32 byte I2C buffers; exceeding the bvuffer silently fails, leavig you waiting around for a call/zoom/etc which just kinda suuucks. . The only ones that don't 32b buffers within this core now are the parts with 128b rtam and 2k of flash. Since there are two buffers, they would have 50% of their SRAM as buffer, plus another 10% or so of it being bpointers to heads and tails, just not tenable. Larger parts supported by DxCore will start getting 130b buffers at 4k of flash ( with nothing getting 64 or anything else in the middle)
non-Arduino-IDE tools may not pass all the defines that we expect - basically, no defines that we platform.txt and boards.txt can normally guarantee can be relied upon to be there!. If Arduino.txt does not see a MEGATINYCORE define, that must have happened. In this case, detect and define a placeholder - checking for that define is how other libraries recognize that this core is in use. Also check a few other important defines for existence, rather than assuming that because my boards.txt and platform.txt will always provide them, that they will be present and one of the valid options - the intent is simply to make sure we don't sleep-walk into a wacky wromg state (imagine an X which is always defined as A, B or C via the boards.txt/platform.txt configuration, one could do /* well it's gotta be C then right? */. But in a situation where we don't fully control the defines passed to the compiler through the command invocation with total certainty is supposed to be supported, we need to complain if there make sure we don't blindly assume that can't-happen-per-our-boards-and-platform-definitions actually can't happen, thus above situation needs to be #if X==A ..... #elif X==B ..... #elif X==C ..... #else #error "X undefined or invalid, X must be #defined as A, B or C" #endif. Doing this is less work than dealing with the support requests that would result from not doing so.
Add some defines to indicate features provided by the core.... This list will be expanded over time:
- CORE_HAS_FASTIO - if defined as 1. indicates that digitalWriteFast() and digitalReadFast() is available.
- CORE_HAS_OPENDRAIN - if defined as 1, indicates that openDrain() and openDrainFast() are available.
- CORE_HAS_PINCONFIG - Indicates that pinConfig() is available. Currently, this is not defined here as this is not yet implemented.
- CORE_HAS_TIMER_TAKEOVER - if defined as 1, takeOverTCxn() functions are available to let user code take full control of TCA0, TCA1 and/or TCD0.
- CORE_HAS_TIMER_RESUME - if defined as 1, the corresponding resume TCxn() functions, which reinitialize them and return them to their normal core-integrated functions (not yet on megaTinyCore)
- ADC_NATIVE_RESOLUTION - This is the maximum resolution of the ADC without using oversampling. 12 for Dx-series. 10 or 12 for tinyAVR.
- ADC_NATIVE_RESOLUTION_LOW - This is the low ADC resolution setting. 10 for all Dx-series parts. Lower-res ADC resp;iutopm option. 8 bits on tinyAVR, 10 on Dx (yes, that means every possible permutation of 2 out of 8, 10, and has beemn released within a few years of each other..)
- DIFFERENTIAL_ADC - This indicates that the part has a differential ADC, irrespective of whether it is exposed.
- SUPPORT_LONG_TONES - This is 1 if the above mentioned long tones are supported.
- CORE_HAS_ANALOG_ENH - This is 1 if the enhanced version of analogRead is available, with automatic oversampling and decimation to extend resolution to 13 or 17 bits (0/1 and 2-series respectively)
- CORE_HAS_ANALOG_DIFF - This is 1 if the differential analogRead is available. It has same features as enhanced, except that it takes a differential measurement.
- ADC_MAX_OVERSAMPLED_RESOLUTION - This is the maximum resolution obtainable via oversampling and decimation using those functions.
- ADC_MAXIMUM_GAIN - This is 0 for all parts except: Those with a programmable gain amplifier, in which case it is the maximum gain available, and those with one or more opamps, which return (indicating that yes there is a gain, but using it is complicated and device-specific.
Correct critical regression impacting PWM via TCA0 WO3, WO4, and WO5. (#335)
Correct canShow() in tinyNeoPixel to permit use when micros() is not available - skip the test and #warn the user that they must make sure that they don't call show() too frequently. WS2812-alikes need 50us pause (according to datasheet - internet says only 20us) in the data between consecutive frames to tell them that it's time to latch the data they got, and if they don't see that before you start blasting out more data, they'll think it's part of the same frame and never turn on.
Correct bug in RTC millis timekeeping that caused reverse time travel due to improper guarding against overflow during millis() processing. Also, it's an average of 1-2 us closer to the actual number now (neglecting any contribution from oscillator inaccuracy - which is of course orders of magnitude higher) (#331)

2.2.8

Correct critical bug that prevented bootloaders from being installed when using the pyupdi-style serial port and resistor. Would report success, but only fuses were set.
Fix bug where the INVEN bit would be unset when doing digitalWrite() on pins that can do TCD PWM; now it is only unset if PWM was actually turned off (which in turn implies that if it was inverted, that was done by analogWrite(pin,255) - that's how we can generate a continuous HIGH output without disconnecting the timer (which would produce a glitch on the other pwm channel)- we set the compare value higher than TOP (which would produce continuous low) and invert the pin.
In the process of above, found both a terribly inefficient bit of code in analogWrite and turnOffPWM, and replaced with a much faster implementation that saves some flash too! By switching to bit_mask for most calculations a variable shift which could run as many as 7 iterations at 4 clocks each was eliminated from analogWrite. A loop that could
Correct constrain, round and similar macros.

2.2.7

Clean up Servo formatting and comments and synchronize with DxCore version of library.
We were waiting for ENRDY to be set before changing enable-protected registers of TCD0. That doesn't appear to be needed. We just can't re-enable it until ENRDY is set. It makes the glitch when turning PWM off or on... maybe 6 CLK_PER shorter? I think under default settings, the loop goes from one iteration to none....
Do not initialize the the compare values of TCA0. 1. They are guaranteed by hardware to start up at 0, and we don't CARE what they start up as, because before the core turns any of them on, it sets them to a value. 24 bytes saved! (STS x 6)
Add takeOverTCA0(), takeOverTCD0(). Calling these will set a flag that tells analogWrite() and digitalWrite() not to try to configure these timers, and instead to act like the pin has no PWM functionality. User assumes responsibility for the management of Waveform Output.
Update avrdude.conf to fix support for Snap, PICKit and Curiosity programmer options.
Fix macro definitions of sq() and constrain() which were still vulnerable to stupid stuff caused by macro leading to arguments being evaluated multiple times.
Add openDrain(), openDrainFast() - LOW, FLOAT, and CHANGE are supported. LOW set pin to output, FLOAT (#defined as 1 now) sets it input, and CHANGE toggles it. It does turn off PWM, and it does set the PORTx.OUT for that pin to 0 so carelessness can't lead you to switching a pin left set to HIGH's output on (on the reasoning that you may be switching a line connected to something that could be damaged if you drove it high). It does not, however, touch the PINnCTRL register (so pullup is left on if you'd already set it that way). However openDrainFast() - the fast-I/O version of that function - does NOT touch the PWM or PORTx.OUT register.
IDE should now highlight a few more keywords associated with megaTinyCore.
Minor formatting improvements in ChangeLog.md.
Update avr-gcc toolchain to azduino3.

2.2.6

Fix for baud rate in twi.c from 2.2.4 actually broke it was worse than it was before. I'm bopeful that now it should again work.
SPI library no longer requires knowing the SS pin when you call SPI.pins() - the SS pin has no special function with the library.

2.2.5

Another board manager installation fix. Sixth time's the charm!
Fix a few of grammar, spelling, etc mistakes.

2.2.4

Some general tidying turned into significant cleanup of neopixel library.
Fix board manager build script - it will now correct the platform.txt during release process.
Grabbed the default baud rate calculation fix from official megaavr core's Wire library. Maybe this will fix some of the occasional I2C problems people have reported?

2.2.3

Add support for MPLAB SNAP and PICkit4 programmers.

2.2.2

Critical bugfix for board manager installations on linux/macos.

2.2.1

Critical bugfix - somehow, the upload and program specifications for avrdude were backwards. Optiboot uploads failed because it was attempting to write fuses, and the new feature of writing safe fuses didn't work when avrdude was the programming tool.

2.2.0

Add support for programming with just a USB serial adapter and 4.7k resistor like pyupdi does. (#187, #285)
On non-Optiboot configurations, set all fuses that the core sets based on menu options, except BODCFG(control brown-out detection) and SYSCFG0(controls configuration of reset/UPDI pin, as well as whether EEPROM is retained) on all uploads. Changing the reset pin configuration could "brick" a part if the user does not have a high voltage programmer, so setting this fuse is not "safe"; similarly, setting the BOD voltage higher than the operating voltage and enabling it will prevent programming. Since the device may be soldered to devices that are not tolerant of the >4.3V required by the highest BOD setting, this would also constitute "bricking". Other fuses cannot render the device unprogrammable, so there is no reason not to program them. Judging by the content of recent issues, this is a frequent point of confusion particularly with the clock speed, despite the fact that it has worked this way on literally every Arduino core released since the dawn of Arduino! (On classic AVRs, changing any fuse could potentially "brick" the part, so this was the only safe behavior). There are no menu options to configure WDTCFGor TCD0CFG, so those aren't touched on program, only upon burn bootloader - if you manually changed those, you probably don't want an upload to undo them, whereas "burn bootloader" will return the chip to a known configuration.
On Optiboot configurations, set all fuses except BODCFGand SYSCFG0 when "upload using programmer" is used (this still removes the bootloader, just like on classic AVRs). Uploads through the bootloader will not set fuses; almost all tools submenu options require "burn bootloader" to change.
Fix nasty bug with Optiboot entry conditions (#259)
Add Ersatz Reset example sketch, and bootloader option.
Correct bug with bootloader version used on 14-24 pin parts when UPDI pin is configured as GPIO.
add millisClockCyclesPerMicrosecond(); what WAS clockCyclesPerMicrosecond() is now this - differemnce is that the millisClockCyclesPerMicrosecond() gives the number of clock cycles on the timebase for the millis timers (so, for TCD0 as millis clock, the unprescaled internal oscillator, otherwise same as clockCyclesPerMicrosecond()) - apparently other libraries use this for things that depend on the system clock... including my own Servo implementation! (it was tested before that was the default millis source on 3216/3217)... This is really nasty when it bites....
Fix Servo library - at long last! I never realized just how broken it was. (#195, #241)
What the heck? When were people going to tell me about the regression on TCD0 PWM pins?! It just didn't happen... botched refactoring of USE_TCD0_PWM AND regression to code from the bad old days before I knew how to get PWM and millis...(#249)
Reduced the magnitude of "glitches" possible on PWM pins when turning PWM off. Corrected PWM duty cycle calculations for TCD0 (it was (2 x dutycycle)/511 instead of (2 x dutycycle)/510 - no, it's not supposed to be 256ths, though it is very often implemented that way (if you count to 255, you get 256ths, because the timer considered 0 to be one count).
analogWrite() is now interrupt-safe for TCD0-controlled pins (this may be addressed for the other pins in a future update - however, it is "naturally" interrupt safe except when either the interrupted analogWrite or the interrupt is turning pins on or off - in contrast, TCD0 analogWrite could break in a variety of ways in almost any situation where it was interrupted)
Also implemented NEW special behavior on the TCD0 PWM pins: analogWrite(pin,0) and analogWrite(pin,255) set pin LOW or HIGH without turning off the PWM. On TCD0, this does not require turning off the timer briefly, which, over time, would cause millis() to lose counts when PWM was also used based on TCD0, in addition to reducing runtime. digitalWrite(), however, does. (also remember that digitalRead(), unlike official cores, NEVER turns off PWM)
Add check for compile time known invalid pins passed to Arduino digital/analog API functions, analogReference and DACReference, as well as compile time known unachievable baud rates on Serial.begin() for Serial (#269)
Correct bug in digitalPinToAnalogInput() when called with invalid values.
analogReadResolution() now requires a constant argument which must be valid - the old implementation was just awful - there are only two (will be a third on the 2-series, as we unfortunately kinda do need to be able to emulate )
Add support for digitalReadFast(), digitalWriteFast() functions. They are only valid if the pin is compile time known constant, and optimize down to something very fast (when second argument is compile time known, a single cycle for write. Looks like 4 cycles for read?) (#205)
Emulate digitalWrite behavior of classic AVRs when pin not OUTPUT, namely, set the PORTx.OUT register so that if it is set output, that's the state it will be in.
Update Logic library to latest version (as with DxCore).
When using an internal reference for the ADC, forcibly enable it. Adjust the example of reading temperature to add the (signed) sigrow correction instead of subtracting it. This appears to get better values, and it is suspected that the code in the datasheet is wrong.

2.1.5

Fix critical issue with "burn bootloader" when speeds other than 5, 10, or 20 MHz was selected on devices with 8, 20, or 24 pins and 14-pin devices using Optiboot.

2.1.4

Fix critical bug in alternate pins for Serial (#254)
Improve compatibility regarding build.board changes with a compatibility layer in case other libraries are checking for the old version. (#253)
Use build.board pattern consistent with other cores (AVR_ATtiny). (#253)
In order to reduce flash usage, do not use UART baud correction based on voltage on 2k and 4k parts (it was always close enough for typical use cases anyway), and those parts are very tightly flash constrained.
Remove UART baud voltage menu for 8-pin parts due to above.
Automatically use U2X USART option at 2 MHz or less, and on higher speed parts when appropriate for the selected baud rate. Most visible impact of this change is that you can now use 115200 baud at 1 MHz. (#188)
Do not apply oscillator voltage (in)correction to baud rate when using external clock.
Reduce flash usage of UART (Serial), particularly on smaller chips, through a great many mechanisms. (#252)
Serial.print/write/flush will no longer play with interrupt priorities, and those functions can no longer hang indefinitely if called from an elevated ISR (not that one should really be printing to serial while in an ISR), like classic AVRs - they will spin and busywait as needed.
Fix build.extra_flags missing entries on in 2.1.x on 24-pin parts with Optiboot.
Move version defines to platform.txt, in hopes of reducing incorrect and inconsistent version numbers in releases... (at least now the version number from {version} and the MEGATINYCORE/MEGATINYCORE_* defines will match!)
Correct issue with enabled/sampled BOD mode with slow sampling.
Include all SUT options in tools submenu, correct issue with 8ms SUT (it was actually setting it to 4ms).
Include serialevent and clocksource setting in name of exported .hex and .lst files.
Add the Serial.printHex() functions from DxCore; Serial.printHex() can be called with a 1, 2, or 4 byte integer to print out it's value in hexadecimal, with leading zero(s). For 2 and 4 byte integers, optional boolean second argument; if true, will swap the order of the two bytes (endianness); can also be called with a pointer to a uint8_t or uint16_t, a length (uint8_t, ie, max length 255), and, optionally, a separator (a single char/int8_t); this will print that many bytes as hex starting at the given pointer; if it's a pointer to a uint16_t, there's the same optional byte order boolean at the end. If you need to use that, but don't want a separator, pass 0 as the third argument.
Merge in timing fix for TWI in slave mode (#235)

2.1.1, 2.1.2, 2.1.3

Urgent bugfixes for critical regressions introduced in 2.1.0.

2.1.0

Improve ADC accuracy when switching references
Fix bug with which parts we thought had the external reference, corrected docs. (#211)
Change handling of reset cause in bootloader, see #213.
Correct bootloader for 8-pin parts with non-swapped serial port to use PIN_PA3 for the blink LED instead of PIN_PA7 which is used when the serial port is on the alternate pins. PA7 is one of the serial pins, and hence is not available for the Optiboot triple blink if the serial port is not swapped. Swapped serial port still used PA7, as that matches a) all other megaTinyCore boards and b) the initial versions of the hardware I sell.
Fix programmer options (#232 and others)
Fix EEPROM library, no more USERROW - this is just the standard EEPROM library. (#200, #168)
Add USERSIG library for writing to the USERROW (also called USER_SIGNATURE)
Writing to flash from app now works on Optiboot parts (Thanks @WestFW) (#212, #233)
Add options for SUT, BOD sampling frequency (#202)
As part of above, rolled all the bod mode options into one menu; this rules out nonsensical options (ex, enabled hold wake until BOD started, when BOD is not disabled in sleep, or more stringent BOD while in sleep)
Wire no longer tries turning on pullups; this caused problems when switching between master and slave, and the internal pullups just aren't strong enough for this! (#223)
Moved USE_TIMERD_PWM to the variant files instead of boards.txt
Corrected maximum sketch size for parts with less than 24 pins when using Optiboot.
Added support for reprogrammming UPDI pin on non-Optiboot board definitions (requires HV UPDI)
Added support for external 32.768 kHz oscillator as millis source (#238)
Actually fix bug with names of exported binaries
In order to maintain compatibility, F() macro now behaves just the same as on official boards. This comes at a cost of performance and size, but allows interoperability with major libraries (#216)
Fixed bug with millis conversion with RTC (any) as clock source (#327)
Added support for external clock sources, including ones that attempt to overclock the device.
Added support for ignoring SerialEvent - this little used and ill-conceived feature imposes a significant cost in time on all parts whether they use it or not.
Pulled in latest logic library (#224). Did not bring in all the examples, which were really repetitive, and added some new ones that are super cool...
Added ModernRevSerial example under megaTinyCore "library" to get silicon rev and serial number and print it to console.

2.0.5

Internal change to ADC initialization (saves a bit of flash) and init_ADC1() function for parts that have ADC1.
Quick fix to naming of .hex and .lst files

2.0.4

Switch to new and improved compiler toolchain - now get informative errors if sketch is too big on parts that use RJMP, bugfix for eeprom.h (not to be confused with EEPROM.h), various header improvements (board manager install only).
Improve naming of exported binary and assembler listings - now includes every setting that could impact the output!
Fix failure to export compiled binary on some linux platforms (#201)
Massive doc improvements.
Improve backwards compatibility of Wire.h (#203)
Fix strange bug in EEPROM.h that was somehow missed
Mark unqualified BOD settings that were removed from datasheet as unofficial, add warning that they may not work correctly (but suspect will be close - they were working for me before I realized they were unsupported! they were listed in io.h before!), and add Microchip's guaranteed operating speeds + BOD levels per datasheet to documentation.
Possibly fix #189!
Fix problem with millis not being entirely disabled when set to be disabled.
Ever so slightly improve baud rate accuracy, reduce space taken by Serial.begin() by a few bytes.
Fix compile error from Tone() on parts without a second type B timer (ie, everything not a 1614, 3216, 1616, 3217, or 1617) when TCB0 was selected as a millis source. (part of #189)
Correct bug in micros() timekeeping when TCA0 is used as millis() timing source (introduced in 1.1.9 - after the exhausive testing for these sorts of issues) (#189)

2.0.2

Fix bug with 1MHz system clock with TCB as milis source (micros was broken)
Remove EXTERNAL_EXPERIMENTAL - newer atpack removes ambiguity (note - we don't use it yet, but we didn't really need to either).
Fix part family defines
Add MEGATINYCORE_SERIES definition
analogReadResolution() added
Wire buffer size (broken in 2.0.0) fixed in very general way, with cases for a wide range
fix tinyNeoPixel on real WS2812's (it previously was busted on real ones, only worked with SK6812 clones) and unsplit the libraries, because architecture improvements make that possible!

2.0.1

Fix bug with some 1-series parts not compiling because of references to external reference introduced by 1.1.10
Add an EXTERNAL_EXPERIMENTAL reference option, since the headers and datasheets disagree about what parts support this
Fix bug in DAC introduced by 2.0.0
Switch to 3 separate tinyNeopixel libraries instead of one, and change the examples and documentation accordingly.
Renumber interrupt modes for consistency with MegaCoreX
Correct EESAVE fuse settings for optiboot boards - it is now always off. With optiboot on the chip, it is likely that the only time chip erase is executed is when UPDI is used to erase the chip to reburn the bootloader, and users would probably expect that to wipe the EEPROM too.

2.0.0

Remove all the UART/SPI/I2C pin mapping menus from tools submenus. Instead, use the newly added .swap() and .pins() methods on these objects to set the pins to be used.
WARNING: POTENTIALLY BREAKING CHANGE: The default pins used for Serial on 8-pin parts in previous versions are not the "default" pins per datasheet (arduino pins 0 and 1); instead, the "alternate" pins were used by default (arduino pins 2 and 3). Note that on the Rev. - and Rev. A breakouts for these parts from my Tindie store, the serial lines from the FTDI header go to the alternate pins, not the "default" ones. (this will be corrected in Rev. B of the board). If you have sketches/hardware using this, you will either need to move connections, or add Serial.swap(1); before calling Serial.begin(). I realize this is inconvenient, but that previous behavior should never have been the case, and, having finally accepted the fact, it was better to cut over quickly than let more people get used to the previous behavior and then change it later.
Improve ADC speed dramatically (it runs in about a quarter of the time it used to!) - I do not expect this to cause any issues with accuracy. The megaavr parts support much higher maximum ADC clock compared to the classic AVRs. We now set the ADC clock near to the top of it's range. In order to prevent this from hurting accuracy when reading high impedance sources, the ADC0.SAMPCTRL is set to SAMPLEN=14 instead of 0. This means samples will be taken for 16 ADC clocks instead of 2. Since the ADC clock is 8 times faster now, this should result in the same sampling time. See the ADC section for more information, including how to get even faster ADC readings from low impedance signals.
digitalRead(), pinMode(), and digitalWrite() were changed back to operating on uint8's instead of the PinMode, PinStatus, etc enums like the official megaavr core does (and unlike how every other core does it). Using the enums, while it was defensible from a software architecture perspective, caused a lot of breakage of common Arduino ideoms that have been in widespread use for ages, for very little benefit. This also applies to things that used BitOrder.
digitalRead(), pinMode(), digitalWrite() and analogWrite() now take advantage of the unified memory architecture of the megaavr parts to improve performance and reduce flash usage by removing the PROGMEM attribute and accompanying pgm_read_byte() calls. This yields a significant improvement in performance of analogWrite() and digitalRead() in particular.
Remove the DAC reference voltage from tools submenu. Now, use the DACReference() function - it can take any of the INTERNAL reference arguments that would be passed to analogReferece().
digitalRead() no longer turns off PWM and DAC output on the pin that is read. There was no technical need for this, and digitalRead() should not change the pin output state!
digitalRead() now returns an int8_t instead of an int16_t - this saves a tiny amount of flash and slightly improves execution time.
digitalRead() now returns -1 if called on a pin that doesn't exist, instead of 0 (LOW). This should make debugging easier, without impacting behavior when valid pin is passed to digitalRead().
Added support for manipulating the millis timer from within libraries or the sketch: init_millis(), stop_millis(), set_millis(), and restart_millis(). These are not expected to be normally used in sketches; these will be used in the upcoming megaTinySleep library which will "switch" millis timekeeping to the RTC when in sleep, and restore the millis value to whatever other timer is normally used.
Fix a bug with the EXTERNAL reference option being defined for the '212 and '412 - the 8-pin parts do not have that reference option, even if they're 1-series and otherwise would

1.1.10

Fix bug with Wire introduced by not testing 1.1.9 changes to Wire.
Fix bug with EEPROM introduced by not testing 1.1.9 changes to EEPROM
Add ability to read from temp sensor, internal reference via ADC, clean up analogReference()
Add some example sketches, including reading temp and Vc

1.1.9

Correct micros() results at 20, 10, and 5 MHz when TCA0 or TCD0 is used as millis source
Correct micros() and millis() long term drift at 20, 10, and 5 Mhz when TCD used as millis source
Reduce time for micros() to return in many situations
Correct PWM duty cycles when TCD0 is used for PWM
Add support for PWM on TCD0 when it is used as millis source
Adjust TCBm period when used for millis timekeeping with 1MHz system clock to reduce time spend in the millis ISR (reduces millis resolution to 2ms)
Lower prescaler on TCA0 to 16 when system clock is 4 Mhz or 5 MHz and 8 when running at 1 MHz (was 64)
Increase prescaler on TCD0 to 64 when used as millis() source with 1 MHz system clock (it still runs from unprescaled 20/16 MHz oscillator) in order to reduce portion of time spent in the ISR. Previously it spent more than 12% of it's time in the ISR.
micros() times returned are now as close to the time when micros() was called as possible
Move millis interrupt to HUNF instead of LUNF when TCA0 is used for timing
Don't prescale TCB clock in Servo at 10MHz or lower for smoother output
Correct TRIM_DURATION in Servo library
Add support for writing to the user row using EEPROM.h
Add support for receiving general call messages in slave mode using the TWI peripheral through the Wire library (Thanks @LordJakson - #146 )
Add support for second address or masking off bits of the address using the TWI0.SADDRMSK register
Added support for the Atmel embedded debugger on the explained pro kits as programmer (thanks @rneurink #149 )
Lots of expanded documentatio

1.1.8

Fix critical bug introduced in 1.1.7 that prevented compilation with TCA0 as millis sourc

1.1.7

Make Servo library work independently of TCA0 prescaler
Fix bug that prevented compilation with RTC as millis source
Improve TCBn as timekeeping source - it is now the best if you can spare a type B timer
Fix tone not moving to TCB1 when millis using TCB0
Improve compile errors if TCB0 used as millis and you try to use tone
Remove dead code relating to TCB2, TCB3 - nothing here has them, why do we have that code here?

1.1.6

Remove option for RTC using external crystal on 412/212/402/202 - these do not support it.
Correct issue with gibberish if using Serial just after Serial.begin()
Fix issue with disabling DAC on 14-pin parts (#141)
Fix issue with missing option to disable DAC on 20-pin optiboot parts.
Fix issue with pulseIn() giving incorrect results. (#142)
Add support for PA0 (UPDI) as IO pin to Optiboot boards (#150)
Fix issues with Logic library and examples (#106)
Remove dependence of tone() and TCB as millis/micros source TCA0 prescaler (#144)
Documentation improvement

1.1.5

Reduce flash used by millis/micros() (#135)
Undo change that broke #130
Eliminate variants.c (#40)
Fix issue with disabling millis not working correctly
Add option to use RTC as millis timer (#133)
Correct and update part-specific doc

1.1.4

Correct issue introduced with 1.1.3 that broke compile for 20-pin parts (#134)
Correct issue when Timer D is specified explicitly as the millis timer
Correct issue when Timer D is used as the millis timer when clock speed is not 20/10/5MH

1.1.3

Fix issue with PWM duty cycle and analogWrite(pin,255) (#123)
Fix issue with some UPDI programmers (#125, #126)
Reduce flash usage of all parts slightly (#127)
Reduce flash usage of Wire library significantly (#128, #129, #130)
Add DAC disabled option (saves flash)
Fix issue with UART baud rate calculation (#131)
Add menu option to control timer used for millis/micros (#124, #132)
Default millis timer for 412,212,1614,814,414,214 changed to TCD0, as it's not used for anything else (#124)

1.1.2

Fix critical issue compiling for 24-pin parts (#118)
Fix issue with eesave menu option (#117)
Fix issue with PWM on PA3 on 14-pin devices. (#115)
Remove unused {upload.extra_files} parameter from platform.txt upload recipe.

1.1.1

Fix issue with board manager installation (#111)
Add support for printf to printable library (#112)
Add menus for I2C and SPI pin mapping (#110)
Correct bug with UART pin mapping menu and xy4/xy6/xy7 optiboot board definitions
Correct bug with digitalPinHasPWM macro on xy2.
Update datasheet links to point to latest dataheet version. This should get rid of all the preliminary datasheet links.
Add row in entry in part-specific doc pages for spxzz bootloader for optiboot board def

1.1.0

Add Logic library (#103)
Improve pinout diagrams (#98)
Add support for the Optiboot bootloader !!! (#52)
Correct sketch size output to account for const variables (#95)
Fix EESAVE option (which was backwards - #93)
Fix Onboard mEDBG programmer for ATTiny416 Xplained Nano (#96)
Add menu options for UART location on all parts (#108)

1.0.6

Add missing NUM_DIGITAL_PINS macros to xy7, xy6.
Fix PWM on Pin 1 (PA7) of xy2
Fix Wire.h to prevent "call of overloaded 'requestFro&, unsigned int&)' is ambiguous" errors with code that works on classic avr.
Expand documentation
Tools -> Programmer selection now used for normal upload

1.0.5

Support more PWM pins on 412/212/402/202
Support both UART locations on 412/212/402/202

1.0.4

Do not specify version of AVRDude in platform.txt (#73)
Board manager installation improvements to prevent breaking USBTinyISP on other installed core

1.0.3

Fix UART (and I suspect I2C) on 412/402 and general PORTMUX initialization.
Add tinyNeoPixel and tinyNeoPixel_Static libraries, examples and documentation, add menu option to select port at 8/10MHz (saves flash)
Pinout chart correction

1.0.2

Fix analogRead(), which was broken on most pins
Fix A11 on ATtiny x04 and x14 parts
Fix 1604 (compile and upload both had separate and unrelated issues)
Board manager installation will no longer require official megaAVR board package to be installed
Correct analog pin macros (these don't appear to be used anywhere, but may be used by third party code)
Add workaround for t402's with bad signature
Improve consistency in boards.tx

1.0.1

Improve TCD0-based PWM pins on parts that have them
Implement DAC output on 1-series
Implement Servo library
Add a number of useful #defines
Fix minor typos
Move LED_BUILTIN to PA7 on all parts. The exact number of this pin will depend on the version of megaTinyCore in use
Improve and expand documentatio

1.0.0

Initial Release

Files

ChangeLog.md

Latest commit

History