DOCSLIB.ORG

First Steps with Embedded Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
First Steps with Embedded Systems First Steps with Embedded Systems Byte Craft Limited 02A4 A ox40; 02A6 B gs&0x20) 02A9 C table(); [email protected] Code Development Systems CDS m The Byte Craft Limited Code Development Do Byte Craft Limited compilers Systems are high-performance embedded support ANSI C? o development packages designed for serious All Byte Craft compilers are ANSI compatible within the developers. They generate small, fast, and limitations of the target hardware. efficient code. They enable the professional How efficient is the optimizer c developer to produce stand-alone single-chip compared to hand-written . microcontroller applications quickly. Developers assembler code? can easily port C language applications written The compiler generates object code as tight and t for other embedded platforms to the CDS. efficient as most hand-written assembler code. f Can I combine C code and www.bytecraft.com assembler in my programs? You can embed assembler code within your C program, a Features using #asm and #endasm preprocessor directives. The ! The Code Development Systems support embedded code can call C functions and directly r entire families of microcontrollers. access C variables. To pass arguments conveniently, ! The optimizing C language cross-compilers are embed your assembly code in the body of a C function. c ANSI-compatible within hardware limitations. What kinds of emulator hardware ! Tight, fast and efficient code optimization do the compilers support? For more information on supported emulator products, generates clean, customized applications. e ! A built-in Macro Assembler allows inline contact Byte Craft Limited support staff. assembly language in C source. How do the compilers handle local t ! CDS generate symbol and source reference variable declarations? Our compilers store locally-declared variables in information for C source-level debugging with y reusable local memory spaces. The scope of local popular emulators. ! variables is protected. C language support for interrupt service What are Byte Craft Limited's b routines and direct access to ports. ! terms? Device files for individual parts precisely For Canada and the U.S.: For company purchases (on control code generation and resource usage. ! approved credit), NET 30 days after shipping. Byte @ Complete user documentation comes with Craft ships next day FedEx free of charge. All other every Code Development System. ! orders must be prepaid, with American Express, VISA, Absolute Code Mode lets you compile directly check with order, or direct wire transfer. o to final code without a separate linking phase. For overseas: All orders, prepaid with American Alternatively, you can use the BClink Express, VISA, check with order, or direct wire transfer. f Optimizing Linker. Either method performs a Shipping is extra. Please call for more information. Please obtain appropriate import documentation. final optimization pass on an entire program. n ! Demonstration versions are available from: If for any reason you are unsatisfied with your i http://www.bytecraft.com/ purchase, you can return it within 30 days for a full Versatility refund. Code Development Systems install under Windows 95, 98, ME, NT, 2000, or under MS/PC 421 King Street North DOS. Waterloo, Ontario CDS provide symbol table information and a Canada listing file: a merged listing of C source and N2J 4E4 generated assembly language to permit detailed Tel: 519-888-6911 Fax: 519-746-6751 analysis. First Steps with Embedded Systems by Byte Craft Limited BYTE CRAFT LIMITED 421 King Street North Waterloo, Ontario Canada N2J 4E4 Telephone: (519) 888-6911 FAX: (519) 746-6751 Email: [email protected] http://www.bytecraft.com Copyright ! 1997, 2002 Byte Craft Limited. Licensed Material. All rights reserved. First Steps with Embedded Systems is protected by copyrights. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise without the prior written permission of Byte Craft Limited. All example and program code is protected by copyright. Printed in Canada 14 November, 2002 Table of Contents 1. Introduction 1 1.1 Typographical Conventions....................................................................... 1 1.2 Explaining the Microcontroller .................................................................2 1.3 Book Contents ...........................................................................................3 2. Microcontroller Overview 5 2.1 What is a Microcontroller?.........................................................................5 2.2 The Microcontroller in a System...............................................................7 2.3 Architecture ...............................................................................................7 2.3.1 Von Neumann ......................................................................................................................8 2.3.2 Von Neumann Memory Map.............................................................................................8 2.3.3 Harvard ..................................................................................................................................9 2.3.4 Harvard Memory Map.......................................................................................................10 2.3.5 The Central Processing Unit ............................................................................................11 2.3.6 Central Processing Unit.....................................................................................................13 2.3.7 ROM.....................................................................................................................................14 2.3.8 RAM.....................................................................................................................................15 2.3.9 I/O Ports.............................................................................................................................16 2.3.10 Timer..................................................................................................................................17 2.3.11 Interrupt Circuitry............................................................................................................18 2.3.12 Buses ..................................................................................................................................19 2.4 Sample Microcontroller Configurations.................................................. 19 2.4.1 Motorola MC68HC705C8 ................................................................................................19 2.4.2 National Semiconductor COP8SAA7 ............................................................................20 2.4.3 Microchip PIC16C54.........................................................................................................20 2.4.4 Microchip PIC16C74.........................................................................................................21 i Table of Contents 3. The Embedded Environment 23 3.1 The Embedded Difference ......................................................................23 3.2 Fabrication Techniques ..........................................................................24 3.3 Memory Addressing and Types ..............................................................24 3.3.1 RAM..................................................................................................................................... 24 3.3.2 ROM.................................................................................................................................... 25 3.3.3 PROM ................................................................................................................................. 25 3.3.4 EPROM .............................................................................................................................. 25 3.3.5 EEPROM ........................................................................................................................... 26 3.3.6 Flash Memory..................................................................................................................... 27 3.3.7 Registers .............................................................................................................................. 27 3.3.8 Scratch Pad ......................................................................................................................... 28 3.4 Interrupts .................................................................................................29 3.4.1 Interrupt Handling ............................................................................................................ 30 3.4.2 Synchronous and Asynchronous Interrupt Acknowledgement................................. 30 3.4.3 Servicing Interrupts........................................................................................................... 31 3.4.4 Interrupt Detection ........................................................................................................... 32 3.4.5 Executing Interrupt Handlers.......................................................................................... 33 3.4.6 Multiple Interrupts ............................................................................................................ 34 3.5 Specific Interrupts ...................................................................................34
Load more

Recommended publications
  • Nintendo Wii Software
    Nintendo wii software A previous update, ( U) introduced the ability to transfer your data from one Wii U console to another. You can transfer save data for Wii U software, Mii. The Wii U video game console's built-in software lets you watch movies and have fun right out of the box. BTW, why does it sound like you guys are crying about me installing homebrew software on my Wii console? I am just wondering because it seems a few of you. The Nintendo Wii was introduced in and, since then, over pay for any of this software, which is provided free of charge to everyone. Perform to Popular Chart-Topping Tunes - Sing up to 30 top hits from Season 1; Gleek Out to Never-Before-Seen Clips from the Show – Perform to video. a wiki dedicated to homebrew on the Nintendo Wii. We have 1, articles. Install the Homebrew Channel on your Wii console by following the homebrew setup tutorial. Browse the Homebrew, Wii hardware, Wii software, Development. The Wii was not designed by Nintendo to support homebrew. There is no guarantee that using homebrew software will not harm your Wii. A crazy software issue has come up. It's been around 10 months since the wii u was turned on at all. Now that we have, it boots up fine and you. Thus, we developed a balance assessment software using the Nintendo Wii Balance Board, investigated its reliability and validity, and. In Q1, Nintendo DS software sales were million, up million units Wii software sales reached million units, a million.
    [Show full text]
  • Also Includes Slides and Contents From
    The Compilation Toolchain Cross-Compilation for Embedded Systems Prof. Andrea Marongiu ([email protected]) Toolchain The toolchain is a set of development tools used in association with source code or binaries generated from the source code • Enables development in a programming language (e.g., C/C++) • It is used for a lot of operations such as a) Compilation b) Preparing Libraries Most common toolchain is the c) Reading a binary file (or part of it) GNU toolchain which is part of d) Debugging the GNU project • Normally it contains a) Compiler : Generate object files from source code files b) Linker: Link object files together to build a binary file c) Library Archiver: To group a set of object files into a library file d) Debugger: To debug the binary file while running e) And other tools The GNU Toolchain GNU (GNU’s Not Unix) The GNU toolchain has played a vital role in the development of the Linux kernel, BSD, and software for embedded systems. The GNU project produced a set of programming tools. Parts of the toolchain we will use are: -gcc: (GNU Compiler Collection): suite of compilers for many programming languages -binutils: Suite of tools including linker (ld), assembler (gas) -gdb: Code debugging tool -libc: Subset of standard C library (assuming a C compiler). -bash: free Unix shell (Bourne-again shell). Default shell on GNU/Linux systems and Mac OSX. Also ported to Microsoft Windows. -make: automation tool for compilation and build Program development tools The process of converting source code to an executable binary image requires several steps, each with its own tool.
    [Show full text]
  • Embedded Linux Systems with the Yocto Project™
    OPEN SOURCE SOFTWARE DEVELOPMENT SERIES Embedded Linux Systems with the Yocto Project" FREE SAMPLE CHAPTER SHARE WITH OTHERS �f, � � � � Embedded Linux Systems with the Yocto ProjectTM This page intentionally left blank Embedded Linux Systems with the Yocto ProjectTM Rudolf J. Streif Boston • Columbus • Indianapolis • New York • San Francisco • Amsterdam • Cape Town Dubai • London • Madrid • Milan • Munich • Paris • Montreal • Toronto • Delhi • Mexico City São Paulo • Sidney • Hong Kong • Seoul • Singapore • Taipei • Tokyo Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. For information about buying this title in bulk quantities, or for special sales opportunities (which may include electronic versions; custom cover designs; and content particular to your business, training goals, marketing focus, or branding interests), please contact our corporate sales depart- ment at [email protected] or (800) 382-3419. For government sales inquiries, please contact [email protected]. For questions about sales outside the U.S., please contact [email protected]. Visit us on the Web: informit.com Cataloging-in-Publication Data is on file with the Library of Congress.
    [Show full text]
  • Design Languages for Embedded Systems
    Design Languages for Embedded Systems Stephen A. Edwards Columbia University, New York [email protected] May, 2003 Abstract ward hardware simulation. VHDL’s primitive are assign- ments such as a = b + c or procedural code. Verilog adds Embedded systems are application-specific computers that transistor and logic gate primitives, and allows new ones to interact with the physical world. Each has a diverse set be defined with truth tables. of tasks to perform, and although a very flexible language might be able to handle all of them, instead a variety of Both languages allow concurrent processes to be de- problem-domain-specific languages have evolved that are scribed procedurally. Such processes sleep until awak- easier to write, analyze, and compile. ened by an event that causes them to run, read and write variables, and suspend. Processes may wait for a pe- This paper surveys some of the more important lan- riod of time (e.g., #10 in Verilog, wait for 10ns in guages, introducing their central ideas quickly without go- VHDL), a value change (@(a or b), wait on a,b), ing into detail. A small example of each is included. or an event (@(posedge clk), wait on clk un- 1 Introduction til clk='1'). An embedded system is a computer masquerading as a non- VHDL communication is more disciplined and flexible. computer that must perform a small set of tasks cheaply and Verilog communicates through wires or regs: shared mem- efficiently. A typical system might have communication, ory locations that can cause race conditions. VHDL’s sig- signal processing, and user interface tasks to perform.
    [Show full text]
  • Computer Architecture and Assembly Language
    Computer Architecture and Assembly Language Gabriel Laskar EPITA 2015 License I Copyright c 2004-2005, ACU, Benoit Perrot I Copyright c 2004-2008, Alexandre Becoulet I Copyright c 2009-2013, Nicolas Pouillon I Copyright c 2014, Joël Porquet I Copyright c 2015, Gabriel Laskar Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being just ‘‘Copying this document’’, no Front-Cover Texts, and no Back-Cover Texts. Introduction Part I Introduction Gabriel Laskar (EPITA) CAAL 2015 3 / 378 Introduction Problem definition 1: Introduction Problem definition Outline Gabriel Laskar (EPITA) CAAL 2015 4 / 378 Introduction Problem definition What are we trying to learn? Computer Architecture What is in the hardware? I A bit of history of computers, current machines I Concepts and conventions: processing, memory, communication, optimization How does a machine run code? I Program execution model I Memory mapping, OS support Gabriel Laskar (EPITA) CAAL 2015 5 / 378 Introduction Problem definition What are we trying to learn? Assembly Language How to “talk” with the machine directly? I Mechanisms involved I Assembly language structure and usage I Low-level assembly language features I C inline assembly Gabriel Laskar (EPITA) CAAL 2015 6 / 378 I Programmers I Wise managers Introduction Problem definition Who do I talk to? I System gurus I Low-level enthusiasts Gabriel Laskar (EPITA) CAAL
    [Show full text]
  • Compiler Construction
    Compiler Construction Chapter 11 Compiler Construction Compiler Construction 1 A New Compiler • Perhaps a new source language • Perhaps a new target for an existing compiler • Perhaps both Compiler Construction Compiler Construction 2 Source Language • Larger, more complex languages generally require larger, more complex compilers • Is the source language expected to evolve? – E.g., Java 1.0 ! Java 1.1 ! . – A brand new language may undergo considerable change early on – A small working prototype may be in order – Compiler writers must anticipate some amount of change and their design must therefore be flexible – Lexer and parser generators (like Lex and Yacc) are therefore better than hand- coding the lexer and parser when change is inevitable Compiler Construction Compiler Construction 3 Target Language • The nature of the target language and run-time environment influence compiler construction considerably • A new processor and/or its assembler may be buggy Buggy targets make it difficult to debug compilers for that target! • A successful source language will persist over several target generations – E.g., 386 ! 486 ! Pentium ! . – Thus the design of the IR is important – Modularization of machine-specific details is also important Compiler Construction Compiler Construction 4 Compiler Performance Issues • Compiler speed • Generated code quality • Error diagnostics • Portability • Maintainability Compiler Construction Compiler Construction 5 Compiler Speed • Reduce the number of modules • Reduce the number of passes Perhaps generate machine
    [Show full text]
  • Sr. Firmware - Embedded Software Engineer
    SR. FIRMWARE - EMBEDDED SOFTWARE ENGINEER Atel USA is a leading provider of high-performance, small form-factor tracking systems for the vehicle recovery, fleet, heavy trucks, and asset tracking industries. Our team has years of experience in developing complex wireless and communications systems. We have shipped several millions of vehicle tracking devices operating on all major cellular networks. We are seeking an enthusiastic embedded software engineer to be a key team member in the design, implementation, and verification of our asset tracking devices and sensory accessories. The Sr. Firmware Engineer will become an integral part of our company and will work as part of a small, multi-disciplinary development team to design, construct and deliver software/firmware for our current and next generation products. Primary Responsibilities: • Work independently on project tasks as well as work as a team member of a larger project team. • Collaborate with hardware/system design engineers to define the product feature set and work within a product development team to deliver firmware that meets or exceeds product requirements. • Engage with customers and product managers to define requirements, develop software architecture, and plan development in dynamic, evolving customer driven environment. • Deliver innovative solutions from concept to prototype to production. • Conduct/participate in engineering reviews to provide technical input on product designs and quality. • Conduct software unit tests to exercise implemented functionality. • Document software designs. • Troubleshoot and remove defects from production software. • Communicate and interact with team and customers to clearly set expectations, share technical details, resolve issues, and report progress. • Participate in brainstorms and otherwise contribute outside your area of expertise.
    [Show full text]
  • Sr. Embedded Software/ Firmware Engineer This Position Is Located at the Corporate Headquarters in Henderson, Nevada
    Sr. Embedded Software/ Firmware Engineer This position is located at the Corporate Headquarters in Henderson, Nevada VadaTech, Inc. is seeking experienced candidates for Senior Embedded Software/Firmware Engineer. Primary Responsibilities: • Responsible for the focus on BIOS and board bring up • Responsible for the coordinating and prioritizing application modifications and bug fixes • Responsible for working with the customer support team to troubleshoot and resolve production issues • Responsible for the support, maintenance and documentation of software functionality • Responsible for Contributing to the development of internal tools to streamline the engineering and build and release processes • Responsible for the production of functional specifications and design documents Desired Skills and Experience • Bachelor’s degree in computer science or related field; master’s degree preferred • 8+ years of related work experience • Fluency in C programming required • Experience with Embedded Bootloader/OS porting required • Experience with U-Boot/Embedded Linux porting and PC BIOS maintenance preferred • Experience with new/untested hardware board bring-up required • Demonstrated ability to read hardware schematics and use lab instruments such as oscilloscopes, multimeters and JTAG probes to resolve problems required • Must be knowledgeable in low-level board-support software/hardware interfacing for DDR3 memory, local bus timings, Ethernet PHYs, NOR/NAND flash, I2C/SPI, and others • Experience with diverse CPU types such as PowerPC/PowerQUICC/QorIQ,
    [Show full text]
  • Embedded Linux Systems
    Dpto Sistemas Electrónicos y de Control Universidad Politécnica de Madrid Embedded Linux Systems Using Buildroot for building Embedded Linux Systems with the Raspberry-PI V1.2 Mariano Ruiz 2014 EUIT Telecomunicación Dpto. Sistemas Electrónicos y de C o n t r o l Page 1 of 41 Page 2 of 41 Table of contents 1 SCOPE ........................................................................................................................................ 6 1.1 Document Overview .............................................................................................................. 6 1.2 Acronyms .............................................................................................................................. 6 2 REFERENCED DOCUMENTS ......................................................................................................... 7 2.1 References ............................................................................................................................. 7 3 LAB1: BUILDING LINUX USING BUILDROOT ................................................................................. 8 3.1 Elements needed for the execution of these LABS. .................................................................. 8 3.2 Starting the VMware .............................................................................................................. 8 3.3 Configuring Buildroot. .......................................................................................................... 11 3.4 Compiling buildroot. ...........................................................................................................
    [Show full text]
  • 1.1 Purpose of Embedded System 1.2 Host and Target Machine 1.2.1
    e-PG Pathshala Subject : Computer Science Paper: Embedded System Module: Embedded Software Development Tools Module No: CS/ES/36 Quadrant 1 – e-text In this module, we will discuss about the host and target machine, Embedded Software development process and Embedded tools. 1.1 Purpose of Embedded System An embedded system is a special-purpose system in which the computer is completely encapsulated by the device it controls. Each embedded system has unique characteristics. The components and functions of hardware and software can be different for each system. Nowadays, embedded software is used in all the electronic devices such as watches, cellular phones etc. This embedded software is similar to general programming. But the embedded hardware is unique. The method of communication between interfaces can vary from processor to processor. It leads to more complexity of software. Engineers need to be aware of the software developing process and tools. There are a lot of things that software development tools can do automatically when the target platform is well defined. This automation is possible because the tools can exploit features of the hardware and operating system on which your program will execute. Embedded software development tools can rarely make assumptions about the target platform. Hence the user has to provide some explicit instructions of the system to the tools. Figure 1.1 shows how an embedded system is developed using a host and a target machine. 1.2 Host and Target machine Figure 1.1 Embedded system using host and target machine 1.2.1 Performance of Host machine The application program developed runs on the host computer.
    [Show full text]
  • Towards Customizable Pedagogic Programming Languages
    TOWARDS CUSTOMIZABLE PEDAGOGIC PROGRAMMING LANGUAGES by Kathryn E. Gray A dissertation submitted to the faculty of The University of Utah in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Science School of Computing The University of Utah August 2006 Copyright c Kathryn E. Gray 2006 All Rights Reserved THE UNIVERSITY OF UTAH GRADUATE SCHOOL SUPERVISORY COMMITTEE APPROVAL of a dissertation submitted by Kathryn E. Gray This dissertation has been read by each member of the following supervisory committee and by majority vote has been found to be satisfactory. Chair: Matthew Flatt Wilson Hsieh Gary Lindstrom Joe Zachary Gilad Bracha THE UNIVERSITY OF UTAH GRADUATE SCHOOL FINAL READING APPROVAL To the Graduate Council of the University of Utah: I have read the dissertation of Kathryn E. Gray in its final form and have found that (1) its format, citations, and bibliographic style are consistent and acceptable; (2) its illustrative materials including figures, tables, and charts are in place; and (3) the final manuscript is satisfactory to the Supervisory Committee and is ready for submission to The Graduate School. Date Matthew Flatt Chair, Supervisory Committee Approved for the Major Department Martin Berzins Chair/Dean Approved for the Graduate Council David S. Chapman Dean of The Graduate School ABSTRACT In introductory education, pedagogic tools and languages can help focus students on the fundamental programming concepts. Subsets of a professional language support the presentation of the language’s syntax in step with the presentation of the underlying concepts, relieving students and instructors from superfluous details. This dissertation presents the design and implementation of pedagogic tools integrated with an introduc- tory computer science course.
    [Show full text]
  • Embedded Firmware Development Languages/Options
    Module -4 Embedded System Design Concepts Characteristics & Quality Attributes of Embedded Systems Characteristics of Embedded System Each Embedded System possess a set of characteristics which are unique to it. Some important characteristics of embedded systems are: Application & Domain Specific Reactive & Real Time Operates in ‘harsh’ environment Distributed Small size and Weight Power Concerns Quality Attributes of Embedded Systems: Represent the non-functional requirements that needs to be addressed in the design of an embedded system. The various quality attributes that needs to be addressed in any embedded system development are broadly classified into Operational Quality Attributes Refers to the relevant quality attributes related to tan embedded system when it is in the operational mode or ‘online ’ mode Non-Operational Quality Attributes The Quality attributes that needs to be addressed for the product ‘not’ on the basis of operational aspects are grouped under this category Operational Quality Attributes Response Throughput Reliability Maintainability Security Safety Non-Operational Quality Attributes Testability & Debug-ability Evolvability Portability Time to Prototype and Market Per Unit and Total Cost Washing Machine – Application Specific Embedded System V Extensively used in Home Automation for washing and drying clothes V Contains User Interface units (I/O) like Keypads, Display unit, LEDs for accepting user inputs and providing visual indications V Contains sensors like, water level sensor, temperature
    [Show full text]