Reusable Firmware Development: A Practical Approach to APIs, HALs and Drivers

Exactly what I needed.

It does go into some basics, but those basics are things overlooked by beginner and intermediate firmware engineers...especially using const, volatile, extern keywords. It really does explain how to start and update an existing foundation for portable firmware.I'm half way through the book and at the practical examples chapters. It's so good that I'm preparing a "lunch and learn" session with our firmware group to compare our practices to this book and how we can improve.We use common firmware across multiple products, and after the first chapter I saw room for improvement on our end.Great read, and recommended to anyone trying to make their code portable.

A very practical book on reusable firmware development. A great reference for a practicing firmware developer with examples provided for each topic.Provides a good insight into the thought process of a renowned embedded systems engineer.

Must read book for one involved with low level peripheral driver development. If you are new to embedded development this will book definitely help to shape carrier in embedded system development. It explains techniques and principles develop device independent driver

Libro sobre desarrollo de firmware, bastante completo, recomendado al 100%, los capitulos de los que consta son:1-Concepts for Developing Portable Firmware2-API and HAL Fundamentals3-Device Driver Fundamentals in C4-Writing Reusable Drivers5-Documenting Firmware with Doxygen6-The Hardware Abstraction Layer Design Process7-HAL Design for GPIO8-HAL Design for SPI9-HAL Design for EEPROM and Memory Devices10-API Design for Embedded Applications11-Testing Portable Embedded Software12-A Practical Approach to Code ReuseY pues como se puede ver viene bastante completo.

First half is light on details and concrete examples but it's important info to know for a junior developer. If you have experience in the industry already you *should* know these topics by heart, but it's still a decent read. I'm still working my way through the second half but I'll update my review when I'm done.There are some weird editing mis-steps that I need to mention. First is that the diagrams were obviously done in colour and then the book was printed in grey scale, so some of the charts are hard to read. Minor issue. Second is that the same chapter quote is listed on two different chapters, which a quick skim of the book should have been caught by the editor.The third deserves its own paragraph. When you write a book on programming you absolutely, positively, need to make sure the programming examples are 100% accurate and correct. A single missing character can be extremely confusing for novice readers. In this case the missing character is the absolute worst character to forget: '*' as a pointer dereference. All of the "volatile" examples on pages 98 & 99 are missing a pointer dereference, making any discussion on volatile pointless (pun-intended).

Geat

Der Autor hat die richtige Intention und versucht eine Lücke zu schliessen. Dies gelingt ihm aber nicht wirklich, weil dem gesamten Buch der rote Faden fehlt. Dafür kommt es quasi ständig zu gebetsmühlenartigen Wiederholungen.Die Wiederholungen gehen sogar so weit, das die Zitate am Anfang von Kapitel 3 und 4 gleich sind.Auch schafft es der Autor nicht eine klare Trennung zwischen Driver und HAL zu ziehen.Im Buch fehlen mir zudem wichtige Aspekte wie der Aufbau einer wiederverwandbaren Projektstruktur mit cmake. Mehr Struktur und ein roter Faden würde dem Buch gut tun.Ich persönlich würde eher die Bücher von Scoot Meyers, Herb Sutter und James O. Coplien empfehlen, dazu dann noch Multi-Platform Code Management von Kevin Jameson sowie eine Prise Domain Driven Design und natürlich Patterns.Für Studenten und Anfänger gibt das Buch aber sicherlich einen guten Einstieg in die Thematik.