ROBERT BOSCH GMBH, MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
ROBERT BOSCH GMBH, RESERVES THE RIGHT TO MAKE CHANGES WITHOUT
FURTHER NOTICE TO THE PRODUCTS DESCRIBED HEREIN. ROBERT BOSCH GMBH
DOES NOT ASSUME ANY LIABILITY ARISING OUT OF THE APPLICATION OR USE OF
ANY PRODUCT OR CIRCUIT DESCRIBED HEREIN.
Bus guardian related pins eray_arm, eray_bgt,
eray_mt, eray_bge1, and eray_bge2 have no function
PRTC1: Configuration parameter CASM[6:0] added
WRHS1: Bit NME changed to PPIT
RDHS1: Bit NME changed to PPIT
Pin eray_scanmode for scan mode control added
TABB added
SIR: Flag SDS added
EILS: Control bits CCLL, EFAL, IIBAL, IOBAL,
TABAL, TABBL added
SILS: Control bit SDSL added
-8/165-
15.12.2006
User’s Manual
Revision 1.2.5 E-Ray
EIES: Control bits CCLE, EFAE, IIBAE, IOBAE,
TABAE, TABBE added
EIER: Control bits CCLE, EFAE, IIBAE, IOBAE,
TABAE, TABBE added
SIES: Control bit SDSE added
SIER: Control bit SDSE added
SUCC2: LT[20:0] range modified
PRTC1: TSST[3:0] range modified, SPP[1:0] added,
configuration of BRP[1:0] for 1.25 MBit/s removed
PRTC2: RXL[5:0] range modified
MHDC: SLT[12:0] range modified
GTUC1: UT[19:0] range modified
GTUC2: MPC[13:0] range modified
GTUC3: Configuration parameterMTIO[5:0] replaced
by MIOA[6:0] and MIOB[6:0]
GTUC4: NIT[13:0] and OCS[13:0] range modified
GTUC5: DEC[7:0] range modified
GTUC7: SSL[9:0] range modified
GTUC8: NMS[12:0] range modified
GTUC9: APO[5:0] and DSI[1:0] range modified
GTUC10: MOC[13:0] range modified
GTUC11: Configuration parameter ECC[1:0] replaced
by EOCC[1:0] and ERCC[1:0]
OCV: OCV[18:0] range modified
SCV: SCCA[10:0], SCCB[10:0] range modified
ACS: Flags can only be reset
MRC: Configuration bits SEC[1:0] added
Register LDTS added
Bus guardian related pins eray_arm, eray_bgt,
eray_mt, eray_bge1, and eray_bge2 removed from
physical layer interface
Chapter 6. Restrictions removed. Description of timing
requirements for data transfers between Message RAM
and IBF / OBF moved to "Addendum to E-Ray
FlexRay IP-Module Specification Revision 1.1"
Revision 1.209.12.05C. HorstSection 3.2 renamed from "Interrupt Flag Interface" to
"Internal Signal and Flag Interface"
manual_about.fm
With this revision it is possible to use message buffer 1
for sync frame transmission in addition to message
buffer 0 if sync frames should have different payloads
on channel A and B
EIR: Handling of bits PERR and RFO same as for
other bits, bit MHF added
SIR: Bit RFF renamed to RFCL, handling of bits
RFNE, RFCL same as for other bits
EILS: Bit MHFL added
SILS: Bit RFFL renamed to RFCLL
EIES, EIER: Bit MHFE added
SIES, SIER: Bit RFFE renamed to RFCLE
-9/165-
15.12.2006
User’s Manual
Revision 1.2.5 E-Ray
Register STPW renamed to STPW1
STPW2: Register added
CCSV: Bits PSL[5:0] added
SWNIT: Bits MTSA, MTSB added
MRC: Bit SPLM added
FCL: Register added
FSR: Register added
MHDF: Register added
MBSC1/2/3/4: Naming of bits changed from MBS to
MBC to distinguish between message buffer status flag
(MBC) and message buffer status register (MBS)
CREL: Register added
ENDN: Register added
Message buffers in Message RAM:
Header 2 and 3updated from received dataframes only
MBS: Bits FTA, FTB, CCS[5:0], RCIS, SFIS, SYNS,
NFIS, PPIS, RESS added
Revision 1.2.117.03.06C. HorstAll changes to previous release are described in
detail in [5].
Revision 1.2.219.05.06C. HorstAll changes to previous release are described in
detail in [6].
Revision 1.2.315.08.06C. HorstAll changes to previous release are described in
detail in [7].
Revision 1.2.4Not published.
Revision 1.2.515.12.06C. HorstAll changes to previous release are described in
detail in [8], [9].
manual_about.fm
-10/165-
15.12.2006
User’s Manual
Revision 1.2.5 E-Ray
1.2 Conventions
The following conventions are used within this document:
Times boldNames of bits and signals
CAPITALSPOC states and CHI commands
1.3 Definitions
FlexRay Frame:Header Segment + Payload Segment
Message Buffer:Header Section + Data Section
Message RAM:Header Partition + Data Partition
Data Frame:FlexRay frame that is not a null frame
1.4 Scope
This document describes the E-Ray FlexRay IP-module and its features from the application programmer’s point of view. All information necessary to integrate the E-Ray module into an user-defined
ASIC is located in the Module Integration Guide. Information about a specific Customer CPU Interface can be found in the respective Customer CPU Interface Specification document.
1.5 References
This document refers to the following E-Ray release:
Revision 1.0.1
This document refers to the following documents:
RefAuthor(s)Title
[1]FlexRay GroupFlexRay Communication System Protocol Specification v2.1 (05/05/12)
[2]FlexRay GroupFlexRay Communication System Protocol Specification v2.1 Revision A
Errata Sheet Version 1 (06/03/29)
[3]FlexRay GroupFlexRay Data Link Layer Conformance Test Specification v2.1 (06/03/27)
[4]AE/EIPAddendum to E-Ray FlexRay IP-Module Specification Revision 1.2.2
[5]AE/EIPChanges E-Ray FlexRay IP-Module Specification v1.2 to v1.2.1
[6]AE/EIPChanges E-Ray FlexRay IP-Module Specification v1.2.1 to v1.2.2
manual_about.fm
[7]AE/EIPChanges E-Ray FlexRay IP-Module Specification v1.2.2 to v1.2.3
[8]AE/EIPChanges E-Ray FlexRay IP-Module Specification v1.2.3 to v1.2.4
[9]AE/EIPChanges E-Ray FlexRay IP-Module Specification v1.2.4 to v1.2.5
-11/165-
15.12.2006
User’s Manual
1.6 Terms and Abbreviations
This document uses the following terms and abbreviations:
TermMeaning
APAction Point
BDBus Driver
BSSByte Start Sequence
CASCollision Avoidance Symbol
CCCommunication Controller
CHIController Host Interface
CIFCustomer Interface Block
CRCCyclic Redundancy Check
FESFrame End Sequence
FSSFrame Start Sequence
Revision 1.2.5 E-Ray
FIFOFirst In First Out (message buffer structure)
FSMFinite State Machine
FSPFrame and Symbol Processing Block
FTMFault Tolerant Midpoint
GIFGeneric Interface Block
GTUGlobal Time Unit Block
IBFInput Buffer
INTInterrupt Control Block
MHDMessage Handler Block
MTMacrotick
MTSMedia Access Test Symbol
NCTNetwork Communication Time
NEMNetwork Management Block
NITNetwork Idle Time
manual_about.fm
NMNetwork Management
OBFOutput Buffer
POCProtocol Operation Control
PRTProtocol Controller Block
SDLSpecification and Description Language
SUCSystem Universal Control Block
TBFTransient Buffer
TDMATime Division Multiple Access (media access method)
The E-Ray module is a FlexRay IP-module that can be integrated as stand-alone device or as part of
an ASIC. It is described in VHDL on RTL level, prepared for synthesis. The E-Ray IP-module performs communication according to the FlexRay protocolspecification v2.1. With maximum specified
sample clock the bitrate is 10 MBit/s. Additional bus driver (BD) hardware is required for connection
to the physical layer.
For communication on a FlexRay network, individual message buffers with up to 254 data bytes are
configurable. The message storage consists of a single-ported Message RAM that holds up to 128
message buffers. All functions concerning the handling of messages are implemented in the Message
Handler. Those functions are the acceptance filtering, the transfer of messages between the two
FlexRay Channel Protocol Controllers and the Message RAM, maintaining the transmissionschedule
as well as providing message status information.
The register set of the E-Ray IP-module can be accessed directlyby an external Host via the module’s
Host interface. These registers are used to control/configure/monitor the FlexRay Channel Protocol
Controllers, Message Handler, Global Time Unit, System Universal Control, Frame and Symbol
Processing, Network Management, Interrupt Control, and to access the Message RAM via Input /
Output Buffer.
The E-Ray IP-module can be connected to a wide range of customer-specific Host CPUs via its
8/16/32-bit Generic CPU Interface.
The E-Ray IP-module supports the following features:
• Conformance with FlexRay protocol specification v2.1
• Data rates of up to 10 Mbit/s on each channel
• Up to 128 message buffers configurable
• 8 Kbyte of Message RAM for storage of e.g. 128 message buffers with max. 48 byte data section
or up to 30 message buffers with 254 byte data section
• Configuration of message buffers with different payload lengths possible
• One configurable receive FIFO
• Each message buffer can be configured as receive buffer, as transmit buffer
or as part of the receive FIFO
• Host access to message buffers via Input and Output Buffer
Input Buffer:Holds message to be transferred to the Message RAM
manual_overview.fm
Output Buffer:Holds message read from the Message RAM
• Filtering for slot counter, cycle counter, and channel
• Maskable module interrupts
• Network Management supported
• 8/16/32-bit Generic CPU Interface, connectable to a wide range of customer-specific Host CPUs
-14/165-
15.12.2006
2.1 Block Diagram
User’s Manual
Revision 1.2.5 E-Ray
Rx_A
Physical
Layer
Host
CPU
Figure 1: E-Ray block diagram
Tx_A
Control
Rx_B
Tx_B
Data
Addr
Control
Interrupt
PRT B
IBF
OBF
Generic CPU IF
Customer CPU IF
PRT A
TBF B
Message Handler
Message RAM
TBF A
GTU
SUC
FSP
NEM
INT
Customer CPU Interface (CIF)
Connects a customer specific Host CPU to the E-Ray IP-module via the Generic CPU Interface.
Generic CPU Interface (GIF)
The E-Ray IP-module is provided with an 8/16/32-bit Generic CPU Interface prepared for the connection to a wide range of customer-specific Host CPUs. Configuration registers, status registers, and
interrupt registers are attached to the respective blocks and can be accesssed via the Generic CPU Interface.
Input Buffer (IBF)
For write access to the message buffers configured in the Message RAM, the Host can write the header and data section for a specific message buffer to the Input Buffer. The Message Handler then transfers the data from the Input Buffer to the selected message buffer in the Message RAM.
manual_overview.fm
Output Buffer (OBF)
For read access to a message buffer configured in the Message RAM the Message Handler transfers
the selected message buffer to the Output Buffer. After the transfer has completed, the Host can read
the header and data section of the transferred message buffer from the Output Buffer.
Message Handler (MHD)
The E-Ray Message Handler controls data transfers between the following components:
• Input / Output Buffer and Message RAM
• Transient Buffer RAMs of the two FlexRay Protocol Controllers and Message RAM
-15/165-
15.12.2006
User’s Manual
Revision 1.2.5 E-Ray
Message RAM (MRAM)
The Message RAM consists of a single-ported RAM that stores up to 128 FlexRay message buffers
together with the related configuration data (header and data partition).
Transient Buffer RAM (TBF A/B)
Stores the data section of two complete messages.
FlexRay Channel Protocol Controller (PRT A/B)
The FlexRay Channel Protocol Controllers consist of shift register and FlexRay protocol FSM. They
are connected to the Transient Buffer RAMs for intermediatemessage storage and to thephysical layer via bus driver BD.
They perform the following functionality:
• Control and check of bit timing
• Reception / transmission of FlexRay frames and symbols
• Check of header CRC
• Generation / check of frame CRC
• Interfacing to bus driver
The FlexRay Channel Protocol Controllers have interfaces to:
• Physical Layer (bus driver)
• Transient Buffer RAM
• Message Handler
• Global Time Unit
• System Universal Control
• Frame and Symbol Processing
• Network Management
• Interrupt Control
Global Time Unit (GTU)
The Global Time Unit performs the following functions:
• Generation of microtick
• Generation of macrotick
• Fault tolerant clock synchronization by FTM algorithm
manual_overview.fm
- rate correction
- offset correction
• Cycle counter
• Timing control of static segment
• Timing control of dynamic segment (minislotting)
• Support of external clock correction
-16/165-
15.12.2006
User’s Manual
System Universal Control (SUC)
The System Universal Control controls the following functions:
• Configuration
• Wakeup
• Startup
• Normal Operation
• Passive Operation
• Monitor Mode
Frame and Symbol Processing (FSP)
The Frame and Symbol Processing controls the following functions:
• Checks the correct timing of frames and symbols
• Tests the syntactical and semantical correctness of received frames
• Sets the slot status flags
Network Management (NEM)
Revision 1.2.5 E-Ray
Handles the network management vector.
Interrupt Control (INT)
The Interrupt Controller performs the following functions:
• Provides error and status interrupt flags
• Enable / disable interrupt sources
• Assignment of interrupt sources to one of the two module interrupt lines
• Enable / disable module interrupt lines
• Manages the two interrupt timers
• Stop watch time capturing
manual_overview.fm
-17/165-
15.12.2006
User’s Manual
Revision 1.2.5 E-Ray
3. Generic Interface
The Generic Interface encapsulates the synthesizable code of the E-Ray design (E-Ray core).All customer specific components like Customer CPU Interfaces and RAM blocks are connected to the Generic Interface.
The Generic CPU Interface connects the E-Ray module to a customer specific Host CPU via the Customer CPU Interface. It supports 8/16/32-bit access modes.
manual_generic_if.fm
-18/165-
15.12.2006
User’s Manual
Revision 1.2.5 E-Ray
4. Programmer’s Model
4.1 Register Map
The E-Ray module allocates an address space of 2 Kbytes (0x0000 to 0x07FF). The registers are organized as 32-bit registers. 8/16-bit accesses are also supported. Host access to the Message RAM is
done via the Input and Output Buffers. They buffer data to be transferred to and from the Message
RAM under control of the Message Handler, avoiding conflicts between Host accesses and message
reception / transmission. Addresses 0x0000 to 0x000F are reserved for customer specific purposes.
All functions related to these addresses are located in the Customer CPU Interface.
The assignment of the message buffers is done according to the scheme shown in Table 1 below. The
number N of available message buffers depends on the payload length of the configured message
buffers. The maximum number of message buffers is 128. The maximum payload length supported is
254 bytes.
The message buffers are separated into three consecutive groups:
• Static + Dynamic Buffers - Transmit / receive buffers assigned to static or dynamic segment
• FIFO- Receive FIFO
The message buffer separation configuration can be changed only in DEFAULT_CONFIG or CON-
FIG state only by programming register MRC (see 4.7.1 Message RAM Configuration (MRC)).
The first group starts with message buffer0 andconsists of static message buffers only. Message buff-
er 0 is dedicated to hold the startup / sync frame or the single slot frame, if the node transmits one, as
configured by SUCC1.TXST, SUCC1.TXSY, and SUCC1.TSM. In addition, message buffer 1 may
be used for sync frame transmission in case that sync frames or single-slot frames should have different payloads on the two channels. In this case bit MRC.SPLM has to be programmed to ’1’ and message buffers 0 and 1 have to be configured with the key slot ID and can be (re)configured in
DEFAULT_CONFIG or CONFIG state only.
The second group consists of message buffers assigned to the static or to the dynamic segment. Message buffers belonging to this group may be reconfigured during run time from dynamic to static or
vice versa depending on the state of MRC.SEC[1:0].
The message buffers belonging to the third group are concatenated to a single receive FIFO.
The address space from 0x0000to 0x000F is reserved for customer-specificregisters. These registers,
if implemented, are located in the Customer CPU Interface block. A description can be found in the
specific Customer CPU Interface specification document.
manual_programmers_model.fm
-23/165-
15.12.2006
User’s Manual
Revision 1.2.5 E-Ray
4.3 Special Registers
4.3.1 Lock Register (LCK)
The Lock Register is write-only. Reading the register will return 0x0000 0000.
Bit31302928272625242322212019181716
LCKR0000000000000000
0x001C W
Reset0000000000000000
Bit 1514131211109876543210
R0000000000000000
WCLK7 CLK6 CLK5 CLK4 CLK3 CLK2 CLK1 CLK0
Reset0000000000000000
CLK[7:0]Configuration Lock Key
ToleaveCONFIGstatebywritingSUCC1.CMD[3:0](commandsREADY,
MONITOR_MODE, ATM, LOOP_BACK), the write operation has to be directly preceded by
two write accesses to the Configuration Lock Key (unlock sequence). If the write sequence
below is interrupted by other write accesses between the second write to the Configuration Lock
Key and the write access to the SUCC1 register, the CC remains in CONFIG state and the
sequence has to be repeated.
First write:LCK.CLK[7:0]= "1100 1110" (0xCE)
Second write: LCK.CLK[7:0]= "0011 0001" (0x31)
Third write:SUCC1.CMD[3:0]
Note: In case that the Host uses 8/16-bit accesses to write CLK[7:0], the programmer has to ensure
that no "dummy accesses" e.g. to the remaining register bytes / words are inserted by the compiler.
manual_programmers_model.fm
-24/165-
15.12.2006
User’s Manual
Revision 1.2.5 E-Ray
4.4 Interrupt Registers
4.4.1 Error Interrupt Register (EIR)
The flags are set when the CC detects one of the listed error conditions. The flags remain set until the
Host clears them.A flag is cleared by writing a ’1’ to the corresponding bit position. Writing a ’0’has
no effect on the flag. A hard reset will also clear the register.
Bit31302928272625242322212019181716
EIRR00000
0x0020 W
Reset0000000000000000
Bit 1514131211109876543210
R0000
W
Reset0000000000000000
TABB LTVB EDB
MHF IOBA IIBAEFARFOPERR CCLCCFSFO SFBM CNA PEMC
PEMCPOC Error Mode Changed
This flag is set whenever the error mode signalled by CCEV.ERRM[1:0] has changed.
1 = Error mode has changed
0 = Error mode has not changed
00000
TABA LTVA EDA
CNACommand Not Accepted
The flag signals that the write access to the CHI command vector SUCC1.CMD[3:0] was not
successful because the requested command was not valid in the actual POC state, or because the
CHI command was locked (CCL = ’1’).
1 = CHI command not accepted
0 = CHI command accepted
SFBMSync Frames Below Minimum
This flag signals that the number of sync frames received during the last communication cycle
was below the limit required by the FlexRay protocol. May be set during startup and therefore
should be cleared by the Host after the CC entered NORMAL_ACTIVE state.
1 = Less than the required minimum of sync frames received
0 = Sync node: 1 or more sync frames received, non-sync node: 2 or more sync frames received
SFOSync Frame Overflow
Set when either the number of sync frames received during the last communication cycle or the
total number of sync frames received during the last double cycle exceeds the maximum number
of sync frames as defined by GTUC2.SNM[3:0].
manual_programmers_model.fm
1 = More sync frames received than configured by GTUC2.SNM[3:0]
0 = Number of received sync frames ≤ GTUC2.SNM[3:0]
CCFClock Correction Failure
This flag is set at the end of the cycle whenever one of the following errors occurred:
• Missing offset and / or rate correction
• Clock correction limit reached
The clock correction status is monitored in registers CCEV and SFS. A failure may occur during
startup,thereforebitCCFshould be clearedbytheHostafter theCCentered
NORMAL_ACTIVE state.
The flag signals that the write access to the CHI command vector SUCC1.CMD[3:0] was not
successful because the execution of the previous CHI command has not yet completed. In this
case bit CNA is also set to ’1’.
1 = CHI command not accepted
0 = CHI command accepted
PERRParity Error
The flag signals a parity error to the Host. It is set whenever one of the flags MHDS.PIBF,
MHDS.POBF, MHDS.PMR, MHDS.PTBF1, MHDS.PTBF2 changes from ’0’ to ’1’.
The flag is set by the CC when a receive FIFO overrun is detected. When a receive FIFO overrun
occurs, the oldest message is overwritten with the actual received message. The actual state of
the FIFO is monitored in register FSR.
1 = A receive FIFO overrun has been detected
0 = No receive FIFO overrun detected
EFAEmpty FIFO Access
This flag is set by the CC when the Host requests the transfer of a message from the receive
FIFO via Output Buffer while the receive FIFO is empty.
1 = Host access to empty FIFO occurred
0 = No Host access to empty FIFO occurred
IIBAIllegal Input Buffer Access
This flag is set by the CC when the Host wants to modify a message buffer via Input Buffer
while the CC is not in CONFIG or DEFAULT_CONFIG state and one of the following conditions applies:
1) The Host writes to the Input Buffer Command Request register to modify the
• Header section of message buffer 0, 1 if configured for transmission in key slot
• Header section of static message buffers with buffer number < MRC.FDB[7:0]
while MRC.SEC[1:0] = "01"
• Header section of any static or dynamic message buffer while MRC.SEC[1:0] = "1x"
• Header and / or data section of any message buffer belonging to the receive FIFO
2) The Host writes to any register of the Input Buffer while IBCR.IBSYH is set to ’1’.
1 = Illegal Host access to Input Buffer occurred
0 = No illegal Host access to Input Buffer occurred
manual_programmers_model.fm
IOBAIllegal Output buffer Access
This flag is set by the CC when the Host requests the transfer of a message buffer from the Message RAM to the Output Buffer while OBCR.OBSYS is set to ’1’.
1 = Illegal Host access to Output Buffer occurred
0 = No illegal Host access to Output Buffer occurred
MHFMessage Handler Constraints Flag
The flag signals a Message Handler constraints violation condition. It is set whenever one of the
flagsMHDF.SNUA,MHDF.SNUB,MHDF.FNFA,MHDF.FNFB,MHDF.TBFA,MHDF.TBFB, MHDF.WAHP changes from ’0’ to ’1’.
Channel-specific error flags:
EDAError Detected on Channel A
This bit is set whenever one of the flags ACS.SEDA, ACS.CEDA, ACS.CIA, ACS.SBVA
changes from ’0’ to ’1’.
1 = Error detected on channel A
0 = No error detected on channel A
LTVALatest Transmit Violation Channel A
The flag signals a latest transmit violation on channel A to the Host.
1 = Latest transmit violation detected on channel A
0 = No latest transmit violation detected on channel A
TABATransmission Across Boundary Channel A
The flag signals to the Host that a transmission across a slot boundary occurred for channel A.
1 = Transmission across slot boundary detected on channel A
0 = No transmission across slot boundary detected on channel A
EDBError Detected on Channel B
This bit is set whenever one of the flags ACS.SEDB, ACS.CEDB, ACS.CIB, ACS.SBVB
changes from ’0’ to ’1’.
1 = Error detected on channel B
0 = No error detected on channel B
LTVBLatest Transmit Violation Channel B
The flag signals a latest transmit violation on channel B to the Host.
1 = Latest transmit violation detected on channel B
0 = No latest transmit violation detected on channel B
TABBTransmission Across Boundary Channel B
The flag signals to the Host that a transmission across a slot boundary occurred for channel B.
1 = Transmission across slot boundary detected on channel B
0 = No transmission across slot boundary detected on channel B
manual_programmers_model.fm
-27/165-
15.12.2006
User’s Manual
Revision 1.2.5 E-Ray
4.4.2 Status Interrupt Register (SIR)
The flags are set when the CC detects one of the listed events. The flags remain set until the Host
clears them. A flag is cleared by writing a ’1’ to the corresponding bit position. Writing a ’0’ has no
effect on the flag. A hard reset will also clear the register.
Bit31302928272625242322212019181716
SIRR000000
0x0024 W
Reset0000000000000000
Bit 1514131211109876543210
R
SDSMBSI SUCS SWE TOBC TIBCTI1TI0NMVC RFCL RFNERXITXICYCS CASWST
W
Reset0000000000000000
MTSB WUPB
000000
MTSA WUPA
WSTWakeup Status
This flag is set when the wakeup status vector CCSV.WSV[2:0] is changed by a protocol event.
1 = Wakeup status changed
0 = Wakeup status unchanged
CASCollision Avoidance Symbol
This flag is set by the CC during STARTUP state when a CAS or a potential CAS was received.
1 = Bit pattern matching the CAS symbol received
0 = No bit pattern matching the CAS symbol received
CYCSCycle Start Interrupt
This flag is set by the CC when a communication cycle starts.
1 = Communication cycle started
0 = No communication cycle started
TXITransmit Interrupt
This flag is set by the CC at the end of frame transmission if bit MBI in the respective message
buffer is set to ’1’ (see Table 17).
1 = At least one frame was transmitted from a transmit buffer with MBI = ’1’
0 = No frame transmitted from a transmit buffer with MBI = ’1’
RXIReceive Interrupt
This flag is set by the CC whenever the set condition of a message buffers ND flag is fulfilled
(see 4.8.6 New Data 1/2/3/4 (NDAT1/2/3/4)), and if bit MBI of that message buffer is set to ’1’
(see Table 17).
manual_programmers_model.fm
1 = At least one ND flag of a receive buffer with MBI = ’1’ has been set to ’1’
0 = No ND flag of a receive buffer with MBI = ’1’ has been set to ’1’
RFNEReceive FIFO Not Empty
This flag is set by the CC when a received valid frame was stored into the empty receive FIFO.
The actual state of the receive FIFO is monitored in register FSR.
1 = Receive FIFO is not empty
0 = Receive FIFO is empty
RFCLReceive FIFO Critical Level
This flag is set when the receive FIFO fill level FSR.RFFL[7:0] is equal or greater than the critical level as configured by FCL.CL[7:0].
This interrupt flag signals a change in the Network Management Vector visible to the Host.
1 = Network management vector changed
0 = No change in the network management vector
TI0Timer Interrupt 0
This flag is set whenever timer 0 matches the conditions configured in register T0C. A Timer
Interrupt 0 is also signalled on pin eray_tint0.
This flag is set whenever a transfer from Input Buffer to the Message RAM has completed and
IBCR.IBSYS has been reset by the Message Handler.
1 = Transfer between Input Buffer and Message RAM completed
0 = No transfer completed
TOBCTransfer Output Buffer Completed
This flag is set whenever a transfer from the Message RAM to the Output Buffer has completed
and OBCR.OBSYS has been reset by the Message Handler.
1 = Transfer between Message RAM and Output Buffer completed
0 = No transfer completed
SWEStop Watch Event
This flag is set after a stop watch activation when the actual cycle counter and macrotick value
are stored in the Stop Watch register (see section 4.4.10 Stop Watch Register 1 (STPW1)).
This flag is set by the CC when the message buffer status MBS has changed if bit MBI of that
message buffer is set (see Table 17).
1 = Message buffer status of at least one message buffer with MBI = ’1’ has changed
0 = No message buffer status change of message buffer with MBI = ’1’
SDSStart of Dynamic Segment
This flag is set by the CC when the dynamic segment starts.
1 = Dynamic segment started
0 = Dynamic segment not yet started
-29/165-
15.12.2006
User’s Manual
Revision 1.2.5 E-Ray
Channel-specific status flags:
WUPAWakeup Pattern Channel A
This flag is set by the CC when a wakeup pattern was received on channel A. Only set when the
CC is in WAKEUP, READY, or STARTUP state, or when in Monitor mode.
1 = Wakeup pattern received on channel A
0 = No wakeup pattern received on channel A
MTSAMTS Received on Channel A (vSS!ValidMTSA)
Media Access Test symbol received on channel A during the preceding symbol window.
Updated by the CC for each channel at the end of the symbol window.
1 = MTS symbol received on channel A
0 = No MTS symbol received on channel A
WUPBWakeup Pattern Channel B
This flag is set by the CC when a wakeup pattern was received on channel B. Only set when the
CC is in WAKEUP, READY, or STARTUP state, or when in Monitor mode.
1 = Wakeup pattern received on channel B
0 = No wakeup pattern received on channel B
MTSBMTS Received on Channel B (vSS!ValidMTSB)
Media Access Test symbol received on channel B during the preceding symbol window.
Updated by the CC for each channel at the end of the symbol window.
1 = MTS symbol received on channel B
0 = No MTS symbol received on channel B
manual_programmers_model.fm
-30/165-
15.12.2006
Loading...
+ 135 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.