AN613 Using Microchip 93 Series Serial Eeproms with Microcontroller SPI Ports

Total Page:16

File Type:pdf, Size:1020Kb

AN613 Using Microchip 93 Series Serial Eeproms with Microcontroller SPI Ports AN613 Using Microchip 93 Series Serial EEPROMs with Microcontroller SPI Ports to make sure it writes (polling ready/busy pin to verify Author: Keith Pazul write cycle completion) and reads properly. A Memory and ASSP Division schematic (Figure 2) is included in this application note to describe exactly how the 93LC56/66 was connected to the microcontroller. INTRODUCTION THEORY OF OPERATION Systems requiring embedded control are becoming more and more sophisticated, with microcontrollers To use an SPI port to communicate with Microchip’s 93 required to control these systems increasing in series Serial EEPROMs, the bytes to be output to the complexity. Many microcontrollers today are being 93XXXX must be aligned such that the LSB of the designed with built-in serial communication capability address is the 8th bit (LSB) of a byte to be output. From to be able to easily access other features that are not there, the bits should fill the byte from right to left built in to the microcontroller itself. Devices like consecutively. If more than 8 bits are required, then two EEPROMs, A/Ds, D/As, LCDs etc. are all being built bytes will be required to be output. This same method with a serial interface to reduce cost, size, pin count, will work for any 93 series device. A 93LC66 was and board area. There are many different serial chosen as the device to write this application note code interfaces on the market used to interface peripherals for, so the following example will be for that particular 2 (I C , Microwire , SPI, for example). One of the serial device. The theory explained below will work for any 93 interfaces that is gaining in popularity is SPI (Serial series device. Peripheral Interface). It is becoming more popular because of its communication speed, simultaneous Since more than 8 bits are required to control a full-duplex communication, and ease of programming. 93LC66, two consecutive bytes are required. Microchip PIC16C64/74 microcontrollers have a built-in High Byte (where the start bit, op code bits, and serial port that can be configured as an SPI port. address MSB reside) Currently, the Microchip Serial EEPROM product line | 0 | 0 | 0 | 0 | SB | OP1 | OP0 | A8 | does not support SPI interface Serial EEPROMs, The High Byte is configured in the following format: SB however it is possible to use the 93 series devices on the is the start bit, OP1 is op code MSB, OP0 is op code SPI port. Any version of Microchip’s 93 series devices LSB, and A8 is the 9th address bit that is required to can be communicated with via the SPI port of a address 512 bytes. The CS can be set before the byte PIC16C64/74. The code for this application note is is output because the leading 0’s output to the 93xxxx written for a Microchip 93LC56/66, but talking to other 93 prevent a start bit from being recognized by the 93xxxx series devices can be accommodated with minor code until the first high bit is sent. changes. See the Theory of Operation section of this application note for more details on how this is Low Byte (8 address LSBs) accomplished. This code was verified by downloading to | A7 | A6 | A5 | A4 | A3 | A2 | A1 | A0 | Microchip’s PICMASTER in-circuit emulator (run at full The Low Byte contains A7-A0, which are the rest of the speed with a 10 MHz crystal) and tested to make sure it address bits required to access 512 bytes. writes (polling ready/busy pin to verify write cycle completion) and reads properly. A schematic (Figure 1) Data output from master MUST be set up on the falling is included in this application note to describe exactly edge of the clock so that it can be read from the how the 93LC56/66 was connected to the PIC16C64/74. 93XXXX on the next rising edge. Receiving data from the 93XXXX MUST also happen on the falling edge of The SPI interface was popularized by the Motorola the clock because the data is output from the 93XXXX 68HCXX microcontrollers. Microchip receives many on the rising edge of the clock. THIS REQUIRES THE requests for Motorola assembly code that uses the SPI CLOCK PHASE BIT OF THE SPI PORT TO BE port of the 68HC11 or 68HC05 to talk to Microchip OPPOSITE FOR RECEIVING THAN IT IS FOR serial EEPROMs. Because of this, Microchip has TRANSMITTING. The clock phase needs to be written 68HC11 assembly code to communicate with its toggled between 0 for transmitting data and 1 for 93 series devices via its SPI port. The program was receiving data. See source code for the exact spot downloaded to a 68HC11 evaluation board and tested where the clock phase bit needs to be changed. 1995 Microchip Technology Inc. DS00613A-page 1 Thi d t t d ith F M k 4 0 4 AN613 FIGURE 1: PIC16C74 TO 93LC56/66 SCHEMATIC VDD PIC16C74 VDD RA0/AN0 RA1/AN1 RA2/AN2 MCLR/VPP RA3/AN3 RA4/T0CKI RA5/AN4/SS VSS RB0/INT RB1 OSC1/CLKIN RB2 RB3 OSC2/CLKOUT RB4 10.0 MHz RB5 RB6 RB7 VDD 15pF 15pF 93LC56/66 RC0/T1OSO/T1CKI CS VCC RC1/T1OSI/CCP2 RC2/CCP1 CLK NC RC3/SCK/SCL RC4/SDI/SDA DI ORG RC5/SDO RC6/TX/CK DO VSS RC7/RX/DT RE0/RD/AN5 RE1/WR/AN6 RE2/CS/AN7 RD0/PSP0 RD1/PSP1 RD2/PSP2 RD3/PSP3 RD4/PSP4 RD5/PSP5 RD6/PSP6 RD7/PSP7 DS00613A-page 2 1995 Microchip Technology Inc. AN613 FIGURE 2: MOTOROLA 68HC11 TO MICROCHIP 93LC56/66 SCHEMATIC MC68HC11E9 E VDD µ VDD PA0/IC3 System + 0.1 F PA1/IC2 PA2/IC0 Power 4.7µF PA3/OC5/OC1 VSS PA4/OC4/OC1 PA5/0C3/0C1 PA6/0C2/0C1 10MΩ EXTAL PA7/PAI/OC1 XTAL STRB 8.0 MHz STRA PB0 18pF 18pF PB1 PB2 PB3 PB4 4.7kΩ PB5 VDD RESET PB6 PB7 4.7kΩ XIRQ PC0 4.7kΩ PC1 IRQ PC2 PC3 PC4 10kΩ PC5 VDD 4.7kΩ PC6 PC7 93LC56/66 MODB/VSTBY CS VCC PD0/RxD MODA/LIR PD1/TxD CLK NC PD2/MISO PD3/MOSI DI ORG PD4/SCK PD5/SS DO VSS PE0/AN0 PE1/AN1 VRH PE2/AN2 PE3/AN3 PE4/AN4 PE5/AN5 VRL PE6/AN6 PE7/AN7 Note: A pull down resistor is included on the CS pin. It deselects the 93LC56/66, always, except for when CS is driven high by the 68HC11. 1995 Microchip Technology Inc. DS00613A-page 3 AN613 Please check the Microchip BBS for the latest version of the source code. For BBS access information, see Section 6, Microchip Bulletin Board Service information, page 6-3. APPENDIX A: PIC16C64/74 SOURCE CODE ;**************************************************** ; ; To use the SPI port to communicate with 3-wire devices, ; the bytes to be output must be aligned such that the LSB of the ; address is the 8th bit (LSB) of a byte to be output. From there, ; the bits should fill the byte from right to left consecutively. ; This same method will work for any 93xxxx device. A 93LC66 was ; chosen as the device to write this application note code for, ; so the following example will be for that particular device. ; The theory explained below will work for any 93 series device. ; ; Since more than 8 bits are required to control a 93LC66, ; two consecutive bytes are required. ; ; High byte (where start bit, op code bits and address MSB reside) ; ; | 0 | 0 | 0 | 0 | SB | OP1 | OP0 | A8 | ; ; The High Byte is configured in the following format: ; SB is the start bit, OP1 is op code MSB, OP0 is op code LSB, and A8 ; is the 9th address bit that is required to address 512 bytes. The CS ; can be set before the byte is output because the leading 0’s output to ; the 93xxxx prevent a start bit from being recognized by the 93xxxx until ; the first high bit is sent. ; ; Low byte (8 address LSBs) ; ; | A7 | A6 | A5 | A4 | A3 | A2 | A1 | A0 | ; ; The Low Byte contains A8-A0, which are address bits required ; to access 512 bytes. ; ; The chip select is set high before sending the first byte out because ; the 93LC66 will not recognize a start bit until both CS and DI are ; high on the rising edge of a clock. ; ; This code is written to use the 16C64/74 SPI port to communicate with a ; Microchip 93LC66. The only other I/O line required besides the SPI port ; pins is a chip select. The ORG pin will be grounded to set up the part ; in x8 mode. ; ; PIN DESCRIPTIONS: ; ; SCK (serial clock) port C, bit 3 ; SDO (serial data out) port C, bit 5 ; SDI (serial data in) port C, bit 4 ; CS (chip select) port C, bit 0 ; ; Transmits from the master MUST happen on the falling edge of the clock ; so they can be read by the 93xxxx on the next rising edge of the clock. ; Receiving from the 93xxx MUST also happen on the falling edge of the ; clock because on the rising edge of the clock, the 93xxxx outputs its bit ; on its DO pin. This requires the CKP bit in the SSPCON register to be set ; to 1 for transmitting data and CKP=0 for receiving data. ; ; This code was written by Keith Pazul on 10/5/94 ; ;********************************************************** ;**************************************************** ; Ram Register Definitions DS00613A-page 4 1995 Microchip Technology Inc. AN613 ;**************************************************** ; ; received bytes from EEPROM memory locations 10h to 13h ; will be stored in RAM registers 20h to 23h. rxdata equ 24h txdata equ 25h addr equ 26h loops equ 27h loops2 equ 28h hibyte equ 29h lobyte equ 2Ah datbyt equ 2Bh ;**************************************************** ; ; Other Definitions ; ;**************************************************** ; ; ;**************************************************** ; Bit Definitions ;**************************************************** ; cs equ 0 sdi equ 4 ;**************************************************** include “c:\mpasm\include\p16cxx.inc” ; register map for PIC16CXX devices org 0x000 ; Reset Vector goto Start ; ;*********************************************************** ; ; This is the transmit/receive routine.
Recommended publications
  • COSMIC C Cross Compiler for Motorola 68HC11 Family
    COSMIC C Cross Compiler for Motorola 68HC11 Family COSMIC’s C cross compiler, cx6811 for the Motorola 68HC11 family of microcontrollers, incorporates over twenty years of innovative design and development effort. In the field since 1986 and previously sold under the Whitesmiths brand name, cx6811 is reliable, field-tested and incorporates many features to help ensure your embedded 68HC11 design meets and exceeds performance specifications. The C Compiler package for Windows includes: COSMIC integrated development environment (IDEA), optimizing C cross compiler, macro assembler, linker, librarian, object inspector, hex file generator, object format converters, debugging support utilities, run-time libraries and a compiler command driver. The PC compiler package runs under Windows 95/98/ME/NT4/2000 and XP. Complexity of a more generic compiler. You also get header Key Features file support for many of the popular 68HC11 peripherals, so Supports All 68HC11 Family Microcontrollers you can access their memory mapped objects by name either ANSI C Implementation at the C or assembly language levels. Extensions to ANSI for Embedded Systems ANSI / ISO Standard C Global and Processor-Specific Optimizations This implementation conforms with the ANSI and ISO Optimized Function Calling Standard C specifications which helps you protect your C support for Internal EEPROM software investment by aiding code portability and reliability. C support for Direct Page Data C Runtime Support C support for Code Bank Switching C runtime support consists of a subset of the standard ANSI C support for Interrupt Handlers library, and is provided in C source form with the binary Three In-Line Assembly Methods package so you are free to modify library routines to match User-defined Code/Data Program Sections your needs.
    [Show full text]
  • M.Tech –Embedded System Design SEMESTER-I S.NO CODE
    CURRICULUM DEPARTMENT OF ELECTRONICS AND COMMUNICATION BRANCH: M.Tech –Embedded System Design SEMESTER-I S.NO CODE SUBJECT NAME L T P C 1 PMA105 Applied Mathematics for Electronics Engineers 3 1 0 4 2 PED101 Microcontroller Based System Design 3 0 0 3 3 PED102 Embedded Systems 3 0 0 3 4 PAE102 Advanced Digital System Design 3 0 0 3 5 PED1E1 Elective-I 3 0 0 3 6 PED1L1 Embedded System Design Lab-I 0 0 4 2 TOTAL CONTACT HOURS- 20 18 SEMESTER-II 1 PED101 ASIC Design 3 0 0 3 2 PED202 Software Technology for Embedded System 3 0 0 3 3 PED203 Real Time Systems 3 0 0 3 4 PED2E2 Elective-II 3 0 0 3 5 PED2E3 Elective-III 3 0 0 3 6 PED2L2 Embedded System Design Lab -II 0 0 4 2 TOTAL CONTACT HOURS -19 17 SEMESTER-III 1. PED3E4 Elective-IV 3 0 0 3 2. PED3E5 Elective-V 3 0 0 3 3. PED3E6 Elective-VI 3 0 0 3 4. PED3P1 Project work phase-I 0 0 12 6 TOTAL CONTACT HOURS-21 15 SEMESTER-IV 1 PED4P2 Project work phase-II 0 0 24 12 TOTAL CONTACT HOURS-24 12 TOTAL CREDITS FOR THE PROGRAMME-62 LIST OF ELECTIVES 1 PED 001 Design of Embedded System 3 0 0 3 2 PED 002 Embedded Control System 3 0 0 3 3 PED 003 Computer Vision and Image Understanding 3 0 0 3 4 PED 004 Distributed Embedded Computing 3 0 0 3 5 PED 005 Design of Digital Control System 3 0 0 3 6 PED 006 Crypto Analytic Systems 3 0 0 3 7 PED 007 Intelligent Embedded Systems 3 0 0 3 8 PAE 006 Artificial Intelligence and Expert systems 3 0 0 3 9 PED102 Embedded systems 3 0 0 3 10 PED201 ASIC Design 3 0 0 3 11 PVL002 Low power VLSI Design 3 0 0 3 12 PVL003 Analog VLSI Design 3 0 0 3 13 PVL004 VLSI Signal processing
    [Show full text]
  • Experience of Teaching the Pic Microcontrollers
    Session 1520 EXPERIENCE OF TEACHING THE PIC MICROCONTROLLERS Han-Way Huang, Shu-Jen Chen Minnesota State University, Mankato, Minnesota/ DeVry University, Tinley Park, Illinois Abstract This paper reports our experience in teaching the Microchip 8-bit PIC microcontrollers. The 8-bit Motorola 68HC11 microcontroller has been taught extensively in our introductory microprocessor courses and used in many student design projects in the last twelve years. However, the microcontroller market place has changed considerably in the recent years. Motorola stopped new development for the 68HC11 and introduced the 8- bit 68HC908 and the 16-bit HCS12 with the hope that customers will migrate their low- end and high-end applications of the 68HC11 to these microcontrollers, respectively. On the other hand, 8-bit microcontrollers from other vendors also gain significant market share in the last few years. The Microchip 8-bit microcontrollers are among the most popular microcontrollers in use today. In addition to the SPI, USART, timer functions, and A/D converter available in the 68HC11 [6], the PIC microcontrollers from Microchip also provide peripheral functions such as CAN, I2C, and PWM. The controller-area- network (CAN) has been widely used in automotive and process control applications. The Inter-Integrated Circuit (I2C) has been widely used in interfacing peripheral chips to the microcontroller whereas the Pulse Width Modulation (PWM) function has been used extensively in motor control. After considering the change in microcontrollers and the technology evolution, we decided to teach the Microchip 8-bit microcontrollers. 1 Several major issues need to be addressed before a new microcontroller can be taught: textbook, demo boards, and development software and hardware tools.
    [Show full text]
  • Chapter 7. Microcontroller Implementation Consideration
    Chapter 7. Microcontroller Implementation Consideration The overall performance of wheel slip control systems have been limited in the past primarily by the unavailability of low cost, flexible, high-speed electronic technology. The application of high speed digital microcontrollers in anti-lock brake systems allows increased computational capabilities and control performance. In this section, a Motorola 68HC11 microcontroller is evaluated for its suitability for the anti-lock brake control application. This family of microcontroller have been used in FLASH lab, Virginia Tech Center for Transportation Research for evaluation of the automatic highway system concepts and technologies (Kachroo, 1995). Due to the unavailability of the small-size electromagnetic brakes, we have not implemented the electromagnetic brakes and its control system on the small-scale vehicle in FLASH lab. But the digital control algorithm of the possible ABS system is evaluated and features of 68HC11 and alternative families of microcontrollers are evaluated to estimate their suitability for ABS application. For regular friction brakes, modulated brake torque can be calculated and applied to every individual wheel because there is a possibility that different wheels are on different road surfaces. On the other hand, due to the location of electromagnetic brakes, its output torque must be applied to all four wheels in an overall base. The anti-lock brake system discussed in this section takes both situations into consideration. 66 7.1. Motorola 68HC11 Microcontroller (Motorola, 1991) The high-density complementary metal-oxide semiconductor (HCMOS) 68HC11 is an advanced 8-bit microcontroller with sophisticated on-chip peripheral capabilities. The HCMOS technology combines smaller size and higher speeds with the lower power and high noise immunity of CMOS.
    [Show full text]
  • ZAP Cross Debuggers for Motorola Microcontrollers
    ZAP Cross Debuggers for Motorola Microcontrollers ZAP is a family of full-featured C and assembly language source-level debuggers designed to give Motorola embedded microcontroller developers a consistent and productive debugging environment across multiple target processors. Key Features: ZAP Addresses Your Debugging Needs At Each Stage of Your Project Provides a Portable Debugging Environment, ZAP’s multiple configurations are designed to address your debugging needs as your project moves from the design stage Debugger for Each Stage of Your Project, to final integration and test; ZAP configurations supported C and Assembler Source-level Debugging, are: software simulation, target monitor, background debug mode, and in-circuit emulator. Each configuration ANSI C Debugging, gives you essentially the same user interface, thus vastly Array and Structure Explorer, improving your productivity, but each addresses a different stage of your project. Debug Fully Optimized Code, Easy-to-use Graphical User Interface, C and Assembler Source-level Debugging If your source code is written in C, you want to debug at the C Extensive Program Control & Analysis Features, level; if parts of your source code are written in assembly Graphical Performance Analysis, language you want to debug at the assembly language level. ZAP automatically supports both modes without any special Code and Data Coverage, options or settings, so you always see your original source C Level Trace, code in the Source window. If you are debugging at the C level, you can activate a Disassembly window that shows you Robust Script language, the corresponding assembly language code for each line of C source. Automated Testing, Real-Time BDM debugging, ANSI C Debugging Hardware Breakpoint support, ZAP provides point and click access to any C object or construct including enums, bit fields, strings, doubles/floats, FLASH and EEPROM Programming, structures and stack frames.
    [Show full text]
  • The ZEN of BDM
    The ZEN of BDM Craig A. Haller Macraigor Systems Inc. This document may be freely disseminated, electronically or in print, provided its total content is maintained, including the original copyright notice. Introduction You may wonder, why The ZEN of BDM? Easy, BDM (Background Debug Mode) is different from other types of debugging in both implementation and in approach. Once you have a full understanding of how this type of debugging works, the spirit behind it if you will, you can make the most of it. Before we go any further, a note on terminology. “BDM” is Motorola’s term for a method of debugging. It also refers to a hardware port on their microcontroller chips, the “BDM port”. Other chips and other manufacturers use a JTAG port (IBM), a OnCE port (Motorola), an MPSD port (Texas Instruments), etc. (more on these later). The type of debugging we will be discussing is sometimes known as “BDM debugging” even though it may use a JTAG port! For clarity, I will refer to it as “on-chip debugging” or OCD. This will include all the various methods of using resources on the chip that are put there to enable complete software debug and aid in hardware debug. This includes processors from IBM, TI, Analog Devices, Motorola, and others. This paper is an overview of OCD debugging, what it is, and how to use it most effectively. A certain familiarity with debugging is assumed, but novice through expert in microprocessor/microcontroller design and debug will gain much from its reading. Throughout this paper I will try to be as specific as possible when it relates to how different chips implement this type of debugging.
    [Show full text]
  • A New Approach in Microprocessor/Microcontroller Courses/Laboratories Material Design and Development
    2006-386: A NEW APPROACH IN MICROPROCESSOR/MICROCONTROLLER COURSES/LABORATORIES MATERIAL DESIGN AND DEVELOPMENT Steve Hsiung, Old Dominion University STEVE C. HSIUNG Steve Hsiung is an associate professor of electrical engineering technology at Old Dominion University. Prior to his current position, Dr. Hsiung had worked for Maxim Integrated Products, Inc., Seagate Technology, Inc., and Lam Research Corp., all in Silicon Valley, CA. Dr. Hsiung also taught at Utah State University and California University of Pennsylvania. He earned his BS degree from National Kauhsiung Normal University in 1980, MS degrees from University of North Dakota in 1986 and Kansas State University in 1988, and a PhD degree from Iowa State University in 1992. Jeff Willis, Utah State University Jeff Willis Jeff Willis is a Software Engineer developing Mission Planning Software at Hill Air Force Base in Utah. He earned a BS degree in Computer Electronic Technology and a Masters degree in Computer Science from Utah State University. As part of his Master’s Thesis he co-authored two papers on self-configuring, deterministically latent intercommunication architectures for satellite payloads. Page 11.78.1 Page © American Society for Engineering Education, 2006 A New Approach in Microprocessor/Microcontroller Courses/Laboratories Material Design and Development Abstract Courses in microprocessors and microcontrollers are standard parts of the Engineering Technology core curricula. The traditional course material developments include both lectures and associated laboratory exercises. No matter how creative is the curriculum; it is usually budgetary constraints that confine the creativity when developing new curricula. This limits the freedom of the major approach in new course development.
    [Show full text]
  • HCS12 V1.5 Core User Guide Version
    not are currently here Freescale Semiconductor, I..nc. Family indicated Product negligent regardingthedesign ormanufactureofthepart. personal injury or deathagainst associated all claims, with costs, such damages,application, and unintended Buyer expenses, shall or and indemnify reasonable and unauthorized hold attorney use,personal Motorola fees and injury arising even its or out officers, if of, death employees, subsidiaries, such directly maysupport affiliates, or occur. claim and or indirectly, distributors Should alleges any sustain harmless Buyer claim that life, purchase of or Motorola or or authorized use was for for Motorola any products use otherneither for as does application any components it in such convey in unintended which any systemsdesign. or license the intended unauthorized Motorola under failure for does its of patent surgical not the rightsMotorola implant assume nor Motorola reserves into any the product the liability the rights could of body, arising right create others. or out to Motorola a other of products make situation the applications are where changes not application intended designed, without or to intended, use further of notice any to product any or products circuit described herein herein; to improve reliability, function or numbers part DragonBall and Family, lines Product product i.MX Freescale Semiconductor,Inc. Original ReleaseDate:12May2000 For More Information OnThis Product, HCS12 V1.5 Core 2010: BGA-packaged Revised: 17August2000 Go to:www.freescale.com Version 1.2 User Guide September to Motorola, Inc Commission, prior Trade States United the International in sale States or United import the for DOCUMENT NUMBER from order Freescale S12CPU15UG/D an from of Because available 1 not are currently here Freescale Semiconductor, I..nc.
    [Show full text]
  • Using As the Gnu Assembler
    Using as The gnu Assembler Version 2.14.90.0.7 The Free Software Foundation Inc. thanks The Nice Computer Company of Australia for loaning Dean Elsner to write the first (Vax) version of as for Project gnu. The proprietors, management and staff of TNCCA thank FSF for distracting the boss while they got some work done. Dean Elsner, Jay Fenlason & friends Using as Edited by Cygnus Support Copyright c 1991, 92, 93, 94, 95, 96, 97, 98, 99, 2000, 2001, 2002 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". Chapter 1: Overview 1 1 Overview This manual is a user guide to the gnu assembler as. Here is a brief summary of how to invoke as. For details, see Chapter 2 [Command-Line Options], page 15. as [-a[cdhlns][=file]] [-D][{defsym sym=val] [-f][{gstabs][{gstabs+] [{gdwarf2][{help] [-I dir][-J][-K][-L] [{listing-lhs-width=NUM][{listing-lhs-width2=NUM] [{listing-rhs-width=NUM][{listing-cont-lines=NUM] [{keep-locals][-o objfile][-R][{statistics][-v] [-version][{version][-W][{warn][{fatal-warnings] [-w][-x][-Z][{target-help][target-options] [{|files ...] Target Alpha options: [-mcpu] [-mdebug | -no-mdebug] [-relax][-g][-Gsize] [-F][-32addr] Target ARC options: [-marc[5|6|7|8]] [-EB|-EL] Target ARM
    [Show full text]
  • Babu Madhav Institute of Information Technology, 2016 UTU
    Babu Madhav Institute of Information Technology, 2016 UTU Course: 060010901 – Embedded System Unit – 1 Introduction to Embedded System SHORT QUESTIONS: 1. What is an embedded system? 2. State the definition of embedded system given by Wayne Wolf. 3. State the full form of ASIP, ASIC. 4. What is a real time embedded system? 5. List the characteristics of a real time embedded system. 6. What is the purpose of the control unit? 7. What is the purpose of the execution unit? 8. List out the type of processors. 9. Give an example of multi core processor. 10. What is power dissipation? 11. Define non-recurring engineering costs. 12. What is the size of microcontrollers in medium sized embedded systems? LONG QUESTIONS: 1. Define embedded system. State the purpose of embedded system and describe briefly how an embedded system differs from a normal system. 2. Explain in detail the components on a normal pc and an embedded system. 3. State the difference between micro-processors and micro-controllers. Explain in detail the types of micro-processors. 4. List and explain the metrics of embedded system. 5. Describe in detail the challenges that can arise while developing embedded systems. MULTIPLE CHOICE QUESTION: 1. For a real time system, if the time limit for execution of the task is not achieved then select the appropriate result which can occur due to the failure: a. The system will only send alarms and do nothing b. The system's watch dog timer will be reset c. The system will have a high chance of being physically damaged d.
    [Show full text]
  • Lpc210x 'Armee'
    LPC210X ‘ARMEE’ Part 1: an ARM processor survey Tony Dixon In the first instalment of a three-part article we will look at recent developments in 32-bit ARM based microcontrollers, concentrating on those devices that are available, do not cost an arm and a leg or require a major investment in surface mount soldering equipment! 46 elektor electronics- 3/2005 DEVELOPMENT BOARD (1) Overview of the Thumb mode (T) ARM7TDMI core An ARM instruction is 32-bits long. The ARM7TDMI proces- sor supports a second instruction set that has been com- pressed into 16-bits, the Thumb instruction set. Faster execu- A[31:0] tion from 16-bit memory and greater code density can usu- ALE ABE I ally be achieved by using the Thumb instruction set instead n Scan c Control of the ARM instruction set, which makes the ARM7TDMI core Address Register r e m particularly suitable for embedded applications. P e C n DBGRQI However the Thumb mode has two limitations and these are: Address t BREAKPTI b Incrementer e u r DBGACK Thumb code usually uses more instructions for the same job, s ECLK b u nEXEC so ARM code is usually best for maximising the performance Register Bank s ISYNC (31 x 32-bit registers) BL[3:0] of the time-critical code. A (6 status registers) L APE U MCLK The Thumb instruction set does not include some instructions b nWAIT that are needed for exception handling, so the ARM code u nRW s A B MAS[1:0] needs to be used for exception handling.
    [Show full text]
  • Using the GNU Compiler Collection
    Using the GNU Compiler Collection For gcc version 4.2.4 Richard M. Stallman and the GCC Developer Community Published by: GNU Press Website: www.gnupress.org a division of the General: [email protected] Free Software Foundation Orders: [email protected] 51 Franklin Street, Fifth Floor Tel 617-542-5942 Boston, MA 02110-1301 USA Fax 617-542-2652 Last printed October 2003 for GCC 3.3.1. Printed copies are available for $45 each. Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc. 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 “GNU General Public License” and “Funding Free Software”, the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled “GNU Free Documentation License”. (a) The FSF’s Front-Cover Text is: A GNU Manual (b) The FSF’s Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Short Contents Introduction ............................................. 1 1 Programming Languages Supported by GCC ............... 3 2 Language Standards Supported by GCC .................. 5 3 GCC Command Options ............................... 7 4 C Implementation-defined behavior ..................... 215 5 Extensions to the C Language Family ................... 223 6 Extensions to the C++ Language .....................
    [Show full text]