This board will allow you to clip in an ESP32-S2 WROOM or WROVER module for programming, prototyping and testing. Slot the module into the pins where it will be held securely while you upload your code.
The Board has two USB micro sockets: The first is connected to a CP2104 USB to UART to upload of your firmware and receive serial messages. The second is directly connected to GPIO19 & 20 that are the onboard USB - & + pins.
The board can be powered from either of the USB sockets, the UART USB has a power switch and the S2 USB will directly power the board. These sockets are separated by diodes so neither can reverse power the other. The S2 USB has bridgeable solder pads so that it can be used to supply USB power if acting as OTG Host.
The CP2104 handles the USB to UART conversion as well as putting the module into “programming mode”.
Where Espressif have enabled programming via the S2 USB and the module can be put in “programming mode” using the IO_0 and Reset buttons.
All GPIO pins are broken out to 2.54mm header pins. Caution should be taken as some pins are used by the WROVER module for PSRAM.
You can purchace the S2-MCB from Tindie
This is the latest unstable release of CircuitPython that will work with the Targett ESP32-S2 Module Clip (WROVER).
Unstable builds have the latest features but are more likely to have critical bugs.
Built-in modules available: _bleio, _pixelbuf, alarm, analogio, audiobusio, audiocore, bitbangio, board, busio, canio, countio, digitalio, displayio, dualbank, framebufferio, frequencyio, gamepad, ipaddress, math, microcontroller, msgpack, neopixel_write, nvm, os, ps2io, pulseio, pwmio, random, rotaryio, rtc, sdcardio, sharpdisplay, socketpool, ssl, storage, struct, supervisor, terminalio, time, touchio, ulab, usb_hid, vectorio, watchdog, wifi
Every time we commit new code to CircuitPython we automatically build binaries for each board and language. The binaries are stored on Amazon S3, organized by board, and then by language. Try them if you want the absolute latest and are feeling daring or want to see if a problem has been fixed.
All previous releases are listed on GitHub, with release notes, and are available for download from Amazon S3. They are handy for testing, but otherwise we recommend using the latest stable release. Some older GitHub release pages include the same binaries for downloading. But we have discontinued including binaries as assets on newer release pages because of the large number of files for each release.