|
马上注册,结交更多好友,享用更多功能,让你轻松玩转社区。
您需要 登录 才可以下载或查看,没有账号?注册
x
同仁们,先看一下介绍,先。适不适合你的需要。
下载有风险,花钱要谨慎!!!!
Introduction
This is a book about debugging. Solving problems. Making the thing
work after you've built it and everything's gone wrong. Debugging
seems to be fading as a skill among hardware and software designers
alike, perhaps for the same reasons that fewer people today like to get
under the hood of their car or build radios from scratch. Whatever the
reason, in this book we look at the reasons why things go wrong in
embedded systems, how to fix them, and how to avoid them altogether.
We'll look at a few hypothetical situations, and at some that
really happened.
For this book, we'll define an embedded system as one using a
microcontroller or microprocessor, performing real-time, real-world
functions. Examples of embedded systems are the microprocessor in a
microwave oven or under the hood of a car, or the electronics that control
a mail-sorting machine for the post office. Although a personal
computer does not fall under this definition, we touch briefly on
embedded applications using PCs as well.
The book emphasizes debugging techniques and tools, but more
importantly, it considers ways to anticipate and prevent bugs. Bugs are
easier to prevent than they are to find.
The audience for this book is embedded software and hardware
engineers, engineers who are moving into the embedded field, and
other engineers who want to understand embedded debugging. Engineers
who have been designing real-time systems since Intel introduced
the 8080 will get less out of the book than someone new to the
field, but there is something in here for everyone.
This is not a book about digital design or software design,
although we look at those issues as a means of avoiding debugging
problems. I've assumed that you know the basics of microprocessor
systems, such as the difference between address and data buses, what
an EPROM and static RAM are, and enough about digital logic to
know what an address decoder is. |
|