Rating: 
Summary: Get this book if you have any interest in embedded code
Review: I've been working for a year now with guys who do embedded software. So many things are now clear to me! Hey, now I now why one guy is working on a monitor task! It's like I've been groping in the dark and someone has turned the lights on. I particulary liked the way the author explained what features are needed for an OS to be a real time OS (RTOS). When you are fresh out of school the experts might explain what's going on, but once you have any experience it's sink or swim. This book will help you avoid sinking.
Rating: 
Summary: Good for students, but only for them
Review: If you are a student who is wondering what the difference between ROM and RAM is and how to compile and run an embedded version of a "hello,world" programm, than you might find some use of this book. It also give a few tips (such as that inlining improves the speed but increases the code size). If you know this already, than this book is a complete waste of your money. If you are developing a real embedded system and you have specific problems and questions, you will not find the answers in this book. In particular, don't get misleaded by mentioning C++ in the title. There are only few sentences about the efficiency of C++ features and they do not go anywhere beyond the general knowledge.
Rating:
Summary: Great Book for Beginners
Review: If you are new to the world of embedded systems, this the way to go. This book explains the fundas very neatly. A little more stress on the hardware part would have made the book even better.
Rating:
Summary: Excellent book for beginners ....
Review: If you have just heard about embedded systems and are interested in knowing more this is "the" book for you.The author presents his views in a simple,lucid manner.The book moves like a story.Once you start it you are tempted to read more and more and more.You just don't feel like putting it down.He explains so many difficult concepts so easily.Hats off to you,Michael !!It's really good that he took one Arcom board and remained stuck to it thruout the book.That helped me a lot to know the subject better.
Rating:
Summary: Greate Book
Review: If you want to explore the Issues of Embedded Systems READ THIS BOOK, Micheal Barr is an real capacity in this area.He should be rewarded for this book, and please please write another book soon
Rating: 
Summary: Not a book for experts
Review: The book is ok if you are a student or if you don't know what embedded systems are. Otherwise it is a total waste of money. For the expert it has no interesting information. C++ is only in the title.
Rating: 
Summary: Good Book, Bad CM
Review: The book is well written, and it introduces embedded systems programming at a novice level. I learned a great deal from the book and the example code. Here are the negative comments, but good things can result from bad so please read the entire review. He states in the book that he has done most of his programming in C. This fact can be seen in the architecture of his C++. For instance, he uses globally constructed classes in different compilation units. This is a no-no according to the author of the language. In addition, the example code was not tested on new versions of the Borland compiler, although he eludes that latter versions should work. They do not. For the good however, in pouring through the code and the book, with different compilers, etc., I learned a great deal about the inner workings of a small RTOS and various related issues. I do recommend this book, but allow yourself plenty of time with the source code.
Rating: 
Summary: Something for the beginner and experienced alike.
Review: This book gives a good introduction without being so basic that the experienced programmer loses interest. I read it cover-to-cover in an afternoon. I've been programming embedded systems for about 5 years, the last year or so in C++ and found the discussion of C vs. C++ as they relate to the embedded world of particular interest. I also learned some new tricks in the Optimization chapter. Every programmer I know has O'Reily books on their shelf. This is my first, definitely not my last.
Rating:
Summary: This book is a most advanced and comprehensive compendium.
Review: This book is indeed quite usefull, as so it has assisted me with essential information that will help: Engineers: design better embedded PC hardware Programmers: write high-performance embedded firmware Technicians: debug obstinate ISA bus gadgets Students: relate abstract theory to applications Enthusiasts: control unique projects with standard PCs The topics range from pure firmware to detailed hardware, including the BIOS routines and circuitry on the PC's side of the ISA bus that you can use throughout your embedded systems designs. Examine: I/O ports, memory, IRQs, and bus cycles Control: hardware with C and Assembly language Adapt: working source code and programs *Gadgets* Build: ISA bus memory and I/O circuits Protect: code with watchdogs and power monitors Identify: hardware with unique serial numbers Display: text and graphics on big LCD panels *Practical Tricks* Run: code in EPROM, EEPROM, or nonvolatile RAM Measure: wait states and interrupt latency Fix: hardware problems with firmware Debug: firmware using hardware outputs Reading Michael Barr's book, "Programming Embedded Systems in C and C++", I couldn't help thinking about Volkswagen Bugs. In the 70's, tinkerers put VW engines into buggies, hovercraft, helicopters, snowmobiles, airplanes, etc. Now, Michael is showing us how to use cheap, reliable, adaptable, and surprisingly powerful PC motherboards as 'volks controllers.' This book's generous code listings, diagrams, projects, and crystal-clear explanations make embedding a PC easier than a VW tune up. -Raymond Edwars, Chief Technical Engineer
Rating:
Summary: A good book, a little sponsored
Review: This book is rather concise and clear. You could take a board and put it to work in minutes. This book also make clear distinction about locators, compiler and other stuffs that could (for the beginner) cause a bit of confusion. I give 4 stars because the book is too tied to a particular board , about the examples. So, if you have something other hardware, you are out of luck.
| 
