Brewery/gravitymon
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updating docs for c3v1

Browse Source
This commit is contained in:
Magnus 2022-11-24 14:49:34 +01:00
parent 88fc94ed8c
commit d4dfccdddd
2 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src_docs/source/compiling.rst
View File

@ -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-debug; Maximum logging for trouble shooting, deep sleep is disabled.
* gravity-release; Standard release * gravity-release; Standard release
* gravity32-release: Version for ESP32 mini. * gravity32-release: Version for ESP32 mini.
* gravity32-c3-release: Version for ESP32 C3 mini. * gravity32c3-release: Version for ESP32 C3 mini v2.1+.
* gravity32-s2-release: Version for ESP32 S2 mini. * gravity32c3v1-release: Version for ESP32 C3 mini v1.0.
* gravity32-lite-release: Version for ESP32 lite (Floaty hardware). * gravity32s2-release: Version for ESP32 S2 mini.
* gravity32lite-release: Version for ESP32 lite (Floaty hardware).
.. warning:: .. 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. The debug target can be unstable and crash the device under certain circumstanses. Excessive logging to the serial port can cause corruption and crashes.

4
src_docs/source/installation.rst
View File

@ -45,8 +45,8 @@ In the /bin directory you will find 4 different firmware builds;
* **firmware32c3.bin** * **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 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. 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** * **firmware32s2.bin**