Core concepts
Hardware knowledge
How Flash grounds its answers in your hardware: the catalog, datasheets, schematics and knowledge packs.
Where it comes from
Flash works from the hardware you select and its documents, not from what a model remembers.
| Source | What the agent gets |
|---|---|
| Target and board | MCU, board and framework from the hardware catalog, confirmed by /init. |
| Components | The exact parts on your board, added with /peripherals. |
| Datasheets | Searchable text with page references. Flash can also read the original page when a table does not extract cleanly (requires Poppler’s pdftoppm). |
| Schematic and PCB | Components, pins and nets from your hardware design: edited in Flash IDE, viewed in VS Code, read by the agent everywhere. |
| Knowledge packs | Curated facts and guidance for a specific component, each with its source. |
Knowledge packs
A knowledge pack, sometimes called a skill, holds curated knowledge for one component: bus addresses, limits and timing with their conditions, usage guidance and common workflows. Every fact cites its source.
Flash applies a pack automatically when it matches the exact part in your project; you never install or call one. Packs are data only: they cannot run code or grant permissions.
Select the exact part
Choose the part number fitted to your board: its own datasheet and knowledge take precedence over the family’s. For a part that is not in the catalog, add a custom peripheral with your own documents.
Ask for grounded answers
Ask Flash to cite the datasheet page or schematic net behind a decision. When the evidence is missing, it says so instead of guessing.
Explain the initialisation sequence for the selected sensor. Cite the datasheet pages and schematic nets you rely on, and list any board details you could not confirm.What it does not prove
A value found in a datasheet still needs checking against your board’s wiring and operating conditions.