SNIP_CLASSIC_FR_SECTION_7_4_2_2_8_3_FrameIDFlexRay

7.4.2.2.8.3 FrameIDFlexRay The layout of the FrameID for a FlexRay bus is shown in Table 7.8. FrameID Byte 0 Bit 7 Bit 6 Bit 5 .. 4 Bit 3 Bits 2 .. 0 Byte 1 Byte 2 Channel B Channel A reserved Slot Valid Slot ID (Bits 10 .. 8) Slot ID (Bits 7 .. 0) Cycle Table 7.8: Layout of FlexRay FrameID [SWS_Mirror_00104] Upstream requirements: SRS_Mirror_00008 ⌈The width of the FrameIDFlexRay field shall be 3 bytes.⌋ [SWS_Mirror_00105] Upstream requirements: SRS_Mirror_00008 ⌈Bits 7 – 6 of Byte 0 of the FrameIDFlexRay shall contain the channel assignment of the reported FlexRay frame. Bit 7 shall be set to 1 if the reported FlexRay frame is available on channel B of the FlexRay controller, otherwise it shall be set to 0. Bit 6 shall be set to 1 if the reported FlexRay frame is available on channel A of the FlexRay controller, otherwise it shall be set to 0. A reported FlexRay frame is either assigned exclusively to channel A or B or to both channels.⌋ This layout of the channel assignment corresponds to the Fr_ChannelType reported by Mirror_ReportFlexRayFrame. [SWS_Mirror_00106] Upstream requirements: SRS_Mirror_00008 ⌈Bits 5 – 4 of Byte 0 of the FrameIDFlexRay are currently reserved. They shall always be set 0.⌋ [SWS_Mirror_00159] Upstream requirements: SRS_Mirror_00008 ⌈Bit 3 of Byte 0 of the FrameIDFlexRay shall contain a flag indicating whether the reported slot ID and cycle are valid (flag is 1) or unused (flag is 0). It shall only be set to 0 when an aggregated error of the FlexRay channels is reported independently of a source frame or transmission conflict. Otherwise it shall always be set to 1.⌋ [SWS_Mirror_00107] Upstream requirements: SRS_Mirror_00008 ⌈Bits 2 – 0 of Byte 0 and Byte 1 of the FrameIDFlexRay shall contain the slot ID of the reported FlexRay frame in network byte order (MSB first).⌋ [SWS_Mirror_00108] Upstream requirements: SRS_Mirror_00008 ⌈Byte 2 of the FrameIDFlexRay shall contain the cycle in which the reported FlexRay frame was sent or received.⌋ Please note: For received frames and for frames sent in the static segment, the cycle is always reliable. For frames sent in the dynamic segment, the actual cycle cannot be known in advance, because the frame might not be transmitted in the planned cycle.