---
id: M06-L01
title: Read the exact board and sensor documents
module: M06
chapters: "12"
checkpoint: CP04
---

# M06-L01 — Read the exact board and sensor documents

Produce a short constraints table whose values can be traced to the correct object and source. Begin with CP04 and the constraints skill from Module 5. This lesson uses documentation only; ownership of the optional board and breakout is unnecessary.

Start by writing the exact example identity: Adafruit Feather ESP32-S3, product 5477, with 4 MB flash and 2 MB PSRAM. The manufacturer distinguishes this from another memory variant. Copying a family name while losing the variant can select an inappropriate build configuration. [Adafruit product 5477](https://www.adafruit.com/product/5477).

Separate four things in your notes: the sensor chip, the breakout containing it, the host board, and the pinned software support package. A chip supply specification describes the silicon's connection. A breakout can add a regulator and expose a different input. A host-board guide explains its connectors. A software variant determines which symbols and initialization apply to the selected build.

For example, the BME280 chip documentation and Adafruit breakout guide describe different supply connection scopes. Read the object and connection point before comparing their numbers. A breakout Vin allowance is not permission to apply that voltage directly to a bare chip. [Bosch BME280 technical data](https://www.bosch-sensortec.com/en/products/environmental-sensors/humidity-sensors-bme280), [Adafruit breakout power pins](https://learn.adafruit.com/adafruit-bme280-humidity-barometric-pressure-temperature-sensor-breakout/pinouts).

Open `docs/hardware.md` and follow its primary links. Record document title, revision or pinned version when available, section, and access date. An access date says when you checked the page; it does not identify the revision of an unseen physical board. Use “physical revision not observed” until such evidence exists.

Ask the constraints skill for claim, value/unit, source section, confidence or missing data, and consequence. Keep the request bounded to the intended interface. A useful output might identify the exact memory variant, connector signals, default address, and unresolved physical jumper state. Review each factual row against the actual section. The consequence is your design interpretation, so label any inference.

The Feather guide describes its STEMMA QT signals and an unpopulated BME280 footprint. The separate breakout guide describes the sensor's address configuration. Neither establishes that a particular unseen assembly is connected or populated. Avoid combining a footprint label, a familiar address, and a confident answer into an invented physical observation. [Feather pinouts](https://learn.adafruit.com/adafruit-esp32-s3-feather/pinouts), [BME280 pinouts](https://learn.adafruit.com/adafruit-bme280-humidity-barometric-pressure-temperature-sensor-breakout/pinouts).

Preserve units and conditions when extracting. The original teaching statement “1000 ms reporting interval” means one second; it is not a measurement of bus latency. A typical number is not automatically a guaranteed limit. When the source does not establish a pin or condition, write the missing item and the decision it affects.

Complete the exercise by reviewing one deliberately mixed-scope proposal. The observable check is a table that another reader can audit without searching an old chat. A valid skill file or a polished response is insufficient if a factual row remains unsupported.

## Resources and completion

Use CP04, Chapter 12, `docs/hardware.md`, `dependencies.json`, and the project constraints skill. Figure references are SS12-01 and SS12-02. Complete [the exercise](exercise.md), then consult the [answer key](answer-key.md). Keep actual source/agent observations distinct from the supplied example.