BS EN 16603-50-52-2014 Space engineering SpaceWire Remote memory access protocol《航天工程 SpaceWire 远程存储访问协议》.pdf

《BS EN 16603-50-52-2014 Space engineering SpaceWire Remote memory access protocol《航天工程 SpaceWire 远程存储访问协议》.pdf》由会员分享，可在线阅读，更多相关《BS EN 16603-50-52-2014 Space engineering SpaceWire Remote memory access protocol《航天工程 SpaceWire 远程存储访问协议》.pdf（112页珍藏版）》请在麦多课文档分享上搜索。

1、BSI Standards PublicationBS EN 16603-50-52:2014Space engineering SpaceWire Remote memoryaccess protocolBS EN 16603-50-52:2014 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of EN16603-50-52:2014.The UK participation in its preparation was entrusted to TechnicalCommit

2、tee ACE/68, Space systems and operations.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. The British Standards In

3、stitution 2014. Published by BSI StandardsLimited 2014ISBN 978 0 580 84189 7ICS 49.140Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 30 September 2014.Amendments

4、issued since publicationDate Text affectedBS EN 16603-50-52:2014EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 16603-50-52 September 2014 ICS 49.140 English version Space engineering - SpaceWire - Remote memory access protocol Ingnierie spatiale - SpaceWire - protocole daccs distance la mmoire

5、 Raumfahrttechnik - SpaceWire - Protokoll zum ferngesteuerten Speicherzugriff This European Standard was approved by CEN on 1 March 2014. CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status

6、of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN and CENELEC member. This European Standard exists in three official versions (English, F

7、rench, German). A version in any other language made by translation under the responsibility of a CEN and CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions. CEN and CENELEC members are the national standards bodies and

8、 national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portug

9、al, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2014 CEN/CENELEC All rights of exploitation in any form and by any means reserved worldwide for CEN national Members and for CENELEC Members. Ref.

10、No. EN 16603-50-52:2014 EBS EN 16603-50-52:2014EN 16603-50-52:2014 (E) 2 Table of contents Foreword 7 1 Scope . 8 2 Normative references . 9 3 Terms, definitions and abbreviated terms 10 3.1 Terms defined in other standards . 10 3.2 Terms specific to the present standard . 10 3.3 Abbreviated terms.

11、10 3.4 Conventions 11 4 Principles 12 4.1 Remote Memory Access Protocol (RMAP) purpose 12 4.2 Guide to clause 5 12 4.3 RMAP operations 13 4.3.1 Introduction . 13 4.3.2 Write commands . 13 4.3.3 Read commands . 14 4.3.4 Read-modify-write . 14 5 Requirements 15 5.1 RMAP command and reply fields 15 5.1

12、.1 Target SpaceWire Address field 15 5.1.2 Target Logical Address field 15 5.1.3 Protocol Identifier field . 15 5.1.4 Instruction field 16 5.1.5 Key field 17 5.1.6 Reply Address field . 17 5.1.7 Initiator Logical Address field 19 5.1.8 Transaction Identifier field . 19 5.1.9 Extended Address field .

13、 19 5.1.10 Address field . 19 5.1.11 Data Length field . 20 BS EN 16603-50-52:2014EN 16603-50-52:2014 (E) 3 5.1.12 Header CRC field 20 5.1.13 Data field . 20 5.1.14 Mask field 20 5.1.15 Data CRC field 20 5.1.16 Reply SpaceWire Address field . 20 5.1.17 Status field 20 5.2 Cyclic Redundancy Code 21 5

14、.3 Write Command 23 5.3.1 Write command format 23 5.3.2 Write reply format 26 5.3.3 Write action . 28 5.4 Read Command . 39 5.4.1 Read command format 39 5.4.2 Read reply format . 41 5.4.3 Read action . 43 5.5 Read-Modify-Write Command. 52 5.5.1 Read-modify-write command format . 52 5.5.2 Read-modify

15、-write reply format . 56 5.5.3 Read-modify-write action. 59 5.6 Error and status codes 70 5.6.1 Error and status codes 70 5.7 Partial Implementations of RMAP . 72 5.7.1 Limited functionality nodes 72 5.7.2 Partial implementations . 72 5.8 RMAP conformance 73 5.8.1 Overview . 73 5.8.2 RMAP partial im

16、plementations 73 Annex A (informative) Example of RMAP CRC implementation 77 A.1 Overview 77 A.2 VHDL implementation of RMAP CRC . 77 A.3 C-code implementation of RMAP CRC . 79 A.4 RMAP CRC test patterns 81 Annex B (informative) Example Service Interface specification . 88 B.1 Overview 88 B.2 Write

17、Service 89 B.2.1 Initiator 89 B.2.2 WRITE.request . 89 BS EN 16603-50-52:2014EN 16603-50-52:2014 (E) 4 B.2.3 WRITE.confirmation 89 B.2.4 Target . 90 B.2.5 WRITE.authorisation.indication . 90 B.2.6 WRITE.authorisation.response . 91 B.2.7 WRITE.data.indication 91 B.2.8 WRITE.data.response . 92 B.2.9 W

18、RITE.indication 92 B.3 Read Service 93 B.3.1 Initiator 93 B.3.2 READ.request . 93 B.3.3 READ.confirmation 93 B.3.4 Target . 94 B.3.5 READ.authorisation.indication . 94 B.3.6 READ.authorisation.response . 95 B.3.7 READ.data.indication 95 B.3.8 READ.data.response 96 B.3.9 READ.indication 96 B.4 Read-M

19、odify-Write Service . 97 B.4.1 Initiator 97 B.4.2 RMW.request 97 B.4.3 RMW.confirmation. 97 B.4.4 Target . 98 B.4.5 RMW.authorisation.indication 98 B.4.6 RMW.authorisation.response 99 B.4.7 RMW.read.data.indication . 99 B.4.8 RMW.read.data.response . 100 B.4.9 RMW.write.data.indication . 100 B.4.10

20、RMW.write.data.response . 101 B.4.11 RMW.indication . 102 Annex C (informative) Mapping to CCSDS SOIS Remote memory access service 103 Bibliography . 108 Figures Figure 5-1: Write Command format 23 Figure 5-2: Write Reply format 26 Figure 5-3: Write Command/Reply sequence . 28 BS EN 16603-50-52:2014

21、EN 16603-50-52:2014 (E) 5 Figure 5-4: Write Command Header Error 30 Figure 5-5: Write Data Authorisation Rejection . 32 Figure 5-6: Write Command Data Error 35 Figure 5-7: Write Reply Error 38 Figure 5-8: Read Command format 39 Figure 5-9: Read Reply format . 41 Figure 5-10: Read Command/Reply seque

22、nce . 44 Figure 5-11: Read Command Header Error 46 Figure 5-12: Read Authorisation Rejection . 49 Figure 5-13: Read Reply Header Error . 51 Figure 5-14: Read Reply Data Error . 52 Figure 5-15: Read-Modify-Write Command format . 53 Figure 5-16: Example Operation of Read-Modify-Write Command . 56 Figu

23、re 5-17: Read-Modify-Write Reply format 57 Figure 5-18: Read-Modify-Write Command/Reply sequence 59 Figure 5-19: Read-Modify-Write Command Header Error . 61 Figure 5-20: Read-Modify-Write Command Data Error . 64 Figure 5-21: Read-Modify-Write Authorisation Rejection 66 Figure 5-22: Read-Modify-Write

24、 Reply Error . 68 Figure 5-23: RMW Reply Data Error . 69 Figure B-1 : SOIS communication architecture . 88 Figure C-1 : RMAP model 103 Figure C-2 : SOIS model 104 Tables Table 5-1: RMAP Command Codes . 16 Table 5-2: Reply Address field size 18 Table 5-3: Example Reply Address field to Reply SpaceWir

25、e Address mappings . 18 Table 5-4: Error and Status codes 71 Table 5-5: SpaceWire RMAP write command . 74 Table 5-6: Example of Write Command Product Characteristics 74 Table 5-7: SpaceWire RMAP Read Command . 75 Table 5-8: Example Read Command Product Characteristics 75 Table 5-9: SpaceWire RMAP Re

26、ad-Modify-Write Command 76 Table 5-10: Example Read-Modify-Write Command Product Characteristics . 76 BS EN 16603-50-52:2014EN 16603-50-52:2014 (E) 6 Table C-1 : Comparison of RMAP and Remote Memory Access primitives 105 Table C-2 : WRITE.request parameters . 106 Table C-3 : WRITE.confirmation param

27、eters 106 Table C-4 : READ.request parameters . 106 Table C-5 : READ.confirmation parameters 106 Table C-6 : RMW.request parameters 107 Table C-7 : RMW.confirmation parameters . 107 BS EN 16603-50-52:2014EN 16603-50-52:2014 (E) 7 Foreword This document (EN 16603-50-52:2014) has been prepared by Tech

28、nical Committee CEN/CLC/TC 5 “Space”, the secretariat of which is held by DIN. This standard (EN 16603-50-52:2014) originates from ECSS-E-ST-50-52C. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by

29、 March 2015, and conflicting national standards shall be withdrawn at the latest by March 2015. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN and/or CENELEC shall not be held responsible for identifying any or all such paten

30、t rights. This document has been prepared under a mandate given to CEN by the European Commission and the European Free Trade Association. This document has been developed to cover specifically space systems and has therefore precedence over any EN covering the same scope but with a wider domain of

31、applicability (e.g. : aerospace). According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav

32、Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. BS EN 16603-50-52:2014EN 16603-50-52:2014 (E) 8 1 Sco

33、pe There is a number of communication protocols that can be used in conjunction with the SpaceWire Standard (ECSS-E-ST-50-12), to provide a comprehensive set of services for onboard user applications. To distinguish between the various protocols a protocol identifier is used, as specified in ECSS-E-

34、ST-50-51. This Standard specifies the Remote Memory Access protocol (RMAP), which is one of these protocols that works over SpaceWire. The aim of RMAP is to support reading from and writing to memory in a remote SpaceWire node. RMAP can be used to configure a SpaceWire network, control SpaceWire nod

35、es, and to transfer data to and from SpaceWire nodes. RMAP is specified in this Standard. This standard may be tailored for the specific characteristic and constrains of a space project in conformance with ECSS-S-ST-00. BS EN 16603-50-52:2014EN 16603-50-52:2014 (E) 9 2 Normative references The follo

36、wing normative documents contain provisions which, through reference in this text, constitute provisions of this ECSS Standard. For dated references, subsequent amendments to, or revision of any of these publications do not apply. However, parties to agreements based on this ECSS Standard are encour

37、aged to investigate the possibility of applying the more recent editions of the normative documents indicated below. For undated references, the latest edition of the publication referred to applies. EN reference Reference in text Title EN 16601-00-01 ECSS-S-ST-00-01 ECSS system - Glossary of terms

38、EN 16603-50-12 ECSS-E-ST-50-12 Space engineering - SpaceWire - Links, nodes, routers and networks EN 16603-50-51 ECSS-E-ST-50-51 Space engineering - SpaceWire protocol identification BS EN 16603-50-52:2014EN 16603-50-52:2014 (E) 10 3 Terms, definitions and abbreviated terms 3.1 Terms defined in othe

39、r standards For the purpose of this Standard, the terms and definitions from ECSS-S-ST-00-01 and ECSS-E-ST-50-51 apply. 3.2 Terms specific to the present standard None. 3.3 Abbreviated terms The following abbreviations are defined and used within this standard: Abbreviation Meaning CRC cyclic redund

40、ancy code EEP error end of packet EOP end of packet FCT flow control token FIFO first in first out ID identifier inc increment Len length LS least-significant LSB least-significant bit MS most-significant MSB most-significant bit RMAP remote memory access protocol RMW read-modify-write SOIS spacecra

41、ft onboard interface services SpW SpaceWire SSNSAP source subnetwork service access point BS EN 16603-50-52:2014EN 16603-50-52:2014 (E) 11 VHDL vhsic hardware description language VHSIC very high speed integrated circuit 3.4 Conventions In this document hexadecimal numbers are written with the prefi

42、x 0x, for example 0x34 and 0xDF15. Binary numbers are written with the prefix 0b, for example 0b01001100 and 0b01. Decimal numbers have no prefix. BS EN 16603-50-52:2014EN 16603-50-52:2014 (E) 12 4 Principles 4.1 Remote Memory Access Protocol (RMAP) purpose The aim of RMAP is to support reading from

43、 and writing to memory in a remote SpaceWire node. RMAP can be used to configure a SpaceWire network, control SpaceWire nodes, and to transfer data to and from SpaceWire nodes. RMAP is specified in this Standard. The remote memory access protocol (RMAP) has been designed to support a wide range of S

44、paceWire applications. Its primary purposes however are to configure a SpaceWire network, to control SpaceWire nodes and to gather data and status information from those nodes. RMAP can operate alongside other communication protocols running over SpaceWire. RMAP can be used to configure SpaceWire ro

45、uting switches, setting their operating parameters and routing table information. It can also be used to monitor the status of those routing switches. RMAP can be used to configure and read the status of nodes on the SpaceWire network. For example, the operating data rate of a node can be set to 100

46、 Mbits/s and the interface can be set to auto-start mode. RMAP can also be used to download and debug software on a remote processor. For simple SpaceWire units without an embedded processor, RMAP can be used to set application configuration registers, to read status information and to read from or

47、write data to memory in the unit. For intelligent SpaceWire units RMAP can provide the basis for a wide range of communication services. Configuration, status gathering and data transfer to and from memory or mailboxes can be supported. 4.2 Guide to clause 5 Specification of the fields used in RMAP

48、commands and replies is given in clause 5. The CRC used by RMAP is specified in clause 5.2. The write command is defined in clause 5.3, the read command in clause 5.4 and the read-modify-write command in clause 5.5. The error codes that are used in RMAP replies are listed in clause 5.6. The way in w

49、hich partial implementations of RMAP can be implemented is described in clause 5.7. Clause 5.8 specifies the conformance statements i.e. clauses that are implemented and the ancillary information that is provided, in order for a supplier to claim conformance to the SpaceWire RMAP standard. Example VHDL and C-code for the 8-bit CRC used by RMAP is given in Annex A. BS EN 16603-50-52:2014EN 16603-50-52:2014 (E) 13 4.3 RMAP operations 4.3.1 Introduction RMAP is used to write to and read from memory, registers, FIFO memory, mailboxes, etc, in a target on a SpaceWire network. Inpu