Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Additional information #14

Open
S5NC opened this issue Apr 10, 2024 · 0 comments
Open

Additional information #14

S5NC opened this issue Apr 10, 2024 · 0 comments

Comments

@S5NC
Copy link

S5NC commented Apr 10, 2024

It would be beneficial to make it clearer that this is for the WROOM series ESP32-S3 modules in particular.

ESP32-S3 recommends a power supply which is capable of supplying 500 mA.
From testing I have seen that BOOT is pulled high very weakly (2+ MΩ). However, this is often not strong enough and an additional resistor (100 kΩ works fine) is needed.
I have found a RC reset circuit to be unreliable if large capacitors are used on the 3.3 V rail. To avoid having to test configurations and assume the properties of the power supply, the MAX809T is a great IC for preventing turning the ESP32 on when it is at an unsafe voltage level (see my implementation of it in the schematic found here).
Including the peripheral schematic would be a nice addition.

You specify ESP32-S3-WROOM-2 on the diagram, but it is also the same for version 1, and 1U.

Routing SPI to custom pins via GPIO matrix limits the communication speed to 80 MHz.

A quick way of knowing if you can't use IO35, IO36, and IO37 is if there is an 'R8' or greater ('R16', etc.) in the chip name (also written at the bottom of the shield, see example). Espressif only use octal SPI in their WROOM modules when they need to, so there is no octal SPI for modules that have less than 'R8'.

A quick way of knowing if #13 applies (As the VDD_SPI voltage of the [chips ending in V have] been set to 1.8 V, the working voltage for GPIO47 and GPIO48 would also be 1.8 V, which is different from other GPIOs) is if the chip name and therefore shield print ends in a 'V'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant