INTRODUCTION

As a leading manufacturer of smart function modules, NAI offers over 100 different modules that cover a wide range of I/O, measurement and simulation, communications, Ethernet switch, and SBC functions. Our ARINC 429/575 Communications Module (AR1) is designed to meet data transfer standards and protocols used in aircraft avionics systems. With its adherence to industry-standard protocols and the ability to support both ARINC 429 and 575 communications, the AR1 offers exceptional performance and reliability. This user manual is designed to help you get the most out of your AR1 function module.

For a brief description of the modules and complete list of specifications, click here for the AR1 data sheet.

AR1 Overview

The AR1 ARINC 429/575 Communications Module offers a variety of features that highlight its role as in data management and as an interface. Some of the key features include:

ARINC communications: The module supports the following ARINC communications:

  • ARINC 429: ARINC 429 is a widely adopted data transfer standard, serving as an alternative to MIL-STD-1553. It utilizes a self-clocking, self-synchronizing data bus protocol with separate transmit and receive ports. The physical connection consists of twisted pairs carrying balanced differential signaling. Each data word is 32 bits in length, with most messages containing a single data word. Messages are transmitted at either 12.5 or 100 kbps, allowing other system elements to monitor the bus messages. The transmitter continuously transmits 32-bit data words or the NULL state. A single-wire pair can accommodate one transmitter and up to 20 receivers. Notably, the receiver end of the protocol enables self-clocking, eliminating the need for transmitting clocking data.

  • ARINC 575: In addition to ARINC 429, the AR1 function module also supports ARINC 575, a data transfer protocol specifically used for the Digital Air Data System (DADS) on commercial and transport aircraft. ARINC 575 defines a digital data bus that distributes crucial air-data information to displays, autopilots, and flight control instrumentation.

While there are minor differences between the digital data bus of ARINC 575 and ARINC 429, the most significant distinction lies in the usage of bit 32. In ARINC 429, bit 32 is reserved for parity, whereas ARINC 575 can utilize bit 32 for either parity (when using BNR encoding) or data (when using BCD encoding).

Receive/Transmit Mode Programmability: Each channel of the module can be programmed to operate in either receive or transmit mode according to your specific application needs.

Flexible Operation: The module supports both 100 kHz and 12.5 kHz operation per channel, allowing you to choose the appropriate speed for your communication requirements.

Transmit Capabilities: Enjoy the convenience of a 255 message FIFO or scheduled transmits per channel, allowing you to efficiently manage and control the transmission of messages. Additionally, asynchronous transmits can be performed alongside scheduled transmits.

Receive Capabilities: Benefit from a 255 message FIFO or mailbox buffering per channel, providing ample storage for incoming messages. This ensures reliable reception and efficient handling of data.

Message Validation: The module supports SDI/Label Filtering, enabling you to validate received messages based on specific criteria per channel. This feature enhances the overall data integrity and ensures only relevant information is processed.

Hardware parity: You have the option to enable selectable hardware parity generation/checking, which adds an extra layer of data integrity verification during transmission and reception.

Receive Time Stamping: Gain valuable insights into message reception with the module’s receive time stamping feature. This allows precise timing analysis and synchronization in your communication system.

Continuous Built-In Test (BIT): The AR1 incorporates continuous BIT functionality, providing self-diagnostics and monitoring capabilities to ensure reliable operation and easy troubleshooting.

Loop-Back Test: Verify the integrity of the module by performing loop-back tests. This feature allows you to validate the communication path and confirm proper functionality.

Tri-State Outputs: The module’s outputs support tri-state functionality, allowing you to control the state of the outputs as needed. This enables seamless integration with other system components.

High and Low-Speed Slew Rate Outputs: The module offers both high and low-speed slew rate outputs, providing flexibility in meeting the requirements of various communication interfaces.

Module Factory Defaults

Speed:12.5 khz
Gap Time:4 bits
Interrupt Level:0
Interrupt Vector:0x00
Transmit Mode:Immediate FIFO
Receive Mode:FIFO
Parity (Odd):Enabled
Receivers:Disabled
Transmitters:Disabled
SDI/Label Matching:Disabled
Number of Words Tx Buffer:0
Number of Words Rx Buffer:0
Rx Buffer, Almost Full:0x80
Tx Buffer, Almost Empty:0x20
Tx-Rx Configuration High:0
Tx-Rx Configuration Low:0
Channel Control High:0
Channel Control Low:0
Built-In-Test:Enabled

PRINCIPLE OF OPERATION

Module AR1 provides up to 12 programmable ARINC-429 channels. Each channel is software selectable for transmit and/or receive, high or low speed, and odd or no parity. Therefore, AR1 can support multiple ARINC 429 and 575 channels simultaneously.

Receive Operation

Serial BRZ data is decoded for logic states: one, zero or null. Once Word Gap is detected (4 null states) the receiver waits for either a zero or one state to start the serial-to-parallel shift function. If a waveform timing fault is detected before the serial/parallel function is complete, operation is terminated and the receiver returns to waiting for Word Gap detection. The serial-to-parallel output data is validated for odd parity, Label and Serial-to-Digital Interface (SDI).

If message validation (filtering) is enabled, the module compares the SDI/Label of incoming ARINC messages to a list of desired SDI/Labels in validation (match) memory and only stores messages with an SDI/Label in the list. The message is stored in the receive FIFO or mailbox, depending if the channel is in FIFO receive mode or mailbox receive mode. In FIFO Receive Mode, received ARINC messages / words are stored with an associated status word and an optional time-stamp value in the channel’s receive FIFO. Additionally, the Rx FIFO can be set for either bounded or circular mode, which determines FIFO behavior when it is full. In bounded mode, newly received ARINC messages are discarded if the FIFO is full whereas in circular mode, new ARINC messages overwrite the oldest messages in the FIFO. In mailbox mode, received ARINC words are stored in mailboxes or records in RAM that are indexed by the SDI/Label of the ARINC word. Each mailbox contains a status word associated with the message, the ARINC message / word, and an optional 32-bit timestamp value. The status word indicates parity error and new message status.

Transmit Operation

Transmitters are tri-stated when TX is not enabled. Transmit operates in one of three modes: Immediate FIFO, Triggered FIFO, and Scheduled. In immediate mode, ARINC data is sent as soon as data is written to the transmit FIFO. In Triggered FIFO mode, a write to the Transmit Trigger register is needed to start transmission of the transmit FIFO contents. Transmission continues until the FIFO is empty. To transmit more data after the FIFO empties out, issue a new trigger after filling the transmit FIFO with new data.

For either FIFO mode, a transmit FIFO Rate register is provided to control rate of transmission. The contents of this register specify the gap time between transmitted words from the FIFO. The default is the minimum ARINC gap time of 4-bit times.

Schedule mode transmits ARINC data words according to a prebuilt schedule table in Transmit Schedule RAM. In the Schedule table, various commands define what messages are sent and the duration of gaps between each message. Note that a Gap (Gap or Fixed Gap) command must be explicitly added in between each Message command otherwise a gap will not be inserted between messages. The ARINC data words and gap times are stored in the Transmit Message RAM and can be updated on the fly as the schedule executes. A write to the Transmit Trigger register initiates the schedule and commands are executed starting from the first command (address 0x0) in the Schedule RAM. While a schedule is running, an ARINC word can be transmitted asynchronously by writing the async data word to the Async Transmit Data register. After it has transmitted, the Async Data Available bit will be cleared from the Channel Status register and the Async Data Sent Interrupt will be set if enabled. The Async Data Available bit in Channel Status also gets cleared by a Stop Cmd in a schedule or if a Transmit Stop command is issued from the Transmit Stop register. Use the Fixed Gap command instead of the Gap command to disable async transmissions during the schedule gap time. Gap and Fixed Gap commands can both be used when building the transmit schedule.

Schedule Transmit Commands

ARINC 429/575 scheduling is controlled by commands that are written to the Transmit Schedule RAM. The available commands are:

Schedule Transmit Commands

Command NameDescription
MessageThis command takes a parameter that specifies the location in Transmit Message memory containing the ARINC data word to be sent. The word is transmitted when the Message command is executed. This ARINC word can be modified in Tx Message memory while the schedule is running.
GapThis command takes a parameter that specifies the location in Transmit Message memory containing a 20-bit gap time value. Values less than 4 are invalid. If the previous command was a Message, then that message is transmitted and then the transmitter waits out the specified gap time transmitting nulls. An exception to this is if there is an async data word available. If the gap time is greater or equal to 40 bit times (4-bit gap time plus one ARINC word plus another 4-bit gap time) an async data word, if available, will be transmitted during this time. If a new async data word is made available and the remaining gap time is large enough to accommodate another async data word transmission, then the new async data word will be transmitted after a 4-bit gap time. Multiple async data word transmissions can thus occur as long as the remaining gap time is large enough to accommodate a message and the required minimum 4-bit gap time. Otherwise, the transmitter waits out the remaining gap time before executing the next command.
Fixed GapThis command takes a parameter that specifies the location in Transmit Message memory containing a 20-bit gap time value. Values less than 4 are invalid. If the previous command was a Message, then that message is transmitted with the specified gap time appended. If the previous command was not a Message, then the transmitter waits for the specified gap time before executing the next command. The difference between the Fixed Gap and Gap command is that Fixed Gap will prevent the transmission of async data words during the gap time. Use Fixed Gap to only allow nulls to be transmitted during the gap time.
PauseThis command causes the transmitter to pause execution of the schedule after transmitting the current word. Either a Transmit Trigger command is issued to resume execution, or a Transmit Stop command is issued to halt execution.
InterruptThis command causes the Schedule Interrupt to be set if Schedule Interrupt is enabled. An unlatched version of this flag is also visible in the channel status register.
JumpJumps to the 9-bit address in Schedule memory pointed to by this command and resumes execution there.
StopThis command causes the transmitter to stop execution of the schedule after transmitting the current word.

ARINC 429/575 Built-In Test

The AR1 module supports three types of built-in tests: Power-On, Continuous Background and Initiated. The results of these tests are logically ORed together and stored in the BIT Dynamic Status and BIT Latched Status registers.

Power-On Self-Test (POST)/Power-On BIT (PBIT)/Start-Up BIT (SBIT)

The power-on self-test is performed on each channel automatically when power is applied and reports the results in the BIT Status register when complete. After power-on, the Power-on BIT Complete register should be checked to ensure that POST/PBIT/SBIT test is complete before reading the BIT Dynamic Status and BIT Latched Status registers.

Continuous Background Built-In Test (CBIT)

The background Built-In-Test or Continuous BIT (CBIT) runs in the background for each enabled channel. In Transmit operations, internal transmit data is compared to loop-back data received by the ARINC receivers. When the channel is configured for Receive operation, receive data is continuously monitored via a secondary parallel path circuit and compared to the primary input receive data. If the data does not match, the technique used by the automatic background BIT test consists of an “add-2, subtract-1” counting scheme. The BIT counter is incremented by 2 when a BIT-fault is detected and decremented by 1 when there is no BIT fault detected and the BIT counter is greater than 0. When the BIT counter exceeds the (programmed) Background BIT Threshold value, the specific channel’s fault bit in the BIT status register will be set. The “add- 2, subtract-1” counting scheme effectively filters momentary or intermittent anomalies by allowing them to “come and go“ before a BIT fault status or indication is flagged (e.g. BIT faults would register when sustained). This prevents spurious faults from registering valid such as those caused by EMI and/or dirty power causing false BIT faults. Putting more “weight” on errors (“add-2”) and less “weight” on subsequent passing results (subtract-1) will result in a BIT failure indication even if a channel “oscillates” between a pass and fail state. Results of the Continuous BIT are stored in the BIT Dynamic Status and BIT Latched Status register.

Initiated Built-In Test (IBIT)

The Initiated Built-In-Test (IBIT) is an internal loopback available for each channel of the AR1 module. The test is initiated by setting the bit for the associated channel in the Test Enabled register to a 1. Once enabled, they must wait at least 3 msec before checking to see if the bit for the associated channel in the Test Enabled register reads a 0. When the AR1 clears the bit, it means that the test has completed, and its results can be checked. The results of the IBIT is stored in the BIT Dynamic Status and BIT Latched Status registers, a 0 indicates that the channel has passed and a 1 indicates that it failed.

Loop-Back Operation

Transmit and receive operation of an AR1 channel can be verified internally by enabling both Tx and Rx on the same channel. Tx Scheduling is not supported when the channel is placed in this mode.

Transient Protection

The module is normally configured for transient protection but can be specified without if protection is implemented externally.

Status and Interrupts

The AR1 Module provide registers that indicate faults or events. Refer to “Status and Interrupts Module Manual” for the Principle of Operation description.

Module Common Registers

The AR1 Module includes module common registers that provide access to module-level bare metal/FPGA revisions & compile times, unique serial number information, and temperature/voltage/current monitoring. Refer to “Module Common Registers Module Manual” for the detailed information.

REGISTER DESCRIPTIONS

The register descriptions provide the register name, Type, Data Range, Read or Write information, Initialized Value, a description of the function and, in most cases, a data table.

Receive Registers

The registers listed are associated with data that is received on the AR1 channels. Two modes of message storage are supported: Receive FIFO and Receive Mailbox.

Receive FIFO Mode Registers

The Receive FIFO Mode Registers contain information about ARINC messages that are received via the Receive FIFO buffer on the AR1 channel. The registers associated with this feature are:

  • Receive FIFO Message Buffer
  • Receive FIFO Message Count
  • Receive FIFO Almost Full Threshold
  • Receive FIFO Size
Receive FIFO Message Buffer
Function:In FIFO receive mode, the received ARINC messages are stored in this buffer.
Type:unsigned binary word (32-bit)
Range:0 to 0xFFFF FFFF
Read/Write:R
Initialized Value:NA
Operational Settings:Perform two reads from this register to retrieve the Status word and the ARINC data word, respectively. If Time Stamping is enabled, perform one more read to retrieve the timestamp.
Message Status Word
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000000000NPE
Data Word
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
DDDDDDDDDDDDDDDD
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
DDDDDDDDDDDDDDDD
*Timestamp Word (if enabled)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
DDDDDDDDDDDDDDDD
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
DDDDDDDDDDDDDDDD
PE = Parity Error1 - Calculated parity does not match the received parity bit.
N = New message1 - Message has not been read yet.
Receive FIFO Message Count
Function:Contains the number of ARINC messages in the receive FIFO in Receive FIFO mode.
Type:unsigned binary word (32-bit)
Range:0 to 255
Read/Write:R
Initialized Value:0
Operational Settings:A received message consists of the message status word and the ARINC data word. If time stamping is enabled, a 32-bit timestamp is also included in the message. For example, if this register reads 1, indicating one message is loaded in the receive FIFO, perform two reads from the Receive FIFO Message Buffer register to retrieve the full message (status word and ARINC data word) if time stamping is disabled or perform three reads from the Receive FIFO Message Buffer register to retrieve the full message (status word, ARINC data word and timestamp word) if time stamping is enabled.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000DDDDDDDD
Receive FIFO Almost Full Threshold
Function:Specifies the level of the receive FIFO buffer, equal or above, at which the Rx FIFO Almost Full Status bit D1 in the Channel Status register, is flagged (High True).
Type:unsigned binary word (32-bit)
Range:0 to 255
Read/Write:R/W
Initialized Value:128 (0x0080)
Operational Settings:If the Interrupt Enable register interrupt is enabled, a SYSTEM interrupt will be generated when the receive FIFO level increases and reaches the threshold level. This register does NOT get reset by a channel reset.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000DDDDDDDD
Receive FIFO Size
Function:Specifies the size of the Rx FIFO buffer. The default size is 255 messages.
Type:unsigned binary word (32-bit)
Range:1 to 255
Read/Write:R/W
Initialized Value:255 (0xFF)
Operational Settings:This setting affects the Rx FIFO size when the Rx FIFO is configured in either Rx FIFO Bounded or Circular mode.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000DDDDDDDD

Receive Mailbox Mode Registers

The registers listed are associated with data that is received on the AR1 channels. Two modes of message storage are supported: Receive FIFO and Receive Mailbox.

The Receive Mailbox Mode Registers contain information about ARINC messages that are received via mailboxes on the AR1 channel. The registers associated with this feature are:

  • Receive FIFO SDI/Label Buffer
  • Receive FIFO SDI/Label Count
  • Receive FIFO Almost Full Threshold
  • Receive FIFO Size
  • Mailbox Status Data
  • Mailbox Message Data
  • Mailbox Timestamp Data
Receive FIFO SDI/Label Buffer
Function:In Mailbox receive mode, SDI/Label of received messages are stored in this buffer.
Type:unsigned binary word (32-bit)
Range:0 to 0x0000 03FF
Read/Write:R
Initialized Value:N/A
Operational Settings:In Mailbox receive mode, this FIFO contains the 10-bit SDI/Label of newly received messages. This provides a list to the user showing which mailboxes contain new messages since the last time this FIFO was read.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
000000A10A9A8A7A6A5A4A3A2A1
A8-A1Label (A8 is MSB and A1 is LSB)
A10-A9SDI
Receive FIFO SDI/Label Count
Function:Contains the number of newly received SDI/Labels in the receive FIFO in Receive Mailbox mode.
Type:unsigned binary word (32-bit)
Range:0 to 255
Read/Write:R
Initialized Value:0
Operational Settings:In Mailbox receive mode, this register contains the number of newly received SDI/Labels in the receive FIFO. The user may perform this number of reads on the Receive FIFO SDI/Label Buffer register to retrieve all SDI/Labels.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000DDDDDDDD
Receive FIFO Almost Full Threshold
Function:Specifies the level of the receive FIFO buffer, equal or above, at which the Rx FIFO Almost Full Status bit D1 in the Channel Status register, is flagged (High True).
Type:unsigned binary word (32-bit)
Range:0 to 255
Read/Write:R/W
Initialized Value:128 (0x0080)
Operational Settings:If the Interrupt Enable register interrupt is enabled, a SYSTEM interrupt will be generated when the receive FIFO level increases and reaches the threshold level. This register does NOT get reset by a channel reset.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000DDDDDDDD
Receive FIFO Size
Function:Specifies the size of the Rx FIFO buffer. The default size is 255 SDI/Labels.
Type:unsigned binary word (32-bit)
Range:1 to 255
Read/Write:R/W
Initialized Value:255 (0xFF)
Operational Settings:This setting affects the Rx FIFO size when the Rx FIFO is configured in either Rx FIFO Bounded or Circular mode.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000DDDDDDDD
Mailbox Status Data
Function:Stores ARINC Status data word.
Type:unsigned binary word (32-bit)
Range:0 to 0x0000 0003
Read/Write:R
Initialized Value:0
Operational Settings:This is a 32-bit value that contains status information associated with the received ARINC word. D1 of 1 indicates that the received ARINC word is a new message. D0 of 1 indicates a parity error is present in the ARINC message. There are 1024 Mailbox Status Data registers, one for each SDI/Label. The user can determine which Mailbox Status Data registers contain new data based on newly received SDI/Labels in the receive FIFO.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000000000NPE
PE = Parity Error1 - Calculated parity does not match the received parity bit.
N = New message1 - This is a new ARINC message.
Mailbox Message Data
Function:Stores ARINC Message data word.
Type:unsigned binary word (32-bit)
Range:0 to 0xFFFF FFFF
Read/Write:R
Initialized Value:0
Operational Settings:This is the 32-bit ARINC data word. There are 1024 Mailbox Message Data registers, one for each SDI/Label. The user can determine which Mailbox Message Data registers contain new data based on newly received SDI/Labels in the receive FIFO.
Mailbox Timestamp Data
Function:Stores ARINC Timestamp data word.
Type:unsigned binary word (32-bit)
Range:0 to 0xFFFF FFFF
Read/Write:R
Initialized Value:0
Operational Settings:This is the 32-bit timestamp associated with the received ARINC word. There are 1024 Mailbox Timestamp Data registers, one for each SDI/Label. The user can determine which Mailbox Timestamp Data registers contain new data based on newly received SDI/Labels in the receive FIFO.

Timestamp Registers

Timestamp Control
Function:Determines the resolution of the timestamp counter.
Type:unsigned binary word (32-bit)
Range:0 to 0x0000 0007
Read/Write:R/W
Initialized Value:0 (1 µsec)
Operational Settings:The LSB can have one of four time values. Set bit D2 to zero out the timestamp counter.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000000000000ZDD
Timestamp Control Register
Bit(s)NameDescription
D31:D3ReservedSet Reserved bits to 0.
D2Zero TimestampSet the bit to zero out the timestamp counter
D1:D0Resolution (R/W)The following sets the Resolution: (0:0) 1 µs ` (0:1) 10 µs ` (1:0) 100 µs + (1:1) 1 ms
Timestamp Value
Function:Reads the current 32-bit timestamp.
Type:unsigned binary word (32-bit)
Range:0 to 0xFFFF FFFF
Read/Write:R
Initialized Value:NA
Operational Settings:The time value of each LSB is determined by the resolution set in the Timestamp Control register.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
DDDDDDDDDDDDDDDD
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
DDDDDDDDDDDDDDDD

Message Validation Registers

If message validation (filtering) is enabled, the module compares the SDI/Label of incoming ARINC messages to a list of desired SDI/Labels in validation (match) memory and only stores messages with an SDI/Label in the list.

Match Enable
Function:Enables or disables reception of ARINC words containing the associated SDI/Label.
Type:unsigned binary word (32-bit)
Range:0 to 1
Read/Write:R/W
Initialized Value:0
Operational Settings:D0 set to 1 enables reception of ARINC words containing the SDI/Label that is associated with this register. This register only takes effect if the MATCH ENABLE bit is set to 1 in the Channel Control Register. There are 1024 Match Enable Data Registers and each register is indexed by the SDI/Label. Note that bit D1 is a reserved bit and it is fixed to 1.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
000000000000001D

Transmit Registers

The registers listed are associated with data that is to be transmitted from the AR1 channels. Two modes of message storage are supported:Transmit FIFO and Transmit Scheduling.

Transmit FIFO Registers

The registers listed are associated with data that is to be transmitted from the AR1 channels. Two modes of message storage are supported: Transmit FIFO and Transmit Scheduling.

The Transmit FIFO Mode Registers contain information about ARINC messages that are to be transmitted via the Transmit FIFO buffer on the AR1 channel. The registers associated with this feature are:

  • Transmit FIFO Message Buffer
  • Transmit FIFO Message Count
  • Transmit FIFO Almost Empty Threshold
  • Transmit FIFO Rate
Transmit FIFO Message Buffer
Function:In immediate or triggered FIFO modes, ARINC messages are placed here prior to transmission.
Type:unsigned binary word (32-bit)
Range:0 to 0xFFFF FFFF
Read/Write:W
Initialized Value:N/A
Operational Settings:ARINC data words are 32-bits. This memory is shared with the Tx Message memory and is only available in Tx FIFO modes.
Transmit FIFO Message Count
Function:Contains the number of ARINC 32-bit words in the transmit FIFO.
Type:unsigned binary word (32-bit)
Range:0 to 255
Read/Write:R
Initialized Value:0
Operational Settings:Used only in the FIFO transmit modes.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000DDDDDDDD
Transmit FIFO Almost Empty Threshold
Function:Specifies the level of the transmit buffer, equal or below, at which the Tx FIFO Almost Empty Status bit D5 in the Channel Status register, is flagged (High True).
Type:unsigned binary word (32-bit)
Range:0 to 255
Read/Write:R/W
Initialized Value:32 decimal (0x0020)
Operational Settings:If the Interrupt Enable register interrupt is enabled, a SYSTEM interrupt will be generated when the receive FIFO level increases and reaches the threshold level. This register does NOT get reset by a channel reset.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000DDDDDDDD
Transmit FIFO Rate
Function:Determines the Gap time between transmitted ARINC messages in FIFO transmit modes.
Type:unsigned binary word (32-bit)
Range:0-0x000F FFFF
Read/Write:R/W
Initialized Value:4
Mode:FIFO
Operational Settings:Each LSB is 1 bit time. Rates less than 4 are not valid. This register does NOT get reset by a channel reset.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
000000000000DDDD
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
DDDDDDDDDDDDDDDD

Transmit Scheduling Registers

The Transmit Scheduling Registers are utilized when the channel is set up to run a Transmit Schedule. The memories/registers associated with this feature are:

  • Transmit Schedule RAM
  • Transmit Message RAM
  • Async Transmit Data Register
Transmit Schedule RAM Command Format
Function:The Transmit Schedule RAM consists of 256 32-bit words that are used to set up a self-running transmit schedule. These are the valid command formats for the Transmit Schedule RAM.
Type:unsigned binary word (32-bit)
Range:0 to 0x0000 FFFF
Read/Write:R/W
Initialized Value:N/A
Operational Settings:Only bits 0 to 15 are utilized for schedule commands. Bits 12 to 15 specify the command type and bits 0 to 7 or 8 specify the command parameter. Only the Message, Gap, Fixed Gap and Jump commands utilize a command parameter. When the schedule starts, commands are executed sequentially starting from schedule RAM address 0x0.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16FUNCTION
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0FUNCTION
0000000000000000STOP CMD
00010000MA7MA6MA5MA4MA3MA2MA1MA0MESSAGE CMD1
00100000MA7MA6MA5MA4MA3MA2MA1MA0GAP CMD1
00110000MA7MA6MA5MA4MA3MA2MA1MA0FIXED GAP CMD1
0100000000000000PAUSE CMD
0101000000000000SCH INTERRUPT CMD
0110000SA8SA7SA6SA5SA4SA3SA2SA1SA0JUMP CMD2
0111000000000000RESERVED
1000000000000000RESERVED
1 MA7-MA0Address of Tx Message memory organized as 256 x 32.
2 SA8-SA0Address of next command in Tx Schedule memory organized as 256 x 32.
Transmit Message RAM Data Format
Function:The Transmit Message RAM consists of 256 32-bit words that are used by the transmit schedule for ARINC message and gap time word storage.
Type:unsigned binary word (32-bit)
Range:0 to 0xFFFF FFFF
Read/Write:R/W
Initialized Value:N/A
Operational Settings:Words that are stored in Transmit Message RAM are utilized by Message, Gap and Fixed Gap commands in the Transmit Schedule. In the case of Message commands, the command parameter specifies an address in Transmit Message RAM that contains the 32-bit ARINC message to transmit. In the case of Gap or Fixed Gap commands, the command parameter specifies an address in Transmit Message RAM that contains the gap time value.
Async Transmit Data
Function:This memory location is the transmit async buffer.
Type:unsigned binary word (32-bit)
Range:0 to 0xFFFF FFFF
Read/Write:R/W
Initialized Value:0
Operational Settings:While a schedule is running, a single 32-bit ARINC message that is intended to be transmitted asynchronously must be written to this register. When an async data word is written to this register, the Async Data Available status bit will get set until the async data word is transmitted. If a gap (not fixed gap) time is greater or equal to 40 bit times (4-bit gap time plus one ARINC word plus another 4-bit gap time) the async data word, if available, will be transmitted during this time.

Transmit Control Registers

Control of the transmission of ARINC messages includes the ability to start/resume, pause and stop the transmission of the message.

Transmit Trigger
Function:Sends a trigger command to the transmitter and is used to start transmission in Triggered FIFO or Scheduled Transmit modes.
Type:unsigned binary word (32-bit)
Range:0 to 0x0000 0FFF
Read/Write:W
Initialized Value:0
Operational Settings:Set bit to 1 for the channel to resume transmission after a scheduled pause or Transmit pause command.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000Ch12Ch11Ch10Ch9Ch8Ch7Ch6Ch5Ch4Ch3Ch2Ch1
Transmit Pause
Function:Sends a command to pause the transmitter after the current word and gap time has finished transmitting.
Type:unsigned binary word (32-bit)
Range:0 to 0x0000 0FFF
Read/Write:W
Initialized Value:0
Modes Affected:Triggered FIFO and Schedule Transmit
Operational Settings:Set bit to 1 for the channel to pause transmission in Triggered FIFO or Scheduled Transmit modes. Issue a Transmit Trigger command to resume transmission or issue a Transmit Stop command to halt transmission.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000Ch12Ch11Ch10Ch9Ch8Ch7Ch6Ch5Ch4Ch3Ch2Ch1
Transmit Stop
Function:Sends a command to stop the transmitter after the current word and gap time has been transmitted.
Type:unsigned binary word (32-bit)
Range:0 to 0x0000 0FFF
Read/Write:W
Initialized Value:0
Modes Affected:All Transmit modes
Operational Settings:Set bit to 1 for the channel to stop transmission.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000Ch12Ch11Ch10Ch9Ch8Ch7Ch6Ch5Ch4Ch3Ch2Ch1

Control Registers

The AR1 control registers provide the ability to reset all the channels in the AR1 module and configuring and controlling individual AR1 channels.

Channel Control
Function:Used to configure and control the channels.
Type:unsigned binary word (32-bit)
Range:See table
Read/Write:R/W
Initialized Value:0
Operational Settings:When writing to this register, the configuration bits must be maintained when setting the control bits.
Bit(s)CONTROL FUNCTIONSDescription
D31:D22RESERVEDSet RESERVED bits to 0.
D21SCHEDULE INTERRUPT CLEARWhen the SCHEDULE INTERRUPT CLEAR bit is set to 1 by the user, the Schedule Interrupt bit (D10) in the Channel Status register can be cleared.
D20RESERVEDSet RESERVED bits to 0.
D19CHANNEL RESETWhen the CHANNEL RESET bit is set to 1 by the user, the channel is held in reset until the user sets the bit to 0. The channel reset causes Tx and Rx FIFO buffers to clear out but channel configuration settings remain unchanged.
D18MATCH MEMORY CLEARWhen the MATCH MEMORY CLEAR bit is set to 1 by the user and if MATCH ENABLE bit is set to 1, all 1024 SDI/Labels will be disabled in Rx Match Memory, which means all received ARINC messages will be filtered out and discarded. This is a self-clearing bit. After setting the bit, allow 100 us to complete.
D17RECEIVE FIFO CLEARWhen the RECEIVE FIFO CLEAR bit is set to 1 then set to 0 by the user, the Rx FIFO buffer is cleared out and the Rx FIFO count goes to zero.
D16TRANSMIT FIFO CLEARWhen the TRANSMIT FIFO CLEAR bit is set to 1 then set to 0 by the user, the Tx FIFO buffer is cleared out and the Tx FIFO count goes to zero.
Bit(s)CONFIGURATION FUNCTIONSDescription/Values
D15:D11RESERVEDSet RESERVED bits to 0.
D10STORE ON ERROR DISABLEIf the STORE ON ERROR DISABLE bit is cleared (0) and odd parity is enabled, received words that contain a parity error will be stored in the receive buffer or mailbox. When the STORE ON ERROR DISABLE bit is set (1) and odd parity is enabled, received words that contain a parity error will NOT be stored in the receive buffer or mailbox.
D9RESERVEDSet RESERVED bit to 0.
D8TIMESTAMP ENABLEWhen TIMESTAMP ENABLE bit is set to 1, the receiver will store a 32-bit time stamp value along with the received ARINC word. There is one time stamp counter per module and it is used across all 12 channels. It has 4 selectable resolutions and can be reset via the Time Stamp Control register. It is recommended to clear the Receive FIFOs whenever the Receive mode or Time Stamp Enable mode is changed to ensure that extraneous data is not leftover from a previous receive operation.
D7MATCH ENABLEWhen the MATCH ENABLE bit is set to 1, the receiver will only store ARINC words which match the SDI/Labels enabled in Rx Match memory.
D6PARITY DISABLEThe PARITY DISABLE bit when set to 0, causes ARINC bit 32 to be treated as an odd parity bit. The transmitter calculates the ARINC odd parity bit and transmits it as bit 32. The receiver will check the received ARINC word for odd parity and will flag an error if is not. When the PARITY DISABLE bit is set to 1, parity generation and checking will be disabled and both the transmitter and receiver will treat ARINC bit 32 as data and pass it on unchanged.
D5HIGH SPEEDThe HIGH SPEED bit is used to select the data rate. 12.5 kHz = 0 + 100 kHz = 1
D4:D3TRANSMIT MODEThe TRANSMIT MODE bits are used to select the Transmit Mode. (0:0) = Immediate FIFO mode ` (0:1) = Schedule mode ` (1:0) = Triggered FIFO mode + (1:1) = Invalid mode
D2TRANSMIT ENABLEThe TRANSMIT ENABLE bit should be set after all transmit parameters have been set up. This is especially important in Immediate FIFO Transmit mode, since this mode will start transmitting as soon as data is put into the Tx FIFO.
D1RECEIVE MODEThe RECEIVE MODE bit is used to select the storage mode (FIFO or Mailbox) of received messages. FIFO = 0
MBOX = 1
D0RECEIVER ENABLEThe RECEIVER ENABLE bit should be set after all receive parameters and filters have been set up. After setting this bit, the module will look for a minimum 4-bit gap time before decoding any ARINC bits to prevent it from receiving a partial ARINC word.
Module Reset
Function:Sends a command to reset the entire 12-channel module to power up conditions.
Type:unsigned binary word (32-bit)
Range:0 or 1
Read/Write:W
Initialized Value:0
Operational Settings:All FIFOs are cleared. However, it does not clear out any memories. Set D0 to 1 to reset the module then set to 0 to bring it out of reset.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000000000000001

ARINC 429/575 Test Registers

The AR1 module provides the ability to run an initiated test (IBIT). Writing a 1 to the bit associated with the channel in the Test Enabled register.

Test Enabled
Function:Set the bit corresponding to the channel you want to run Initiated Built-In-Test.
Type:unsigned binary word (32-bit)
Data Range:0 to 0x0000 0FFF
Read/Write:R/W
Initialized Value:0x0 Operational Settings: Set bit to 1 for channel to run an Initiated BIT test. Failures in the BIT test are reflected in the BIT Status registers for the corresponding channels that fail. In addition, an interrupt (if enabled in the BIT Interrupt Enable register) can be triggered when the BIT testing detects failures. Bit is self-clearing and does so upon completion of the test. Allow at least 3 ms per channel for the test enabled bits to clear after enabling. Note that running Initiated BIT test on a channel will interrupt operation of the channel and all FIFOs will get cleared. The system implementation should take this behavior into consideration.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000Ch12Ch11Ch10Ch9Ch8Ch7Ch6Ch5Ch4Ch3Ch2Ch1

Background BIT Threshold Programming Registers

The Background BIT Threshold register provides the ability to specify the minimum time before the BIT fault is reported in the BIT Status registers. The Reset BIT register provides the ability to reset the BIT counter used in CBIT.

Background BIT Threshold
Function:Sets background BIT Threshold value to use for all channels for BIT failure indication.
Data Range:1 to 65,535
Read/Write:R/W
Initialized Value:5
Operational Settings:This value represents the background BIT error “count” that, when surpassed, will cause the BIT status to indicate failure.
Reset BIT
Function:Resets the CBIT internal circuitry and count mechanism. Set the bit corresponding to the channel you want to clear.
Type:unsigned binary word (32-bit)
Data Range:0 to 0x0000 0FFF
Read/Write:W
Initialized Value:0
Operational Settings:Set bit to 1 for channel to resets the CBIT mechanisms. Bit is self-clearing.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000Ch12Ch11Ch10Ch9Ch8Ch7Ch6Ch5Ch4Ch3Ch2Ch1

Module Common Registers

Refer to “Module Common Registers Module Manual” for the register descriptions.

Status and Interrupt Registers

The AR1 Module provides status registers for BIT and Channel.

Channel Status Enable
Function:Determines whether to update the status for the channels. Does NOT prevent BIT from executing; only prevents the update of results to the status registers. This feature can be used to “mask” status bit updates of unused channels in status registers that are bitmapped by channel.
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0x0000 0FFF (Channel Status)
Read/Write:R/W
Initialized Value:0x0000 0FFF Operational Settings: When the bit corresponding to a given channel in the Channel Status Enabled register is not enabled (0) the status update will be masked. This applies to all statuses that are bitmapped by channel (BIT Status and Summary Status).

Note

Background BIT will continue to run even if the Channel Status Enabled is set to 0.

Note

If latched status has been set for any channel bit, disabling the channel status update will NOT clear the latched status bit. To clear latched bits and disable their status updates, follow these steps:

  1. Disable channels in Channel Status Enable register.

  2. Read the Latched Status register.

  3. Clear the Latched Status register with the value read from step 2.

  4. Read the Latched Status register; should not read any errors (0) on channels that have been disabled.

D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000Ch12Ch11Ch10Ch9Ch8Ch7Ch6Ch5Ch4Ch3Ch2Ch1

BIT Status

There are four registers associated with the BIT Status: Dynamic, Latched, Interrupt Enable, and Set Edge/Level Interrupt.

BIT Status
Function:Sets the corresponding bit associated with the channel's BIT register.
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0x0000 0FFF
Read/Write:R (Dynamic), R/W (Latched, Interrupt Enable, Edge/Level Interrupt)
Initialized Value:0
BIT Dynamic Status
BIT Latched Status
BIT Interrupt Enable
BIT Set Edge/Level Interrupt
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000Ch12Ch11Ch10Ch9Ch8Ch7Ch6Ch5Ch4Ch3Ch2Ch1

Channel Status

There are four registers associated with the Channel Status: Dynamic, Latched, Interrupt Enable, and Set Edge/Level Interrupt. Use this register to read current or real-time status. The Built-In-Test Error bit is latched and will stay set once an error is detected. It can be cleared by reading the BIT Status register. The Schedule Interrupt bit can be cleared by reading the Interrupt Status register when enabled or it can be cleared via the Channel Control register. See specific registers for function description and programming.

The Rx Data Available bit is set when the receive FIFO is not empty. The Rx FIFO Overflow bit will set whenever the receiver has to discard data because the receive FIFO was full and new data was received. The Async Data Available bit in Channel Status also gets cleared by a Stop Cmd in a schedule or if a Transmit Stop command is issued from the Transmit Stop register. The Tx Run bit is set whenever the transmitter is executing a schedule or actively transmitting the contents of the transmit FIFO. The Tx Pause bit is set whenever the transmitter has been paused in schedule mode. Some events are NOT latched. They are dynamic.

Channel Status
Function:Sets the corresponding bit associated with the event type. There are separate registers for each channel.
Type:unsigned binary word (32-bit)
Range:0 to 0x0000 3FFF
Read/Write:R (Dynamic), R/W (Latched, Interrupt Enable, Edge/Level Interrupt)
Initialized Value:N/A
Channel Dynamic Status
Channel Latched Status
Channel Interrupt Enable
Channel Set Edge/Level Interrupt
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00DDDDDDDDDDDDDD
BitDescriptionConfigurable?Configuration Register
D0Rx Data AvailableNo
D1Rx FIFO Almost FullYesReceive FIFO Almost Full Threshold
D2Rx FIFO FullYesReceive FIFO Size
D3Rx FIFO OverflowYesReceive FIFO Size
D4Tx FIFO EmptyNo
D5Tx FIFO Almost EmptyYesTransmit FIFO Almost Empty Threshold
D6Tx FIFO FullNo
D7Parity ErrorNo
D8Receive ErrorNo
D9Built-in-Test ErrorNo
D10Schedule InterruptNo
D11Async Data AvailableNo
D12Tx RunNo
D13Tx PauseNo
Summary Status
Function:Sets the corresponding bit associated with the channel that has data available to receive in its Receive FIFO Mode or Receive Mailbox Mode registers.
Type:unsigned binary word (32-bits)
Data Range:0x0000 0000 to 0x0000 0FFF
Read/Write:R (Dynamic), R/W (Latched, Interrupt Enable, Set Edge/Level Interrupt)
Initialized Value:0
Summary Dynamic Status
Summary Latched Status
Summary Interrupt Enable
Summary Set Edge/Level Interrupt
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000Ch12Ch11Ch10Ch9Ch8Ch7Ch6Ch5Ch4Ch3Ch2Ch1

Interrupt Vector and Steering

When interrupts are enabled, the interrupt vector associated with the specific interrupt can be programmed (typically with a unique number/identifier) such that it can be utilized in the Interrupt Service Routine (ISR) to identify the type of interrupt. When an interrupt occurs, the contents of the Interrupt Vector registers is reported as part of the interrupt mechanism.

In addition to specifying the interrupt vector, the interrupt can be directed (“steered”) to the native bus or to the application running on the onboard ARM processor.

Note

the Interrupt Vector and Interrupt Steering registers are mapped to the Motherboard Common Memory and these registers are associated with the Module Slot position (refer to Function Register Map).

Interrupt Vector
Function:Set an identifier for the interrupt.
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R/W
Initialized Value:0
Operational Settings:When an interrupt occurs, this value is reported as part of the interrupt mechanism.
Interrupt Steering
Function:Sets where to direct the interrupt.
Type:unsigned binary word (32-bit)
Data Range:See table Read/Write: R/W
Initialized Value:0
Operational Settings:When an interrupt occurs, the interrupt is sent as specified:
Direct Interrupt to VME1
Direct Interrupt to ARM Processor (via SerDes) (Custom App on ARM or NAI Ethernet Listener App)2
Direct Interrupt to PCIe Bus5
Direct Interrupt to cPCI Bus6

FUNCTION REGISTER MAP

KEY

Configuration/Control
Status
Incoming Data
Outgoing Data
RECEIVE FIFO MODE REGISTERS
NOTE: Base Address - 0x4000 0000
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x1104Receive FIFO Message Buffer Ch 1R0x1110Receive FIFO Message Count Ch 1R
0x1204Receive FIFO Message Buffer Ch 2R0x1210Receive FIFO Message Count Ch 2R
0x1304Receive FIFO Message Buffer Ch 3R0x1310Receive FIFO Message Count Ch 3R
0x1404Receive FIFO Message Buffer Ch 4R0x1410Receive FIFO Message Count Ch 4R
0x1504Receive FIFO Message Buffer Ch 5R0x1510Receive FIFO Message Count Ch 5R
0x1604Receive FIFO Message Buffer Ch 6R0x1610Receive FIFO Message Count Ch 6R
0x1704Receive FIFO Message Buffer Ch 7R0x1710Receive FIFO Message Count Ch 7R
0x1804Receive FIFO Message Buffer Ch 8R0x1810Receive FIFO Message Count Ch 8R
0x1904Receive FIFO Message Buffer Ch 9R0x1910Receive FIFO Message Count Ch 5R
0x1A04Receive FIFO Message Buffer Ch 10R0x1A10Receive FIFO Message Count Ch 6R
0x1B04Receive FIFO Message Buffer Ch 11R0x1B10Receive FIFO Message Count Ch 7R
0x1C04Receive FIFO Message Buffer Ch 12R0x1C10Receive FIFO Message Count Ch 8R
0x1108Receive FIFO Almost Full Threshold Ch 1R/W0x1124Receive FIFO Size Ch 1R/W
0x1208Receive FIFO Almost Full Threshold Ch 2R/W0x1224Receive FIFO Size Ch 2R/W
0x1308Receive FIFO Almost Full Threshold Ch 3R/W0x1324Receive FIFO Size Ch 3R/W
0x1408Receive FIFO Almost Full Threshold Ch 4R/W0x1424Receive FIFO Size Ch 4R/W
0x1508Receive FIFO Almost Full Threshold Ch 5R/W0x1524Receive FIFO Size Ch 5R/W
0x1608Receive FIFO Almost Full Threshold Ch 6R/W0x1624Receive FIFO Size Ch 6R/W
0x1708Receive FIFO Almost Full Threshold Ch 7R/W0x1724Receive FIFO Size Ch 7R/W
0x1808Receive FIFO Almost Full Threshold Ch 8R/W0x1824Receive FIFO Size Ch 8R/W
0x1908Receive FIFO Almost Full Threshold Ch 9R/W0x1924Receive FIFO Size Ch 9R/W
0x1A08Receive FIFO Almost Full Threshold Ch 10R/W0x1A24Receive FIFO Size Ch 10R/W
0x1B08Receive FIFO Almost Full Threshold Ch 11R/W0x1B24Receive FIFO Size Ch 11R/W
0x1C08Receive FIFO Almost Full Threshold Ch 12R/W0x1C24Receive FIFO Size Ch 12R/W
RECEIVE MAILBOX MODE REGISTERS
NOTE: Base Address - 0x4000 0000
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x1104Receive FIFO SDI/Label Buffer Ch 1R0x1110Receive FIFO SDI/Label Count Ch 1R
0x1204Receive FIFO SDI/Label Buffer Ch 2R0x1210Receive FIFO SDI/Label Count Ch 2R
0x1304Receive FIFO SDI/Label Buffer Ch 3R0x1310Receive FIFO SDI/Label Count Ch 3R
0x1404Receive FIFO SDI/Label Buffer Ch 4R0x1410Receive FIFO SDI/Label Count Ch 4R
0x1504Receive FIFO SDI/Label Buffer Ch 5R0x1510Receive FIFO SDI/Label Count Ch 5R
0x1604Receive FIFO SDI/Label Buffer Ch 6R0x1610Receive FIFO SDI/Label Count Ch 6R
0x1704Receive FIFO SDI/Label Buffer Ch 7R0x1710Receive FIFO SDI/Label Count Ch 7R
0x1804Receive FIFO SDI/Label Buffer Ch 8R0x1810Receive FIFO SDI/Label Count Ch 8R
0x1904Receive FIFO SDI/Label Buffer Ch 9R0x1910Receive FIFO SDI/Label Count Ch 9R
0x1A04Receive FIFO SDI/Label Buffer Ch 10R0x1A10Receive FIFO SDI/Label Count Ch 10R
0x1B04Receive FIFO SDI/Label Buffer Ch 11R0x1B10Receive FIFO SDI/Label Count Ch 11R
0x1C04Receive FIFO SDI/Label Buffer Ch 12R0x1C10Receive FIFO SDI/Label Count Ch 12R
0x1108Receive FIFO Almost Full Threshold Ch 1R/W0x1124Receive FIFO Size Ch 1R/W
0x1208Receive FIFO Almost Full Threshold Ch 2R/W0x1224Receive FIFO Size Ch 2R/W
0x1308Receive FIFO Almost Full Threshold Ch 3R/W0x1324Receive FIFO Size Ch 3R/W
0x1408Receive FIFO Almost Full Threshold Ch 4R/W0x1424Receive FIFO Size Ch 4R/W
0x1508Receive FIFO Almost Full Threshold Ch 5R/W0x1524Receive FIFO Size Ch 5R/W
0x1608Receive FIFO Almost Full Threshold Ch 6R/W0x1624Receive FIFO Size Ch 6R/W
0x1708Receive FIFO Almost Full Threshold Ch 7R/W0x1724Receive FIFO Size Ch 7R/W
0x1808Receive FIFO Almost Full Threshold Ch 8R/W0x1824Receive FIFO Size Ch 8R/W
0x1908Receive FIFO Almost Full Threshold Ch 9R/W0x1924Receive FIFO Size Ch 9R/W
0x1A08Receive FIFO Almost Full Threshold Ch 10R/W0x1A24Receive FIFO Size Ch 10R/W
0x1B08Receive FIFO Almost Full Threshold Ch 11R/W0x1B24Receive FIFO Size Ch 11R/W
0x1C08Receive FIFO Almost Full Threshold Ch 12R/W0x1C24Receive FIFO Size Ch 12R/W
![](/modules/AR1/images/AR01_Img02.jpg)
TIMESTAMP REGISTERS
NOTE: Base Address - 0x4000 0000
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x100CTimestamp ControlR/W0x1010Timestamp ValueR
MESSAGE VALIDATION REGISTERS
![](/modules/AR1/images/AR01_Img03.jpg)
TRANSMIT FIFO REGISTERS
NOTE: Base Address - 0x4000 0000
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x1100Transmit FIFO Message Buffer Ch 1W0x1114Transmit FIFO Message Count Ch 1R
0x1200Transmit FIFO Message Buffer Ch 2W0x1214Transmit FIFO Message Count Ch 2R
0x1300Transmit FIFO Message Buffer Ch 3W0x1314Transmit FIFO Message Count Ch 3R
0x1400Transmit FIFO Message Buffer Ch 4W0x1414Transmit FIFO Message Count Ch 4R
0x1500Transmit FIFO Message Buffer Ch 5W0x1514Transmit FIFO Message Count Ch 5R
0x1600Transmit FIFO Message Buffer Ch 6W0x1614Transmit FIFO Message Count Ch 6R
0x1700Transmit FIFO Message Buffer Ch 7W0x1714Transmit FIFO Message Count Ch 7R
0x1800Transmit FIFO Message Buffer Ch 8W0x1814Transmit FIFO Message Count Ch 8R
0x1900Transmit FIFO Message Buffer Ch 9W0x1914Transmit FIFO Message Count Ch 9R
0x1A00Transmit FIFO Message Buffer Ch 10W0x1A14Transmit FIFO Message Count Ch 10R
0x1B00Transmit FIFO Message Buffer Ch 11W0x1B14Transmit FIFO Message Count Ch 11R
0x1C00Transmit FIFO Message Buffer Ch 12W0x1C14Transmit FIFO Message Count Ch 12R
0x110CTransmit FIFO Almost Empty Threshold Ch 1R/W0x111CTransmit FIFO Rate Ch 1R/W
0x120CTransmit FIFO Almost Empty Threshold Ch 2R/W0x121CTransmit FIFO Rate Ch 2R/W
0x130CTransmit FIFO Almost Empty Threshold Ch 3R/W0x131CTransmit FIFO Rate Ch 3R/W
0x140CTransmit FIFO Almost Empty Threshold Ch 4R/W0x141CTransmit FIFO Rate Ch 4R/W
0x150CTransmit FIFO Almost Empty Threshold Ch 5R/W0x151CTransmit FIFO Rate Ch 5R/W
0x160CTransmit FIFO Almost Empty Threshold Ch 6R/W0x161CTransmit FIFO Rate Ch 6R/W
0x170CTransmit FIFO Almost Empty Threshold Ch 7R/W0x171CTransmit FIFO Rate Ch 7R/W
0x180CTransmit FIFO Almost Empty Threshold Ch 8R/W0x181CTransmit FIFO Rate Ch 8R/W
0x190CTransmit FIFO Almost Empty Threshold Ch 9R/W0x191CTransmit FIFO Rate Ch 9R/W
0x1A0CTransmit FIFO Almost Empty Threshold Ch 10R/W0x1A1CTransmit FIFO Rate Ch 10R/W
0x1B0CTransmit FIFO Almost Empty Threshold Ch 11R/W0x1B1CTransmit FIFO Rate Ch 11R/W
0x1C0CTransmit FIFO Almost Empty Threshold Ch 12R/W0x1C1CTransmit FIFO Rate Ch 12R/W
TRANSMIT SCHEDULING REGISTERS
NOTE: Base Address - 0x4000 0000
![](/modules/AR1/images/AR01_Img04.jpg)
![](/modules/AR1/images/AR01_Img05.jpg)
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x1120Async Transmit Data Ch 1R/W
0x1220Async Transmit Data Ch 2R/W
0x1320Async Transmit Data Ch 3R/W
0x1420Async Transmit Data Ch 4R/W
0x1520Async Transmit Data Ch 5R/W
0x1620Async Transmit Data Ch 6R/W
0x1720Async Transmit Data Ch 7R/W
0x1820Async Transmit Data Ch 8R/W
0x1920Async Transmit Data Ch 9R/W
0x1A20Async Transmit Data Ch 10R/W
0x1B20Async Transmit Data Ch 11R/W
0x1C20Async Transmit Data Ch 12R/W
TRANSMIT CONTROL REGISTERS
NOTE: Base Address - 0x4000 0000
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x1000Tx TriggerR/W0x1004Tx PauseR/W
0x1008Tx StopR/W
CONTROL REGISTERS
NOTE: Base Address - 0x400 0000
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x1118Channel Control Ch 1R/W0x1014Module ResetW
0x1218Channel Control Ch 2R/W
0x1318Channel Control Ch 3R/W
0x1418Channel Control Ch 4R/W
0x1518Channel Control Ch 5R/W
0x1618Channel Control Ch 6R/W
0x1718Channel Control Ch 7R/W
0x1818Channel Control Ch 8R/W
0x1918Channel Control Ch 9R/W
0x1A18Channel Control Ch 10R/W
0x1B18Channel Control Ch 11R/W
0x1C18Channel Control Ch 12R/W
MODULE COMMON REGISTERS
Refer to “Module Common Registers Module Manual” for the Module Common Registers Function Register Map.
BIT REGISTERS
*When an event is detected, the bit associated with the event is set in this register and will remain set until the user clears the event bit. Clearing the bit requires writing a '1' back to the specific bit that was set when read (i.e., write-1-to-clear, writing a “1” to a bit set to “1” will set the bit to “0).
NOTE: Base Address - 0x4000 0000
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x0800Dynamic StatusR
0x0804Latched Status*R/W
0x0808Interrupt EnableR/W
0x080CSet Edge/Level InterruptR/W
0x0248Test EnabledR/W0x02ACPower-on BIT Complete++R
0x02B8Background BIT ThresholdR/W0x02BCBIT Count ClearW
++After power-on, Power-on BIT Complete should be checked before reading the BIT Latched Status.
CHANNEL STATUS REGISTERS
NOTE: Base Address - 0x4000 0000
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x02B0Channel Status EnableR/W
*When an event is detected, the bit associated with the event is set in this register and will remain set until the user clears the event bit. Clearing the bit requires writing a '1' back to the specific bit that was set when read (i.e., write-1-to-clear, writing a “1” to a bit set to “1” will set the bit to “0).
NOTE: Base Address - 0x4000 0000
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x0810Dynamic Status Ch 1R0x0820Dynamic Status Ch 2R
0x0814Latched Status Ch 1*R/W0x0824Latched Status Ch 2*R/W
0x0818Interrupt Enable Ch 1R/W0x0828Interrupt Enable Ch 2R/W
0x081CSet Edge/Level Interrupt Ch 1R/W0x082CSet Edge/Level Interrupt Ch 2R/W
0x0830Dynamic Status Ch 3R0x0840Dynamic Status Ch 4R
0x0834Latched Status Ch 3*R/W0x0844Latched Status Ch 4*R/W
0x0838Interrupt Enable Ch 3R/W0x0848Interrupt Enable Ch 4R/W
0x083CSet Edge/Level Interrupt Ch 3R/W0x084CSet Edge/Level Interrupt Ch 4R/W
0x0850Dynamic Status Ch 5R0x0860Dynamic Status Ch 6R
0x0854Latched Status Ch 5*R/W0x0864Latched Status Ch 6*R/W
0x0858Interrupt Enable Ch 5R/W0x0868Interrupt Enable Ch 6R/W
0x085CSet Edge/Level Interrupt Ch 5R/W0x086CSet Edge/Level Interrupt Ch 6R/W
0x0870Dynamic Status Ch 7R0x0880Dynamic Status Ch 8R
0x0874Latched Status Ch 7*R/W0x0884Latched Status Ch 8*R/W
0x0878Interrupt Enable Ch 7R/W0x0888Interrupt Enable Ch 8R/W
0x087CSet Edge/Level Interrupt Ch 7R/W0x088CSet Edge/Level Interrupt Ch 8R/W
0x0890Dynamic Status Ch 9R0x08A0Dynamic Status Ch 10R
0x0894Latched Status Ch 9*R/W0x08A4Latched Status Ch 10*R/W
0x0898Interrupt Enable Ch 9R/W0x08A8Interrupt Enable Ch 10R/W
0x089CSet Edge/Level Interrupt Ch 9R/W0x08ACSet Edge/Level Interrupt Ch 10R/W
0x08B0Dynamic Status Ch 11R0x08C0Dynamic Status Ch 12R
0x08B4Latched Status Ch 11*R/W0x08C4Latched Status Ch 12*R/W
0x08B8Interrupt Enable Ch 11R/W0x08C8Interrupt Enable Ch 12R/W
0x08BCSet Edge/Level Interrupt Ch 11R/W0x08CCSet Edge/Level Interrupt Ch 12R/W
INTERRUPT REGISTERS
The Interrupt Vector and Interrupt Steering registers are located on the Motherboard Memory Space and do not require any Module Address Offsets. These registers are accessed using the absolute addresses listed in the table below.
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x0500Module 1 Interrupt Vector 1 - BITR/W0x0600Module 1 Interrupt Steering 1 - BITR/W
0x0504Module 1 Interrupt Vector 2 - Channel Status Ch 1R/W0x0604Module 1 Interrupt Steering 2 - Channel Status Ch 1R/W
0x0508Module 1 Interrupt Vector 3 - Channel Status Ch 2R/W0x0608Module 1 Interrupt Steering 3 - Channel Status Ch 2R/W
0x050CModule 1 Interrupt Vector 4 - Channel Status Ch 3R/W0x060CModule 1 Interrupt Steering 4 - Channel Status Ch 3R/W
0x0510Module 1 Interrupt Vector 5 - Channel Status Ch 4R/W0x0610Module 1 Interrupt Steering 5 - Channel Status Ch 4R/W
0x0514Module 1 Interrupt Vector 6 - Channel Status Ch 5R/W0x0614Module 1 Interrupt Steering 6 - Channel Status Ch 5R/W
0x0518Module 1 Interrupt Vector 7 - Channel Status Ch 6R/W0x0618Module 1 Interrupt Steering 7 - Channel Status Ch 6R/W
0x051CModule 1 Interrupt Vector 8 - Channel Status Ch 7R/W0x061CModule 1 Interrupt Steering 8 - Channel Status Ch 7R/W
0x0520Module 1 Interrupt Vector 9 - Channel Status Ch 8R/W0x0620Module 1 Interrupt Steering 9 - Channel Status Ch 8R/W
0x0524Module 1 Interrupt Vector 10 - Channel Status Ch 9R/W0x0624Module 1 Interrupt Steering 10 - Channel Status Ch 9R/W
0x0528Module 1 Interrupt Vector 11 - Channel Status Ch 10R/W0x0628Module 1 Interrupt Steering 11 - Channel Status Ch 10R/W
0x052CModule 1 Interrupt Vector 12 - Channel Status Ch 11R/W0x062CModule 1 Interrupt Steering 12 - Channel Status Ch 11R/W
0x0530Module 1 Interrupt Vector 13 - Channel Status Ch 12R/W0x0630Module 1 Interrupt Steering 13 - Channel Status Ch 12R/W
0x0534 to 0x0564Module 1 Interrupt Vector 14 to 26 - ReservedR/W0x0634 to 0x0664Module 1 Interrupt Steering 14 to 26 - ReservedR/W
0x0568Module 1 Interrupt Vector 27 - Summary StatusR/W0x0668Module 1 Interrupt Steering 27 - Summary StatusR/W
0x056C to 0x057CModule 1 Interrupt Vector 28 to 32 - ReservedR/W0x066C to 0x067CModule 1 Interrupt Steering 28 to 32 - ReservedR/W
0x0700Module 2 Interrupt Vector 1 - BITR/W0x0800Module 2 Interrupt Steering 1 - BITR/W
0x0704Module 2 Interrupt Vector 2 - Channel Status Ch 1R/W0x0804Module 2 Interrupt Steering 2 - Channel Status Ch 1R/W
0x0708Module 2 Interrupt Vector 3 - Channel Status Ch 2R/W0x0808Module 2 Interrupt Steering 3 - Channel Status Ch 2R/W
0x070CModule 2 Interrupt Vector 4 - Channel Status Ch 3R/W0x080CModule 2 Interrupt Steering 4 - Channel Status Ch 3R/W
0x0710Module 2 Interrupt Vector 5 - Channel Status Ch 4R/W0x0810Module 2 Interrupt Steering 5 - Channel Status Ch 4R/W
0x0714Module 2 Interrupt Vector 6 - Channel Status Ch 5R/W0x0814Module 2 Interrupt Steering 6 - Channel Status Ch 5R/W
0x0718Module 2 Interrupt Vector 7 - Channel Status Ch 6R/W0x0818Module 2 Interrupt Steering 7 - Channel Status Ch 6R/W
0x071CModule 2 Interrupt Vector 8 - Channel Status Ch 7R/W0x081CModule 2 Interrupt Steering 8 - Channel Status Ch 7R/W
0x0720Module 2 Interrupt Vector 9 - Channel Status Ch 8R/W0x0820Module 2 Interrupt Steering 9 - Channel Status Ch 8R/W
0x0724Module 2 Interrupt Vector 10 - Channel Status Ch 9R/W0x0824Module 2 Interrupt Steering 10 - Channel Status Ch 9R/W
0x0728Module 2 Interrupt Vector 11 - Channel Status Ch 10R/W0x0828Module 2 Interrupt Steering 11 - Channel Status Ch 10R/W
0x072CModule 2 Interrupt Vector 12 - Channel Status Ch 11R/W0x082CModule 2 Interrupt Steering 12 - Channel Status Ch 11R/W
0x0730Module 2 Interrupt Vector 13 - Channel Status Ch 12R/W0x0830Module 2 Interrupt Steering 13 - Channel Status Ch 12R/W
0x0734 to 0x0764Module 2 Interrupt Vector 14 to 26 - ReservedR/W0x0834 to 0x0864Module 2 Interrupt Steering 14 to 26 - ReservedR/W
0x0768Module 2 Interrupt Vector 27 - Summary StatusR/W0x0868Module 2 Interrupt Steering 27 - Summary StatusR/W
0x076C to 0x077CModule 2 Interrupt Vector 28 to 32 - ReservedR/W0x086C to 0x087CModule 2 Interrupt Steering 28 to 32 - ReservedR/W
0x0900Module 3 Interrupt Vector 1 - BITR/W0x0A00Module 3 Interrupt Steering 1 - BITR/W
0x0904Module 3 Interrupt Vector 2 - Channel Status Ch 1R/W0x0A04Module 3 Interrupt Steering 2 - Channel Status Ch 1R/W
0x0908Module 3 Interrupt Vector 3 - Channel Status Ch 2R/W0x0A08Module 3 Interrupt Steering 3 - Channel Status Ch 2R/W
0x090CModule 3 Interrupt Vector 4 - Channel Status Ch 3R/W0x0A0CModule 3 Interrupt Steering 4 - Channel Status Ch 3R/W
0x0910Module 3 Interrupt Vector 5 - Channel Status Ch 4R/W0x0A10Module 3 Interrupt Steering 5 - Channel Status Ch 4R/W
0x0914Module 3 Interrupt Vector 6 - Channel Status Ch 5R/W0x0A14Module 3 Interrupt Steering 6 - Channel Status Ch 5R/W
0x0918Module 3 Interrupt Vector 7 - Channel Status Ch 6R/W0x0A18Module 3 Interrupt Steering 7 - Channel Status Ch 6R/W
0x091CModule 3 Interrupt Vector 8 - Channel Status Ch 7R/W0x0A1CModule 3 Interrupt Steering 8 - Channel Status Ch 7R/W
0x0920Module 3 Interrupt Vector 9 - Channel Status Ch 8R/W0x0A20Module 3 Interrupt Steering 9 - Channel Status Ch 8R/W
0x0924Module 3 Interrupt Vector 10 - Channel Status Ch 9R/W0x0A24Module 3 Interrupt Steering 10 - Channel Status Ch 9R/W
0x0928Module 3 Interrupt Vector 11 - Channel Status Ch 10R/W0x0A28Module 3 Interrupt Steering 11 - Channel Status Ch 10R/W
0x092CModule 3 Interrupt Vector 12 - Channel Status Ch 11R/W0x0A2CModule 3 Interrupt Steering 12 - Channel Status Ch 11R/W
0x0930Module 3 Interrupt Vector 13 - Channel Status Ch 12R/W0x0A30Module 3 Interrupt Steering 13 - Channel Status Ch 12R/W
0x0934 to 0x0964Module 3 Interrupt Vector 14 to 26 - ReservedR/W0x0A34 to 0x0A64Module 3 Interrupt Steering 14 to 26 - ReservedR/W
0x0968Module 3 Interrupt Vector 27 - Summary StatusR/W0x0A68Module 3 Interrupt Steering 27 - Summary StatusR/W
0x096C to 0x097CModule 3 Interrupt Vector 28 to 32 - ReservedR/W0x0A6C to 0x0A7CModule 3 Interrupt Steering 28 to 32 - ReservedR/W
0x0B00Module 4 Interrupt Vector 1 - BITR/W0x0C00Module 4 Interrupt Steering 1 - BITR/W
0x0B04Module 4 Interrupt Vector 2 - Channel Status Ch 1R/W0x0C04Module 4 Interrupt Steering 2 - Channel Status Ch 1R/W
0x0B08Module 4 Interrupt Vector 3 - Channel Status Ch 2R/W0x0C08Module 4 Interrupt Steering 3 - Channel Status Ch 2R/W
0x0B0CModule 4 Interrupt Vector 4 - Channel Status Ch 3R/W0x0C0CModule 4 Interrupt Steering 4 - Channel Status Ch 3R/W
0x0B10Module 4 Interrupt Vector 5 - Channel Status Ch 4R/W0x0C10Module 4 Interrupt Steering 5 - Channel Status Ch 4R/W
0x0B14Module 4 Interrupt Vector 6 - Channel Status Ch 5R/W0x0C14Module 4 Interrupt Steering 6 - Channel Status Ch 5R/W
0x0B18Module 4 Interrupt Vector 7 - Channel Status Ch 6R/W0x0C18Module 4 Interrupt Steering 7 - Channel Status Ch 6R/W
0x0B1CModule 4 Interrupt Vector 8 - Channel Status Ch 7R/W0x0C1CModule 4 Interrupt Steering 8 - Channel Status Ch 7R/W
0x0B20Module 4 Interrupt Vector 9 - Channel Status Ch 8R/W0x0C20Module 4 Interrupt Steering 9 - Channel Status Ch 8R/W
0x0B24Module 4 Interrupt Vector 10 - Channel Status Ch 9R/W0x0C24Module 4 Interrupt Steering 10 - Channel Status Ch 9R/W
0x0B28Module 4 Interrupt Vector 11 - Channel Status Ch 10R/W0x0C28Module 4 Interrupt Steering 11 - Channel Status Ch 10R/W
0x0B2CModule 4 Interrupt Vector 12 - Channel Status Ch 11R/W0x0C2CModule 4 Interrupt Steering 12 - Channel Status Ch 11R/W
0x0B30Module 4 Interrupt Vector 13 - Channel Status Ch 12R/W0x0C30Module 4 Interrupt Steering 13 - Channel Status Ch 12R/W
0x0B34 to 0x0B64Module 4 Interrupt Vector 14 to 26 - ReservedR/W0x0C34 to 0x0C64Module 4 Interrupt Steering 14 to 26 - ReservedR/W
0x0B68Module 4 Interrupt Vector 27 - Summary StatusR/W0x0C68Module 4 Interrupt Steering 27 - Summary StatusR/W
0x0B6C to 0x0B7CModule 4 Interrupt Vector 28 to 32 - ReservedR/W0x0C6C to 0x0C7CModule 4 Interrupt Steering 28 to 32 - ReservedR/W
0x0D00Module 5 Interrupt Vector 1 - BITR/W0x0E00Module 5 Interrupt Steering 1 - BITR/W
0x0D04Module 5 Interrupt Vector 2 - Channel Status Ch 1R/W0x0E04Module 5 Interrupt Steering 2 - Channel Status Ch 1R/W
0x0D08Module 5 Interrupt Vector 3 - Channel Status Ch 2R/W0x0E08Module 5 Interrupt Steering 3 - Channel Status Ch 2R/W
0x0D0CModule 5 Interrupt Vector 4 - Channel Status Ch 3R/W0x0E0CModule 5 Interrupt Steering 4 - Channel Status Ch 3R/W
0x0D10Module 5 Interrupt Vector 5 - Channel Status Ch 4R/W0x0E10Module 5 Interrupt Steering 5 - Channel Status Ch 4R/W
0x0D14Module 5 Interrupt Vector 6 - Channel Status Ch 5R/W0x0E14Module 5 Interrupt Steering 6 - Channel Status Ch 5R/W
0x0D18Module 5 Interrupt Vector 7 - Channel Status Ch 6R/W0x0E18Module 5 Interrupt Steering 7 - Channel Status Ch 6R/W
0x0D1CModule 5 Interrupt Vector 8 - Channel Status Ch 7R/W0x0E1CModule 5 Interrupt Steering 8 - Channel Status Ch 7R/W
0x0D20Module 5 Interrupt Vector 9 - Channel Status Ch 8R/W0x0E20Module 5 Interrupt Steering 9 - Channel Status Ch 8R/W
0x0D24Module 5 Interrupt Vector 10 - Channel Status Ch 9R/W0x0E24Module 5 Interrupt Steering 10 - Channel Status Ch 9R/W
0x0D28Module 5 Interrupt Vector 11 - Channel Status Ch 10R/W0x0E28Module 5 Interrupt Steering 11 - Channel Status Ch 10R/W
0x0D2CModule 5 Interrupt Vector 12 - Channel Status Ch 11R/W0x0E2CModule 5 Interrupt Steering 12 - Channel Status Ch 11R/W
0x0D30Module 5 Interrupt Vector 13 - Channel Status Ch 12R/W0x0E30Module 5 Interrupt Steering 13 - Channel Status Ch 12R/W
0x0D34 to 0x0D64Module 5 Interrupt Vector 14 to 26 - ReservedR/W0x0E34 to 0x0E64Module 5 Interrupt Steering 14 to 26 - ReservedR/W
0x0D68Module 5 Interrupt Vector 27 - Summary StatusR/W0x0E68Module 5 Interrupt Steering 27 - Summary StatusR/W
0x0D6C to 0x0D7CModule 5 Interrupt Vector 28 to 32 - ReservedR/W0x0E6C to 0x0E7CModule 5 Interrupt Steering 28 to 32 - ReservedR/W
0x0F00Module 6 Interrupt Vector 1 - BITR/W0x1000Module 6 Interrupt Steering 1 - BITR/W
0x0F04Module 6 Interrupt Vector 2 - Channel Status Ch 1R/W0x1004Module 6 Interrupt Steering 2 - Channel Status Ch 1R/W
0x0F08Module 6 Interrupt Vector 3 - Channel Status Ch 2R/W0x1008Module 6 Interrupt Steering 3 - Channel Status Ch 2R/W
0x0F0CModule 6 Interrupt Vector 4 - Channel Status Ch 3R/W0x100CModule 6 Interrupt Steering 4 - Channel Status Ch 3R/W
0x0F10Module 6 Interrupt Vector 5 - Channel Status Ch 4R/W0x1010Module 6 Interrupt Steering 5 - Channel Status Ch 4R/W
0x0F14Module 6 Interrupt Vector 6 - Channel Status Ch 5R/W0x1014Module 6 Interrupt Steering 6 - Channel Status Ch 5R/W
0x0F18Module 6 Interrupt Vector 7 - Channel Status Ch 6R/W0x1018Module 6 Interrupt Steering 7 - Channel Status Ch 6R/W
0x0F1CModule 6 Interrupt Vector 8 - Channel Status Ch 7R/W0x101CModule 6 Interrupt Steering 8 - Channel Status Ch 7R/W
0x0F20Module 6 Interrupt Vector 9 - Channel Status Ch 8R/W0x1020Module 6 Interrupt Steering 9 - Channel Status Ch 8R/W
0x0F24Module 6 Interrupt Vector 10 - Channel Status Ch 9R/W0x1024Module 6 Interrupt Steering 10 - Channel Status Ch 9R/W
0x0F28Module 6 Interrupt Vector 11 - Channel Status Ch 10R/W0x1028Module 6 Interrupt Steering 11 - Channel Status Ch 10R/W
0x0F2CModule 6 Interrupt Vector 12 - Channel Status Ch 11R/W0x102CModule 6 Interrupt Steering 12 - Channel Status Ch 11R/W
0x0F30Module 6 Interrupt Vector 13 - Channel Status Ch 12R/W0x1030Module 6 Interrupt Steering 13 - Channel Status Ch 12R/W
0x0F34 to 0x0F64Module 6 Interrupt Vector 14 to 26 - ReservedR/W0x1034 to 0x1064Module 6 Interrupt Steering 14 to 26 - ReservedR/W
0x0F68Module 6 Interrupt Vector 27 - Summary StatusR/W0x1068Module 6 Interrupt Steering 27 - Summary StatusR/W
0x0F6C to 0x0F7CModule 6 Interrupt Vector 28 to 32 - ReservedR/W0x106C to 0x107CModule 6 Interrupt Steering 28 to 32 - ReservedR/W

ARINC 429/575 HARDWARE BLOCK DIAGRAM

Figure 1. AR1 Hardware Block Diagram

ARINC 429/575 PROCESSING BLOCK DIAGRAM

Figure 2. AR1 Processing Block Diagram

APPENDIX A: REGISTER NAME CHANGES FROM PREVIOUS RELEASES

This section provides a mapping of the register names used in this document against register names used in previous releases.

Rev C - Register NamesRev B - Register Names
Receive FIFO Mode Registers
Receive FIFO Message BufferReceive FIFO Message Buffer
Receive FIFO Message CountReceive FIFO Message Count
Receive FIFO Almost Full ThresholdReceive FIFO Almost Full Threshold
Receive FIFO SizeReceive FIFO Size
Receive Mailbox Mode Registers
Receive FIFO SDI/Label BufferReceive FIFO SDI/Label Buffer
Receive FIFO SDI/Label CountReceive FIFO SDI/Label Count
Receive FIFO Almost Full ThresholdReceive FIFO Almost Full Threshold
Receive FIFO SizeReceive FIFO Size
Mailbox Status DataMailbox Status Data
Mailbox Message DataMailbox Message Data
Mailbox Timestamp DataMailbox Timestamp Data
Timestamp Registers
Timestamp ControlTimestamp Control
Timestamp ValueTimestamp Value
Message Validation Registers
Match EnableMatch Enable
Transmit FIFO Registers
Transmit FIFO Message BufferTransmit FIFO Message Buffer
Transmit FIFO Message CountTransmit FIFO Message Count
Transmit FIFO Almost Empty ThresholdTransmit FIFO Almost Empty Threshold
Transmit FIFO RateTransmit FIFO Rate
Transmit Scheduling Registers
Transmit Schedule RAM Command FormatTransmit Schedule RAM Command Format
Transmit Message RAM Data FormatTransmit Message RAM Data Format
Async Transmit DataAsync Transmit Data
Transmit Control Registers
Transmit TriggerTransmit Trigger
Transmit PauseTransmit Pause
Transmit StopTransmit Stop
Control Registers
Channel ControlChannel Control
Module ResetModule Reset
ARINC 429/575 Test Registers
Test EnabledTest Enabled
Background BIT Threshold Programming Registers
Background BIT ThresholdBackground BIT Threshold
Reset BITReset BIT
Status and Interrupt Registers
Channel Status Enabled
BIT Dynamic StatusBIT Dynamic Status
BIT Latched StatusBIT Latched Status
BIT Interrupt EnableBIT Interrupt Enable
BIT Set Edge/Level InterruptBIT Set Edge/Level Interrupt
Channel Dynamic StatusChannel Dynamic Status
Channel Latched StatusChannel Latched Status
Channel Interrupt EnableChannel Interrupt Enable
Channel Set Edge/Level InterruptChannel Set Edge/Level Interrupt
Summary Dynamic StatusSummary Dynamic Status
Summary Latched StatusSummary Latched Status
Summary Interrupt EnableSummary Interrupt Enable
Summary Set Edge/Level InterruptSummary Set Edge/Level Interrupt

APPENDIX B: PIN-OUT DETAILS

Pin-out details (for reference) are shown below, with respect to DATAIO. Additional information on pin-outs can be found in the Motherboard Operational Manuals.

[columns = “1,1,1,1,1,1,1”]

Module Signal + (Ref Only)44-Pin I/O50-Pin I/O (Mod Slot 1-J3)50-Pin I/O (Mod Slot 2-J4)50-Pin I/O (Mod Slot 3-J3)50-Pin I/O (Mod Slot 3-J4)ARINC 429/575 + (AR1)
DATIO121012AR429-A-CH01
DATIO224352627AR429-B-CH01
DATIO331123AR429-A-CH02
DATIO425362728AR429-B-CH02
DATIO551345AR429-A-CH03
DATIO627382930AR429-B-CH03
DATIO771456AR429-A-CH04
DATIO829393031AR429-B-CH04
DATIO981567AR429-A-CH05
DATIO1030403132AR429-B-CH05
DATIO11101789AR429-A-CH06
DATIO1232423334AR429-B-CH06
DATIO131218917AR429-A-CH07
DATIO1434433442AR429-B-CH07
DATIO1513191018AR429-A-CH08
DATIO1635443543AR429-B-CH08
DATIO1715211220AR429-A-CH09
DATIO1837463745AR429-B-CH09
DATIO1917221321AR429-A-CH10
DATIO2039473846AR429-B-CH10
DATIO2118231422AR429-A-CH11
DATIO2240483947AR429-B-CH11
DATIO2320251624AR429-A-CH12
DATIO2442504149AR429-B-CH12
DATIO2541234
DATIO2626372829
DATIO2791678
DATIO2831413233
DATIO2914201119
DATIO3036453644
DATIO3119241523
DATIO3241494048
DATIO336
DATIO3428
DATIO3511
DATIO3633
DATIO3716
DATIO3838
DATIO3921
DATIO4043
N/A

FIRMWARE REVISION NOTES

This section identifies the firmware revision in which specific features were released. Prior revisions of the firmware would not support the features listed.

FeatureFPGABare Metal (BM)
Firmware RevisionRelease DateFirmware RevisionRelease Date
Background BIT Threshold Programming1.000229/18/2019 4:23:29 PM2.31/10/2020 11:05:30 AM
Test Enabled1.000229/18/2019 4:23:29 PM2.31/10/2020 11:05:30 AM
Summary Status1.000229/18/2019 4:23:29 PM2.31/10/2020 11:05:30 AM

REVISION HISTORY

Module Manual - AR1 Revision History

C2023-06-13EC0 C10472, transition to docbuilder format. Replaced “Specifications” section with “Data Sheet” section”. Pg.7, updated Introduction; replaced Features with AR1 Overview. Pg.16, added Timestamp Control Registers bit definition table. Pg.17, added Timestamp Value bit table. Pg.22, added bit D21; made bit D11 reserved. Pg.23, changed bit D5 from SPEED to HIGH SPEED. Pg.26, added Channel Status Enabled. Pg.28, removed Summary Events Table. Pg.35, added Channel Status Enabled offset. Pg.45, added Channel Status Enabled to Appendix A. Pg.46, added Appendix B.
C12023-07-28EC0 C10590, pg.5, updated 2nd and 3rd sentence of 4th paragraph in general description.
C22024-01-12AR1 ECO C11154, pg.11/25/34, added module common registers.

DOCS.NAII REVISIONS

Revision DateDescription
2026-05-01Formatting updates throughout manual (non-technical changes).

STATUS AND INTERRUPTS

Status registers indicate the detection of faults or events. The status registers can be channel bit-mapped or event bit-mapped. An example of a channel bit-mapped register is the BIT status register, and an example of an event bit-mapped register is the FIFO status register.

For those status registers that allow interrupts to be generated upon the detection of the fault or the event, there are four registers associated with each status: Dynamic, Latched, Interrupt Enabled, and Set Edge/Level Interrupt.

Dynamic Status: The Dynamic Status register indicates the current condition of the fault or the event. If the fault or the event is momentary, the contents in this register will be clear when the fault or the event goes away. The Dynamic Status register can be polled, however, if the fault or the event is sporadic, it is possible for the indication of the fault or the event to be missed.

Latched Status: The Latched Status register indicates whether the fault or the event has occurred and keeps the state until it is cleared by the user. Reading the Latched Status register is a better alternative to polling the Dynamic Status register because the contents of this register will not clear until the user commands to clear the specific bit(s) associated with the fault or the event in the Latched Status register. Once the status register has been read, the act of writing a 1 back to the applicable status register to any specific bit (channel/event) location will “clear” the bit (set the bit to 0). When clearing the channel/event bits, it is strongly recommended to write back the same bit pattern as read from the Latched Status register. For example, if the channel bit-mapped Latched Status register contains the value 0x0000 0005, which indicates fault/event detection on channel 1 and 3, write the value 0x0000 0005 to the Latched Status register to clear the fault/event status for channel 1 and 3. Writing a “1” to other channels that are not set (example 0x0000 000F) may result in incorrectly “clearing” incoming faults/events for those channels (example, channel 2 and 4).

Interrupt Enable: If interrupts are preferred upon the detection of a fault or an event, enable the specific channel/event interrupt in the Interrupt Enable register. The bits in Interrupt Enable register map to the same bits in the Latched Status register. When a fault or event occurs, an interrupt will be fired. Subsequent interrupts will not trigger until the application acknowledges the fired interrupt by clearing the associated channel/event bit in the Latched Status register. If the interruptible condition is still persistent after clearing the bit, this may retrigger the interrupt depending on the Edge/Level setting.

Set Edge/Level Interrupt: When interrupts are enabled, the condition on retriggering the interrupt after the Latch Register is “cleared” can be specified as “edge” triggered or “level” triggered. Note, the Edge/Level Trigger also affects how the Latched Register value is adjusted after it is “cleared” (see below).

  • Edge triggered: An interrupt will be retriggered when the Latched Status register change from low (0) to high (1) state. Uses for edge-triggered interrupts would include transition detections (Low-to-High transitions, High-to-Low transitions) or fault detections. After “clearing” an interrupt, another interrupt will not occur until the next transition or the re-occurrence of the fault again.

  • Level triggered: An interrupt will be generated when the Latched Status register remains at the high (1) state. Level-triggered interrupts are used to indicate that something needs attention.

Interrupt Vector and Steering

When interrupts are enabled, the interrupt vector associated with the specific interrupt can be programmed with a unique number/identifier defined by the user such that it can be utilized in the Interrupt Service Routine (ISR) to identify the type of interrupt. When an interrupt occurs, the contents of the Interrupt Vector registers is reported as part of the interrupt mechanism. In addition to specifying the interrupt vector, the interrupt can be directed (“steered”) to the native bus or to the application running on the onboard ARM processor.

Interrupt Trigger Types

In most applications, limiting the number of interrupts generated is preferred as interrupts are costly, thus choosing the correct Edge/Level interrupt trigger to use is important.

Example 1: Fault detection

This example illustrates interrupt considerations when detecting a fault like an “open” on a line. When an “open” is detected, the system will receive an interrupt. If the “open” on the line is persistent and the trigger is set to “edge”, upon “clearing” the interrupt, the system will not regenerate another interrupt. If, instead, the trigger is set to “level”, upon “clearing” the interrupt, the system will re-generate another interrupt. Thus, in this case, it will be better to set the trigger type to “edge”.

Example 2: Threshold detection

This example illustrates interrupt considerations when detecting an event like reaching or exceeding the “high watermark” threshold value. In a communication device, when the number of elements received in the FIFO reaches the high-watermark threshold, an interrupt will be generated. Normally, the application would read the count of the number of elements in the FIFO and read this number of elements from the FIFO. After reading the FIFO data, the application would “clear” the interrupt. If the trigger type is set to “edge”, another interrupt will be generated only if the number of elements in FIFO goes below the “high watermark” after the “clearing” the interrupt and then fills up to reach the “high watermark” threshold value. Since receiving communication data is inherently asynchronous, it is possible that data can continue to fill the FIFO as the application is pulling data off the FIFO. If, at the time the interrupt is “cleared”, the number of elements in the FIFO is at or above the “high watermark”, no interrupts will be generated. In this case, it will be better to set the trigger type to “level”, as the purpose here is to make sure that the FIFO is serviced when the number of elements exceeds the high watermark threshold value. Thus, upon “clearing” the interrupt, if the number of elements in the FIFO is at or above the “high watermark” threshold value, another interrupt will be generated indicating that the FIFO needs to be serviced.


Dynamic and Latched Status Registers Examples

The examples in this section illustrate the differences in behavior of the Dynamic Status and Latched Status registers as well as the differences in behavior of Edge/Level Trigger when the Latched Status register is cleared.

Figure 1. Example of Module’s Channel-Mapped Dynamic and Latched Status States

No Clearing of Latched StatusClearing of Latched Status (Edge-Triggered)Clearing of Latched Status(Level-Triggered)
TimeDynamic StatusLatched StatusActionLatched StatusActionLatched
T00x00x0Read Latched Register0x0Read Latched Register0x0
T10x10x1Read Latched Register0x10x1
T10x10x1Write 0x1 to Latched RegisterWrite 0x1 to Latched Register
T10x10x10x00x1
T20x00x1Read Latched Register0x0Read Latched Register0x1
T20x00x1Read Latched Register0x0Write 0x1 to Latched Register
T20x00x1Read Latched Register0x00x0
T30x20x3Read Latched Register0x2Read Latched Register0x2
T30x20x3Write 0x2 to Latched RegisterWrite 0x2 to Latched Register
T30x20x30x00x2
T40x20x3Read Latched Register0x1Read Latched Register0x3
T40x20x3Write 0x1 to Latched RegisterWrite 0x3 to Latched Register
T40x20x30x00x2
T50xC0xFRead Latched Register0xCRead Latched Register0xE
T50xC0xFWrite 0xC to Latched RegisterWrite 0xE to Latched Register
T50xC0xF0x00xC
T60xC0xFRead Latched Register0x0Read Latched0xC
T60xC0xFRead Latched Register0x0Write 0xC to Latched Register
T60xC0xFRead Latched Register0x00xC
T70x40xFRead Latched Register0x0Read Latched Register0xC
T70x40xFRead Latched Register0x0Write 0xC to Latched Register
T70x40xFRead Latched Register0x00x4
T80x40xFRead Latched Register0x0Read Latched Register0x4

Interrupt Examples

The examples in this section illustrate the interrupt behavior with Edge/Level Trigger.

Figure 2. Illustration of Latched Status State for Module with 4-Channels with Interrupt Enabled

TimeLatched Status (Edge-Triggered - Clear Multi-Channel)Latched Status (Edge-Triggered - Clear Single Channel) 2+Latched Status (Level-Triggered - Clear Multi-Channel)Action
LatchedActionLatchedActionLatchedT1 (Int 1)
Interrupt Generated++``+
Read Latched Registers
0x1Interrupt Generated++``+
Read Latched Registers
0x1Interrupt Generated++``+
Read Latched Registers
0x1T1 (Int 1)
Write 0x1 to Latched RegisterWrite 0x1 to Latched RegisterWrite 0x1 to Latched RegisterT1 (Int 1)
0x00x0Interrupt re-triggers++``+
Note, interrupt re-triggers after each clear until T2.
0x1T3 (Int 2)
Interrupt Generated++``+
Read Latched Registers
0x2Interrupt Generated++``+
Read Latched Registers
0x2Interrupt Generated++``+
Read Latched Registers
0x2T3 (Int 2)
Write 0x2 to Latched RegisterWrite 0x2 to Latched RegisterWrite 0x2 to Latched RegisterT3 (Int 2)
0x00x0Interrupt re-triggers++``+
Note, interrupt re-triggers after each clear until T7.
0x2T4 (Int 3)
Interrupt Generated++``+
Read Latched Registers
0x1Interrupt Generated++``+
Read Latched Registers
0x1Interrupt Generated++``+
Read Latched Registers
0x3T4 (Int 3)
Write 0x1 to Latched RegisterWrite 0x1 to Latched RegisterWrite 0x3 to Latched RegisterT4 (Int 3)
0x00x0Interrupt re-triggers++``+
Note, interrupt re-triggers after each clear and 0x3 is reported in Latched Register until T5.
0x3T4 (Int 3)
0x00x0Interrupt re-triggers++``+
Note, interrupt re-triggers after each clear until T7.
0x2T6 (Int 4)
Interrupt Generated++``+
Read Latched Registers
0xCInterrupt Generated++``+
Read Latched Registers
0xCInterrupt Generated++``+
Read Latched Registers
0xET6 (Int 4)
Write 0xC to Latched RegisterWrite 0x4 to Latched RegisterWrite 0xE to Latched RegisterT6 (Int 4)
0x0Interrupt re-triggers++``+
Write 0x8 to Latched Register
0x8Interrupt re-triggers++``+
Note, interrupt re-triggers after each clear and 0xE is reported in Latched Register until T7.
0xET6 (Int 4)
0x00x0Interrupt re-triggers++``+
Note, interrupt re-triggers after each clear and 0xC is reported in Latched Register until T8.
0xCT6 (Int 4)
0x00x0Interrupt re-triggers++``+
Note, interrupt re-triggers after each clear and 0x4 is reported in Latched Register always.
0x4

REVISION HISTORY

Motherboard Manual - Status and Interrupts Revision History
RevisionRevision DateDescription
C2021-11-30C08896; Transition manual to docbuilder format - no technical info change.

DOCS.NAII REVISIONS

Revision DateDescription
2026-03-02Formatting updates to document; no technical changes.
Link to original

MODULE COMMON REGISTERS

The registers described in this document are common to all NAI Generation 5 modules.

Module Information Registers

The registers in this section provide module information such as firmware revisions, capabilities and unique serial number information.

FPGA Version Registers

The FPGA firmware version registers include registers that contain the Revision, Compile Timestamp, SerDes Revision, Template Revision and Zynq Block Revision information.

FPGA Revision
Function:FPGA firmware revision
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Value corresponding to the revision of the board's FPGA
Operational Settings:The upper 16-bits are the major revision and the lower 16-bits are the minor revision.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Major Revision Number
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Minor Revision Number
FPGA Compile Timestamp
Function:Compile Timestamp for the FPGA firmware.
Type:unsigned binary word (32-bit)
Data Range:N/A
Read/Write:R
Initialized Value:Value corresponding to the compile timestamp of the board's FPGA
Operational Settings:The 32-bit value represents the Day, Month, Year, Hour, Minutes and Seconds as formatted in the table:
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
day (5-bits)month (4-bits)year (6-bits)hr
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
hour (5-bits)minutes (6-bits)seconds (6-bits)
FPGA SerDes Revision
Function:FPGA SerDes revision
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Value corresponding to the SerDes revision of the board's FPGA
Operational Settings:The upper 16-bits are the major revision, and the lower 16-bits are the minor revision.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Major Revision Number
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Minor Revision Number
FPGA Template Revision
Function:FPGA Template revision
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Value corresponding to the template revision of the board's FPGA
Operational Settings:The upper 16-bits are the major revision, and the lower 16-bits are the minor revision.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Major Revision Number
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Minor Revision Number
FPGA Zynq Block Revision
Function:FPGA Zynq Block revision
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Value corresponding to the Zynq block revision of the board's FPGA
Operational Settings:The upper 16-bits are the major revision, and the lower 16-bits are the minor revision.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Major Revision Number
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Minor Revision Number

Bare Metal Version Registers

The Bare Metal firmware version registers include registers that contain the Revision and Compile Time information.

Bare Metal Revision
Function:Bare Metal firmware revision
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Value corresponding to the revision of the board's Bare Metal
Operational Settings:The upper 16-bits are the major revision and the lower 16-bits are the minor revision.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Major Revision Number
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Minor Revision Number
Bare Metal Compile Time
Function:Provides an ASCII representation of the Date/Time for the Bare Metal compile time.
Type:24-character ASCII string - Six (6) unsigned binary word (32-bit)
Data Range:N/A
Read/Write:R
Initialized Value:Value corresponding to the ASCII representation of the compile time of the board's Bare Metal
Operational Settings:The six 32-bit words provide an ASCII representation of the Date/Time. The hexadecimal values in the field below represent: May 17 2019 at 15:38:32

Note

little-endian order of ASCII values

Word 1 (Ex. 0x2079614D)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Space (0x20)Month ('y' - 0x79)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Month ('a' - 0x61)Month ('M' - 0x4D)
Word 2 (Ex. 0x32203731)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Year ('2' - 0x32)Space (0x20)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Day ('7' - 0x37)Day ('1' - 0x31)
Word 3 (Ex. 0x20393130)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Space (0x20)Year ('9' - 0x39)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Year ('1' - 0x31)Year ('0' - 0x30)
Word 4 (Ex. 0x31207461)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Hour ('1' - 0x31)Space (0x20)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
'a' (0x74)'t' (0x61)
Word 5 (Ex. 0x38333A35)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Minute ('8' - 0x38)Minute ('3' - 0x33)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
':' (0x3A)Hour ('5' - 0x35)
Word 6 (Ex. 0x0032333A)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
NULL (0x00)Seconds ('2' - 0x32)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Seconds ('3' - 0x33)':' (0x3A)

FSBL Version Registers

The FSBL version registers include registers that contain the Revision and Compile Time information for the First Stage Boot Loader (FSBL).

FSBL Revision
Function:FSBL firmware revision
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Value corresponding to the revision of the board's FSBL
Operational Settings:The upper 16-bits are the major revision, and the lower 16-bits are the minor revision.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Major Revision Number
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Minor Revision Number
FSBL Compile Time
Function:Provides an ASCII representation of the Date/Time for the FSBL compile time.
Type:24-character ASCII string - Six (6) unsigned binary word (32-bit)
Data Range:N/A
Read/Write:R
Initialized Value:Value corresponding to the ASCII representation of the Compile Time of the board's FSBL
Operational Settings:The six 32-bit words provide an ASCII representation of the Date/Time.

The hexadecimal values in the field below represent: May 17 2019 at 15:38:32

Note

little-endian order of ASCII values

Word 1 (Ex. 0x2079614D)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Space (0x20)Month ('y' - 0x79)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Month ('a' - 0x61)Month ('M' - 0x4D)
Word 2 (Ex. 0x32203731)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Year ('2' - 0x32)Space (0x20)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Day ('7' - 0x37)Day ('1' - 0x31)
Word 3 (Ex. 0x20393130)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Space (0x20)Year ('9' - 0x39)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Year ('1' - 0x31)Year ('0' - 0x30)
Word 4 (Ex. 0x31207461)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Hour ('1' - 0x31)Space (0x20)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
'a' (0x74)'t' (0x61)
Word 5 (Ex. 0x38333A35)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Minute ('8' - 0x38)Minute ('3' - 0x33)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
':' (0x3A)Hour ('5' - 0x35)
Word 6 (Ex. 0x0032333A)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
NULL (0x00)Seconds ('2' - 0x32)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Seconds ('3' - 0x33)':' (0x3A)

Module Serial Number Registers

The Module Serial Number registers include registers that contain the Serial Numbers for the Interface Board and the Functional Board of the module.

Interface Board Serial Number
Function:Unique 128-bit identifier used to identify the interface board.
Type:16-character ASCII string - Four (4) unsigned binary words (32-bit)
Data Range:N/A
Read/Write:R
Initialized Value:Serial number of the interface board
Operational Settings:This register is for information purposes only.
Functional Board Serial Number
Function:Unique 128-bit identifier used to identify the functional board.
Type:16-character ASCII string - Four (4) unsigned binary words (32-bit)
Data Range:N/A
Read/Write:R
Initialized Value:Serial number of the functional board
Operational Settings:This register is for information purposes only.
Module Capability
Function:Provides indication for whether or not the module can support the following: SerDes block reads, SerDes FIFO block reads, SerDes packing (combining two 16-bit values into one 32-bit value) and floating point representation. The purpose for block access and packing is to improve the performance of accessing larger amounts of data over the SerDes interface.
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0x0000 0107
Read/Write:R
Initialized Value:0x0000 0107
Operational Settings:A “1” in the bit associated with the capability indicates that it is supported.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000000Flt-Pt00000PackFIFO BlkBlk
Module Memory Map Revision
Function:Module Memory Map revision
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Value corresponding to the Module Memory Map Revision
Operational Settings:The upper 16-bits are the major revision and the lower 16-bits are the minor revision.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Major Revision Number
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Minor Revision Number

Module Measurement Registers

The registers in this section provide module temperature measurement information.

Temperature Readings Registers

The temperature registers provide the current, maximum (from power-up) and minimum (from power-up) Zynq and PCB temperatures.

Interface Board Current Temperature
Function:Measured PCB and Zynq Core temperatures on Interface Board.
Type:signed byte (8-bits) for PCB and signed byte (8-bits) for Zynq core temperatures
Data Range:0x0000 0000 to 0x0000 FFFF
Read/Write:R
Initialized Value:Value corresponding to the measured PCB and Zynq core temperatures based on the table below
Operational Settings:The upper 16-bits are not used, and the lower 16-bits are the PCB and Zynq Core Temperatures. For example, if the register contains the value 0x0000 202C, this represents PCB Temperature = 32° Celsius and Zynq Temperature = 44° Celsius.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
PCB TemperatureZynq Core Temperature
Functional Board Current Temperature
Function:Measured PCB temperature on Functional Board.
Type:signed byte (8-bits) for PCB
Data Range:0x0000 0000 to 0x0000 00FF
Read/Write:R
Initialized Value:Value corresponding to the measured PCB on the table below
Operational Settings:The upper 24-bits are not used, and the lower 8-bits are the PCB Temperature. For example, if the register contains the value 0x0000 0019, this represents PCB Temperature = 25° Celsius.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000PCB Temperature
Interface Board Maximum Temperature
Function:Maximum PCB and Zynq Core temperatures on Interface Board since power-on.
Type:signed byte (8-bits) for PCB and signed byte (8-bits) for Zynq core temperatures
Data Range:0x0000 0000 to 0x0000 FFFF
Read/Write:R
Initialized Value:Value corresponding to the maximum measured PCB and Zynq core temperatures since power-on based on the table below
Operational Settings:The upper 16-bits are not used, and the lower 16-bits are the maximum PCB and Zynq Core Temperatures. For example, if the register contains the value 0x0000 5569, this represents maximum PCB Temperature = 85° Celsius and maximum Zynq Temperature = 105° Celsius.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
PCB TemperatureZynq Core Temperature
Interface Board Minimum Temperature
Function:Minimum PCB and Zynq Core temperatures on Interface Board since power-on.
Type:signed byte (8-bits) for PCB and signed byte (8-bits) for Zynq core temperatures
Data Range:0x0000 0000 to 0x0000 FFFF
Read/Write:R
Initialized Value:Value corresponding to the minimum measured PCB and Zynq core temperatures since power-on based on the table below
Operational Settings:The upper 16-bits are not used, and the lower 16-bits are the minimum PCB and Zynq Core Temperatures. For example, if the register contains the value 0x0000 D8E7, this represents minimum PCB Temperature = -40° Celsius and minimum Zynq Temperature = -25° Celsius.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
PCB TemperatureZynq Core Temperature
Functional Board Maximum Temperature
Function:Maximum PCB temperature on Functional Board since power-on.
Type:signed byte (8-bits) for PCB
Data Range:0x0000 0000 to 0x0000 00FF
Read/Write:R
Initialized Value:Value corresponding to the measured PCB on the table below
Operational Settings:The upper 24-bits are not used, and the lower 8-bits are the PCB Temperature. For example, if the register contains the value 0x0000 0055, this represents PCB Temperature = 85° Celsius.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000PCB Temperature
Functional Board Minimum Temperature
Function:Minimum PCB temperature on Functional Board since power-on.
Type:signed byte (8-bits) for PCB
Data Range:0x0000 0000 to 0x0000 00FF
Read/Write:R
Initialized Value:Value corresponding to the measured PCB on the table below
Operational Settings:The upper 24-bits are not used, and the lower 8-bits are the PCB Temperature. For example, if the register contains the value 0x0000 00D8, this represents PCB Temperature = -40° Celsius.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
00000000PCB Temperature

Higher Precision Temperature Readings Registers

These registers provide higher precision readings of the current Zynq and PCB temperatures.

Higher Precision Zynq Core Temperature
Function:Higher precision measured Zynq Core temperature on Interface Board.
Type:signed word (16-bits) for integer part and unsigned word (16-bits) for fractional part
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Measured Zynq Core temperature on Interface Board
Operational Settings:The upper 16-bits represent the signed integer part of the temperature and the lower 16-bits represent the fractional part of the temperature with the resolution of 1/1000 of degree Celsius. For example, if the register contains the value 0x002B 0271, this represents Zynq Core Temperature = 43.625° Celsius, and value 0xFFF6 0177 represents -10.375° Celsius.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Signed Integer Part of Temperature
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Fractional Part of Temperature
Higher Precision Interface PCB Temperature
Function:Higher precision measured Interface PCB temperature.
Type:signed word (16-bits) for integer part and unsigned word (16-bits) for fractional part
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Measured Interface PCB temperature
Operational Settings:The upper 16-bits represent the signed integer part of the temperature and the lower 16-bits represent the fractional part of the temperature with the resolution of 1/1000 of degree Celsius. For example, if the register contains the value 0x0020 007D, this represents Interface PCB Temperature = 32.125° Celsius, and value 0xFFE8 036B represents -24.875° Celsius.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Signed Integer Part of Temperature
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Fractional Part of Temperature
Higher Precision Functional PCB Temperature
Function:Higher precision measured Functional PCB temperature.
Type:signed word (16-bits) for integer part and unsigned word (16-bits) for fractional part
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Measured Functional PCB temperature
Operational Settings:The upper 16-bits represent the signed integer part of the temperature and the lower 16-bits represent the fractional part of the temperature with the resolution of 1/100 of degree Celsius. For example, if the register contains the value 0x0018 004B, this represents Functional PCB Temperature = 24.75° Celsius, and value 0xFFD9 0019 represents -39.25° Celsius.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Signed Integer Part of Temperature
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Fractional Part of Temperature

Module Health Monitoring Registers

The registers in this section provide module temperature measurement information. If the temperature measurements reaches the Lower Critical or Upper Critical conditions, the module will automatically reset itself to prevent damage to the hardware.

Module Sensor Summary Status
Function:The corresponding sensor bit is set if the sensor has crossed any of its thresholds.
Type:unsigned binary word (32-bits)
Data Range:See table below
Read/Write:R
Initialized Value:0
Operational Settings:This register provides a summary for module sensors. When the corresponding sensor bit is set, the Sensor Threshold Status register for that sensor will indicate the threshold condition that triggered the event.
Bit(s)Sensor
D31:D6Reserved
D5Functional Board PCB Temperature
D4Interface Board PCB Temperature
D3:D0Reserved

Module Sensor Registers

The registers listed in this section apply to each module sensor listed for the Module Sensor Summary Status register. Each individual sensor register provides a group of registers for monitoring module temperatures readings. From these registers, a user can read the current temperature of the sensor in addition to the minimum and maximum temperature readings since power-up. Upper and lower critical/warning temperature thresholds can be set and monitored from these registers. When a programmed temperature threshold is crossed, the Sensor Threshold Status register will set the corresponding bit for that threshold. The figure below shows the functionality of this group of registers when accessing the Interface Board PCB Temperature sensor as an example.

Sensor Threshold Status
Function:Reflects which threshold has been crossed
Type:unsigned binary word (32-bits)
Data Range:See table below
Read/Write:R
Initialized Value:0
Operational Settings:The associated bit is set when the sensor reading exceed the corresponding threshold settings.
Bit(s)Description
D31:D4Reserved
D3Exceeded Upper Critical Threshold
D2Exceeded Upper Warning Threshold
D1Exceeded Lower Critical Threshold
D0Exceeded Lower Warning Threshold
Sensor Current Reading
Function:Reflects current reading of temperature sensor
Type:Single Precision Floating Point Value (IEEE-754)
Data Range:Single Precision Floating Point Value (IEEE-754)
Read/Write:R
Initialized Value:N/A
Operational Settings:The register represents current sensor reading as a single precision floating point value. For example, for a temperature sensor, register value 0x41C6 0000 represents temperature = 24.75° Celsius.
Sensor Minimum Reading
Function:Reflects minimum value of temperature sensor since power up
Type:Single Precision Floating Point Value (IEEE-754)
Data Range:Single Precision Floating Point Value (IEEE-754)
Read/Write:R
Initialized Value:N/A
Operational Settings:The register represents minimum sensor value as a single precision floating point value. For example, for a temperature sensor, register value 0x41C6 0000 represents temperature = 24.75° Celsius.
Sensor Maximum Reading
Function:Reflects maximum value of temperature sensor since power up
Type:Single Precision Floating Point Value (IEEE-754)
Data Range:Single Precision Floating Point Value (IEEE-754)
Read/Write:R
Initialized Value:N/A
Operational Settings:The register represents maximum sensor value as a single precision floating point value. For example, for a temperature sensor, register value 0x41C6 0000 represents temperature = 24.75° Celsius.
Sensor Lower Warning Threshold
Function:Reflects lower warning threshold of temperature sensor
Type:Single Precision Floating Point Value (IEEE-754)
Data Range:Single Precision Floating Point Value (IEEE-754)
Read/Write:R/W
Initialized Value:Default lower warning threshold (value dependent on specific sensor)
Operational Settings:The register represents sensor lower warning threshold as a single precision floating point value. For example, for a temperature sensor, register value 0xC220 0000 represents temperature = -40.0° Celsius.
Sensor Lower Critical Threshold
Function:Reflects lower critical threshold of temperature sensor
Type:Single Precision Floating Point Value (IEEE-754)
Data Range:Single Precision Floating Point Value (IEEE-754)
Read/Write:R/W
Initialized Value:Default lower critical threshold (value dependent on specific sensor)
Operational Settings:The register represents sensor lower critical threshold as a single precision floating point value. For example, for a temperature sensor, register value 0xC25C 0000 represents temperature = -55.0° Celsius.
Sensor Upper Warning Threshold
Function:Reflects upper warning threshold of temperature sensor
Type:Single Precision Floating Point Value (IEEE-754)
Data Range:Single Precision Floating Point Value (IEEE-754)
Read/Write:R/W
Initialized Value:Default upper warning threshold (value dependent on specific sensor)
Operational Settings:The register represents sensor upper warning threshold as a single precision floating point value. For example, for a temperature sensor, register value 0x42AA 0000 represents temperature = 85.0° Celsius.
Sensor Upper Critical Threshold
Function:Reflects upper critical threshold of temperature sensor
Type:Single Precision Floating Point Value (IEEE-754)
Data Range:Single Precision Floating Point Value (IEEE-754)
Read/Write:R/W
Initialized Value:Default upper critical threshold (value dependent on specific sensor)
Operational Settings:The register represents sensor upper critical threshold as a single precision floating point value. For example, for a temperature sensor, register value 0x42FA 0000 represents temperature = 125.0° Celsius.

FUNCTION REGISTER MAP

KEY

Configuration/Control
Measurement/Status/Board Information
MODULE INFORMATION REGISTERS
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x003CFPGA RevisionR0x0074Bare Metal RevisionR
0x0030FPGA Compile TimestampR0x0080Bare Metal Compile Time (Bit 0-31)R
0x0034FPGA SerDes RevisionR0x0084Bare Metal Compile Time (Bit 32-63)R
0x0038FPGA Template RevisionR0x0088Bare Metal Compile Time (Bit 64-95)R
0x0040FPGA Zynq Block RevisionR0x008CBare Metal Compile Time (Bit 96-127)R
0x0090Bare Metal Compile Time (Bit 128-159)R
0x0094Bare Metal Compile Time (Bit 160-191)R
0x007CFSBL RevisionR
0x00B0FSBL Compile Time (Bit 0-31)R
0x00B4FSBL Compile Time (Bit 32-63)R
0x00B8FSBL Compile Time (Bit 64-95)R
0x00BCFSBL Compile Time (Bit 96-127)R
0x00C0FSBL Compile Time (Bit 128-159)R
0x00C4FSBL Compile Time (Bit 160-191)R
0x0000Interface Board Serial Number (Bit 0-31)R0x0010Functional Board Serial Number (Bit 0-31)R
0x0034Interface Board Serial Number (Bit 32-63)R0x0014Functional Board Serial Number (Bit 32-63)R
0x0008Interface Board Serial Number (Bit 64-95)R0x0018Functional Board Serial Number (Bit 64-95)R
0x000CInterface Board Serial Number (Bit 96-127)R0x001CFunctional Board Serial Number (Bit 96-127)R
0x0070Module CapabilityR
0x01FCModule Memory Map RevisionR
MODULE MEASUREMENTS REGISTERS
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x0200Interface Board PCB/Zynq Current TempR0x0208Functional Board PCB Current TempR
0x0218Interface Board PCB/Zynq Max TempR0x0228Functional Board PCB Max TempR
0x0220Interface Board PCB/Zynq Min TempR0x0230Functional Board PCB Min TempR
0x02C0Higher Precision Zynq Core TemperatureR
0x02C4Higher Precision Interface PCB TemperatureR
0x02E0Higher Precision Functional PCB TemperatureR
MODULE HEALTH MONITORING REGISTERS
OFFSETREGISTER NAMEACCESSOFFSETREGISTER NAMEACCESS
0x07F8Module Sensor Summary StatusR
![](/_shared/images/Module_Sensor_Registers_Memory_Map.png)

REVISION HISTORY

Motherboard Manual - Module Common Registers Revision History
RevisionRevision DateDescription
C2023-08-11ECO C10649, initial release of module common registers manual.
C12024-05-15ECO C11522, removed Zynq Core/Aux/DDR Voltage register descriptions from Module Measurement Registers. Pg.16, updated Module Sensor Summary Status register to add PS references; updated Bit Table to change voltage/current bits to 'reserved'. Pg.16, updated Module/Power Supply Sensor Registers description to better describe register functionality and to add figure. Pg.17, added 'Exceeded' to threshold bit descriptions. Pg.17-18, removed voltage/current references from sensor descriptions. Pg.20, removed Zynq Core/Aux/DDR Voltage register offsets from Module Measurement Registers. Pg.20, updated Module Health Monitoring Registers offset tables.
C22024-07-10ECO C11701, pg.16, updated Module Sensor Summary Status register to remove PS references;updated Bit Table to change PS temperature bits to 'reserved'. Pg.16, updated Module SensorRegisters description to remove PS references. Pg.20, updated Module Health MonitoringRegisters offset tables to remove PS temperature register offsets.

DOCS.NAII REVISIONS

Revision DateDescription
2025-11-05Corrected register offsets for Interface Board Min Temp and Function Board Min & Max Temps.
2026-03-02Formatting updates to document; no technical changes.
Link to original

NAI Cares

North Atlantic Industries (NAI) is a leading independent supplier of Embedded I/O Boards, Single Board Computers, Rugged Power Supplies, Embedded Systems and Motion Simulation and Measurement Instruments for the Military, Aerospace and Industrial Industries. We accelerate our clients’ time-to-mission with a unique approach based on a Configurable Open Systems Architecture™ (COSA®) that delivers the best of both worlds: custom solutions from standard COTS components.

We have built a reputation by listening to our customers, understanding their needs, and designing, testing and delivering board and system-level products for their most demanding air, land and sea requirements. If you have any applications or questions regarding the use of our products, please contact us for an expedient solution.

Please visit us at: www.naii.com or select one of the following for immediate assistance:

Documentation

https://www.docs.naii.com

FAQ

http://www.naii.com/faqs

Application Notes

http://www.naii.com/applicationnotes

Calibration and Repairs

http://www.naii.com/calibrationrepairs

Call Us

(631) 567-1100

Link to original