Chip to Ship · ESP32 in five phases

Learn

Intro, terms, and tools

Chip to Ship turns a dev board into something you can hold up and demo in five phases. You prepare the kit, practice blink and Serial, produce sensor + connect work, prove it is safe and working, then present a physical product story — not a Cloudflare URL.

GPIO (general-purpose input/output) pins are where wires plug in — numbers on the board matter; check a pinout diagram. Sketch is the program you upload to the board (Arduino calls them sketches). Serial is text sent between board and laptop in the Serial Monitor — your first proof the code is alive.

With a parent, unpack on a dry desk — no drinks near the board. Confirm a data-capable USB cable (charge-only cables fail silently). Install Arduino IDE or PlatformIO and add ESP32 board support. Never plug in without a parent nearby the first time.

You’ll know it when: kit photo + terms list + IDE open with ESP32 board selected.

If stuck: Charge-only cable? Swap cables before blaming code. Board not in the list? Follow Espressif docs for board manager URL.

Parent tip: Stay nearby for first USB plug-in — agree when they ask for help vs experiment alone.

Learn

Install tools and blink

With a parent, unpack the kit on a clear, dry desk — no drinks near the board. Confirm you have a data-capable USB cable (charge-only cables are a classic stuck point). Install Arduino IDE or PlatformIO and add ESP32 board support from the Espressif docs.

Select the right board and COM port, then upload the classic blink sketch. Open Serial Monitor at the matching baud rate and print a hello with your name or a joke. Photograph the blinking LED — that’s your first hardware proof.

You’ll know it when: blinking LED + Serial line with your name or joke.

If stuck: Check COM port, cable, and board selection. Search your exact board model + “blink ESP32”. Hold the BOOT button on some boards while uploading.

Parent tip: Stay nearby for the first USB plug-in — agree when they ask for help vs when they experiment alone.

Learn

Wire sensor and send data out

Pick one sensor and find a pinout diagram for your board — GPIO numbers are not the same as the silkscreen labels on every module. Wire with a breadboard diagram; keep power and ground clear; no loose wires on a metal desk. Have a parent do a second-eyes check before you plug USB back in.

Print readings in plain words (“bright”, “23°C”, “too close”) so a non-coder can understand Serial. Make an LED or buzzer react when a threshold is crossed — that’s the start of a product behaviour, not just raw numbers.

Connect the board to home Wi‑Fi or Bluetooth so the sensor leaves the Serial Monitor. Never hard-code passwords in a file you’ll push online — use a local secrets header or type credentials only on your machine. Guest Wi‑Fi or a phone hotspot is fine if your family prefers it.

Serve a tiny page from the ESP32, use a simple phone-friendly readout, or bridge values another way your family can open on the couch. Success is “they can see the number without your laptop Serial window” — not a public website on the internet.

You’ll know it when: Serial output + threshold reaction + live readout on phone browser on home network.

If stuck: Swap sensor pins one at a time; never force connectors. If values jump wildly, check pull-ups, ground shared with the board, and whether the sensor needs 3.3V not 5V. Print Wi‑Fi status codes to Serial first; fix connection before any UI. If the page won’t load, confirm phone and board are on the same network and check the IP in Serial.

Parent tip: Be the second pair of eyes on wiring before power-on. Share guest Wi‑Fi or a hotspot if you prefer.

Learn

Safety check and one fix

Audit your code and notes: no Wi‑Fi passwords in files you might share. Secrets stay offline — local header or typed only on your machine.

Invite family to see the live readout once — couch demo on home network counts. Narrate what the sensor means in plain words.

Fix one wiring or code bug you noticed during the demo. Write what broke and what you changed.

You’ll know it when: secrets OK note + family saw readout + one fix note.

If stuck: Wi‑Fi flakes? Fall back to Serial on laptop and narrate — still valid proof before present phase.

Parent tip: Cheer the fix, not just the blink — debugging is the craft.

Learn

Tell the product story

Name the product (plant monitor, desk thermometer, door alert…). Write who it’s for and what problem the sensor solves. Mount the board so wires don’t flop — cardboard and tape beat a tangle on the table. This week’s demo is the physical thing in your hands, not a polished marketing site.

Practice: story → live readout → one cost, power, or enclosure choice for v2. Film a 30-second backup video in case live Wi‑Fi fails. Invite family to ask one question after you finish.

You’ll know it when: named, mounted build with live readout and a one-line v2 note.

If stuck: If Wi‑Fi flakes, fall back to Serial on a laptop screen and narrate — still a valid product demo. Tape beats another hour of “perfect” wiring.

Parent tip: Time the demo — cut filler, cheer the finish, ask one curious question.