What is an errata document and why must you check it?

An errata document lists the ways the actual manufactured silicon deviates from what the datasheet and reference manual describe, in other words, the chip's known bugs: a peripheral that doesn't behave as documented, a register that reads or writes differently than specified, a corner case that misbehaves, often with a recommended software or hardware workaround, and tied to specific silicon revisions. You must check it because the documentation describes the intended design, but real chips have bugs, and a baffling problem where a peripheral does something the reference manual says is impossible is very frequently a documented erratum, engineers who don't know errata exists can waste days fighting an issue the vendor already knows about and has a workaround for. The discipline is to check the errata for your exact silicon revision (which you can read from a device ID register or the chip markings), because issues are fixed or introduced across revisions, so the errata for rev A may not match rev B. Practically, when something behaves inexplicably and your code looks correct, the errata is one of the first places to look, right alongside re-reading the register description and checking your clock configuration. It's a core part of working with real hardware: the datasheet tells you what should happen, the errata tells you what actually happens on this revision.