St. Petersburg State University of Aerospace Instrumentation Institute of High-Performance Computer and Network Technologies

Similar documents
1 CONTROL CHARACTERS AND CONTROL CODES

Reducing SpaceWire Time-code Jitter

SpaceWire ECSS-E50-12A International SpaceWire Seminar (ISWS 2003)

SpaceWire 101. Webex Seminar. February 15th, 2006

The Operation and Uses of the SpaceWire Time-Code International SpaceWire Seminar 2003

Improvements to the Distributed Interrupts Scheme

Space engineering. SpaceWire Protocols

Test and Verification of SpaceWire Developments and VLSI Implementations.

SpaceWire Standard Problems and Evolution Lines. Experience of implementation and application

Implimentation of SpaceWire Standard in SpaceWire CODEC using VHDL

Second revision of STP-ISS Transport. Protocol for Spacecraft On-board Networks

SpaceWire Link Interface RTL Verification

6 Remote memory access protocol (normative)

Space engineering. SpaceWire Links, nodes, routers and networks. ECSS-E-ST-50-12C 31 July 2008

CHAPTER 11 INTERRUPTS PROGRAMMING

Analysis of the Transport Protocol Requirements for the SpaceWire On-board Networks of Spacecrafts

SpaceWire RMAP Protocol

These three counters can be programmed for either binary or BCD count.

Aeroflex Colorado Springs Application Note

Page 1 SPACEWIRE SEMINAR 4/5 NOVEMBER 2003 JF COLDEFY / C HONVAULT

SoCWire: a SpaceWire inspired fault tolerant Network on Chip approach for reconfigurable System-on-Chip in Space applications

Scheduling Mechanisms for SpaceWire Networks

SpaceWire Router Data Sheet

Research and Analysis of Flow Control Mechanism for Transport Protocols of the SpaceWire Onboard Networks

The SpaceWire CODEC International SpaceWire Seminar (ISWS 2003) 4-5 November 2003, ESTEC Noordwijk, The Netherlands

GAISLER. SpaceWire CODEC with RMAP GRSPW / GRSPW-FT CompanionCore Data Sheet

STUDY, DESIGN AND SIMULATION OF FPGA BASED USB 2.0 DEVICE CONTROLLER

8051 Serial Communication

MCS-51 Serial Port A T 8 9 C 5 2 1

SAM-2 Letter Ballot comment HP 71 expressed a concern long held by the SAM-2/3 editor, to whit:

IEEE 1394 Link Core Specification

Section III. Transport and Communication

SpaceFibre Specification Draft F3

Embedded Systems Programming

e-pg Pathshala Subject : Computer Science Paper: Embedded System Module: Interrupt Handling Module No: CS/ES/13 Quadrant 1 e-text

STC101 PARALLEL ----v ... E. co Signals CD

CoE3DJ4 Digital Systems Design. Chapter 5: Serial Port Operation

BLE 1.4 SPI Driver Design Version 1.x (Draft)

Using UART in radio data transmission with the CDP-02 module By Tomihiko Uchikawa

spwr_base & spwr_chan

Lecture-12 INTERNAL ARCHITECTURE OF INTEL 8085: The Functional Block Diagram Of 8085 Is Shown In Fig 16.

Microcontroller Systems. ELET 3232 Topic 23: The I 2 C Bus

SCUBA-2 PCI Card DSP Code Overview

STUP. SpaceWire Protocol

4) In response to the the 8259A sets the highest priority ISR, bit and reset the corresponding IRR bit. The 8259A also places

TETRA MoU TTR Technical Ver Report July 2004

Communication Protocol Manual JOFRA CTC, ITC, MTC, ETC and Compact Copyright 2008 AMETEK Denmark A/S

Advanced Computer Networks. Rab Nawaz Jadoon DCS. Assistant Professor COMSATS University, Lahore Pakistan. Department of Computer Science

1 MALP ( ) Unit-1. (1) Draw and explain the internal architecture of 8085.

Standardizing Information and Communication Systems

SpaceWire-R DRAFT. SCDHA Issue September 2013

CHAPTER 4 DATA COMMUNICATION MODES

DEVICE DRIVERS AND TERRUPTS SERVICE MECHANISM Lesson-15: Writing Device Driving ISRs in a System

AMCP/5-WP/72 APPENDIX D (ENGLISH ONLY)

SCSI is often the best choice of bus for high-specification systems. It has many advantages over IDE, these include:

DELPHI CORPORATION. LIN to RS-232 Gateway Systems Analysis INterface Tool (SAINT) Users Guide

Architecture of 8085 microprocessor

Standardizing Information and Communication Systems

SpaceNet - SpaceWire-T. Initial Protocol Definition

Universal Serial Bus - USB 2.0

Computer Peripherals

SpaceWire RMAP Protocol

Fig.12.5 Serial Data Line during Serial Communication

SpaceWire-RT Project and Baseline Concepts

Ultrabeam RCU-06 USB port description

Module 3. Embedded Systems I/O. Version 2 EE IIT, Kharagpur 1

e-pg Pathshala Subject: Computer Science Paper: Embedded System Module: Interrupt Programming in Embedded C Module No: CS/ES/20 Quadrant 1 e-text

D3.2 SpaceWire-RT Updated Specification

The SPI supports data bus widths of 32 bits.

William Stallings Data and Computer Communications. Chapter 7 Data Link Control

Asynchronous Transmission. Asynchronous Serial Communications & UARTS

SpaceWire Remote Memory Access Protocol

DRAFT Date: May ECSS-E Space Engineering. SpaceWire: SERIAL POINT-TO-POINT LINKS DRAFT

Configuring Dial-on-Demand Routing

CSE 473 Introduction to Computer Networks. Midterm Exam Review

CHAPTER 5 REGISTER DESCRIPTIONS

INTERNATIONAL STANDARD

A. This Errata sheet represents the known bugs, anomalies and work-arounds for the ADuC812 MicroConverter.

Design Of Linux USB Device Driver For LPC2148 Based Data Acquisition System Including GSM.

The RS-485 user manual for B800 series communication

Remote Memory Access in Embedded Networked Systems

Request for Comments: 1139 January 1990

SC68C652B. 1. General description. 2. Features

TMS320C672x DSP Serial Peripheral Interface (SPI) Reference Guide

Chapter 13 Direct Memory Access and DMA-Controlled I/O

Figure 6 1 shows a block diagram of the UART core. shift register. shift register

Microprocessor Architecture

The SMCS332SpW and SMCS116SpW: Development Status

11 ASYNCHRONOUS SERIAL PORTS

GNOME485. Ethernet to RS485 converter Eas y to use. Security features. Virtual serial port. 2/16/2006 w w w. p a p o u c h.

DVB Interaction Channel through the Public switched Telecommunications System (PSTN) / Integrated Services Digital Network (ISDN)

Section 6.2, IP Routing. Section 6.4, IP/VPN Policy. Section 6.5, IP Quality of Service. Section 6.6, The BANDIT as Firewall

ROUTING CONSORTIUM TEST SUITE

Conto D1 MODBUS COMMUNICATION PROTOCOL

Embedded Systems and Software. Serial Communication

D3.1 - SpaceWire-RT SDL Simulation Validation Plan

An Interrupt is either a Hardware generated CALL (externally derived from a hardware signal)

1. Communication protocol on SPI

SpaceWire Network Performance Evaluation During the Streaming STP Data Transmition

Embedded Systems and Software

Transcription:

St. Petersburg State University of Aerospace Instrumentation Institute of High-Performance Computer and Network Technologies Extended Control Codes for Distributed Interrupts in SpaceWire Networks (draft 1.0) Yuriy Sheynin, Sergey Gorbachev Sheynin@online.ru 29 th of October, 2004 St. Petersburg

2 7.3 Control characters and control codes a. A control character shall be formed from a parity bit, a data-control flag and a two-bit control code with the data-control flag set to one to indicate that the current character is a control character. NOTE The different control characters are illustrated in Figure 16. Control characters P 1 0 0 FCT Flow control token P 1 P 1 0 1 1 0 EOP Normal end of packet EEP Error end of packet P 1 1 1 ESC Escape Control codes P 1 1 1 0 1 0 0 P 1 1 1 1 0 T0 T1 T2 T3 T4 T5 0 0 NULL P 1 1 1 1 0 I0 I1 I2 I3 I4 I5 0 1 P 1 1 1 1 0 I0 I1 I2 I3 I4 I5 1 0 LSB MSB Time-code Interrupt-code Pole-code Fig. 16: SpaceWire control characters and control codes b. The NULL control code shall be formed from ESC followed by the flow control token (FCT). NOTE 1 The parity bit in the middle of the control code is zero, in accordance with subclause 7.4 b.). NOTE 2 NULL is transmitted whenever a link is not sending data or control tokens, to keep the link active and to support link disconnect detection (see clause 8). c. The other three control codes (Time-Code, Interrupt-code and Pole-code) shall be formed from ESC followed by a single data character. NOTE The parity bit in the middle of this control codes is one, in accordance with subclause 7.4 b.). d. Six bits of time information shall be held in the least significant six bits of the Time-Code (T0-T5) and the two most significant bits (C6=0, C7=0) shall contain control flags that are distributed isochronously with the Time-Code.

3 NOTE The Time-Code is used to distribute system time information (see subclause 8.12) and control flags (C6=0, C7=0) isochronous with the time-code distribution. f. Six bits of interrupt information shall be held in the least significant six bits of the Interrupt-Code (I0-I5) and the two most significant bits (C6=0, C7=1) shall contain control flags that are distributed isochronously with the Interrupt-Code. NOTE The Interrupt-Codes is used to distribute interrupt request information from interrupt sources (see subclause 8.13) and control flags (C6=0, C7=1) isochronous with the interrupt-code distribution. g. Six bits of interrupt pole information shall be held in the least significant six bits of the Pole-Code (I0-I5) and the two most significant bits (C6=1, C7=0) shall contain control flags that are distributed isochronously with the Pole-Code. NOTE The Pole-Code is used to distribute interrupt pole information from interrupt handlers (see subclause 8.13) and control flags (C6=1, C7=0) isochronous with the pole-code distribution. 8.13. System interrupts distribution (normative) 8.13.1 General As defined in subclause 7.3, a interrupt control codes (Interrupt-Code and Poll-Code) comprises the ESC character followed by a single 8-bit data character. The data character contains two control flags (C6, C7) and a six-bit interrupt source identifier. 8.13.2 Handling a) Interrupt code represents an interrupt request. It shall be issued by a node that will be considered as the interrupt-master for this interrupt. b) One of 64 interrupt signals (interrupt source identifiers) could be identified by the Interrupt code. c) Any link controller shall manage the distribution of the interrupt request and poll information. d) Each node or router shall contain one 64-bit interrupt source register (ISR) for Interrupt codes distribution. e) The interrupt-master link interface shall have an INTR_IN input, which can be asserted by its host system the interrupt source. f) When the interrupt-master link interface receives an interrupt request (INTR_IN is asserted) with a six-bit interrupt source identifier, it shall set an appropriate bit to '1' in the 64-bit ISR. Then it shall send out an Interrupt-Code with the six-bit interrupt source identifier field of the data character and the other two bits set to the C6=0, C7=1 value of the control flags. g) The Interrupt-Code shall be sent out as soon as the current character or control code would be transmitted. However, the Time-code shall have priority for transmission over the Interrupt-code. h) Interrupt-Codes shall not be sent out until the link interface is in the Run state (see subclause 8.5).

4 i) When a link interface in a node or in a router receives an Interrupt-Code it shall check the correspondent bit in the 64-bit ISR to be reset to 0. If the bit is 0 then the link controller shall set the correspondent bit in the ISR to 1 and assert its INTR_OUT output signal at the link controller interface. It can be accompanied by the six-bit interrupt source identifier of the incoming Interrupt code. j) If the router or node receives an Interrupt-Code and the correspondent bit in the 64- bit ISR is equal to 1 the Interrupt-Code shall be ignored and the link interface should not issue the INTR_OUT output signal. NOTE. It prevents repeated Interrupt-Code propagation in a circular network. k) In a node, the INTR_OUT signal goes to the host, where it can be used as a hardware interrupt request. l) In a router the INTR_OUT signal propagates to all the links output ports of the router (except the port that have issued the INTR_OUT signal) so that they all emit the Interrupt-Code with the same control flags (C6=0, C7=1) and the same six-bit interrupt source identifier field of the data character, which was received by the router. m) An Interrupt-Code should be accepted for handling in some node of the SpaceWire interconnection. The node will be called the Interrupt Handler. n) In a node, which can be an Interrupt Handler, the link interface shall have a POLL_IN input, which can be asserted by its host system the interrupt handler, in response to an Interrupt-Code receipt. o) When the link interface receives an Interrupt poll (POLL_IN asserted) with a six-bit interrupt source identifier it shall reset appropriate bit in the 64-bit ISR to '0' and then send out a Poll-Code with the six-bit interrupt source identifier field of the data character. The other two bits shall be set to the value of the control flags C6=1, C7=0. p) The Poll-Code shall be sent out as soon as the current character or control code is transmitted. The Time-code shall have priority for transmission over the Poll-Code. The Poll-Code shall have priority for transmission over an Interrupt-Code. q) Poll-Codes shall not be sent out until a link interface is in the Run state (see subclause 8.5). r) When a link controller in a node or in a router receives a Poll-Code it shall check the correspondent bit in the 64-bit ISR to be set to 1. If the bit is 1 then the link controller shall reset it to 0. s) If the node was the source of the Interrupt-Code, for which the received Poll-code is the reply, the link interface shall assert its Poll_OUT output signal at the link controller interface. It can be accompanied by the six-bit interrupt source identifier from the incoming Poll-Code. t) In a router the Poll_OUT signal propagates to all the links output ports of the router (except the port that have issued the Poll_OUT signal) so that they all emit the Poll- Code with the same control flags (C6=1, C7=0) and the same six-bit interrupt source identifier field of the data character, which was received by the router.

5 u) If a router or a node receives a Poll-Code and the correspondent bit in the 64-bit ISR is equal to 0 the Poll-Code shall be ignored and the link interface should not issue the Poll_OUT output signal. NOTE. It prevents repeated Poll-Code propagation in a circular network.