Read,
never invented
Pins, voltages, and registers come straight from the part’s datasheet — not from the model’s memory.
Describe your project in plain English. Tinqer sources the parts, draws the wiring, writes the firmware (Arduino or ESP-IDF), and runs it on a simulated ESP32 — so you test before you buy. No datasheets, no fried boards.
{ "id": "oled", "type": "ssd1306", "i2c": "0x3c" }, { "id": "btn_left", "pins": { "OUT": 25 } }, { "id": "btn_drop", "pins": { "OUT": 33 } }
## Bill of Materials | ESP32-DevKitC-V4 | Espressif | | SSD1306 OLED 128×64 | I²C 0x3c | | Tactile button ×5 | 6×6 mm |
/* — Button input — */ if (btn_pressed(BTN_LEFT)) { if (valid(cur_piece, cur_rot, cur_row, cur_col - 1)) cur_col--; } if (btn_pressed(BTN_ROTATE)) {█
// no output yet
One agent runs the whole journey — and when the compiler complains, it reads the error and fixes its own code. You just watch the lights come on.
Plain English. That’s the whole spec.
A schematic from real, in-stock parts.
Firmware that fixes its own compile errors.
Compiled and booted on an emulated ESP32, live in your browser.
Same binary, real hardware. No drivers.
A wrong pin number isn’t a stack trace — it’s smoke. So Tinqer never works from memory.
Pins, voltages, and registers come straight from the part’s datasheet — not from the model’s memory.
Resistor values and power budgets are calculated by tools, then checked against the limits.
Hit an unfamiliar part and Tinqer flags it and asks — it never improvises around the gap.
0 guesses.
Tinqer reads them so you don’t. Bring an idea — leave with a working device.
Works in Chrome & Edge today — Web Serial does the flashing.