-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Digistump digispark ATTiny85 compile time noise #233
Comments
PlatformIO uses the core versions that are available for the board, they've not written that themselves. To my knowledge the core is at https://github.com/digistump/DigistumpArduino/. You would need to ask them to fix the errors in their code. Given that the last update was 4 years ago I don't think they'll respond though. Seems pretty abondend. But I did stumble upon a forked & improved version of the core: https://github.com/ArminJo/DigistumpArduino. You can install that in your Arduino IDE and see if the code there works and doesn't have the warnings. Then you can raise a feature request to use that new core. But after all, these are warnings that can be ignored I think. |
Thanks for the reply and thanks for the link. To be honest, I mistrust code that leaves warnings during compile time. Even if they can be safely ignored - possibly a bad habit of mine. I always fear to overlook something important.
This works very well for me now. As of ArminJo's DigistumpArduino core, could you kindly point me to a location describing on how to install a custom core in VSCode/PlatformIO? I'll gladly give it a try then. |
@maxgerhardt |
Mainly work has to be done in this repository (platform-atmelavr) to add the board defnitions (in JSON format, A nice-to-have in the repository would just be that it has a There's also a really hacky way to include a different core. Change what used
I'll quickly see what changes need to be done here and check back then. Edit: Oh I've actually seen that the core already has some packaged versions which seem to be in the PlatformIO format.. |
Okay so it's actually much easier than expected to test it. Just use a Tested with
and it builds without warnings, uploads and runs on my Digispark USB device. Tested a simple Blinky. Others should be able to test the core too that way. @ArminJo can you create a |
Tested it on my source too and compiles w/o any issues. |
@maxgerhardt But what's about the new micronucleus binaries for the different OS? |
For that you would have to create a package (see above links with PlatformIO sticks the Micronucleus upload tool in a (Linux has only a folder with just the See https://bintray.com/platformio/tool-packages and search for "tool-micronucleus". A reference {
"name": "tool-micronucleus",
"version": "1.200.4",
"description": "ATTiny usb bootloader with a strong emphasis on bootloader compactness",
"keywords": [
"tools",
"uploader"
],
"license": "GPL-2.0-or-later",
"system": [
"linux_x86_64"
],
"repository": {
"type": "git",
"url": "https://github.com/micronucleus/micronucleus"
}
} Whereas the So the uploaded archives at https://github.com/ArminJo/DigistumpArduino/tree/master/tools are almost perfect, they're just missing the A created archive can then also be tested by again using
(example). |
OK Thanks, |
It's using semver / semantic versioning. Here's an example and explanation. For version 2.5 i'd encode it as When you use the package in PlatformIO per example above and compile any project, PlatformIO will also tell you how it's decoded the inner version at the start of the output, e.g.
|
@maxgerhardt Ok I prepared the tools zip files. @anno73 what would you suggest? As told, I use Eclipse and Sloeber, and have no experience with PIO. |
The drivers are not auto-installed, they are just referenced in documentation so that users can install it themselves. |
Thanks! |
I updated to v1.7.1. Upon first compile I get following errors:
Second compile then works nice again. Is this an issue of PIO or the v1.7.1 package? I think I had the same issue with initially changing to v1.7.0. |
So I followed the instructions from @maxgerhardt :
Now I'm almost there, there is only one error left:
If I manually call the now unpacked and updated micronucleus to upload the hex, everything works fine. So how do I convince pio that micronucleus now uses different commandline options? |
Ah, that doesn't work anymore with platform-atmelavr/builder/main.py Lines 184 to 192 in dec3edd
So to fix that there are two options:
In general you would add
the If I read docs correctly it should need a
so that will call Check that the installed micronucleos tool is in |
@maxgerhardt |
I'll open a proper issue or PR for full-integration of the new core, then that will be directly addressed in the platform code. |
Works perfect. I'm looking forward to the integration into pio, but this is a usable workaround. Thank you all. |
Feature request opened as linked above this comment. |
Hi guys!
When compiling for a digispark, I get a lot of warning noise. I do not know how important this is but it makes me at least nervous every time I compile my code :-)
It boils down to
Any chance to get this fixed please?
Br, Alex.
github project: https://github.com/anno73/IoT-Universal-Socket-Strip/tree/master/software/relay
platformio.ini:
Compile time output:
The text was updated successfully, but these errors were encountered: