ESP32 - revision history

Dank: /* SoCs, modules, devkits */

2025-03-19T03:00:45Z

SoCs, modules, devkits

← Older revision		Revision as of 03:00, 19 March 2025
Line 17:		Line 17:
	Let's have an example.		Let's have an example.

	Consider the [https://www.espressif.com/en/products/socs/esp32-c6 ESP32-C6] family of SoCs ([[https://www.espressif.com/sites/default/files/documentation/esp32-c6_datasheet_en.pdf datasheet]). Each includes a unicore RISC-V running at up to 160 MHz. They are available in QFN40 and QFN32 SMD packaging. The QFN40 package (the true ESP32-C6) has no onboard flash. The ESP32-C6FH<i>x</i> and ESP32-C6FN<i>x</i> in QFN32 packaging sport <i>x</i> MB of flash, supporting High and Normal temperatures, respectively. SoCs consist of the CPU, RAM, EEPROM—all of the ICs necessary for the ESP32-C6 feature set. The F[HN]x SoCs lack GPIO10, GPIO11, GPIO14, SPICS0, SPIQ, SPIWP, VDD_SPI, and SPIHD, but gain SDIO_CLK and SDIO_CMD, for 30 vs 24 exposed pins.		Consider the [https://www.espressif.com/en/products/socs/esp32-c6 ESP32-C6] family of SoCs ([https://www.espressif.com/sites/default/files/documentation/esp32-c6_datasheet_en.pdf datasheet]). Each includes a unicore RISC-V running at up to 160 MHz. They are available in QFN40 and QFN32 SMD packaging. The QFN40 package (the true ESP32-C6) has no onboard flash. The ESP32-C6FH<i>x</i> and ESP32-C6FN<i>x</i> in QFN32 packaging sport <i>x</i> MB of flash, supporting High and Normal temperatures, respectively. SoCs consist of the CPU, RAM, EEPROM—all of the ICs necessary for the ESP32-C6 feature set. The F[HN]x SoCs lack GPIO10, GPIO11, GPIO14, SPICS0, SPIQ, SPIWP, VDD_SPI, and SPIHD, but gain SDIO_CLK and SDIO_CMD, for 30 vs 24 exposed pins.

	[[File:esp32c6mini.png\|thumb\|The ESP32-C6-MINI-1 and -1U have the same pinout.]]		[[File:esp32c6mini.png\|thumb\|The ESP32-C6-MINI-1 and -1U have the same pinout.]]

Dank: /* Annoyances */

2025-03-19T02:59:14Z

Annoyances

← Older revision		Revision as of 02:59, 19 March 2025
Line 4:		Line 4:
	* There are plenty of SMT MOSFETs that will work with the ESP32's 3.3V 20 mA outputs...		* There are plenty of SMT MOSFETs that will work with the ESP32's 3.3V 20 mA outputs...
	** but the only through-hole MOSFET I've found that works a damn is the (pricey!) Infineon [https://www.digikey.com/en/products/detail/infineon-technologies/IRLZ44NPBF/ IRLZ44N].		** but the only through-hole MOSFET I've found that works a damn is the (pricey!) Infineon [https://www.digikey.com/en/products/detail/infineon-technologies/IRLZ44NPBF/ IRLZ44N].
			** the [https://www.infineon.com/cms/en/product/power/mosfet/n-channel/irlb8721/ IRLB8721] also works well
	* The ADC is known to be nonlinear and generally not great.		* The ADC is known to be nonlinear and generally not great.

Dank: /* Annoyances */

2025-03-12T16:33:38Z

Annoyances

← Older revision		Revision as of 16:33, 12 March 2025
Line 2:		Line 2:

	==Annoyances==		==Annoyances==
	* There are plenty of SMT MOSFETs that will work with the ESP32's 3.3V 20 mA outputs..		* There are plenty of SMT MOSFETs that will work with the ESP32's 3.3V 20 mA outputs...
	** but the only through-hole MOSFET I've found that works a damn is the (pricey!) Infineon [https://www.digikey.com/en/products/detail/infineon-technologies/IRLZ44NPBF/ IRLZ44N].		** but the only through-hole MOSFET I've found that works a damn is the (pricey!) Infineon [https://www.digikey.com/en/products/detail/infineon-technologies/IRLZ44NPBF/ IRLZ44N].
	* The ADC is known to be nonlinear and generally not great.		* The ADC is known to be nonlinear and generally not great.

Dank: /* Annoyances */

2025-03-12T16:33:28Z

Annoyances

← Older revision		Revision as of 16:33, 12 March 2025
Line 2:		Line 2:

	==Annoyances==		==Annoyances==
	* There are plenty of SMT MOSFETs that will work with the ESP32's 3.3V 20 mA outputs, but the only through-hole MOSFET I've found that works a damn ~~off~~ is the (pricey!) Infineon [https://www.digikey.com/en/products/detail/infineon-technologies/IRLZ44NPBF/ IRLZ44N].		* There are plenty of SMT MOSFETs that will work with the ESP32's 3.3V 20 mA outputs..
			** but the only through-hole MOSFET I've found that works a damn is the (pricey!) Infineon [https://www.digikey.com/en/products/detail/infineon-technologies/IRLZ44NPBF/ IRLZ44N].
	* The ADC is known to be nonlinear and generally not great.		* The ADC is known to be nonlinear and generally not great.

Dank: /* Annoyances */

2025-03-12T16:33:10Z

Annoyances

← Older revision		Revision as of 16:33, 12 March 2025
Line 2:		Line 2:

	==Annoyances==		==Annoyances==
	* There are plenty of SMT MOSFETs that will work with the ESP32, but the only through-hole MOSFET I've found that works a damn off ~~its 3.3V output~~ is the (pricey!) Infineon [https://www.digikey.com/en/products/detail/infineon-technologies/IRLZ44NPBF/ IRLZ44N].		* There are plenty of SMT MOSFETs that will work with the ESP32's 3.3V 20 mA outputs, but the only through-hole MOSFET I've found that works a damn off is the (pricey!) Infineon [https://www.digikey.com/en/products/detail/infineon-technologies/IRLZ44NPBF/ IRLZ44N].
	* The ADC is known to be nonlinear and generally not great.		* The ADC is known to be nonlinear and generally not great.
	* Devkits with an onboard RGB LED often need a bridge soldered between two points on the board before the LED will function (possibly to avoid accidental eye damage; it's pretty bright).

	==Boot modes==		==Boot modes==

Dank: /* Devkit notes */

2025-03-12T16:32:31Z

Devkit notes

← Older revision		Revision as of 16:32, 12 March 2025
Line 43:		Line 43:
	* Powering via 5V USB is recommended.		* Powering via 5V USB is recommended.
	* Voltage on GPIO47 and GPIO48 is only 1.8 (V<sub>SPI</sub>), unlike the other pins (3.3, V<sub>DD</sub>).		* Voltage on GPIO47 and GPIO48 is only 1.8 (V<sub>SPI</sub>), unlike the other pins (3.3, V<sub>DD</sub>).
	* There are no default I<sup>2</sup>C pins. All GPIOs can be used with either of the two controllers with no penalty.
	* Some devkits require the two RGB pads to be shorted before their WS2812 RGB LED can be used		* Some devkits require the two RGB pads to be shorted before their WS2812 RGB LED can be used
	** I suspect this is because the WS2812 can damage the eyes if looked at directly? Unsure.		** I suspect this is because the WS2812 can damage the eyes if looked at directly? Unsure.

Dank at 16:32, 12 March 2025

2025-03-12T16:32:07Z

@@ Line 36: / Line 36: @@
 ==Product line==
 As of 2024-12:
-===SoCs===
 {| class="wikitable sortable"
 |-
@@ Line 132: / Line 152: @@
 |}
 ===Modules===
 {| class="wikitable sortable"
 |-
@@ Line 563: / Line 585: @@
 |-
 |}
 ==External links==

Dank at 12:49, 21 January 2025

2025-01-21T12:49:21Z

← Older revision		Revision as of 12:49, 21 January 2025
Line 5:		Line 5:
	* The ADC is known to be nonlinear and generally not great.		* The ADC is known to be nonlinear and generally not great.
	* Devkits with an onboard RGB LED often need a bridge soldered between two points on the board before the LED will function (possibly to avoid accidental eye damage; it's pretty bright).		* Devkits with an onboard RGB LED often need a bridge soldered between two points on the board before the LED will function (possibly to avoid accidental eye damage; it's pretty bright).

			==Boot modes==
			There is a bootloader in ROM that runs once the reset is released. The values of strapping pins selects SPI or Download boot mode. In SPI boot mode, the program is run from SRAM after being fetched from flash (Normal Boot), or run directly from flash (Direct Boot); this is determined by inspection of the program header. In Download boot mode, the program is provided over UART, and either written to SPI flash or run directly from SRAM. Software can request a reboot into Download mode. eFuses can disable various paths through the bootloader. Note that the program in flash is commonly a second-stage bootloader, and it is thus which launches the actual user application.

	==SoCs, modules, devkits==		==SoCs, modules, devkits==
	There is a three part nomenclature (taken from the [https://products.espressif.com/#/product-selector Product Selector]): the SoC, the module, and the devkit. The SoC is the lowest-level component; it contains the processor(s), radio(s), SRAM, and possibly flash+PSRAM. A module adds several elements to the SoC (perhaps most importantly, an FCC-approved RF stack), but will still require some circuit design to use. A devkit bundles a module onto a PCB along with other components (perhaps most importantly, a USB interface), and can generally be used by itself.		There is a three part nomenclature (taken from the [https://products.espressif.com/#/product-selector Product Selector]): the SoC, the module, and the devkit. The SoC is the lowest-level component; it contains the processor(s), radio(s), SRAM, eFuses, and possibly flash+PSRAM. A module adds several elements to the SoC (perhaps most importantly, an FCC-approved RF stack), but will still require some circuit design to use. A devkit bundles a module onto a PCB along with other components (perhaps most importantly, a USB interface), and can generally be used by itself.

	[[File:Espc6.png\|thumb\|QFN40 ESP32-C6 and QFN32 ESP32-C6-F[HN]<i>x</i> pinouts.]]		[[File:Espc6.png\|thumb\|QFN40 ESP32-C6 and QFN32 ESP32-C6-F[HN]<i>x</i> pinouts.]]

Dank: /* ESP-IDF */

2025-01-21T06:00:55Z

ESP-IDF

← Older revision		Revision as of 06:00, 21 January 2025
Line 30:		Line 30:

	==ESP-IDF==		==ESP-IDF==
	Espressif provides the [https://idf.espressif.com/ ESP-IDF] as a thin development framework for the ESP32 family, with a unified community [https://components.espressif.com/ component registry]. ESP-IDF projects will typically use [[CMake]] and include <tt>project.cmake</tt> from an ESP-IDF installation.		Espressif provides the [https://idf.espressif.com/ ESP-IDF] as a thin development framework for the ESP32 family, with a unified community [https://components.espressif.com/ component registry]. ESP-IDF projects will typically use [[CMake]] and include <tt>project.cmake</tt> from an ESP-IDF installation. ESP-IDF includes a port of [[FreeRTOS]], though its use is not required.

	==Product line==		==Product line==

Dank: /* ESP-IDF */

2025-01-21T05:58:59Z

ESP-IDF

← Older revision		Revision as of 05:58, 21 January 2025
Line 30:		Line 30:

	==ESP-IDF==		==ESP-IDF==
	Espressif provides the [https://idf.espressif.com/ ESP-IDF] as a thin development framework for the ESP32 family, with a unified community [https://components.espressif.com/ component registry]. ESP-IDF projects will typically use [[CMake]].		Espressif provides the [https://idf.espressif.com/ ESP-IDF] as a thin development framework for the ESP32 family, with a unified community [https://components.espressif.com/ component registry]. ESP-IDF projects will typically use [[CMake]] and include <tt>project.cmake</tt> from an ESP-IDF installation.

	==Product line==		==Product line==