1.6.0 - A new era. DU, EB support added

[SpenceKonde]

Released changes

1.6.0

• 1.6.0 should be treated as a test release, because I need to get the new toolchain into the testing environment in order for the automated tests to see what doesn't compile, but the test environment only gets the previous release's dependencies, so until I release with the new toolchain, I can't do automated tests against it.
• OSCCFG is now written for Dx-series parts. We have never supported any option other that 0x00 on those parts, and the hardware only supports one other value, which starts the chip on the 32 kHz oscillator.
• Support for the PTC peripheral on DA parts
• Correct bug with EA-series parts having the SYSCFG0 fuse set during normal uploads, which is inappropriate, because if the UPDIPINCFG bit is not 1, the chip can only be reprogrammed with an exotic HV programmer.
• Corrected a bug with EA-series parts incorrectly calculating the UPDIPINCFG bit as 0 in all cases. In combination with the above, unlucky users who were able to get an upload to attempt would promptly brick the chip, since nobody has HV programmers. Sorry bout that \o/ I'm not even certain there is a programming problem, or if I'd just attempted to program every chip I had mounted on a board....
• Correct bug with EA-series parts failing to correctly configure clock speed.
• Add support for EB-series to tools menus, permitting compile tests once I get the toolchain ready.
• Brutal restructuring of Arduino.h.
• keywords.txt for DxCore contained numerous deficiencies of varying severities. It was rebuilt de novo. Slightly less disorganized this time.
• device_timer_pins.h design deemed hopelessly defective. Functionally identical file regenerated de novo.
• Fix issue with 0ms SUT.
• Update toolchain to add support EB, small flash EA, and DU.
• Completely reimplement the timer detection code in analogWrite, digitalPinToTimerNow and turnOffPWM (hence digitalWrite). Appears to now work correctly.
• Correct version number to 1.6.0 (it has read 1.6.10 and 1.6.11 previously during development, which obviously was not correct). Once all problems are sorted out, 1.7.0 will be released as a better tested codebase
• Fix MAX38903 library (I was trying to use one of the damned boards!)
• Remove the UPDI as GPIO pin option from non-optiboot parts
  • An analysis of all plausible hardware configurations (there aren't many with relevant differences for this matter) revealed that, with the UPDI as GPIO option selected, there was no combination of hardware connections and software options which would write a working sketch to the part with the UPDI disabled fuse set:
    • We only wrote that fuse on burn bootloader.
    • It can brick the part, so ya can't have general audience libraries doing that on upload!
    • But if you don't do it on upload, then you have to do it with burn bootloader
    • Which means you need an HV programmer to upload
    • We have no support for one as I'm not aware of any widely available ones.
    • Ergo, the only thing which could result from the option as implemented was to soft-brick devices.
    • Bricking user devices is not an intended feature, despite some evidence to the contrary (see third item in changelist)
• Major documentation improvements focusing on main README.md.
• Major documentation improvements focusing on Ref_Analog and Ref_Interrupts, the latter of which was previously the same file from megaTinyCore.
• Correct bug in ADC init code that set Ex-series parts to the wrong ADC clock speed.

---

This discussion was created from the release 1.6.0 - A new era. DU, EB support added.

[MX682X]

@SpenceKonde can we get PICkit 5 and the PICkit Basic as Programmers? avrdude supports them for a while now...
There are multiple options that can simplify programming if they were supported aswell, like
-xvtarg=3.3 / =5.0 to supply power during programming (3.3 and 5V respectively (don't worry, I made sure to check the Vcc voltage before supplying power to avoid accidents))
-Evcc to keep providing power after Programming
-xhvupdi to supply a HV Pulse (for PK4/5 only) (auto-detection if UPDI pin or RST pin)

[SpenceKonde]

That means we need to update avrdude, that needs to be done, but I want to get functionality working on all the parts before we start messing with a project as intimidating as switching avrdude versions. I mean, I've never done that before....

[MX682X]

I was able to make a more or less a drop in replacement. Simply replacing the binary and config files. (As a workaround)

[MX682X]

actually, this reminds me that your avrdude config file has an error, I don't know if I mentioned that or if it is alreay fixed. The Chip ID of the AVR32DD28 is wrong. config: 1E 95 29 actual: 1E 95 39