Firmware build options
The flags of mcuctl firmware build. How to use them is in
Build firmware.
Option |
What it does |
|---|---|
|
The target. |
|
Modules to compile in: names from |
|
Builds CircuitPython-compatible firmware instead: CircuitPython’s own ports and boards ( |
|
esp32 flash size. Upstream’s generic boards assume 4 MB, which most module sets outgrow. Leave it out to keep the board’s own |
|
When the image doesn’t fit, |
|
Deletes this target’s build folder first |
|
Builds under |
|
Parallel jobs. The default is every core |
|
An argument for |
|
The omnipython-builds checkout. See Finding the tools you need |
|
The MicroPython tree, if it isn’t found on its own |
Builds land in builds/<port>/[<board>/]<variant>/, and CircuitPython ones in
builds/circuitpython/<port>/<board or variant>/. Each folder records what
went into it. build_mp.py’s options are in its
reference.
The other firmware commands
Command |
What it does |
|---|---|
|
The ports, then a port’s boards and variants, then the modules; |
|
The modules |
|
The resolved MicroPython, ESP-IDF, emsdk and build-system paths |
|
Build, streaming |
|
Report the firmware built for a selection |
|
Delete a selection’s build folder |
|
An esptool-first chip, flash and security probe |
|
Flash a built or downloaded artifact ( |
|
The official firmware catalog. |
|
Print an image’s partition table; |
|
esp32 partition override ( |