Hacker News new | ask | show | jobs
by wilted-iris 475 days ago
This is unfortunately not emphasized with many breakout boards. It pays off to skim errata sections at the start of a project. All hardware has errata, and it ranges from incorrect details and minor malfunctions all the way through to broken peripherals and all manner of critical malfunctions.
2 comments

To be clear, this isn't a problem with the breakout board. The issue is inside the microcontroller itself, which, iiuc, is why there is such a long lead time on fixing it.
While I agree that reading the errata absolutely should be on the "mandatory TODO before you start" list for any project (esp with new/unfamiliar hardware), one should be equally aware that manufacturers aren't always transparent about the defects in their products, sometimes failing to note that entire subsystems, frankly, don't work.