← Featured Sprints

Board-Up Sprint

2 weeks · US$ 2,800 · special price through Dec 31, 2026 · 10 slots at this price

Your Board, Running Real Firmware, in Two Weeks.

Ship us your boards and schematics. We bring up the firmware on your hardware (power, clocks, drivers, connectivity and an update path), wire a test rig to it, and hand you a written list of what stands between this board and your pilot.

  • Bring-up firmware. Clocks, power, peripherals and drivers on ESP32, ESP8266 or Arduino-class boards (embedded Linux modules and other families on request), in a repo with a CI build.
  • Connectivity and update path. Data from the board to your backend over Wi-Fi or BLE with MQTT, or wired Modbus and serial links. Over-the-air updates working, or designed with a signing plan when the hardware isn't ready.
  • HIL test rig. A hardware-in-the-loop rig wired to your board that runs the smoke test on every build. It stays with you.
  • Bring-up report. What works, what doesn't, hardware findings for your EE, and the punch list to pilot.
  • If the board doesn't reach the agreed milestones for reasons on our side, we refund it in full. The clock starts when the boards arrive.
  • Sign a build or retainer within 30 days and the full fee comes off it.
  • Code, test rig, report and findings are yours either way.

For: Hardware teams with boards back from fab.

  • A board that talks. Peripherals verified on your hardware and data reaching your backend.
  • A test rig you keep. A hardware-in-the-loop rig that runs the smoke test on every build, shipped to you at the end.
  • A pilot punch list. Hardware findings for your EE and everything left before your pilot, in order, with an estimate for each item.
  • Before day 1. You ship 3 boards with schematics and the bill of materials. We start on the same MCU's dev kit while they travel.
  • Week 1. Power-on, clocks, peripherals and drivers, with a live debug session alongside your hardware person.
  • Week 2. Connectivity, update path, the test rig running the smoke test, the report and a readout call.
  • After. Boards and test rig ship back to you.
  • Your first or second board spin is back from fab and nobody owns the firmware yet.
  • Your firmware engineer is overloaded and the board is waiting.
  • ESP32 and ESP8266, Arduino-class boards, Modbus and custom serial hardware.
  • There is no schematic yet: start with a Firmware Discovery Sprint.
  • Safety-certified medical or automotive firmware: we scope that separately.
“The team at ByteNana is top tier. They always know how to accomplish whatever programming project I throw at them.”
Trey, CEO, AceminotUpwork reviewThe work Firmware, software and IoT projects.
“He developed a driver for custom hardware with very little guidance. He proposed and implemented a serial protocol that made it very easy for us to interface with the hardware.”
Jonas, client of Nathan (our CTO)Upwork reviewThe work A Modbus driver for a custom Arduino-based board.
“I needed help troubleshooting an problem with a prototype we were building on breadboard. He was knowledgeable and quick thinking. We identified the problem and fixed it in no time.”
Andrew, client of Nathan (our CTO)Upwork reviewThe work An updater for ESP8266 devices and an environment sensor.

Read the full client reviews →

Start a Board-Up Sprint

Board-Up Sprint: what teams ask first.

What if our board has a hardware bug?

We document it, work around it where we can, and tell your EE exactly what we saw. Finding it now is cheaper than finding it after the next spin.

Do we really need to ship hardware?

Yes, 3 boards. Bring-up happens on real hardware, never only in a simulator. Boards and the test rig ship back to you at the end.

What is the test rig?

A hardware-in-the-loop (HIL) bench wired to your board that runs the smoke test on every firmware build, so a broken build is caught before it reaches a device. It is yours.

Which microcontrollers?

ESP32 and ESP8266 are proven in production with clients, along with Arduino-class boards and Modbus hardware. Other families (STM32, nRF) and embedded Linux modules: ask.

Who owns the code?

You do, from the first commit.

What comes after?

Most teams move to a build retainer or a part-time tech lead to take the board to pilot.

Tell us about your board.

Send the schematic summary and the deadline. A tech lead replies within one business day with what we would check first.

Ready to build with ByteNana?

Initialize your project →