Trueverit ESP32 Universal IoT Driver MK II
Enhanced version of the original driver board - supports advanced control features and secure updates.
Trueverit ESP32 Universal IoT Driver MK II Pinout
18 pins| Pin | GPIO | Labels | Status | Capabilities | Notes |
|---|---|---|---|---|---|
| 1 | 1 | TXETH_PHY_ADDRPWM | uart | uart | |
| 2 | 2 | T2ETH_PHY_POWERPWM | strapping | touch | |
| 3 | 3 | RXPWM | uart | uart | |
| 4 | 4 | SCLT0PWM | safe | touch · i2c | |
| 5 | 5 | SSPWM | strapping | spi | |
| 6 | 12 | TX1PWM | strapping | - | |
| 7 | 13 | RX1PWM | strapping | - | |
| 8 | 14 | ETH_PHY_MDIOPWM | strapping | - | |
| 9 | 15 | SDAPWM | strapping | i2c | |
| 10 | 16 | ETH_PHY_MDCPWM | safe | - | |
| 11 | 18 | LED_BUILTINSCKPWM | safe | spi | |
| 12 | 23 | MOSIPWM | safe | spi | |
| 13 | 32 | MISOA4T9PWM | safe | adc · touch · spi | |
| 14 | 33 | TX2A5T8PWM | safe | adc · touch | |
| 15 | 34 | A6 | strapping | adc | |
| 16 | 35 | A7 | strapping | adc | |
| 17 | 36 | A0 | strapping | adc | |
| 18 | 39 | RX2A3 | strapping | adc |
Start with these
6 pins with no boot or system involvementFreely assignable - no strapping, flash, USB or JTAG duties. Ideal first picks for buttons, sensors and LEDs.
Fine - with a little care
12 pins · 11 things to knowTXGPIO1 Default UART0 TX pin for USB-serial programming and console. UART
Connected to on-board USB-UART for uploading and logs; drives serial output at boot, so using as GPIO can disrupt programming or console.
T2GPIO2 Bootstrapping pin (must be low or floating at reset); internal pull-down. Strapping
If driven HIGH on reset (while IO0 is LOW), selects an unsupported SDIO boot mode, causing boot failure.
RXGPIO3 Default UART0 RX pin for USB-serial programming (console input). UART
Used for receiving data from USB-UART (programming); also pulled HIGH at boot for console communication, so using as GPIO can disrupt uploads.
SSGPIO5 Bootstrapping pin; internal pull-up; VSPI CS0 (default SPI chip-select); acts as FSPIWP (flash write-protect) on internal-flash variants. Strapping
Must be HIGH during boot; if pulled LOW at reset, alters SDIO slave timing and may prevent normal boot.
TX1GPIO12 Bootstrapping pin; JTAG TDI; sets flash voltage (VDD_SDIO); also HSPIQ (flash data line). Strapping
Keep LOW during boot (internal PD); pulling HIGH at reset selects 1.8V flash mode, causing flash brownout if 3.3V flash is used.
RX1GPIO13 JTAG clock pin (TCK); also ADC2 channel 4 / Touch4 input. JTAG
Used for JTAG debugging (TCK); avoid using as GPIO if JTAG is needed.
ETH_PHY_MDIOGPIO14 JTAG mode select pin (TMS); also HSPI CLK and PWM-capable GPIO. JTAG
Used for JTAG debugging (TMS); driving it as GPIO may interfere with JTAG or produce spurious signals at boot.
SDAGPIO15 Bootstrapping pin; JTAG TDO; controls UART0 boot log output; also HSPICS0 (secondary SPI CS). Strapping
Keep HIGH during boot (internal PU); if LOW on reset, bootloader log is silenced and boot mode may change.
A6GPIO34 Input-only GPIO (no output driver); ADC1 channel 6. Other
Cannot be used as output (no drive capability); only suitable for analog/digital input.
A7GPIO35RX2GPIO39 Input-only GPIOs with ADC1 channels - no output driver Other
Cannot be used as output; only suitable for input.
- A7Input-only GPIO (no output driver); ADC1 channel 7.
- RX2Input-only GPIO (no output); ADC1 channel 3, Hall sensor VN.
A0GPIO36 Input-only GPIO (no output); ADC1 channel 0, Hall sensor VP. Other
Cannot be used as output; only suitable for input (e.g., analog read).
All 18 pins on the Trueverit ESP32 Universal IoT Driver MK II are usable GPIO.
Peripheral wiring is straightforward: I²C is mapped to SDA on GPIO15 and SCL on GPIO4; the SPI bus (MOSI, MISO, SCK, SS) is broken out in full; TX/RX on GPIO1 and GPIO3 cover serial logging and flashing.
Beyond plain digital I/O you get 6 ADC-capable pins for sensors and battery monitoring and 4 capacitive-touch inputs.
12 of the exposed pins carry boot-time or system duties on the ESP32 (TX, T2, RX and 9 more) - check the guidance above before wiring anything to them. SCL, ETH_PHY_MDC, LED_BUILTIN, MOSI and 2 more are free of any such role - the safest first picks.
Getting started
flash your first firmware in ~2 minutesBoard: ESP32 Dev Module Flash Size: 4MB (32Mb) Flash Mode: DIO Partition Scheme: Default 4MB with spiffs (1.2MB APP/1.5MB SPIFFS) Upload Speed: 921600
// toggle GPIO4 - wire an LED and resistor to it
void setup() {
pinMode(4, OUTPUT);
}
void loop() {
digitalWrite(4, HIGH); delay(500);
digitalWrite(4, LOW); delay(500);
}[env:esp32-trueverit-iot-driver-mkii]
platform = espressif32
board = esp32dev
framework = arduino
monitor_speed = 115200
upload_speed = 921600esp32dev - or type it after board =.esp32:
board: esp32dev
variant: esp32
framework:
type: esp-idf
# blink - GPIO4
output:
- platform: gpio
pin: 4
id: led_out
light:
- platform: binary
name: "LED"
output: led_outesp32dev (same ids as PlatformIO).esptool.py --chip esp32 --port /dev/ttyACM0 \
--baud 921600 write_flash 0x1000 firmware.bin--port = your /dev/tty* (macOS/Linux) or COMx (Windows).Specifications
ESP32 · vs other ESP32 chips →About this board
Inside sits the ESP32 - a dual-core Xtensa with both Bluetooth Classic and BLE.
Only 18 GPIO are broken out, where most ESP32 boards manage about 24 - worth checking the pinout covers what you need.
Around the module: wired Ethernet (DP83848).
Resources
Similar boards
