MCUdude
commented
5 years ago @ivankravets is there any way I could contribute, so any of this could happen?
Closed MCUdude closed 5 years ago
MCUdude
commented
5 years ago @ivankravets is there any way I could contribute, so any of this could happen?
ivankravets
commented
5 years ago Sorry, I missed this issue :( Sure, we would be thankful in any contribution.
Ideally, would be good if we have a separate framework package per each Arduino AVR core. However, to simplify the integration process, we created this repository https://github.com/platformio/platformio-pkg-framework-arduinoavr So, you can actually make a PR and I'll merge and re-deploy to our CDN.
These files are located in your machine by %HOME_DIR%/.platformio/platforms/atmelavr/***. You can edit them on a local machine for testing purpose.
MightyCore has the additional option of turning on of off LTO (link time optimization). How can this feature be turned on or off in the platformio.ini file?
See example:
If possible, I'd also like to re-structure the JSON file(s) a bit to make the platformio.ini file a little sleeker.
Each known/generic board has own JSON manifest. If you need some extra configuration settings, you can extend it. See https://github.com/platformio/platform-atmelavr
;board_build.pinout = standard ; (or bobuino or sanguino)
[env:myenv]
...
board_build. variant = ...If you have any questions, I would be glad to help.
MCUdude
commented
5 years ago About updating the corefiles, How is it done? The version hosted over at platformio/platformio-pkg-framework-arduinoavr is very old, but the version present on my computer is much newer. Will you guys take care of the updating, or do I have to submit a PR?
;board_build.pinout = standard ; (or bobuino or sanguino) [env:myenv] ... board_build. variant = ...
I tried this but no other variant than standard is preset at the moment. I'm not really sure where the "new" pinout files go. It would be awesome if you could add these files and update the corefiles. I promise to do the testing!
As for the LTO option, how about a generic LTO option for AVR targets such as AVR_LTO
build_flags = -D AVR_LTOIt should cover the needs for most users.
I'm not really sure how it should be implemented though. Here's how it's done in the boards.txt file.
ivankravets
commented
5 years ago Could you re-test with the upstream version? See https://docs.platformio.org/en/latest/platforms/atmelavr.html#upstream
build_flags = -D AVR_LTO
In this case, no need to reinvent wheels. This is actually an issue of Arduino IDE builder which is so primitive and does not allow to configure the build process. I see that LTO is enabled by default. If developers don't need LTO, they can remove flags
[env:myenv]
...
build_unflags = -fltoI tried this but no other variant than standard is preset at the moment.
I've just added 3 variants:
Does it work for you?
MCUdude
commented
5 years ago Could you re-test with the upstream version?
I'll do it right away!
In this case, no need to reinvent wheels. This is actually an issue of Arduino IDE builder which is so primitive and does not allow to configure the build process. I see that LTO is enabled by default. If developers don't need LTO, they can remove flags
That's a pretty easy way of disabling LTO. I'll add it to my personal platformIO template 👍
I've just added 3 variants: ... Does it work for you?
Maybe we should add mightycore as a prefix? as in mightycore_standard, mightycore_bobuino and mightycore_sanguino? IMO this will be easier to maintain when my other AVR Arduino cores get added later.
ivankravets
commented
5 years ago Done! Please re-run pio update.
MCUdude
commented
5 years ago Cool! Quick question. I installed PlatformIO through VS Code, and everything is working fine there. On the other hand my terminal app keeps telling me that the pio/platformio command isn't found.
Do you recommend installing platformIO in my terminal too, or will the these two separate installs collide?
ivankravets
commented
5 years ago Just click on "Terminal" icon on the bottom toolbar or from PlatformIO left sidebar. It will populate PATH with PlatformIO Core.
MCUdude
commented
5 years ago Well. I ran pio update, and updated to the latest version (3.6.7). However it still hasn't fetched your latest commit:
> Executing task in folder Testproject_2019: platformio run <
Processing MightyCore (framework: arduino; platform: https://github.com/platformio/platform-atmelavr.git; board: mightycore32)
-------------------------------------------------------------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/atmelavr/mightycore32.html
PLATFORM: Atmel AVR > MightyCore ATmega32
HARDWARE: ATMEGA32 16MHz 2KB RAM (31.50KB Flash)
Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF MODES: FINDER(chain) COMPATIBILITY(soft)
Collected 12 compatible libraries
Scanning dependencies...
No dependencies
Compiling .pioenvs/MightyCore/src/main.cpp.o
Archiving .pioenvs/MightyCore/libFrameworkArduinoVariant.a
Indexing .pioenvs/MightyCore/libFrameworkArduinoVariant.a
In file included from src/main.cpp:1:0:
/Users/hans/.platformio/packages/framework-arduinoavr/cores/MightyCore/Arduino.h:316:26: fatal error: pins_arduino.h: No such file or directory
**********************************************************************
* Looking for pins_arduino.h dependency? Check our library registry!
*
* CLI > platformio lib search "header:pins_arduino.h"
* Web > https://platformio.org/lib/search?query=header:pins_arduino.h
*
**********************************************************************
compilation terminated.
Compiling .pioenvs/MightyCore/FrameworkArduino/CDC.cpp.o
Compiling .pioenvs/MightyCore/FrameworkArduino/HardwareSerial.cpp.o
*** [.pioenvs/MightyCore/src/main.cpp.o] Error 1
In file included from /Users/hans/.platformio/packages/framework-arduinoavr/cores/MightyCore/USBAPI.h:33:0,
from /Users/hans/.platformio/packages/framework-arduinoavr/cores/MightyCore/CDC.cpp:19:
/Users/hans/.platformio/packages/framework-arduinoavr/cores/MightyCore/Arduino.h:316:26: fatal error: pins_arduino.h: No such file or directory
**********************************************************************
* Looking for pins_arduino.h dependency? Check our library registry!
*
* CLI > platformio lib search "header:pins_arduino.h"
* Web > https://platformio.org/lib/search?query=header:pins_arduino.h
*
**********************************************************************
compilation terminated.
*** [.pioenvs/MightyCore/FrameworkArduino/CDC.cpp.o] Error 1
In file included from /Users/hans/.platformio/packages/framework-arduinoavr/cores/MightyCore/HardwareSerial.cpp:29:0:
/Users/hans/.platformio/packages/framework-arduinoavr/cores/MightyCore/Arduino.h:316:26: fatal error: pins_arduino.h: No such file or directory
**********************************************************************
* Looking for pins_arduino.h dependency? Check our library registry!
*
* CLI > platformio lib search "header:pins_arduino.h"
* Web > https://platformio.org/lib/search?query=header:pins_arduino.h
*
**********************************************************************
compilation terminated.
*** [.pioenvs/MightyCore/FrameworkArduino/HardwareSerial.cpp.o] Error 1
=========================================================== [ERROR] Took 0.86 seconds ===========================================================
The terminal process terminated with exit code: 1
Terminal will be reused by tasks, press any key to close it.
My current platformio.ini file looks like this
[env:MightyCore]
platform = https://github.com/platformio/platform-atmelavr.git
board = mightycore32
framework = arduino
board_build.mcu = atmega32
board_build.f_cpu = 16000000L
;board_upload.maximum_size = 32768
board_upload.speed = 115200
board_build.variant = mightycore_sanguino
upload_port = /dev/cu.usbserial*
;build_unflags = -fltoIs there anything I'll have to do in order to "re-fetch"?
MCUdude
commented
5 years ago Sorry, I actually ran pio upgrade instead of pio update. It's working fine now. I'll test some more and report back later. BTW what's up with the boards selection menu? ATmega1284 appears four times! Oh, and are you able to change my "signature" from Mcudude to MCUdude 😉?
ivankravets
commented
5 years ago ATmega1284 appears four times!
It seems that you have 4 dev/platforms of AtmelAVR with different Git revision. Please navigate to PIO Home > Platforms and remove duplicate.
"signature" from Mcudude to MCUdude
Changed ;)
MCUdude
commented
5 years ago After some more testing, I can confirm that everything seems to be working just fine. When this be available through platform = atmelavr? I'm currently writing a simple guide for MightyCore users, and I want to refer to the generic atmelavr platform rather than a specific git repo.
ivankravets
commented
5 years ago I've just released a new version => https://github.com/platformio/platform-atmelavr/releases/tag/v1.13.0
Please uninstall all Git dev/platforms and use stable.
I'm currently writing a simple guide for MightyCore users
Great! 👍 We would be thankful for this guide. You can refer developers to this configuration file http://docs.platformio.org/en/latest/projectconf.html
MCUdude
commented
5 years ago Sorry for picking up the thread again, but avrdude.conf is missing some targets.
I'm not sure where this file is located, but could you add the following lines to avrdude.conf?
Even though some of these AVRs have the same signature it's still nice to be able to use the actual part number for board_build.mcu.
We're currently missing ATmega164A, ATmega164PA, ATmega324A, ATmega324PB, ATmega644A and ATmega644PA
#------------------------------------------------------------
# ATmega164A
#------------------------------------------------------------
# similar to ATmega164P
part parent "m164p"
id = "m164a";
desc = "ATmega164A";
signature = 0x1e 0x94 0x0f;
ocdrev = 3;
;
#------------------------------------------------------------
# ATmega164PA
#------------------------------------------------------------
# similar to ATmega164P
part parent "m164p"
id = "m164pa";
desc = "ATmega164PA";
signature = 0x1e 0x94 0x0a;
ocdrev = 3;
;
#------------------------------------------------------------
# ATmega324A
#------------------------------------------------------------
# similar to ATmega324P
part parent "m324p"
id = "m324a";
desc = "ATmega324A";
signature = 0x1e 0x95 0x15;
ocdrev = 3;
;
#------------------------------------------------------------
# ATmega324PB
#------------------------------------------------------------
# similar to ATmega324P
part parent "m324p"
id = "m324pb";
desc = "ATmega324PB";
signature = 0x1e 0x95 0x17;
ocdrev = 3;
memory "efuse"
size = 1;
min_write_delay = 4500;
max_write_delay = 4500;
read = "0 1 0 1 0 0 0 0 0 0 0 0 1 0 0 0",
"x x x x x x x x o o o o o o o o";
write = "1 0 1 0 1 1 0 0 1 0 1 0 0 1 0 0",
"x x x x x x x x x x x x i i i i";
;
;
#------------------------------------------------------------
# ATmega644A
#------------------------------------------------------------
# similar to ATmega164p
part parent "m644"
id = "m644a";
desc = "ATmega644A";
signature = 0x1e 0x96 0x09;
ocdrev = 3;
;
#------------------------------------------------------------
# ATmega644PA
#------------------------------------------------------------
# similar to ATmega164p
part parent "m644"
id = "m644pa";
desc = "ATmega644PA";
signature = 0x1e 0x96 0x0a;
ocdrev = 3;
;
Thanks! Please re-run pio update :)
MCUdude
commented
5 years ago Cool! I may start planning for MiniCore support then! Many users have requested MiniCore PlatformIO support 😉
ivankravets
commented
5 years ago Great! Please ping me if you need any help from our side 😊
MCUdude
commented
5 years ago Great! I'll probably open a new issue here when the questions start to pile up 🙂
Hi!
As the maintainer of MightyCore, I would like to provide better documentation on how to use PlatformIO with the Arduino core. If this turns out to be a success I'd like to add some of my other Arduino cores as well. I know fuse settings is difficult, so I will leave this out of the question for now.
First, the MightyCore version that's included here is
very old and outdated. EDIT: turns out it's only behind by a few commits. Are these files updated manually by the platformIO team, or automatically when I push a commit or issue a new release?MightyCore has the additional option of turning on of off LTO (link time optimization). How can this feature be turned on or off in the platformio.ini file?
MightyCore contains three different pinouts or variants. Standard, Bobuino, and Sanguino. How can one of these pinouts be selected using the platformio.ini file?
If possible, I'd also like to re-structure the JSON file(s) a bit to make the platformio.ini file a little sleeker. Is possible to make one single JSON file for all MightyCore devices? Then all other settings will have to be provided in the ini file.
Is it also possible that some sort of platformio.ini template is loaded into the project after you've selected MightyCore as your board? If so I could add some additional settings (shown below).
Ideally, I'd like a working platformio.ini file to look like this: