FlexRay Communications System Protocol Specification v2.1 Revision A

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "FlexRay Communications System Protocol Specification v2.1 Revision A"

Transcription

1 FlexRay Communications System Protocol Specification v2.1 Revision A

2 Disclaimer Disclaimer This document as released by the FlexRay Consortium is intended for the purpose of information only. The use of material contained in this document requires membership within the FlexRay Consortium or an agreement with the FlexRay Consortium. The FlexRay Consortium will not be liable for any unauthorized use of this Specification. Following the completion of the development of the FlexRay Communications System Specifications commercial exploitation licenses will be made available to End Users by way of an End User's License Agreement. Such licenses shall be contingent upon End Users granting reciprocal licenses to all Core Partners and non-assertions in favor of all Premium Associate Members, Associate Members and Development Members. All details and mechanisms concerning the bus guardian concept are defined in the FlexRay Bus Guardian Specifications. The FlexRay Communications System is currently specified for a baud rate of 10 Mbit/s. It may be extended to additional baud rates. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the publisher. The word FlexRay and the FlexRay logo are registered trademarks. Copyright FlexRay Consortium. All rights reserved. The Core Partners of the FlexRay Consortium are BMW AG, DaimlerChrysler AG, Freescale Halbleiter Deutschland GmbH, General Motors Corporation, Philips GmbH, Robert Bosch GmbH, and Volkswagen AG. Page 2 of 8

3 Introduction 1 Scope The scope of the errata sheet is to publish changes in the protocol specification between specification releases and to document the changes from one release to the next. The documented changes must have a technical impact. Typing and spelling errors are not covered in this sheet. Grammatical corrections are only covered if the change may have a technical impact. 2 References [PS05] FlexRay Communications System - Protocol Layer Specification, v2.1, FlexRay Consortium, May [PS05A] FlexRay Communications System - Protocol Layer Specification, v2.1 Revision A, FlexRay Consortium, December [EPL05A] FlexRay Communications System - Electrical Physical Layer Specification, v2.1 Revision A, FlexRay Consortium, December Notational Conventions In this document the same acronyms and abbreviations, notational conventions and SDL extensions are used as described and used in [PS05A]. The item numbering is organized in the following way: <version number>.<item number>[.<sub item number>] The version number will be increased after every publication of the errata sheet. The item number is a consecutive number inside a version starting with 1. The version and the item numbers of a published errata sheet will not change in later publications. Optional sub item numbers are used to document a complex change (e.g. more than one figure, table or paragraph was modified). The modifications belonging to one item have to be seen as a whole including all sub items. All entries in the errata sheet contain changes against the v2.1 revision A specification, not the specification as modified by previous errata. If an errata is modified by a later errata the original errata will remain in the document, but it will be marked as superseded by errata X.Y, which indicates the new errata. The new errata will be marked as This errata supersedes errata Y.M and Z.N. Page 3 of 8

4 4 Version History Revision Date Items Table 1: Version history. Page 4 of 8

5 Item 1.01 Synopsis: TxD shall be HIGH after CAS/MTS transmission Location: [PS05A] Figure 3-18 on page 72 Original: * (standby, ready) transmit frame on A (vtype, vtf) prepbitstream(vtf, zbitstream, zbitstreamlength); TRANSMIT_BIT_ STREAM TRANSMIT_FES DYNFRAME TRANSMIT_DTS STATFRAME, DYNFRAME transmit symbol on A (vtype) SYMBOL prepcasstream (zbit Stream, zbitstreamlength); SYMBOL zcodecmode? WAKEUP WUPDEC control on A (GO) WUP BITSTRB control on A (STANDBY), WUPDEC control on A (STANDBY), decoding halted on A WUP_ENCODING set TxEN to HIGH, BITSTRB control on A (GO), decoding started on A wait for CE start Page 5 of 8

6 Replaced by: * (standby, ready) transmit frame on A (vtype, vtf) transmit symbol on A (vtype) BITSTRB control on A (STANDBY), WUPDEC control on A (STANDBY), decoding halted on A STATFRAME, DYNFRAME prepbitstream(vtf, zbitstream, zbitstreamlength); SYMBOL prepcasstream (zbit Stream, zbitstreamlength); WUP TRANSMIT_BIT_ STREAM TRANSMIT_FES DYNFRAME TRANSMIT_DTS SYMBOL zcodecmode? WAKEUP WUPDEC control on A (GO) wait for CE start WUP_ENCODING set TxD to HIGH, set TxEN to HIGH, BITSTRB control on A (GO), decoding started on A Notes: This errata entry is also valid for the FlexRay Protocol specification v2.1. Page 6 of 8

7 Item 1.02 Synopsis: Configuration of pchannels Location: [PS05A] section Original: 1. the enumeration pchannels that indicates the channels to which the node is connected, Replaced by: 26. the enumeration pchannels that indicates the channels to which the node is connected. The configuration of channels supported by the device, pchannels, has a unique characteristic in that it may affect significant hardware details of the implementation. It is expected that dual channel devices need to be able to support single channel operation, and that single channel devices are configurable to work on either channel A or channel B. As a result, it is required that an implementation be able to configure pchannels, but the ability to configure this more than once while the CC is in the power on state (see section 2.1.1) is not required. This mechanism does not need to be available in POC:config. A device may not, however, allow this parameter to be modified in the POC:ready, POC:normal active, POC:normal passive, or POC:halt states, or in any of the states that are defined in the WAKEUP and STARTUP macros of the POC process. Notes: The item was moved in the numbered list in section from the first position (number 1) to the last position (number 26). This errata entry is also valid for the FlexRay Protocol specification v2.1 [PS05]. Page 7 of 8

8 8 Page 8 of 8