Uploaded July 2020 | Updated September 2026, 2 weeks ago
DEMO CODE and platformio.ini example at:
technocoma.blogspot.com/p/blog-page_18.html
As I use more than one IDE for the development of code for the ESP32, I would like to demonstrate, alternatively the benefits of platform IO, as opposed to Arduino IDE, if you are a more seasoned developer who is looking for more features. One will find that the installation and time to get up and running is also significantly quicker by comparison. This is by no means an attack or slight on Arduino IDE, just an alternative. I still use Arduino IDE in many smaller projects and demos, but not for larger complex ones.
The video goes into the specifics as to the ground up installation of platform IO and connected to the same TTGO T-display device as in the last project.
For this specific demonstration, there will be no importation, I will be doing a cut and paste do demonstrate compatibility, showing all that is required to accomplish this task. Most of which should be obvious. One notable difference is the addition of Arduino.h in the include section which will be needed in platform.io.
Another important file platformio.ini allows for a non centralized configuration per project , per device. This is different from Arduino's global based config. This is revisited as library configs and serial speed configs are demonstrated. Libraries are not installed per se, but compiled in on a per project basis. This file provides more value than this, also compile time options, which was useful for TFT_ESPI setting all display parameters within that file under build_flags.
As we compile with no errors after our work we end up with the same output product on the device. I do however find a strange issue which ill get into in the follow on video before I expand on Platformio.
#arduino #platformio #esp32
DEMO CODE and platformio.ini example at:
technocoma.blogspot.com/p/blog-page_18.html
As I use more than one IDE for the development of code for the ESP32, I would like to demonstrate, alternatively the benefits of platform IO, as opposed to Arduino IDE, if you are a more seasoned developer who is looking for more features. One will find that the installation and time to get up and running is also significantly quicker by comparison. This is by no means an attack or slight on Arduino IDE, just an alternative. I still use Arduino IDE in many smaller projects and demos, but not for larger complex ones.
The video goes into the specifics as to the ground up installation of platform IO and connected to the same TTGO T-display device as in the last project.
For this specific demonstration, there will be no importation, I will be doing a cut and paste do demonstrate compatibility, showing all that is required to accomplish this task. Most of which should be obvious. One notable difference is the addition of Arduino.h in the include section which will be needed in platform.io.
Another important file platformio.ini allows for a non centralized configuration per project , per device. This is different from Arduino's global based config. This is revisited as library configs and serial speed configs are demonstrated. Libraries are not installed per se, but compiled in on a per project basis. This file provides more value than this, also compile time options, which was useful for TFT_ESPI setting all display parameters within that file under build_flags.
As we compile with no errors after our work we end up with the same output product on the device. I do however find a strange issue which ill get into in the follow on video before I expand on Platformio.
#arduino #platformio #esp32
