探索嵌入式硬件深度：新知识全书系列

5星 · 超过95%的资源需积分: 15 189 浏览量更新于2024-07-30 1 收藏 10.3MB PDF 举报

《嵌入式硬件：新尼斯全知道系列》是一套深入探讨嵌入式系统硬件开发的专业书籍，由业界知名作者如Lucio Di Jasio、Tim Wilmshurst、Dogan Ibrahim、John Morton、Martin Bates等人合作编写。该系列书籍旨在提供超越传统教材的深度和广度，特别关注那些在一般教科书中难以触及的复杂主题，如Cache（高速缓存）和DMA（直接内存访问）技术。 "Newnes Know It All" 系列包括几本专门针对不同领域的嵌入式硬件著作，例如： 1. **PIC微控制器：全知道** - 由多位专家共同编著，深入讲解基于PIC微控制器的设计与开发，帮助读者掌握这一关键领域的核心技术。 2. **嵌入式软件：全知道** - Jean Labrosse、Jack Ganssle等作者分享嵌入式软件开发的最佳实践，涵盖了编程、调试、性能优化等方面的知识。 3. **嵌入式硬件：全知道** - 由Jack Ganssle、Tammy Noergaard等作者合作，聚焦于嵌入式硬件设计的底层原理，讨论了系统架构、接口设计、电源管理等核心硬件技术。 4. **无线网络：全知道** - Praphul Chandra、Daniel M. Dobkin等作者联手，为读者揭示无线网络技术在嵌入式系统中的应用，包括Wi-Fi、蓝牙等无线通信协议和实现策略。 5. **射频与无线技术：全知道** - Bruce Fette、Roberto Aiello等作者合作，介绍了射频技术和无线通信的最新进展，适合研究和工程技术人员深入了解相关技术。通过这些书籍，读者不仅能学习到扎实的理论知识，还能获得实践经验，了解在实际项目中如何有效地运用Cache和DMA等高级技术来提升系统性能。对于嵌入式系统工程师和爱好者来说，这套系列书无疑是一份宝贵的参考资料。如果你对嵌入式硬件开发有深入研究的需求，或者希望拓宽专业视野，这些书籍将是不容错过的学习资源。更多关于新尼斯出版社的信息，可以访问 www.newnespress.com 进行查询。

www.newnespress.com

senior design engineer in cable modem and automation groups. David holds both a B.S. and

M. Eng. in Electrical Engineering from Cornell University.

Walt Kester (Appendix C) is the editor of Data Conversion Handbook. He is a corporate

staff applications engineer at Analog Devices. For more than 35 years at Analog Devices,

he has designed, developed, and given applications support for high-speed ADCs, DACs,

SHAs, op amps, and analog multiplexers. Besides writing many papers and articles, he

prepared and edited eleven major applications books which form the basis for the Analog

Devices world-wide technical seminar series including the topics of op amps, data conversion,

power management, sensor signal conditioning, mixed-signal, and practical analog design

techniques. Walt has a BSEE from NC State University and MSEE from Duke University.

Tammy Noergaard (Chapters 1, 2, 3, 4, Appendices B and C) is the author of Embedded

Systems Architecture. Since beginning her embedded systems career in 1995, she has had

wide experience in product development, system design and integration, operations, sales,

marketing, and training. Noergaard worked for Sony as a lead software engineer developing

and testing embedded software for analog TVs. At Wind River she was the liaison engineer

between developmental engineers and customers to provide design expertise, systems

conﬁ guration, systems integration, and training for Wind River embedded software (OS,

Java, device drivers, etc.) and all associated hardware for a variety of embedded systems in

the Consumer Electronic market. Most recently she was a Field Engineering Specialist and

Consultant with Esmertec North America, providing project management, system design,

system integration, system conﬁ guration, support and expertise for various embedded Java

systems using Jbed in everything from control systems to medical devices to digital TVs.

Noergaard has lectured to engineering classes at the University of California at Berkeley and

Stanford, the Embedded Internet Conference, and the Java User’s Group in San Jose, among

others.

Bob Perrin (Chapter 9) is the author of Embedded Systems Design Using the Rabbit 3000

Microprocessor. He got his start in electronics at the age of nine when his mother gave him

a “150-in-one Projects” kit from Radio Shack for Christmas. He grew up programming a

Commodore PET. In 1990, Bob graduated with a BSEE from Washington State University.

Since then Bob has been working as an engineer designing digital and analog electronics.

He has published about twenty technical articles, most with Circuit Cellar.

About the Authors xv

Prelims-H8584.indd xvPrelims-H8584.indd xv 8/17/07 7:21:11 PM8/17/07 7:21:11 PM

www.newnespress.com

CHAPTR

Embedded Hardware Basics

Jack Ganssle

Tammy Noergaard

CHAPTER 1

1.1 Lesson One on Hardware: Reading Schematics

This section is equally important for embedded hardware and software engineers. Before

diving into the details, note that it is important for all embedded designers to be able to under-

stand the diagrams and symbols that hardware engineers create and use to describe their hard-

ware designs to the outside world. These diagrams and symbols are the keys to quickly and

efﬁ ciently understanding even the most complex hardware design, regardless of how much or

little practical experience one has in designing hardware. They also contain the information an

embedded programmer needs to design any software that requires compatibility with the hard-

ware, and they provide insight to a programmer as to how to successfully communicate the

hardware requirements of the software to a hardware engineer.

There are several different types of engineering hardware drawings, including:

•

Block diagrams, which typically depict the major components of a board (processors,

buses, I/O, memory) or a single component (a processor, for example) at a systems

architecture or higher level. In short, a block diagram is a basic overview of the hard-

ware, with implementation details abstracted out. While a block diagram can reﬂ ect

the actual physical layout of a board containing these major components, it mainly

depicts how different components or units within a component function together at a

systems architecture level. Block diagrams are used extensively throughout this book

(in fact, Figures 1.5a–e later in this chapter are examples of block diagrams) because

they are the simplest method by which to depict and describe the components within a

system. The symbols used within a block diagram are simple, such as squares or rec-

tangles for chips and straight lines for buses. Block diagrams are typically not detailed

enough for a software designer to be able to write all the low-level software accurately

enough to control the hardware (without a lot of headaches, trial and error, and even

some burned-out hardware!). However, they are very useful in communicating a basic

overview of the hardware, as well as providing a basis for creating more detailed

hardware diagrams.

•

Schematics. Schematics are electronic circuit diagrams that provide a more detailed

view of all the devices within a circuit or within a single component—everything from

Ch01-H8584.indd 1Ch01-H8584.indd 1 8/17/07 12:08:48 PM8/17/07 12:08:48 PM

2 Chapter 1

www.newnespress.com

processors down to resistors. A schematic diagram is not meant to depict the physical

layout of the board or component, but provides information on the ﬂ ow of data in the

system, deﬁ ning what signals are assigned where—which signals travel on the various

lines of a bus, appear on the pins of a processor, and so on. In schematic diagrams,

schematic symbols are used to depict all the components within the system. They

typically do not look anything like the physical components they represent but are a

type of “shorthand” representation based on some type of schematic symbol standard.

A schematic diagram is the most useful diagram to both hardware and software

designers trying to determine how a system actually operates, to debug hardware, or

to write and debug the software managing the hardware. See Appendix A for a list of

commonly used schematic symbols.

•

Wiring diagrams. These diagrams represent the bus connections between the major

and minor components on a board or within a chip. In wiring diagrams, vertical and

horizontal lines are used to represent the lines of a bus, and either schematic symbols

or more simpliﬁ ed symbols (that physically resemble the other components on the

board or elements within a component) are used. These diagrams may represent an

approximate depiction of the physical layout of a component or board.

•

Logic diagrams/prints. Logic diagrams/prints are used to show a wide variety of circuit

information using logical symbols (AND, OR, NOT, XOR, and so on) and logical inputs

and outputs (the 1’s and 0’s). These diagrams do not replace schematics, but they can be

useful in simplifying certain types of circuits in order to understand how they function.

•

Timing diagrams. Timing diagrams display timing graphs of various input and output

signals of a circuit, as well as the relationships between the various signals. They are

the most common diagrams (after block diagrams) in hardware user manuals and data

sheets.

Regardless of the type, to understand how to read and interpret these diagrams, it is important

to ﬁ rst learn the standard symbols, conventions, and rules used. Examples of the symbols used

in timing diagrams are shown in Table 1.1, along with the conventions for input/output signals

associated with each of the symbols.

An example of a timing diagram is shown in Figure 1.1. In this ﬁ gure, each row represents a

different signal. In the case of the signal rising and falling symbols within the diagram, the

rise time or fall time is indicated by the time it takes for the signal to move from LOW to

HIGH or vice versa (the entire length of the diagonal line of the symbol). In comparing two

signals, a delay is measured at the center of the rising or falling symbols of each signal being

compared. In Figure 1.1, there is a fall time delay between signals B and C and signals A and

C in the ﬁ rst falling symbol. In comparing the ﬁ rst falling symbol of signals A and B in the

ﬁ gure, no delay is indicated by the timing diagram.

Ch01-H8584.indd 2Ch01-H8584.indd 2 8/17/07 12:08:49 PM8/17/07 12:08:49 PM

剩余536页未读，继续阅读

justin_sun730

粉丝: 0
资源: 1

探索嵌入式硬件深度：新知识全书系列

Embedded Software: Know It All

嵌入式系统硬件设计

Embedded Hardware-Newnes Know it all series

embedded software: know it all

iar embedded workbench ide - 8051 10.20.1

vesa proposed embedded displayport v1.4b d3.pdf

java中 将byte[]类型数据转为pdf，并在指定坐标位置添加文字，要求使用com.itextpdf.text.pdf

Spring boot Unable to start embedded Tomcat报错 java.lang.NoSuchMethodError: javax.servlet.ServletCont...

最新资源

java中将byte[]类型数据转为pdf，并在指定坐标位置添加文字，要求使用com.itextpdf.text.pdf