UPDATE: This post is a work in progress, it reflects my current thinking on the best way to start and run a micropython project on an ESP32, but I’ve been looking into this for only a few days, so it may change a lot.
PREVIOUS: Flashing the MicroPython firmware on an ESP32
- Notes: WORK IN PROGRESS: tidy up later
- ToDO: Add header image with board and micropython logo
Don’t just dump your code anywhere, make a decision about where to put it! For me, this is C:\Users\Gregw\microcontroller-home
From Windows Terminal
- Set up folder structure. Adjust to taste! Don’t forget the tab key to autocomplete partial folder and file names.
Getting to a REPL prompt is a good start, but you need to be able to write code in a capable editor, with intellisense, or context-aware auto-completion, because you’re 50x more productive when you can type a dot after the name of an object, and your editor suggests all applicable properties and methods on that object. Without this, you’ll be spending over 99% of your time trawling documentation.
I’ve tried out VS Code extensions for
MicroPython IDE, with varied degrees of success (tip: don’t bother even trying the MicroPyhton IDE in Windows, it does nothing).
The Best Options I can find are…
- It is assumed you’ve installed all the prereqs listed in the previous post
- Install NodeJs
- use the LTS version, 64bit msi for Windows I also accepted the recommendation to install additional tools, which includes the windows package manager “chocolatey”
I’ve chosen to install the following globally, as you will likely use these tools in many projects.
|I am also not using virtual environments for each project, since micropython dependencies are managed separately by micropy-cli.
pip install esptool micropy-cli
micropy stubs search "esp32"
micropy stubs add "esp32-micropython-1.12.0"
New Project Setup
Blinking an LED is the Hello World of the microcontroller world.
These step apply to all new projects. I am using a separate python virtual environment for each project, which is a couple more steps for each projec, but keeps each project nicely self-contained.
After a lot of thought, I’ve decided on the following project naming convention…
Once you get hundreds of projects stacking up, you come to realise that good naming matters a lot. More on naming in another post.
micropy init oled-esp32-upy
select all 5 options using space bar and up/down arrows, with Enter to Ok your selection
then select the stub: esp32-micropython-1.12.0
When VS Code opens, it will ask if you want to install the recommended Extensions. Go ahead and do it.
I will not be using VS Code’s Workspaces feature, but if you regularly switch between different types of projects e.g. Rust and MicroPython, Workspaces are extremely useful.
- Install the VS Code PyMakr extension
Once the above steps have been done once in a project folder, next time you want to work on that same project, you just need to navigate to that folder and start VS Code.
Hello World on the Display
Copy code from https://raw.githubusercontent.com/micropython/micropython/master/drivers/display/ssd1306.py to src/ssd1306.py
- “install” it using micropy’s package manager so we get intellisense
micropy install -p ./src/ssd1306.py ssd1306
import machine, ssd1306
i2c = machine.I2C(scl=machine.Pin(4), sda=machine.Pin(5))
oled = ssd1306.SSD1306_I2C(128, 64, i2c, 0x3c)
oled.text("Hello World", 0, 0)
- Upload your modified main.py
TODO: screenshot of vscode pymakr integration (animated gif better)