Updating docs for c3v1
This commit is contained in:
parent
88fc94ed8c
commit
d4dfccdddd
@ -30,9 +30,10 @@ In the platformio config there are 3 targets defined
|
||||
* gravity-debug; Maximum logging for trouble shooting, deep sleep is disabled.
|
||||
* gravity-release; Standard release
|
||||
* gravity32-release: Version for ESP32 mini.
|
||||
* gravity32-c3-release: Version for ESP32 C3 mini.
|
||||
* gravity32-s2-release: Version for ESP32 S2 mini.
|
||||
* gravity32-lite-release: Version for ESP32 lite (Floaty hardware).
|
||||
* gravity32c3-release: Version for ESP32 C3 mini v2.1+.
|
||||
* gravity32c3v1-release: Version for ESP32 C3 mini v1.0.
|
||||
* gravity32s2-release: Version for ESP32 S2 mini.
|
||||
* gravity32lite-release: Version for ESP32 lite (Floaty hardware).
|
||||
|
||||
.. warning::
|
||||
The debug target can be unstable and crash the device under certain circumstanses. Excessive logging to the serial port can cause corruption and crashes.
|
||||
|
@ -45,8 +45,8 @@ In the /bin directory you will find 4 different firmware builds;
|
||||
|
||||
* **firmware32c3.bin**
|
||||
|
||||
This is the release build for an ESP32c3-mini variant. When flashing an ESP32 you also need the *partition32c3.bin* file that outlines the flash memory structure. Due to
|
||||
the size of the firmware we are using a custom partition setup.
|
||||
This is the release build for an ESP32c3-mini variant v2.1 or newer. When flashing an ESP32 you also need the *partition32c3.bin* file that outlines the flash memory structure. Due to
|
||||
the size of the firmware we are using a custom partition setup. If you have a v1.0 board use the firmware32c3v1.bin instead.
|
||||
|
||||
* **firmware32s2.bin**
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user