Embedded Systems Architecture 2nd edition

【实例简介】
Embedded Systems Architecture:A Comprehensive Guide for Engineers and Programmers second edition Tammy Noergaard
Embedded Systems Architecture A Comprehensive Guide for Engineers and Programmers Tammy nergaard AMSTERDAM· BOSTON· HEIDELBERG· LONDON· NEWYORK· OXFORD· PARIS SAN DIEGO· SAN FRANCISCO· SINGAPORE· SYDNEY· TOKYO ELSEVIER Newnes is an imprint of elsevie Newnes Newnes is an imprint of Elsevier The boulevard, Langford Lane, Kidlington, Oxford, OX5 IGB 225 Wyman Street, Waltham, MA 02451, USA First edition 2005 Second edition 2013 Copyright o 2013, 2005 Elsevier Inc. All rights reserved No part of this publication may be reproduced or transmitted in any form or by any means electronic or mechanical, including photocopying, recording, or any information storage and retrieval system, without permission in writing from the publisher. Details on how to seek permission, further information about the Publishers permissions policies and our arrangement with organizations such as the CopyrightClearanceCenterandtheCopyrightLicensingAgency,canbefoundatourwebsitewww.elsevier.com/ permissions This book and the individual contributions contained in it are protected under copyright by the Publisher(other than as may be noted herein) Notices Knowledge and best practice in this field are constantly changing. As new research and experience broaden our understanding, changes in research methods, professional practices, or medical treatment may become necessar Practitioners and researchers must always rely on their own experience and knowledge in evaluating and using any information, methods, compounds, or experiments described herein In using such information or methods they should be mindful of their own safety and the safety of others, including parties for whom they have a professional responsibility To the fullest extent of the law, neither the Publisher nor the authors, contributors, or editors, assume any liability for any injury and/or damage to persons or property as a matter of products liability, negligence or otherwise, or from any use or operation of any methods, products, instructions, or ideas contained in the material herein British library cataloguing-in-Publication Data A catalogue record for this book is available from the British Library Library of Congress Cataloguing-in-Publication Data A catalog record for this book is available from the Library of Congress ISBN:978-0-12-382196-6 For information on all Newnes publications visit our website at store. elsevier. com Typeset by MPs Limited, Chennai, India www.adl-mps.com Printed and bound in the united states 1314151610987654321 Working together to grow libraries in developing countries www.elsevier.comiwww.bookaid.orgiwww.sabre.org elsevier OOKAd Sabre Foundation Foreword to the first Edition When Tammy Noergaard first told me she wanted to write a soup-to-nuts book about building embedded systems I tried to dissuade her. This field is so vast, requiring insight into electronics, logic circuits, computer design, software engineering, C, assembly, and far more But as we talked she showed me how the industrys literature lacks a definitive work on the subject. I warned her of the immensity of the project A year and many discussions later Fedex arrived with the review copy of this book. At approximately 700 pages it's appropriately twice the size of almost any other opus on the subject. The book you're holding truly is"A Comprehensive Guide for Engineers and Programmers. "Sure, the minutiae of programming a PIC's timer might have been left out, but the scope is vast and important expensive end-phase of maintenance. She treats hardware and software as an integrated o Tammy starts with the first principles of electronics and advances through software to th whole, which sort of defines the nature of embedded systems. Ironically, though, developers are increasingly specialized. More than a few software folks havent a clue about transistors while too many EEs cant accurately define middleware. I fear readers may skip those chapters that dont immediately pertain to the project at hand Resist any such temptation, gentle reader! Become a true master, an embedded sage, by broadening your horizons to cover all aspects of this fascinating field. We engineers are professionals; you and I know this in our hearts. Yet true professionals are those who learn new things, who apply newly evolving technologies to solve problems. Consider doctors the discovery and production of penicillin in the 1940s changed the profession of medicine forever. Any doc who ignored this new technology, who continued to practice using only the skills learned in college, was suddenly rendered a butcher Software and hardware developers are faced with the same situation. c wasn't taught when i went to school. The fPga hadn't been invented GOTOS were still just fine, thank you. We learned to program microprocessors in machine code using primitive toolchains. Today--well, we know how much has changed The rate of change is increasing; change's first derivative is an ever-escalating positive number. Professional developers will read this book from cover to cover, and will constantly seek out other sources of information. If you re not at least surfing through a half dozen xii foreword to the first edition technical magazines a month and reading a handful of books like this per year, then it wont take a cretaceous asteroid to make you a dinosaur Some of this book might surprise you. Ten pages about reading datasheets? Fact is, datasheets are dense formal compilations of contractual material. The vendor promises the part will do" as long as we use it in an agreed-on manner. Violate any of perhaps thousands of specifications and the part will either not work or will be unreliable. With some parts dissipating 100 watts or more, even such arcana as thermal characteristics are as important as the device's instruction set Tammy's generous use of examples elucidates the more obscure points. Engineering- whether hardware or software--is the art of building things and solving problems The academics can work with dry theory we practicing developers often learn best by seein how something works. So the chapter on device drivers does explain the intricacies of building these often-complex bits of code, but couples the explanation to a wealth of real-world examples Finally, Tammys words about the Architecture Business Cycle of embedded systems resonate strongly with me. We dont build these things just to have a good time(though we sure hope to have one along the way), but to solve important business problems. Every decision we make has business implications. Use too little horsepower and development costs skyrocket sometimes to the point of making the project unviable. a poor analysis of the problem that leads you to toss in an excess of Flash might drive costs unacceptably high. Select a component(hardware or software) from a failing company and your outfit may share in the vendor s demise Enjoy this book, and futureproof your career at the same time Jack Ganssle Acknowledgments My greatest debt in creating this second edition goes to my readers and reviewers, who I hope will be pleasantly surprised to see how many of their suggestions have been incorporated into the book. They include Dr Al M. Zied, both of my brothers(especially my younger brother who also provided me the inspiration to write this book in the first place), Jack Ganssle, and Steve bailey Thank you to my publisher Elsevier, specifically to the Elsevier team for their hard work and dedication in making this book a reality I would also like to acknowledge my terma team members as some of the most talented I have been lucky enough to work with, as well as my mentor when I was with Sony Electronics, Kazuhisa Maruoka. Maruoka-san patiently trained me to design televisions and gave me such a strong foundation upon which to grow, as well as my manager at Sony Electronics, Satoshi Ishiguro, who took a chance and hired me. My journey in the embedded systems field that has led me to writing this book began with the great people I worked with at Sony in Japan and in San Diego Thank you to my family for their support For my beautiful girls Mia and Sarah, thank you for always gifting me with endless smiles, hugs, and kisses. Thank you, Mom and my brothers and sister in Southern California for their support and for encouraging me every step of the way Finally, a very special thanks to Kenneth Knudsen and his welcoming, loving family. Also the us Embassy for all their support, other fellow Americans here in Denmark, and to the lovely Danes I have been lucky enough to have in my life---shining the light on the hardest days while i was working to finish this edition in Denmark. To all the other friends who have touched Mia's, Sarahs, and my life here in Denmark. I will always be grateful about the author Tammy Noergaard is uniquely qualified to write about all aspects of embedded systems. Since beginning her career, she has gained wide experience in product development, system design and integration, operations, sales, marketing, and training. She has design experience using many hardware platforms, operating systems, middleware, and languages. Tammy worked for Sony as a lead software engineer developing and testing embedded software for analog tvs and also managed and trained new embedded engineers and programmers The televisions she helped to develop in Japan and California were critically acclaimed and rated #l in Consumer Reports magazines. She has consulted internationally for many years, for companies including Esmertec and windriver, and has been a guest lecturer in engineering classes at the University of California at Berkeley, Stanford University, as well as giving technical talks at the invitation of Aarhus University for professionals and students in Denmark. Tammy has also given professional talks at the Embedded Internet Conference and the Java User's Group in San Jose over the years. Most recently, her experience has been utilized in Denmark to help ensure the success of fellow team members and organizations in building best-in-class embedded systems XV SECTION Introduction to Embedded Systems Introduction to Embedded Systems The field of embedded systems is wide and varied and it is difficult to pin down exact definitions or descriptions. However, Chapter 1 introduces a useful model that can be applied to any embedded system This model is introduced as a means for the reader to understand the major components that make up different types of electronic devices, regardless of their complexity or differences. Chapter 2 introduces and defines the common standards adhered to when building an embedded system Because this book is an overview of embedded systems architecture, covering every possible standards-based component that could be implemented is beyond its scope. Therefore, significant examples of current standards-based components have been selected, such as networking and Java, to demonstrate how standards define major components in an embedded system. The intention is for the reader to be able to use the methodology behind the model, standards, and real-world examples to understand any embedded system, and to be able to apply any other standard to an embedded systems design CHAPTER 1 A Systems Approach to Embedded Systems Design In This Chapter Defining embedded system Introducing the design process Defining an embedded systems architecture Discussing the impact of architecture Summarizing the remaining sections of the book 1.1 What Is an Embedded System? An embedded system is an applied computer system as distinguished from other types of computer systems such as personal computers(PCs) or supercomputers. However, you will find that the definition of embedded system"is fluid and difficult to pin down, as it constantly evolves with advances in technology and dramatic decreases in the cost of implementing various hardware and software components. Internationally, the field has outgrown many of its traditional descriptions. Because the reader will likely encounter some of these descriptions and definitions, it is important to understand the reasoning behind them and why they may or may not be accurate today, and to be able to discuss them knowledgeably. The following are a few of the more common descriptions of an embedded system Embedded systems are more limited in hardware and/or software functionality than a PC. This holds true for a significant subset of the embedded systems family of computer systems. In terms of hardware limitations, this can mean limitations in processing performance, power consumption, memory, hardware functionality, etc In software, this typically means limitations relative to a PC--fewer applications, scaled-down applications, no operating system(Os)or a limited OS, or less abstraction-level code. However, this definition is only partially true today as boards and software typically found in PCs of the past and present have been repackaged into more complex embedded system designs An embedded system is designed to perform a dedicated function. Most embedded devices are primarily designed for one specific function. However, we now see devices such as personal data assistant(PDa)/cell phone hybrids, which are embedded systems designed to be able to do a variety of primary functions. Also, the latest digital TVs Embedded Systems Architecture Copyright o 2013, 2005 Elsevier Inc. All rights reserve 【实例截图】
【核心代码】