<< 1 >>
Rating: 
Summary: Think carefully before you buy
Review: I bought this book based on the previous reviewer's recommendation. However, I must admit that I was very disappointed with the book after opening it. The book is a collection of author's tips, and talks nothing about "firmware". Don't waste your money, unless you want to have something to read at bedtime.
Rating: 
Summary: A MUST have book for your Embedded Systems bookshelf!
Review: If you are involved with embedded system designs, this is a book for you. Mr. Ganssle brings some of his numerous years of experience as well as the experience of other well know authors in this book.You will get hardware and software design tips and techniques, ways to improve code quality, debugging techniques, ways to speed up math functions, two chapters on state machines, how to do memory tests, discussions on reentrancy, the correct way to use a watchdog and much, much more. You will find Jack's writing style both clear and pleasant. A MUST have on your embedded bookshelf.
Rating:
Summary: A MUST have book for your Embedded Systems bookshelf!
Review: If you are involved with embedded system designs, this is a book for you. Mr. Ganssle brings some of his numerous years of experience as well as the experience of other well know authors in this book. You will get hardware and software design tips and techniques, ways to improve code quality, debugging techniques, ways to speed up math functions, two chapters on state machines, how to do memory tests, discussions on reentrancy, the correct way to use a watchdog and much, much more. You will find Jack's writing style both clear and pleasant. A MUST have on your embedded bookshelf.
Rating: 
Summary: Good For Large Dev Teams
Review: It's true this book is NOT a comprehensive guide to developing firmware from conception to delivery. It is, however, a practical guide to several aspects of the firmware development process--especially if you work on a large team or for a big company. Unlike most books covering this topic (I have at least half a dozen recent examples) it's fairly easy to read. Ganssle drops in just enough humor and "real life" anecdotes to keep the reader engaged in what would otherwise be pretty dry material.
Sadly, I've yet to find the "one complete book" that someone should read above all others. Some are aimed at hobbyists, some are aimed at those working within the structure of a large company. Some focus more on specific target environments, some focus more on high level concepts with few real-world examples.
Jack's books are mostly written from the perspective of working with large firmware development groups at large companies. If you're a one or two person show, his books may not be the best match. A lot of what's diccussed relates to things like coding standards, interfacing with management, teamwork, version control, project schedules, etc. The material is largely written from the perspective of different groups performing hardware development, firmware development, product testing and product maintenance.
The most benefit from Jack's books would likely come from having senior management read them. Unfortunately, senior managers are among the least likely to read such books. So it's up to those further down the hierarchy to "sell" his concepts to others within the company.
Rating:
Summary: Fun to read, but not a handbook.
Review: The book is a collection of articles in various aspect of embedded programming. I found out I already read some of them on www.embedded.com. It is not a tutorial to someone totally new to embedded world, but it is very useful if you already have two years experience (or more). I feel it is a great book because there is something I can learn and apply to my project. It is fun to read a chapter when I have half hour.
I do not give it a five star because it names itself Handbook, but not cover enough topic and lack of further reference if you want to dig deeper.
<< 1 >>
| 
