Seich
/
HomeSpan
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update Solutions.md

This commit is contained in:
HomeSpan 2024-02-18 10:21:28 -06:00 committed by GitHub
parent 694723b959
commit 6bc1483dcb
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/Solutions.md
View File

@ -14,6 +14,14 @@
* *As an alternative*, instead of adding a pull-up resistor, you can simply exclude (or comment out) the `Serial.begin()` line in your sketch. This prevents the problem of HomeSpan hanging when you power it through the 5V pin, but it unfortunately means the Serial Monitor will not function when you connect the board to your computer, and you will need to add back `Serial.begin()` whenever you want to use the Serial Monitor.
#### *HomeSpan crashes when I enable PSRAM, but works fine if I disable PSRAM*
* If your ESP32 comes with Quad or Octal PSRAM, the chip will likely need to use one or more additional I/O pins so that it can access the PSRAM using an extended SPI bus, as required for these types of PSRAM. If you happen to use one of those pins for something else (e.g an input button, an LED, etc.) the ESP32 will likely crash whenever PSRAM is enabled. The solution is to check the documentation for your board to see what pins are reserved for use when PSRAM is enabled, and don't use those pins for anything else.
#### *The Serial Monitor is reporting* "gpio: gpio_set_level(226): GPIO output gpio_num error"
* This is an ESP32-generated error message and it occurs if you try to set the output of a pin that either does not exist on your chip, or does exist but it is input-only (i.e. it cannot be used as a output). This typically occurs when you try to compile code for one chip (such as an ESP32-S2) on another chip (such as an ESP32-C3). The code will compile fine, but may produce the above error during run-time. The solution is to check the documentation for your board and use only pins that exist for your chip, are not reserved for internal functions, and are not input-only.
---
[↩️](../README.md) Back to the Welcome page