Boards that serve their own screen
Firmware in C, the screen as a definition, and a host that never changes when you add a device.
Foundations4 lessons23 min
- 1On a Chip — Firmware in C, the Screen as a DefinitionPutting a screen on an eval board usually means adding a graphics stack and reflashing. Instead the board hands over its capabilities as tools and its screen as a resource. Attached to an STM32H723 on the desk, turned the LED on, and rendered the 656-byte screen the board handed over.6 min
- 2The Device Hands Over Its Screen — Two Boards, Each Giving Its Own DefinitionChange one premise. The screen is defined by the device, not the host. Then a device nobody has seen before can be operated the moment it attaches. Confirmed on an STM32 and an ESP32 sitting on a desk — no simulation, real boards handing over their own screens, a real LED lighting. And the screen carries control, not just picture.5 min
- 3One More Device Attached — The Host Was Not TouchedPutting several devices on one screen normally means the host writes the joining logic, so every added device means editing the host. Here that joining moves down into the document. We put three devices on one page, added a third, and checked whether the hash of the host binary changed. Then we killed one.5 min
- 4When the Instrument Has No Dedicated SoftwareInstruments already know how to talk. The problem is that three vendors answer three ways — exponent notation, a carriage return, a value with the unit glued on. Those three were made one shape and put on one screen. And the screen shows the number the meter said, not the number the knob was set to.7 min