Can't compile programs for attiny1616 any more, it was working before #958
-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
OK, quick update, I continued troubleshooting and I have now gotten things to compile and flash again by downgrading megaTinyCore to 2.6.5. Is this something that I should report as an issue instead? |
Beta Was this translation helpful? Give feedback.
-
Normally, yes, you should create an issue. In this one specific case, please don't, yours would be the 8th duplicate of the issue I closed, it is fixed in github - the last release broke 1-series parts and official Microchip boards fix will be in next release when it is tested and I can assure myself that it's tested because the CI will have been corrected as well. This went undetected because of deficiencies in the CI testing and a bug in the CLI regarding unspecified menus in an FQBN taking the value of "none of the above" instead of requiring it to take a value. That is often the default (generally not through intentional action, just the normal development process will tend to lead to submenus with nothing defined on their default setting. This wasn't such a case though. The upshot of it was that anything with a TCD (1-series) wouldn't compile if it was enabled for PWM and and nothing that didn't support the PWM mapping changes (ie, the microchip boards) would compile at all, and the CI missed both of those. |
Beta Was this translation helpful? Give feedback.
-
Thank you, I will close this discussion then. |
Beta Was this translation helpful? Give feedback.
Normally, yes, you should create an issue. In this one specific case, please don't, yours would be the 8th duplicate of the issue I closed, it is fixed in github - the last release broke 1-series parts and official Microchip boards fix will be in next release when it is tested and I can assure myself that it's tested because the CI will have been corrected as well.
This went undetected because of deficiencies in the CI testing and a bug in the CLI regarding unspecified menus in an FQBN taking the value of "none of the above" instead of requiring it to take a value. That is often the default (generally not through intentional action, just the normal development process will tend to lead to…