Rating: 
Summary: Excellent book, excellent content, very well written!
Review: I shouldn't need to say more; If you're interested in learning about writing software for embedded systems, this book will take you by the hand and get you there without a lot of fuss or difficulty in trying to figure out advanced topics from a 50,000ft perspective. It drills into each discussion using simplified but not simpleton characteristics of this writer's excellent skill. I recommend this book to every software engineer starting on the path to developing embedded systems. The use of uCOS-II is a decent idea, especially for everyone interested in doing a little embedded systems development using PC hardware...however, I believe that it is a less-than perfect choice because of the rather limited compiler choices for uCOS-II, which should at least include GNU's gcc, but doesn't last time I checked.
Rating:
Summary: Great for beginners and undergraduate level students
Review: I started working on an embedded platform 1 year ago. Although now I have a good understanding of a lot of the aspects of the system, I never get the big picture. This book provides exactly what I needed. If you are a working software engineer and have spent years doing high level programming, the first few chapters will give you a good review of low-level-close-to-the-machine things that you need to know, which is also very useful for students as these are very important concepts that they need to understand to have a solid foundation to conquer higher level, more abstract CS subjects. In embedded system, bugs in task code can bring down the device. Author has done a very good job explaining how to protect shared data using mechanism provided by a RTOS. The communication between interrupt/task and among tasks are also discussed thoroughly. Unlike the other reviewer, I found the use of the C!! language in this book a very clever way to abstract away the hardware dependent code from the point being discussed. Consider it pseudo comment if you will. BTW, the excellent typesetting and use of fonts also makes it a very pleasant experience reading this book. Looking forward to see a more advanced text on embedded system from this author in the future.
Rating: 
Summary: Way to basic!
Review: I've been working with embedded systems for 10 years, and found lots of info, I hadn't seen or read before. The chapters on hardware is good info, and the review of RTOS architectures and core functions was a nice refresher. If you're new to embedded system design, then I'd highly recommend this book to nail down the basics.
Rating:
Summary: A must-read Embedded Software Primer
Review: If you are going to buy only one book on Embedded Software Programming, this should be the one. The author introduces virtually everything an engineer needs to know about programming embedded systems. There are two chapters describing hardware stuff that is useful for the software engineer to know. There is a chapter on Interrupts. There are three chapters on programming in an RTOS environment. All of the chapters include coding examples on what to do, and also examples of code with bugs to watch out for. There is also a chapter on debugging techniques. All of the other FIVE STAR reviews (and many of the FOUR STAR ones as well) contain more specific points which I won't repeat here. However, I will echo what I said at the beginnning. If there is only one book you are going to buy about programming embedded systems, this should be the one.
Rating:
Summary: A must-read Embedded Software Primer
Review: If you are going to buy only one book on Embedded Software Programming, this should be the one. The author introduces virtually everything an engineer needs to know about programming embedded systems. There are two chapters describing hardware stuff that is useful for the software engineer to know. There is a chapter on Interrupts. There are three chapters on programming in an RTOS environment. All of the chapters include coding examples on what to do, and also examples of code with bugs to watch out for. There is also a chapter on debugging techniques. All of the other FIVE STAR reviews (and many of the FOUR STAR ones as well) contain more specific points which I won't repeat here. However, I will echo what I said at the beginnning. If there is only one book you are going to buy about programming embedded systems, this should be the one.
Rating:
Summary: Way to basic!
Review: It's just what it say "a primer". This book seems like it would be great for someone who has never programmed for embedded systems. However, if you have even a few months experiance under your belt, this book is a big waste of time. I purchased this book to use a quick refresh after being away from embedded programming for a few years. Sent it back after reading about 25% and skimming the rest.
Rating:
Summary: A very good primer.
Review: My friend recommended this book to me when I wanted to understand the fundamentals of Embedded systems. The chapters on Hardware overview took me back memory lanes when I was at college. Good refresher. What I most liked about the book is the section that deals with choices of embedded architecture and how and when to chose specific architecture. Book is accompanied by a CD with a kernel of an embedded OS along with the source code. Haven't had the time to go over the CD. Nevertheless, I got what I wanted regarding embedded systems. I can understand embedded system much better now. Currently, this is the only good book on fundamentals of embedded systems in the market.
Rating:
Summary: A necessary book for entry level engineers with C skills
Review: The book provides very useful information for anyone that wishes to learn embedded software from the ground up. Great for entry level engineers, or professionals wishing to make a lateral move into embedded systems. The book has two clearly written chapters dedicated to hardware fundamentals; describing I/O .vs. memory mapping, how interrupts function, memory types including PROM's, and microprocessor basics. A chapter is dedicated to one of the single most inportant issues in embedded systems SHARED DATA and how to prevent corrupting it. Chapter 5 discusses four basic software methods to servicing interrupts. Chapters 6,7, and 8 clearly introduce the concept of an RTOS (Real Time Operating System). Chapter 9 is a must read for those new to embedded systems. It discusses development tools and the steps required to get your final code onto the target system. It explains what a cross-compiler is and why they are used in embedded systems. This is a very good book for engineers with C skills!
Rating:
Summary: Too basic
Review: This book gives a solid overview of embedded systems and how they work in conjunction with hardware and software, but it does not give enough in depth analysis of embedded systems. For example, the book tries to show how to write certain software for embedded applications, but gives too generic examples using a created language called "C!" It would be more effective of a book if it had actual examples of embedded software such as device drivers, etc. Otherwise, it does a solid job of explaining the basics of different interrupts, semaphores, etc.
Rating: 
Summary: Good introduction in embedded systems
Review: This book is a GREAT introductory book into the embedded world. Even if you are an experienced embedded engineer, you'll find this book useful to remember basic concepts you might have forgotten with time, but maybe you'll find it TOO BASIC for you.
| 
