Debugging Embedded Microprocessor Systems |  | Author: Stuart Ball Publisher: Newnes Category: Book
List Price: $63.95 Buy Used: $9.58 as of 9/5/2010 00:00 CDT details You Save: $54.37 (85%)
New (14) Used (15) from $9.58
Seller: phoenixfriends Rating: 3 reviews
Media: Paperback Pages: 256 Number Of Items: 1 Shipping Weight (lbs): 0.8 Dimensions (in): 9.2 x 6 x 0.5
ISBN: 0750699906 Dewey Decimal Number: 004.16 EAN: 9780750699907
Availability: Usually ships in 1-2 business days
| |
| Also Available In:
|
| Similar Items:
| |
| Editorial Reviews:
Product Description Debugging Embedded Microprocessor Systems provides techniques for engineers, technicians, and students who need to correct design faults in embedded systems. Using real-world scenarios, designers can learn practical, time-saving ways to avoid and repair potentially costly problems. Prevention is stressed.
In this book, the author addresses hardware and software issues, including up-front design techniques to prevent bugs and contain design creep. Practical advice includes descriptions of common tools which can be used to help identify and repair bugs, as well as test routines. RTOS and embedded PC environments are also covered.
Each chapter of Debugging Embedded Microprocessor Systems opens with an example design problem which illustrates real-world issues such as design changes, time pressures, equipment or component availability, etc. Case studies of past debugging projects are presented in the final chapter.
Addresses real-world issues like design changes, time pressures, equipment or component availability Practical, time-saving methods for preventing and correcting design problems Covers debugging tools and programmer test routines
|
| Customer Reviews: A black art May 8, 2002 Neil (Cambridge, UK) 3 out of 3 found this review helpful
Having being inolved in debugging embedded systems from a hardware and software perspective for a number of years, I found it amusing that someone else out there shared my sentiments. Mr. Ball has a good logical approach to fault finding and these techniques can be learnt saving years of 'doing it the hard way'. As for Mr. Ball's attitude towards marketing\management, well I found it amusing and unless you are very lucky, always present to some extent in the workplace. I would strongly recommend buying this book as hardware and software are so closely related in an embedded system that coverage of both disciplines in extremely valuable. Learning about the stunts that Management can pull is generally not covered outside of a Dilbert strip.
Learning to debug in the Real World December 14, 2008 Lisa Simone (Bridgewater, NJ USA) One thing I really like about this book is that the author includes many of his experiences debugging problems in the real world. Only a few textbooks contain these interesting and informative vignettes, but I think they are incredibly helpful in driving a point home. (They also make a textbook a lot more interesting!)
He emphasizes a few gems that we're are guilty of at one time or another...."don't ignore symptoms!" Sometimes those symptoms seem to have NOTHING to do with the problem at hand! He includes several sources of error with examples that are often overlooked - things as obvious as boundary conditions and timing errors. While it is easy for an instructor or colleague to say, "did you check the boundary conditions?," really understanding all the permutations of functional testing is often overlooked.
Some of the specific information is a little dated, but that doesn't invalidate the usefulness of many debugging techniques that transcend advances in the technology itself.
Lisa Simone, If I Only Changed the Software, Why is the Phone on Fire?: Embedded Debugging Methods Revealed: Technical Mysteries for Engineers
Practical information but opinionated. February 19, 1999 14 out of 15 found this review helpful
This book describes some practical debugging techniques. The reading is not very heavy. My biggest complaint is that the author appears to carry a big chip on his shoulder regarding the relationship between engineering and marketing, sales, and management. Unfortunately, this detracts from what would otherwise be a good book. Some of the comments made against management and marketing indicate quite a bit of resentment that has built up over the years. This book should not have been the vehicle to express it.
|
|
|
|