Hardware Examples Overview

Editable, board-specific examples that connect generated ForgeUI contracts to developer-owned physical hardware code.

A proven hardware integration pattern

Hardware Examples are ordinary editable ForgeUI projects paired with board-specific wiring, stable generated API contracts, developer-owned example code and physical proof records. They demonstrate integration boundaries; they are not Native Components and ForgeUI does not take ownership of arbitrary hardware drivers.

text

GPIO input
  → developer-owned code
  → generated Runtime SDK
  → ForgeUI UI

ForgeUI UI control
  → genuine generated UserEvent
  → developer-owned code
  → GPIO output

Five physically proven examples

Example	Device / allocation	Status
01 — GPIO Digital I/O	GPIO2/4 buttons; GPIO3/5 LEDs	PHYSICALLY PROVEN
02 — I²C FRAM Persistence	MB85RC256V at 0x50 on shared GPIO7/8	PHYSICALLY PROVEN
03 — SPI NFC/RFID	PN532 on GPIO28–31; GPIO2 reset	PHYSICALLY PROVEN
04 — Online Services — Live Weather	Stock C6 Wi-Fi + certificate-verified Open-Meteo HTTPS	PHYSICALLY PROVEN
05 — GPS / GNSS	u-blox NEO-8 on UART1 GPIO3/GPIO4	PHYSICALLY PROVEN

Hardware Example 01GPIO Digital I/O wiring, generated contracts and proof.Open guide →Hardware Example 02Shared-bus FRAM identity, write/read/verify and power-cycle persistence.Open guide →Hardware Example 03Software-SPI PN532 identity, polling, UID and presentation de-duplication.Open guide →Hardware Example 04Live Open-Meteo conditions, forecast, time, icons and dynamic local backgrounds.Open guide →Hardware Example 05Full-duplex UART GPS/GNSS, live NMEA fields and UBX request/response proof.Open guide →Board Hardware / Pinout EvidenceAudited ownership, restrictions and conditional allocations.Open guide →

Exclusive generated selection

Selecting a Hardware Example replaces the active example project. Only that example's UI is generated, implementation is linked and runtime is initialized. Mixed example contracts are rejected; unselected examples remain preserved but inactive.