Once you have connected a display to your microcontroller, the next step is to program it: your firmware needs to instruct the display on what to show.
Overview
There are two primary approaches to programming firmware for displays:
1. C++ Code
This method involves writing the source code yourself, which requires basic programming skills. Using traditional development environments like Arduino IDE or PlatformIO, you:
- Compose the source code.
- Compile it into a binary file.
- Upload the binary to your microcontroller.
These platforms offer libraries and prebuilt modules for most display types, making it accessible even if you’re not an expert programmer.
2. ESPHome
ESPHome is a modern development environment that does not require programming skills. Instead of writing code, you:
- Describe the desired behavior and configuration of your components using a simple YAML file.
- ESPHome generates the source code, compiles it, and uploads it to your microcontroller automatically.
Both methods come with prebuilt libraries and components that support a wide variety of displays. This ensures you can get started quickly, whether you prefer a hands-on coding approach or a simplified configuration-based workflow. Even if you choose the programming route, advanced programming knowledge is not required.
I2C Address
If your display comes with a I2C interface, you will need to know the I2C address that is assigned to the display.
Slow Website?
This website is very fast, and pages should appear instantly. If this site is slow for you, then your routing may be messed up, and this issue does not only affect done.land, but potentially a few other websites and downloads as well. Here are simple steps to speed up your Internet experience and fix issues with slow websites and downloads..
Comments
Please do leave comments below. I am using utteran.ce, an open-source and ad-free light-weight commenting system.
Here is how your comments are stored
Whenever you leave a comment, a new github issue is created on your behalf.
-
All comments become trackable issues in the Github Issues section, and I (and you) can follow up on them.
-
There is no third-party provider, no disrupting ads, and everything remains transparent inside github.
Github Users Yes, Spammers No
To keep spammers out and comments attributable, all you do is log in using your (free) github account and grant utteranc.es the permission to submit issues on your behalf.
If you don’t have a github account yet, go get yourself one - it’s free and simple.
If for any reason you do not feel comfortable with letting the commenting system submit issues for you, then visit Github Issues directly, i.e. by clicking the red button Submit Issue at the bottom of each page, and submit your issue manually. You control everything.
Discussions
For chit-chat and quick questions, feel free to visit and participate in Discussions. They work much like classic forums or bulletin boards. Just keep in mind: your valued input isn’t equally well trackable there.
(content created Jan 22, 2025)