You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ChangeLog.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,18 +10,21 @@ These items are in addition to what was listed under changes already in release.
10
10
* Enhancement: Implement sleep library
11
11
* Re-add SPI attach and detach.
12
12
* Ensure libraries in sync with megaTinyCore.
13
+
* Add support for DU-series to tools menus, permitting compile tests once I get the toolchain ready.
13
14
14
15
## 1.6.0
15
16
These are typically planned for release in a future version (usually the next one) as noted.
17
+
* 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.
16
18
* Support for the PTC peripheral on DA parts
17
19
* 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.
18
20
* 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....
19
21
* Correct bug with EA-series parts failing to correctly configure clock speed.
20
-
* Add support for EB-series to tools menus, permitting compile tests.
22
+
* Add support for EB-series to tools menus, permitting compile tests once I get the toolchain ready.
23
+
* Not yet expected to work.
21
24
* Brutal restructuring of Arduino.h.
22
25
* keywords.txt for DxCore contained numerous deficiencies of varying severities. It was rebuilt de novo. Slightly less disorganized this time.
* At some point in the recent past, I must have angered the gods of C, and suddenly millis disabled stopped working - the system would hang (actually, with in-depth investigation, it was shown to be bootlooping - before it called init(), it was calling 0x0000 (a dirty reset) instead of eliding a weakly defined function with nothing in the body except a return, or with an empty body. Why was it doing this? And why only when millis was disabled?). millis disabled is a key piece of core functionality, necessitating an urgent fix. Moving the definitions into main.cpp resolved this issue. (#485)
# The maximum size and data size attributes are overridden by the selected chip. If you are avoiding specifying that somehow, there is no hope of anything working, so don't do that.
160
158
# Each top-level entry supports at least a dozen parts with varying memory constraints.
# The maximum size and data size attributes are overridden by the selected chip. If you are avoiding specifying that somehow, there is no hope of anything working, so don't do that.
194
+
# Each top-level entry supports at least a dozen parts with varying memory constraints.
# The maximum size and data size attributes are overridden by the selected chip. If you are avoiding specifying that somehow, there is no hope of anything working, so don't do that.
625
-
# Each top-level entry supports at least a dozen parts with varying memory constraints.
# The maximum size and data size attributes are overridden by the selected chip. If you are avoiding specifying that somehow, there is no hope of anything working, so don't do that.
663
+
# Each top-level entry supports at least a dozen parts with varying memory constraints.
# The maximum size and data size attributes are overridden by the selected chip. If you are avoiding specifying that somehow, there is no hope of anything working, so don't do that.
1120
-
# Each top-level entry supports at least a dozen parts with varying memory constraints.
# The maximum size and data size attributes are overridden by the selected chip. If you are avoiding specifying that somehow, there is no hope of anything working, so don't do that.
1162
+
# Each top-level entry supports at least a dozen parts with varying memory constraints.
# The maximum size and data size attributes are overridden by the selected chip. If you are avoiding specifying that somehow, there is no hope of anything working, so don't do that.
1627
1640
# Each top-level entry supports at least a dozen parts with varying memory constraints.
0 commit comments