Conventions Used in This Book:TypographyThe following typographical conventions are used in this book:ItalicIndicates new terms, URLs, filenames, and file extensions.Constant widthUsed for program listings, as well as within paragraphs to refer to program elements such as variable or function names, data types, and keywords.This book uses the following formatting conventions:TypographyThe following typographical conventions are used in this book:ItalicIndicates new terms, URLs, filenames, and file extensions.Constant widthUsed for program listings, as well as within paragraphs to refer to program elements such as variable or function names, data types, and keywords.TerminologyA microcontroller is a processor with onboard goodies like RAM, code space (usually flash), and various peripheral interfaces (e.g., I/O lines). Your code runs on a processor or central processing unit (CPU). A microprocessor is a small processor, but the definition of “small” changes.A microcontroller is a processor that integrates built-in “goodies” like random access memory (RAM), code storage space (usually flash), and various peripheral interfaces (e.g., input/output lines). Your code runs on a processor or central processing unit (CPU). A microprocessor is a small processor, but the definition of “small” is constantly changing.A DSP (digital signal processor) is a specialized form of microcontroller that focuses on signal processing, usually sampling analog signals and doing something interesting with the result. Usually, a DSP is also a microcontroller, but it has special tweaks to make it perform math operations faster (in particular, multiply and add).A digital signal processor (DSP) is a specialized microcontroller focused on signal processing, typically sampling analog signals and performing meaningful operations on the results. Generally, a DSP is also a microcontroller, but it has some special optimizations that allow it to execute mathematical operations (especially multiplication and addition) more quickly.
- special tweaks: This translates to “special optimizations,” vividly describing the targeted improvements made by the DSP to enhance computation speed, avoiding the cumbersome accumulation of technical jargon.
As I wrote this book, I wanted to use the correct terminology so you’d get used to it. However, with so many names for the piece of the system that is running your code, I didn’t want to add confusion by changing the name. So, I stick with the term processor to represent whatever you are using to implement your system. Most of the material is applicable to whatever you actually have.While writing this book, I aimed to use accurate terminology so you would become accustomed to these expressions. However, there are so many names for the component in the system that runs your code, I didn’t want to create confusion by frequently changing terms. Therefore, I consistently use the term “processor” to refer to any device you use to implement your system. Most of the content is applicable regardless of the specific device you are using.Using Code ExamplesThis book is here to help you get your job done. In general, you may use the code in this book in your programs and documentation. You do not need to contact us for permission unless you’re reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from O’Reilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your product’s documentation does require permission.This book aims to assist you in completing your work. Generally, you can use the code in this book in your own programs and documentation. You do not need to contact us for permission unless you are copying a significant portion of the code. For instance, writing a program that utilizes several code snippets from this book does not require permission; however, selling or distributing a CD-ROM containing examples from O’Reilly books does require permission. Citing this book and quoting example code to answer a question does not require permission, but incorporating a substantial amount of example code from this book into your product’s documentation does require permission.We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example: “Making Embedded Systems by Elecia White (O’Reilly). Copyright 2012 Elecia White”.We welcome but do not require attribution. An attribution typically includes the title, author, publisher, and ISBN. For example: “Making Embedded Systems by Elecia White (O’Reilly). Copyright ©2012 Elecia White”.If you feel your use of code examples falls outside fair use or the permission given above, feel free to contact us at [email protected].If you believe your use of code examples exceeds the bounds of fair use or the permissions granted above, please feel free to contact us at [email protected].Safari Books OnlineSafari Books Online is an on-demand digital library that lets you easily search over 7,500 technology and creative reference books and videos to find the answers you need quickly.Safari Books Online is an on-demand digital library that allows you to easily search over 7,500 technology and creative reference books and videos to quickly find the answers you need.With a subscription, you can read any page and watch any video from your library online. Read books on your cell phone and mobile devices. Access new titles before they are available for print, and get exclusive access to manuscripts in development and post feedback for the authors. Copy and paste code samples, organize your favorites, download chapters, bookmark key sections, create notes, print out pages, and benefit from tons of other time-saving features.With a subscription, you can read any page and watch any video from your library online. You can read books on your cell phone and mobile devices. You can access new titles before they are available in print, and gain exclusive access to manuscripts in development, providing feedback to the authors. Additionally, you can copy and paste code samples, organize your favorites, download chapters, bookmark key sections, create notes, print pages, and enjoy many other time-saving features.O’Reilly Media has uploaded this book to the Safari Books Online service. To have full digital access to this book and others on similar topics from O’Reilly and other publishers, sign up for free at http://my.safaribooksonline.com.O’Reilly Media has uploaded this book to the Safari Books Online service. To gain full digital access to this book and others on similar topics from O’Reilly and other publishers, please sign up for free at http://my.safaribooksonline.com.How to Contact UsPlease address comments and questions concerning this book to the publisher:O’Reilly Media, Inc.1005 Gravenstein Highway NorthSebastopol, CA 95472800-998-9938 (in the United States or Canada)707-829-0515 (international or local)707-829-0104 (fax)For comments and questions regarding this book, please contact the publisher:O’Reilly Media, Inc.1005 Gravenstein Highway NorthSebastopol, CA 95472800-998-9938 (in the United States or Canada)707-829-0515 (international or local)707-829-0104 (fax)We have a web page for this book, where we list errata, examples, and any additional information. You can access this page at:http://shop.oreilly.com/product/0636920017776.doWe have a webpage for this book, where we list errata, examples, and any additional information. You can access this page at:http://shop.oreilly.com/product/0636920017776.doTo comment or ask technical questions about this book, send email to:[email protected]For more information about our books, conferences, Resource Centers, and the O’Reilly Network, see our website at:http://www.oreilly.comReferences:
[1]. “Making Embedded Systems” by Elecia White. Southeast University Press.
Previous Issues:Reading English Literature on Embedded System Development: Making Embedded Systems: 1. Preface_1Reading English Literature on Embedded System Development: Making Embedded Systems: 1. Preface_2Reading English Literature on Embedded System Development: Making Embedded Systems: 1. Preface_3Click the card below to follow this public account:: If you like it, remember to “share” and “recommend” or “like” or “leave a message“.