[{"_1":2,"_42":-5,"_43":-5},"loaderData",{"_3":4,"_10":11,"_40":-5,"_41":-5},"root",{"_5":-5,"_6":-5,"_7":-5,"_8":9},"user","shoppingCartId","toast","locale","en","routes/_store+/_readers+/email_author.$slug/route",{"_12":13,"_39":-5},"book",{"_14":15,"_16":17,"_18":19,"_20":21,"_22":23,"_24":25},"id","Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6Qm9va1Byb2R1Y3QvNjM3MjI","title","The Guide to I2C Debugging","state","published","contactAuthorMethod","email","aboutText","

I was challenged a few years ago to write a book about debugging low-level protocol issues. I was well-known at work for my understanding of I2C, SPI, and UART protocols. As an embedded software and firmware engineer, I've tackled these issues in C, assembly language, and verilog. Maybe it was time to share my 30 years of experience.

This book was meant to be a terse guide to debugging common issues. As I started writing, I caught myself adding prequel chapters about embedded software in general. I know the book needs to be fixed.

This book is very much a work in progress. The version shared here was \"completed\" during a three-month sabbatical, so is necessarily short, with omissions, errors, and a few stub paragraphs alluding to information yet to come. I am sharing the text here, offering it for free. If there is enough engagement, then I will continue development of the book.

","authors",[26],{"_14":27,"_28":29,"_5":30},"Z2lkOi8vbGVhbnB1Yi9TdG9yZTo6UHJvZHVjdEF1dGhvci82NzU3Mg","name","Alex O'Donnell",{"_31":32},"avatar",{"_33":34,"_35":36,"_37":38},"url","https://secure.gravatar.com/avatar/f75bc32a2d955ba6f78d991a1494c3a8?r=pg&d=mm","styleName","medium","exists",true,"currentUser","routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

Email the author