You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
1Thanks for your response dda!Zach– Zach2023-11-01 23:20:58 +00:00Commented Nov 1, 2023 at 23:20
-
Why would a pin be labeled as a GPIO if in can't be properly used as a general purpose input or output? As in, shouldn't they just be labeled as just VSPI_HD etc instead to avoid confusion?Zach– Zach2023-11-01 23:22:59 +00:00Commented Nov 1, 2023 at 23:22
-
1@Zach I don't think that's an issue, most of the pins on modern MCUs have multiple functions--you decide which ones to utilize. Checking the schematics, I don't see any external quad-SPI peripherals (as dda indicates, most commonly used for flash chips). Another indicator is that it's probably not the pins (aside from GPIO2, we've conclusively established that it's linked to a blue LED...but why is the LED bank dimly lightning up during initialization?) it worked with other ESP32-Wroom modules, which are also the modules used on the NodeMCU-32S board(s).Nick S.– Nick S.2023-11-02 01:26:02 +00:00Commented Nov 2, 2023 at 1:26
-
@Zach okay, I checked on the Espressif docs and yes, pin 16 is indeed not recommended to be used as a GPIO pin (it still can be, of course, but it could lead to unknown behavior as you've experienced)--nothing about pin 21 though.Nick S.– Nick S.2023-11-02 16:56:38 +00:00Commented Nov 2, 2023 at 16:56
-
@Zach it is possible to have different functionalities on the same pin - just don't use them all at once. In the case of the VSPI pins, if there's no Flash chip, and the VSPI bus isn't inited (eg if the code checked whether there's a chip, and didn't deinit afterwards, oops), they can be used.dda– dda2023-11-03 08:16:23 +00:00Commented Nov 3, 2023 at 8:16
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. arduino-uno), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you