Making Embedded Systems [Repost]

×

Making Embedded Systems [Repost]

Close

Optimize your system to reduce cost and increase performance
Develop an architecture that makes your software robust in resource-constrained environments
Explore sensors, motors, and other I/O devices
Do more with less: reduce RAM consumption, code space, processor cycles, and power consumption
Learn how to update embedded code directly in the processor
Discover how to implement complex mathematics on small processors
Understand what interviewers look for when you apply for an embedded systems job

I was extremely interested in reading this book, partly because it falls in my area of expertise, or at least I thought from the title that it would, and partly because I frequently find gaps in my knowledge base that books like this can fill. On this second point I could not have asked for a better volume. The breadth and depth of the examples and explanations gave me a greater understanding of many of the nuances of embedded systems programming than I had to begin with. The book is well-written and very well organized, and could easily be used as a textbook.

My only regret with the book initially was that it focuses solely on the interface between hardware and software, and does not cover embedded operating systems at all. At first I found this disappointing, and I still think some options could be discussed in an appendix, but I understand that is not the purpose of the book - and quite honestly, I learned so much from it that I can see why the author chose not to include that discussion.

I can't emphasize enough the value of gap-filling knowledge with a book like this.

I would highly recommend this book to anyone learning embedded systems programming who needs to know why an operating system is (or isn't) a good idea for a given project or hardware solution. You should know this stuff before attempting to choose an operating system, which I think is the author's point, and it is very well made