Errata Lens: an ESP32 agent that knows when the datasheet is wrong

Description and use

Errata Lens is a tool that checks whether a specific ESP32 erratum applies to the chosen silicon revision, using a Knowledge Base and GROQ queries.

Problem

ESP32 datasheet is identical across silicon revisions, but errata differ; engineers cannot quickly determine if a bug applies to their exact revision, leading to wasted time and potential failures.

Outcome

The agent accurately reports revision‑specific errata, such as identifying that WDT‑3.15 only appears on v3.x and that GPIO‑3.11 is a known glitch on v1.1. It provides counts of fixed and new errata when upgrading revisions, enabling informed decisions.

Workflow

• 1. User selects silicon revision in the web app.
• 2. User asks a question (e.g., "Is GPIO36 safe with Wi‑Fi on?").
• 3. Agent identifies revision via local tool or user input.
• 4. Agent queries Knowledge Base for datasheet statements.
• 5. Agent queries GROQ database for errata affecting that revision.
• 6. Agent compiles answer with datasheet, errata overrides, and revision context.
• 7. User reviews answer and takes action.

Evidence

Errata Lens answers ESP32 questions the way a careful senior engineer does: it checks whether the chip's errata overrides the datasheet, for the exact silicon revision on your board.

Source

The build distilled 118 documents into 23 entries, tagging the errata topics [core] because the Knowledge Base's purpose names them.

Source

It got those counts (25 on v1.1, 23 on v3.1) from GROQ joins, then read the Knowledge Base for the WDT-3.15 workaround: a level 4/5 timer interrupt on each core.

Source