DOCSLIB.ORG

Xilinx DS577 XPS 16550 UART (V3.00A), Data Sheet

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

0 XPS 16550 UART (v3.00a) DS577 September 16, 2009 00 Product Specification Introduction LogiCORE™ Facts This document provides the specification for the XPS Core Specifics 16550 UART (Universal Asynchronous Virtex-4®, Virtex-4Q, Virtex-4QV, Receiver/Transmitter) Intellectual Property (IP). Virtex-5, Virtex-5FX, Virtex-6, Virtex-6CX, Spartan-3 AN, The XPS 16550 UART described in this document has Spartan®-3E, Automotive Supported Device Spartan-3E, Spartan-3, Automotive been incorporating features described in National Family Spartan-3, Spartan-3A, Automotive . Semiconductor PC16550D UART with FIFOs data sheet Spartan-3A, Spartan-3A DSP, The National Semiconductor PC16550D data sheet is Automotive Spartan-3A DSP, Spartan-6 referenced throughout this document and should be used as the authoritative specification. Differences Version of Core xps_uart16550 v3.00a between the National Semiconductor PC16550D and Resources Used the XPS 16550 UART are highlighted in Specification Min Max Exceptions section. Slices Refer to the Table 17, Table 18 and LUTs Features Table 19, Table 20, Table 21 FFs • Connects as a 32-bit Slave on PLB V4.6 bus of 32, 64 Block RAMs N/A and 128 bits data width Special Features N/A • Hardware and software register compatible with all standard 16450 and 16550 UARTs Provided with Core • Implements all standard serial interface protocols Documentation Product Specification − 5, 6, 7 or 8 bits per character Design File Formats VHDL − Odd, Even or no parity detection and Constraints File N/A generation Verification N/A − 1, 1.5 or 2 stop bit detection and generation Instantiation Template N/A − Internal baud rate generator and separate Reference Designs & receiver clock input N/A Application notes − Modem control functions Design Tool Requirements − Prioritized transmit, receive, line status and Xilinx Implementation modem control interrupts ISE® 11.3 or later Tools − False start bit detection and recover Mentor Graphics ModelSim v6.4b − Verification Line break detection and generation or later − Internal loop back diagnostic functionality Mentor Graphics ModelSim v6.4b Simulation − 16 byte transmit and receive FIFOs or later Synthesis XST 11.3 or later Support Provided by Xilinx, Inc. © 2006-2009 Xilinx, Inc., XILINX, the Xilinx logo, Virtex, Spartan, ISE and other designated brands included herein are trademarks of Xilinx in the United States and other countries. All other trademarks are the property of their respective owners. DS577 September 16, 2009 www.xilinx.com 1 Product Specification XPS 16550 UART (v3.00a) Functional Description The XPS 16550 UART implements the hardware and software functionality of the ubiquitous National Semiconductor 16550 UART, that works in both 16450 and 16550 UART modes. For complete details please refer the National Semiconductor data sheet. The XPS 16550 UART performs parallel to serial conversion on characters received from the CPU and serial to parallel conversion on characters received from a modem or microprocessor peripheral. The XPS 16550 UART is capable of transmitting and receiving 8, 7, 6, or 5 bit characters, with 2, 1.5 or 1 stop bits and odd, even or no parity. The XPS 16550 UART can transmit and receive independently. The device can be configured and it’s status monitored via the internal register set. The XPS 16550 UART is capable of signaling receiver, transmitter and modem control interrupts. These interrupts can be masked, are prioritized and can be identified by reading an internal register. The device contains a 16 bit, programmable, baud rate generator and independent 16 byte transmit and receive FIFOs. The FIFOs can be enabled or disabled through software control. The top-level block diagram for the XPS 16550 UART is shown in Figure 1. Figure Top x-ref 1 Serial PLB PLB IPIC UART Interface IPIC_IF Interface Interface Module Interface UART16550 Modem Interface DS577_01_020609 Figure 1: XPS 16550 UART Top-level Block Diagram The top level modules of the XPS 16550 UART are: • PLB Interface Module • IPIC_IF • UART16550 The detailed block diagram for the XPS 16550 UART is shown in Figure 2. 2 www.xilinx.com DS577 September 16, 2009 Product Specification XPS 16550 UART (v3.00a) Figure Top x-ref 2 IP2INTC_Irpt Freeze UART16550 rxrdyN Bus2IP_Clk rclk Receiver Bus2IP_Reset RBR FIFO1 sin THR FIFO1 sout le wr 2 u FCR Transmitter txrdyN rd LCR PLB IPIC_IF LSR ce Mod a IP2Bus_Ack IER baudoutN IP2Bus_Error IIR MCR PLB Interf Bus2IP_Data[24:31] MSR IP2Bus_IntrEvent SCR nd Control a xin IP2Bus_Data[24:31] DLL Baud xout DLM Generator ctsn Decode dcdn dsrn Modem rin Logic dtrn rtsn out1N out2N ddis Note: 1. 16450 UART mode does not support the FCR. 2. 16450 UART mode does not support the FIFOs. DS577_02_020609 Figure 2: XPS 16550 UART Detailed Block Diagram PLB Interface Module PLB Interface Module provides bidirectional interface between UART 16550 module and the PLB. The base element of the PLB Interface Module is slave attachment, which provides the basic functionality of PLB slave operation. IPIC_IF IPIC_IF module incorporates logic to acknowledge the write and read transactions initiated by the plbv46 slave single module to write into the UART 16550 module registers and read from UART 16550 module registers. UART 16550 UART 16550 provides all the core features for transmission, reception of data and modem features of UART. The UART 16550 module of XPS 16550 UART can be configured for 16450 or 16550 mode of operation. This is accomplished by the usage of generic C_IS_A_16550. DS577 September 16, 2009 www.xilinx.com 3 Product Specification XPS 16550 UART (v3.00a) If C_IS_A_16550 set to one, the UART 16550 module has FIFOs instantiated to support 16550 mode of operation. When C_IS_A_16550 is set to zero, the UART 16550 module works without FIFOs in 16450 mode. In 16550 mode, the FIFOs can be enabled by configuring FCR register. XPS 16550 UART I/O Signals The XPS 16550 UART I/O signals are listed and described in Table 1. Table 1: XPS 16550 UART I/O Signals Initial Port Signal Name Interface I/O State Description System Signals Freezes UART for software P1 Freeze System I - debug (active high) Device interrupt output to microprocessor interrupt input P2 IP2INTC_Irpt System O 0 or system interrupt controller (active high) P3 SPLB_Clk System I - PLB clock P4 SPLB_Rst System I - PLB reset (active high) PLB Master Interface Signals P5 PLB_ABus[0 : C_SPLB_AWIDTH-1] PLB I - PLB address bus PLB primary address valid P6 PLB_PAValid PLB I - indicator PLB_masterID[0 : P7 PLB I - PLB current master identifier C_SPLB_MID_WIDTH - 1] P8 PLB_RNW PLB I - PLB read not write P9 PLB_BE[0 : [C_SPLB_DWIDTH/8] - 1] PLB I - PLB byte enables P10 PLB_size[0 : 3] PLB I - PLB transfer size P11 PLB_type[0 : 2] PLB I - PLB transfer type P12 PLB_wrDBus[0 : C_SPLB_DWIDTH - 1] PLB I - PLB write data bus Unused PLB Master Interface Signals P13 PLB_UABus[0 : 31] PLB I - PLB upper address bits P14 PLB_SAValid PLB I - PLB secondary address valid PLB secondary to primary read P15 PLB_rdPrim PLB I - request indicator PLB secondary to primary write P16 PLB_wrPrim PLB I - request indicator P17 PLB_abort PLB I - PLB abort bus request P18 PLB_busLock PLB I - PLB bus lock P19 PLB_MSize[0 : 1] PLB I - PLB data bus width indicator P20 PLB_TAttribute[0 : 15] PLB I - PLB transfer attribute P21 PLB_lockerr PLB I - PLB lock error P22 PLB_wrBurst PLB I - PLB burst write transfer P23 PLB_rdBurst PLB I - PLB burst read transfer P24 PLB_wrPendReq PLB I - PLB pending bus write request 4 www.xilinx.com DS577 September 16, 2009 Product Specification XPS 16550 UART (v3.00a) Table 1: XPS 16550 UART I/O Signals (Contd) Initial Port Signal Name Interface I/O Description State P25 PLB_rdPendReq PLB I - PLB pending bus read request PLB pending read request P26 PLB_rdPendPri[0 : 1] PLB I - priority PLB pending write request P27 PLB_wrPendPri[0 : 1] PLB I - priority P28 PLB_reqPri[0 : 1] PLB I - PLB current request priority PLB Slave Interface Signals P29 Sl_addrAck PLB O 0 Slave address acknowledge P30 Sl_SSize[0 : 1] PLB O 0 Slave data bus size P31 Sl_wait PLB O 0 Slave wait indicator P32 Sl_rearbitrate PLB O 0 Slave rearbitrate bus indicator P33 Sl_wrDack PLB O 0 Slave write data acknowledge Slave write transfer complete P34 Sl_wrComp PLB O 0 indicator P35 Sl_rdBus[0 : C_SPLB_DWIDTH-1] PLB O 0 Slave read data bus P36 Sl_rdDack PLB O 0 Slave read data acknowledge Slave read transfer complete P37 Sl_rdComp PLB O 0 indicator Sl_MBusy[0 : P38 PLB O 0 Slave busy indicator C_SPLB_NUM_MASTERS - 1] Sl_MWrErr[0 : P39 PLB O 0 Slave write error indicator C_SPLB_NUM_MASTERS - 1] Sl_MRdErr[0 : P40 PLB O 0 Slave read error indicator C_SPLB_NUM_MASTERS - 1] Unused PLB Slave Interface Signals Slave terminate write burst P41 Sl_wrBTerm PLB O 0 transfer P42 Sl_rdWdAddr[0 : 3] PLB O 0 Slave read word address Slave terminate read burst P43 Sl_rdBTerm PLB O 0 transfer Sl_MIRQ[0 : P44 PLB O 0 Master interrupt request C_SPLB_NUM_MASTERS - 1] UART Signals 16 x clock signal from the P45 baudoutN Serial O 1 transmitter section of the UART Receiver 16x clock (Optional, may be driven externally under P46 rclk Serial I - control of the C_HAS_EXTERNAL_RCLK parameter) P47 sin Serial I - Serial data input P48 sout Serial O 1 Serial data output DS577 September 16, 2009 www.xilinx.com 5 Product Specification XPS 16550 UART (v3.00a) Table 1: XPS 16550 UART I/O Signals (Contd) Initial Port Signal Name Interface I/O Description State Baud rate generator reference clock (Optional, may be driven P49 xin Serial I - externally under control of the C_HAS_EXTERNAL_XIN parameter) If C_HAS_EXTERNAL_XIN = 0, xout will be 0, if C_HAS_EXTERNAL_XIN = 1 P50 xout Serial O - xout can be used as Baud rate generator reference feedback clock Clear to send (active low). When low, this indicates that P51 ctsN Modem I - the MODEM or data set is ready to exchange data.
Recommended publications
  • Configurable RISC-V Softcore Processor for FPGA Implementation

    Configurable RISC-V Softcore Processor for FPGA Implementation

    1 Configurable RISC-V softcore processor for FPGA implementation Joao˜ Filipe Monteiro Rodrigues, Instituto Superior Tecnico,´ Universidade de Lisboa Abstract—Over the past years, the processor market has and development of several programming tools. The RISC-V been dominated by proprietary architectures that implement Foundation controls the RISC-V evolution, and its members instruction sets that require licensing and the payment of fees to are responsible for promoting the adoption of RISC-V and receive permission so they can be used. ARM is an example of one of those companies that sell its microarchitectures to participating in the development of the new ISA. In the list of the manufactures so they can implement them into their own members are big companies like Google, NVIDIA, Western products, and it does not allow the use of its instruction set Digital, Samsung, or Qualcomm. (ISA) in other implementations without licensing. The RISC-V The main goal of this work is the development of a RISC- instruction set appeared proposing the hardware and software V softcore processor to be implemented in an FPGA, using development without costs, through the creation of an open- source ISA. This way, it is possible that any project that im- a non-RISC-V core as the base of this architecture. The plements the RISC-V ISA can be made available open-source or proposed solution is focused on solving the problems and even implemented in commercial products. However, the RISC- limitations identified in the other RISC-V cores that were V solutions that have been developed do not present the needed analyzed in this thesis, especially in terms of the adaptability requirements so they can be included in projects, especially the and flexibility, allowing future modifications according to the research projects, because they offer poor documentation, and their performances are not suitable.
  • DAN189 EXAR UARTS in GPS APPLICATIONS March 2007 EXAR UARTS in GPS APPLICATIONS

    DAN189 EXAR UARTS in GPS APPLICATIONS March 2007 EXAR UARTS in GPS APPLICATIONS

    DAN189 EXAR UARTS IN GPS APPLICATIONS March 2007 EXAR UARTS IN GPS APPLICATIONS 1.0 INTRODUCTION This application note describes where an Exar UART can be used in a Global Positioning System (GPS) application. GPS has traditionally been used in military applications such as marine navigation, aircraft navigation, and weapon’s guidance. However, GPS applications have recently expanded to industrial and consumer applications such as vehicle navigation systems, fleet management, and personal navigation. In these applications, the Exar UART can be used in the GPS receiver and in the GPS application. FIGURE 1. GPS APPLICATION EXAMPLES GPS Applications Marine Navigation System Aircraft Navigation System Vehicle Navigation System Fleet Management System Personal Navigation System GPS Receiver TX RX UART RX TX UART 1.1 GPS Receiver A GPS receiver typically includes the following: • RF block for receiving the GPS data and converting it to digital data • Microprocessor for processing the data • ROM to store the firmware for processing the data • RAM used by the microprocessor for data processing • UART to send data to the GPS application The figure below shows a block diagram of a GPS receiver. FIGURE 2. GPS RECEIVER BLOCK DIAGRAM ROM RAM RF Block TX Microprocessor UART RX 1 DAN189 EXAR UARTS IN GPS APPLICATIONS The figure below shows a block diagram of an automobile GPS navigation system: FIGURE 3. AUTOMOBILE GPS NAVIGATION SYSTEM EXAMPLE Keypad ROM RAM Radio CD RX GPS UART Microprocessor DVD TX LCD The UART that has been used in the GPS receiver or in the GPS application has typically been an industry standard 16550 UART or a UART that is available on the microprocessor.
  • Ds430 Opb 16550 Uart

    Ds430 Opb 16550 Uart

    0 OPB 16550 UART (v1.00d) DS430 December 2, 2005 0 0 Product Specification Introduction LogiCORE™ Facts This document provides the specification for the OPB Core Specifics 16550 UART (Universal Asynchronous QPro™-R Virtex™-II, QPro Receiver/Transmitter) Intellectual Property (IP). Virtex-II, Spartan™-II, Spartan-IIE, Supported Device Spartan-3, Spartan-3E, Virtex, The OPB 16550 UART described in this document has Family Virtex-II, Virtex-II Pro, Virtex-4, been designed incorporating features described in Virtex-E National Semiconductor PC16550D UART with FIFOs data Version of Core opb_uart16550 v1.00d sheet (June,1995),Discontinued (http://www.national.com/pf/PC/PC16550D.html). Resources Used The National Semiconductor PC16550D data sheet is Min Max referenced throughout this document and should be Slices 283 417 used as the authoritative specification. Differences LUTs 328 545 between the National Semiconductor implementation and the OPB 16550 UART Point Design implementation FFs 275 338 are highlighted and explained in Specification Block RAMs Exceptions. Provided with Core Features Documentation Product Specification • Hardware and software register compatible with all Design File Formats VHDL standard 16450 and 16550 UARTs Constraints File N/A • Implements all standard serial interface protocols Verification N/A - 5, 6, 7, or 8 bits per character Instantiation Template N/A - Odd, Even, or no parity detection and generation Reference Designs None - 1, 1.5, or 2 stop bit detection and generation Design Tool Requirements - Internal baud rate generator and separate receiver Xilinx Implementation ISE 6.1i or later clock input Tools - Modem control functions Verification ModelSim SE/EE 5.8e or later Simulation IPModelSim SE/EE 5.8e or later - False start bit detection and recovery - Prioritized transmit, receive, line status, and Synthesis XST modem control interrupts Support - Line break detection and generation Support provided by Xilinx, Inc.
  • Serial Communication Buses

    Serial Communication Buses

    Computer Architecture 10 Serial Communication Buses Made wi th OpenOffi ce.org 1 Serial Communication SendingSending datadata oneone bitbit atat oneone time,time, sequentiallysequentially SerialSerial vsvs parallelparallel communicationcommunication cable cost (or PCB space), synchronization, distance ! speed ? ImprovedImproved serialserial communicationcommunication technologytechnology allowsallows forfor transfertransfer atat higherhigher speedsspeeds andand isis dominatingdominating thethe modernmodern digitaldigital technology:technology: RS232, RS-485, I2C, SPI, 1-Wire, USB, FireWire, Ethernet, Fibre Channel, MIDI, Serial Attached SCSI, Serial ATA, PCI Express, etc. Made wi th OpenOffi ce.org 2 RS232, EIA232 TheThe ElectronicElectronic IndustriesIndustries AllianceAlliance (EIA)(EIA) standardstandard RS-232-CRS-232-C (1969)(1969) definition of physical layer (electrical signal characteristics: voltage levels, signaling rate, timing, short-circuit behavior, cable length, etc.) 25 or (more often) 9-pin connector serial transmission (bit-by-bit) asynchronous operation (no clock signal) truly bi-directional transfer (full-duplex) only limited power can be supplied to another device numerous handshake lines (seldom used) many protocols use RS232 (e.g. Modbus) Made wi th OpenOffi ce.org 3 Voltage Levels RS-232RS-232 standardstandard convertconvert TTL/CMOS-levelTTL/CMOS-level signalssignals intointo bipolarbipolar voltagevoltage levelslevels toto improveimprove noisenoise immunityimmunity andand supportsupport longlong cablecable lengthslengths TTL/CMOS → RS232: 0V = logic zero → +3V…+12V (SPACE) +5V (+3.3V) = logic one → −3V…−12V (MARK) Some equipment ignores the negative level and accepts a zero voltage level as the "OFF" state The "dead area" between +3V and -3V may vary, many receivers are sensitive to differentials of 1V or less Made wi th OpenOffi ce.org 4 Data frame CompleteComplete one-byteone-byte frameframe consistsconsists of:of: start-bit (SPACE), data bits (7, 8), stop-bits (MARK) e.g.
  • FPGA Architecture: Survey and Challenges Full Text Available At

    FPGA Architecture: Survey and Challenges Full Text Available At

    Full text available at: http://dx.doi.org/10.1561/1000000005 FPGA Architecture: Survey and Challenges Full text available at: http://dx.doi.org/10.1561/1000000005 FPGA Architecture: Survey and Challenges Ian Kuon University of Toronto Toronto, ON Canada [email protected] Russell Tessier University of Massachusetts Amherst, MA USA [email protected] Jonathan Rose University of Toronto Toronto, ON Canada [email protected] Boston – Delft Full text available at: http://dx.doi.org/10.1561/1000000005 Foundations and Trends R in Electronic Design Automation Published, sold and distributed by: now Publishers Inc. PO Box 1024 Hanover, MA 02339 USA Tel. +1-781-985-4510 www.nowpublishers.com [email protected] Outside North America: now Publishers Inc. PO Box 179 2600 AD Delft The Netherlands Tel. +31-6-51115274 The preferred citation for this publication is I. Kuon, R. Tessier and J. Rose, FPGA Architecture: Survey and Challenges, Foundations and Trends R in Elec- tronic Design Automation, vol 2, no 2, pp 135–253, 2007 ISBN: 978-1-60198-126-4 c 2008 I. Kuon, R. Tessier and J. Rose 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, mechanical, photocopying, recording or otherwise, without prior written permission of the publishers. Photocopying. In the USA: This journal is registered at the Copyright Clearance Cen- ter, Inc., 222 Rosewood Drive, Danvers, MA 01923. Authorization to photocopy items for internal or personal use, or the internal or personal use of specific clients, is granted by now Publishers Inc for users registered with the Copyright Clearance Center (CCC).
  • SCR1 SDK. Altera Arria-V Starter Kit Edition. Quick Start Guide

    SCR1 SDK. Altera Arria-V Starter Kit Edition. Quick Start Guide

    SCR1 SDK. Altera Arria-V Starter Kit Edition. Quick Start Guide © Syntacore, [email protected] Version 1.4, 2019-04-08 Table of Contents Revision History . 2 1. Setup equipment. 3 1.1. Prerequisites . 3 2. SDK HW assembly . 4 2.1. Connecting serial console . 4 2.2. Pins assignment. 4 3. Arria-V HW image update . 6 4. Booting the new FPGA image . 8 5. Resetting the board: . 9 6. UART connection settings . 9 7. Using UART terminal . 10 7.1. Load binary images to the Memory address . 10 7.2. Example: Dhrystone run from TCM memory . 12 7.3. Using OpenOCD. 13 7.3.1. Installing OpenOCD . 13 7.3.2. Starting the OpenOCD server. 13 7.3.3. Downloading and running an image using OpenOCD. 14 8. Building SDK FPGA-project for the Arria V GX SDK. 16 8.1. General structure of the SDK project. 16 8.2. Additional requirements for compilation . 16 8.3. Building SDK FPGA project. 17 8.3.1. FPGA firmware generation (sof-format) . 17 8.3.2. Converting FPGA-image to the board flash memory image (flash-format) . 17 8.3.3. SDK-specific pins assignment in FPGA-project . 19 8.4. SCR1 SDK FPGA-project functional description . 20 8.4.1. Common project structure . 20 8.4.2. Qsys SoC module structure. 20 8.4.3. Description of the blocks used in the SDK project . 21 8.4.3.1. SCR1-core. 21 8.4.3.2. AXI bridge . 21 8.4.3.3. Opencores UART 16550 IP . 21 8.4.4.
  • Xilinx Vivado – „EDK” Embedded Development) 4

    Xilinx Vivado – „EDK” Embedded Development) 4

    EFOP-3.4.3-16-2016-00009 A fels őfokú oktatás min őségének és hozzáférhet őségének együttes javítása a Pannon Egyetemen EMBEDDED SYSTEM DEVELOPMENT (MISAM154R) Created by Zsolt Voroshazi, PhD [email protected] Updated: 02 March. 2020. 2. FPGAS & PLATFORMS Embedded Systems Topics covered 1. Introduction – Embedded Systems 2. FPGAs, Digilent ZyBo development platform 3. Embedded System - Firmware development environment (Xilinx Vivado – „EDK” Embedded Development) 4. Embedded System - Software development environment (Xilinx VITIS – „SDK”) 5. Embedded Base System Build (and Board Bring-Up) 6. Adding Peripherals (from IP database) to BSB 7. Adding Custom (=own) Peripherals to BSB 8. Design and Development of Complex IP cores and applications (e.g. camera/video/ audio controllers) 3 Further references • XILINX official website: http://www.xilinx.com • EE Journal – Electronic Engineering: http://www.eejournal.com/design/embedded • EE Times - News: http://www.eetimes.com/design/embedded 4 PLD & FPGA CIRCUITS General description PAST … • Before ’80s, designing logic networks for digital circuits, modern development tools were not yet available as today. • The design of high complexity (multi I/O) logical combination and sequential networks was therefore slow and cumbersome, often coupled with paper- based design, multiple manual checks, and calculations. • We could not talk about advanced design and simulation tools (CAD) either, so there was a high probability of error in a prototype design. 6 … AND PRESENT • Today, all of these are available in an automated way (EDA - Electronic Design Automation), which, in addition to the use of Programmable Logic Devices (PLD), is relatively fast for both Printed Circuit Boards (PCB) and Application-specific Integrated Circuits and Processors (ASIC / ASSP).
  • Low-Profile PCI Cards: a New Approach to Inner Space • Lavalanche Winners! • Distributor Profile Lava I/O News

    Low-Profile PCI Cards: a New Approach to Inner Space • Lavalanche Winners! • Distributor Profile Lava I/O News

    April 2002 Vol.4 No.4 Inside this issue: • Low-profile PCI cards: A New Approach to Inner Space • Lavalanche Winners! • Distributor profile Lava I/O News Low-Profile PCI Cards: A New Approach to Inner Space Most of us remember our first impression on looking inside the chassis of a desktop or tower computer: is that all there is? Apart from the motherboard, power supply, drives and cables, a few cards, and dust bunnies, things were pretty empty in there. And while we knew that air had to circulate inside the case, the empty spaces inside still seemed a bit large. Notebook computers came along and really confirmed the impression that the inside of typical computers had enough extra space for a game of baseball. sets standards for the PCI bus generally. As well as defining a maximum height for Low-profile PCI cards follow the “PCI Local cards designated as “low-profile”, the low-pro- The reason for all the empty space is historical: Bus Specification, Revision 2.2” or later, but file PCI specification also outlines two low-pro- the original PC's expansion cards were loaded in addition adopt the form factor require- file PCI card lengths —short (called “MD1”) with lots of separate and large components. ments of the new "PCI Engineering Change and long (“MD2”).An MD1 low-profile card has They were rather tall, and needed to be so. Notice —Low Profile PCI Card". Designed as a a maximum length of 4.72" (119.91 mm). An However, as integrated circuit technology collaborative effort by the PCI Special Interest MD2 card is longer than an MD1 card, but not advanced, expansion boards got smaller and Group and companies including IBM and longer than 6.6" (167.64 mm).
  • Z182 Com Port Appnote

    Z182 Com Port Appnote

    HIGH PERFORMANCE PC COMMUNICATION Zilog PORT USING THE Z182 MICROCONTROLLER HIGH PERFORMANCE PC COMMUNICATION PORT USING THE Z182 o meet the demands of high speed communications on the Information Superhighway, Zilog's Z182-based PC Communication Port "COMPORT.S™" software code provides the user with increased data buffering capabilities for faster communication between PCs T and modems. INTRODUCTION With the advent of the Information Superhighway, users will handle heavy traffic at only a sustained rate of 57.6 Kbps. be able to access information quickly and easily by means This factor, combined with limited CPU bandwidth (due to of PC/Modem communications. However, user-friendly complex operating systems), means users cannot take full operating systems, capable of processing large amounts advantage of the high throughput that today’s modems of data, become so performance intensive that data com- can accommodate. munication becomes a bottleneck. Although there have been many advances in modem and PC design, a satis- PC Week's labs (July 1992) analyzed the serial card factory solution to the PC/modem communication bottle- bottleneck issue and their tests showed that a standard neck has not been found. serial card could not reliably sustain data transfer over 19.2 Kbps. However, when using a 16550 UART loaded The PC/Modem communication bottleneck is caused by serial card, the user could expect 57.6 Kbps of reliable, the PC standard serial cards used to connect to the sustained data transfer. This is great for V.32bis, but what modems. Conventional serial cards were designed to about V.FAST and beyond? Serial Port Limitations If you look at a PC Standard Serial Card, you will find a 8250 quickly to interrupts in a multi-tasking system? The answer or 16450 UART as well as RS-232 line drivers.
  • XR20M1170 Data Sheet

    XR20M1170 Data Sheet

    XR20M1170 I2C/SPI UART WITH 64-BYTE FIFO JUNE 2019 REV. 1.1.2 GENERAL DESCRIPTION FEATURES 1.62 to 3.6 Volt operation The XR20M11701 is a high performance universal asynchronous receiver and transmitter (UART) with Selectable I2C/SPI interface 64 byte TX and RX FIFOs and a selectable I2C/SPI SPI clock frequency up to slave interface. The XR20M1170 operates from 1.62 to 3.63 volts. The enhanced features in the 18MHz at 3.3V XR20M1170 include a programmable fractional baud 16MHz at 2.5V rate generator, an 8X and 4X sampling rate that 8MHz at 1.8V allows for a maximum baud rate of 16Mbps at 3.3V. The standard features include 16 selectable TX and Full-featured UART RX FIFO trigger levels, automatic hardware (RTS/ Data rate of up to 16Mbps at 3.3V CTS) and software (Xon/Xoff) flow control, and a Data rate of up to 12.5Mbps at 2.5V complete modem interface. Onboard registers provide the user with operational status and data Data rate of up to 8Mbps at 1.8V error flags. An internal loopback capability allows Fractional baud rate generator system diagnostics. The XR20M1170 is available in Transmit and receive FIFOs of 64 bytes the 24-pin QFN, 16-pin QFN, 24-pin TSSOP and 16- 16 selectable TX and RX FIFO trigger levels pin TSSOP packages. Automatic hardware (RTS/CTS) flow control NOTE: 1 Covered by U.S. Patent #5,649,122 Automatic software (Xon/Xoff) flow control APPLICATIONS Halt and resume transmission control Portable appliances Automatic RS-485 half-duplex direction control output via RTS# Battery-operated devices Wireless Infrared (IrDA 1.0 and 1.1) encoder/ Cellular data devices decoder Factory automation and process controls Automatic sleep mode (< 15uA at 3.3V) General purpose I/Os Full modem interface Crystal oscillator (up to 24MHz) or external clock (up to 64MHz) input 24-QFN, 16-QFN, 24-TSSOP, 16-TSSOP packages FIGURE 1.
  • Stratix II Vs. Virtex-4 Power Comparison & Estimation Accuracy

    Stratix II Vs. Virtex-4 Power Comparison & Estimation Accuracy

    White Paper Stratix II vs. Virtex-4 Power Comparison & Estimation Accuracy Introduction This document compares power consumption and power estimation accuracy for Altera® Stratix® II FPGAs and Xilinx Virtex-4 FPGAs. The comparison addresses all components of power: core dynamic power, core static power, and I/O power. This document uses bench-measured results to compare actual dynamic power consumption. To compare power estimation accuracy, the analysis uses the vendor-recommended power estimation software tools. The summary of these comparisons are: Altera’s Quartus® II PowerPlay power analyzer tool is accurate (to within 20%), while Xilinx’s tools are significantly less accurate. Stratix II devices exhibit lower dynamic power than Virtex-4 devices, resulting in total device power that is equal. Having an accurate FPGA power estimate is important to avoid surprises late in the design and prototyping phase. Inaccurate estimates can be costly and cause design issues, including: board re-layout, changes to power-management circuitry, changes cooling solution, unreliable FPGA operation, undue heating of other components, and changes to the FPGA design. Furthermore, without accurate power estimates, it is impossible for the designer and FPGA CAD software to optimize design power. This white paper contains the following sections: Components of total device power Power estimation and measurement methodology Core dynamic power comparison – power tool accuracy and bench measurements Core Static power comparison I/O power comparison Total device power summary For competitive comparisons on performance and density between Stratix II and Virtex-4 devices, refer to the following white papers from the Altera web site: Stratix II vs.
  • Microprocessors and Microcontrollers (EE-231) Main Objectives

    Microprocessors and Microcontrollers (EE-231) Main Objectives

    Microprocessors and Microcontrollers (EE-231) Main Objectives • 16550 Communication Device • ADC and DAC interfacing 16550 Programmable Communications Interface • National Semiconductor Corp’s PC16550D is a programmable communications interface designed to connect to virtually any type of serial interface. • 16550 is a universal asynchronous receiver/transmitter (UART) fully compatible with Intel microprocessors. • 16550 operates at 0–1.5 M baud. – baud rate is bps (bits transferred per second) including start, stop, data, and parity • 16550 also includes a programmable baud rate generator and separate FIFOs for input and output data to ease the load on the microprocessor. • Each FIFO contains 16 bytes of storage. • The most common communications interface found in the PC and many modems. Asynchronous Serial Data • Asynchronous serial data are transmitted and received without a clock and in frames as shown in figure. – each frame contains a start bit, seven data bits, parity, and one stop bit • Most Internet services use 10 bits, but normally do not use parity. • instead, eight data bits are transferred, replacing parity with a data bit 16550 Functional Description • The device is available as a 40-pin DIP (dual in-line package) or as a 44-pin PLCC (plastic leadless chip carrier). • Two completely separate sections are responsible for data communications. – the receiver and the transmitter • Because each sections is independent, 16550 is able to function in simplex, half-duplex, or full-duplex modes. The pin-out of the 16550 UART. 16550 Functional Description • A major feature of the 16550 is its internal receiver and transmitter FIFO (first-in, first-out) memories. • Because each is 16 bytes deep, the UART requires attention from the processor only after receiving 16 bytes of data.