75G5 DATA SHEET

Click here for the 75G5 Data Sheet

INTRODUCTION

North Atlantic Industries (NAI) is a leading independent supplier of rugged COTS embedded computing products for industrial, commercial aerospace, and defense markets. Aligned with MOSA, SOSA and FACE standards, NAI’s Configurable Open System Architecture™ (COSA®) accelerates a customer’s time-to-mission by providing the most modular, agile, and rugged COTS portfolio of embedded smart modules, I/O boards, Single Board Computers (SBCs), Power Supplies and Ruggedized Systems of its kind. COSA products are pre-engineered to work together, enabling easy changes, reuses, or repurposing down the road. By utilizing FPGAs and SoCs, NAI has created smart modules that enable the rapid creation of configurable mission systems while reducing or eliminating SBC overhead.

NAI’s 75G5 3U cPCI Multifunction I/O and Communications Board is a compact, rugged processing board which provides low power/high-performance I/O capabilities specifically designed for demanding aerospace, defense, and industrial applications. When combined with these smart modules, the board’s modular I/O approach makes it a highly flexible and integrable solution for demanding computing environments.

75G5 Overview

The 75G5 3U cPCI Multifunction I/O and Communications Board offers a variety of features designed to meet the needs of complex requirements for integrated multifunction I/O-intensive, mission-critical applications. Some of the key features include:

3U cPCI Form Factor: The 75G5 is housed in a 3U cPCI form factor, ensuring compatibility with existing CompactPCI systems while providing a compact yet power solution for your application.

Control via Gig-E or PCI Bus: The 75G5 provides easy integration into a system by way of Gig-E or PCI Bus interface control capability. Gig-E interface is ideal for systems requiring high-speed communication, while PCI Bus interface enables the board to efficiently manage and control data transfers.

Connection Flexibility: The 75G5 provides flexibility in connectivity options, with the ability to connect to devices via the front panel, rear panel, or both. This feature is particularly useful in different mounting or space-constrained scenarios.

2x 10/100/1000 Base-T Ethernet: The 75G5 has two 10/100/1000 Base-T Ethernet ports, with the option to have one to the rear, one to the front I/O, or both to the rear.

Less than 5 Watts Motherboard Power Dissipation: With a power dissipation of less than 5 watts, the 75G5 consumes minimal power while delivering its multifunctional capabilities, making it suitable for use in power-sensitive applications.

Support for three independent, smart function: The board can support up to three independent, smart function modules based on the COSA® architecture. With over 100 modules to choose from, this allows for a wide range of input and output capabilities, including analog and digital I/O, signal generation and acquisition, and communication interfaces. Each function module slot has an independent x1 SerDes interface for motherboard-to-smart module interface, to offload the host processor from I/O management.

Background Built-In-Test (BIT): The 75G5 board continually checks and reports on the health of each channel, allowing for proactive maintenance and reducing the likelihood of downtime.

Software Support Kits (SSKs): SSKs and drivers are available to make the board easier to integrate into a system and develop software.

VICTORY Interface Services: NAI offers VICTORY Interface Services as an option, providing an open industry-standard approach for integrating different components in a system.

Commercial and rugged mechanical options: The 75G5 is available in both commercial and rugged models, making it suitable for a wide range of applications.

Operating temperature: The board has a wide operating temperature range, with models operating from:

  • 0° C to 70° C (commercial model)
  • -40° C to +85° C (rugged model)

SOFTWARE SUPPORT

The ENAIBL Software Support Kit (SSK) is supplied with all system platform based board level products. This platform’s SSK contents include html format help documentation which defines board specific library functions and their respective parameter requirements. A board specific library and its source code is provided (module level ‘C’ and header files) to facilitate function implementation independent of user operating system (O/S). Portability files are provided to identify Board Support Package (BSP) dependent functions and help port code to other common system BSPs. With the use of the provided help documentation, these libraries are easily ported to any 32-bit O/S such as RTOS or Linux.

The latest version of a board specific SSK can be downloaded from our website www.naii.com in the software downloads section. A Quick-Start Software Manual is also available for download where the SSK contents are detailed, Quick-Start Instructions provided and GUI applications are described therein. For other operating system support, contact factory.

Link to original

SPECIFICATIONS

General for the Motherboard

Signal Logic Level:Automatically supports either 5 V or 3.3 V cPCI bus
Power (Motherboard):`5 VDC @ 0.7 A (typical) ±12 V @ 0 mA (certain modules may require `/-12 V for operation) Add power for each individual module
Temperature, Operating:"C" =0° C to +70° C, "H" =-40° C to +85° C (See Part Number Designation section)
Storage Temperature:-55° C to +105° C
Temperature Cycling:Each board is cycled from -40° C to +85° C for options "C" or “H”
General size
     Height:3.94" / 100 mm (3U)
     Width:0.8” / 20.3 mm (4HP)
     Depth:6.3“ / 160 mm deep
Weight:12.5 oz. (354 g) unpopulated (approx.) Then add weight for each module (typically 1.5 oz. (42 g) each)

Specifications are subject to change without notice.

Environmental

Unless otherwise specified, the following table outlines the general Environmental Specifications design guidelines for board level products of North Atlantic Industries. All our cPCI, VME and OpenVPX boards are designed for either air or conduction cooling. All boards also incorporate appropriate stiffening to ensure performance during shock and vibration but also to assure reliable operation (lower fatigue stresses) over the service life of the product.

ParametersLevel
1 / Commercial-AC (Air Cooled)2 / Rugged-AC (Air Cooled)3 / Rugged-CC (Conduction Cooled)
Temperature - Operating0° C to 70° C, AmbientH-40° C to 85° C, AmbientI-40° C to 85° C, at wedge lock thermal interface
Temperature - Storage-40° C to 85° C-55° C to 105° C-55° C to 105° C
Humidity - Operating0 to 95%, non-condensing0 to 95%, non-condensing0 to 95%, non-condensing
Humidity - Storage0 to 95%, non-condensing0 to 95%, non-condensing0 to 95%, non-condensing
Vibration - SineA2 g peak, 15 Hz - 2 kHzB6 g peak, 15 Hz - 2 kHzB10 g peak, 15 Hz - 2 kHzC
Vibration - RandomD.002 g2 /Hz, 15 Hz - 2 kHz0.04 g2 /Hz, 15 Hz - 2 kHz0.1 g2 /Hz, 15 Hz - 2 kHzE
ShockF20 g peak, half-sine, 11 ms30 g peak, half-sine 11 ms40 g peak, half-sine, 11 ms
Low PressureGUp to 15,000 ft.Up to 50,000 ft.Up to 50,000 ft.

Notes:

A. Based on sweep duration of ten minutes per axis on each of the three mutually perpendicular axes. B. Displacement limited to 0.10 D.A. from 15 to 44 Hz. C. Displacement limited to 0.436 D.A. from 15 to 21 Hz. D. 60 minutes per axis on each of the three mutually perpendicular axes. E. Per MIL-STD-810G, Method 5.14.6 Procedure I, Fig.514.6C-6 Category 7 tailored (11.65 Grms): 15 Hz - 2 kHz; ASD (PSD) at 0.04 g2/Hz between 15 Hz - 150 Hz, increasing @ 4 dB/octave from 0.04 g2/Hz to 0.1 g /Hz between 150 Hz - 300 Hz, 0.1 g2/Hz between 300 Hz - 1000 Hz, decreasing @ 6 dB/octave from 0.1 g2/Hz to 0.025 g2/Hz between 1000 Hz - 2000 Hz. Three hits per direction per axis (total of 18 hits). F. Three hits per direction per axis (total of 18 hits). G. For altitudes higher than 50,000 ft., contact NAI. H. High temperature operation requires 350 lfm minimum air flow across cover/heatsink (module dependent). I. High temperature operation requires 600 lfm minimum air flow across cover/heatsink (module dependent).

Specifications subject to change without notice

REGISTER MEMORY MAP ADDRESSING

The register map address consists of the following:

• cPCI/PCIe BAR or Base Address for the Board • Module Slot Base Address • Function Offset Address

Board Base Address

The table below lists the BAR used for access to the motherboard and module registers. The second BAR is used internally for motherboard and module firmware updates. The other cPCI/PCIe BARs not listed are not used.

NAI BoardsDevice IDBusMotherboard and Module Register AccessMotherboard and Module Firmware Updates
Slave Boards
75G50x7581cPCIeBAR 0 Size: Module Dependent (minimum 64K Bytes)BAR 1 Size: 1M Bytes

Module Slot and Function Addresses

The memory map for the modules are dependent on the types of modules on the board and the order in which the modules are installed on the board as well as the firmware installed on the motherboard. The function modules are enumerated allowing for dynamic memory space allocation and therefore the “start” address of the module function register area is factory pre-defined (and read from) the Module Address register. Refer to Figure 1 for an example.

Figure 1. Register Memory Map Addressing for Motherboards with 3 Modules

Address Calculation

Motherboard Registers

Read/Write access to the motherboard registers starts with the base address for the board and then the motherboard base offset address.

For example, to address Module Slot 1 Start Address register (i.e. register address = 0x0400):

  1. Start with the base address for the board.
  2. Add the motherboard register address offset.
Motherboard Address =Base Address
Motherboard Address Offset
= 0x0000 0400
0x0000 0000 + 0x0400

Module Registers:

Read/Write access to the Function module’s registers start with the base address of the board. Add the “content” for the Module Start Address and then, add the specific module function register offset.

For example, to address an appropriate/specific function module with a register offset:

  1. Start with the base address for the board.
  2. Add the value (contents) from the module base address offset register (contents/value of Motherboard Memory register for Module 1 (i.e., @ 0x0400) = 0x4000.
  3. Then add the specific module function Register Offset of interest (i.e., A/D Reading Ch 1 @ 0x1000)
(Function Specific) Address =Base Address +Module Base Address Offset +Function Register Offset= 0x0000 5000
0x0000 00000x40000x1000

REGISTER DESCRIPTIONS

Module Information Registers

The Module Slot Addressing Ready, Module Slot Address, Module Slot Size, and Module Slot ID registers provide information about the modules detected on the board.

Module Slot Addressing Ready

Function:Indicates that the module slots are ready to be addressed.
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:0xA5A5A5A5
Operational Settings:This register will contain the value of 0xA5A5A5A5 when the module addresses have been determined.
Link to original

Module Slot Address
Function:Specifies the Base Address for the module in the specific slot position.
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Based on board's module configuration.
Operational Settings:0x0000 0000 indicates no Module found.
Link to original

Module Slot Size
Function:Specifies the Memory Size (in bytes) allocated for the module in the specific slot position.
Type:unsigned binary word (32-bit)
Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Assigned by factory for the module.
Operational Settings:0x0000 0000 indicates no Module found.
Link to original

Module Slot ID
Function:Specifies the Model ID for the module in the specified slot position.
Type:4-character ASCII string
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Assigned by factory for the module.
Operational Settings:The Module ID is formatted as four ASCII bytes: three characters followed by a space. Module IDs are in little-endian order with a single space following the first three characters. For example, 'TL1' is '1LT', 'SC1' is '1CS' and so forth. Example below is for “TL1” (MSB justified). All value of 0000 0000 indicates no Module found.
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
ASCII Character (ex: 'T' - 0x54)ASCII Character (ex: 'L' - 0x4C)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
ASCII Character (ex: '1' - 0x31)ASCII Space (' ' - 0x20)
Link to original

Hardware Information Registers

The registers identified in this section provide information about the board’s hardware

Product Serial Number
Function:Specifies the Board Serial Number.
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Initialized Value:Serial number assigned by factory for the board.
Operational Settings:N/A
Link to original

Platform

Function: Specifies the Board Platform Identifier. Values are for the ASCII characters for the NAI valid platforms (Identifiers).

Type: unsigned binary word (32-bit)

Data Range: See table below.

Read/Write: R

Initialized Value: ASCII code is for the Platform Identifier of the board

Operational Settings: Valid NAI platform and the associated value for the platform is shown below:

NAI PlatformPlatform IdentifierASCII Binary Values (Note: little-endian order of ascii values)
cPCI750x0000 3537

Model

Function: Specifies the Board Model Identifier. Value is for the ASCII characters for the NAI valid model.

Type: unsigned binary word (32-bit)

Data Range: See table below.

Read/Write: R

Initialized Value: ASCII code is for the Model Identifier of the board

Operational Settings: Example of NAI model and the associated value for the model is shown below:

NAI ModelASCII Binary Values (Note: little-endian order of ascii values)
G0x0000 0047

Generation

Function: Specifies the Board Generation. Identifier values are for the ASCII characters for the NAI valid generation identifiers.

Type: unsigned binary word (32-bit)

Data Range: See table below.

Read/Write: R

Initialized Value: ASCII code is for the Generation Identifier of the board

Operational Settings: Example of NAI generation and the associated value for the generation is shown below:

NAI GenerationASCII Binary Values (Note: little-endian order of ascii values)
50x0000 0035

Processor Count/Ethernet Count

Function: Specifies the Processor Count and Ethernet Count

Type: unsigned binary word (32-bit)

Data Range: See table below.

Read/Write: R

Operational Settings:

 Processor Count - Integer: indicates the number of unique processor types on the motherboard.
NAI BoardProcessor CountDescription
cPCI75G51Xilinx Zynq 7015 with Dual Core Cortex A9
 Ethernet Interface Count - Indicates the number of Ethernet interfaces on the product motherboard. For example, Single Ethernet = 1; Dual

Ethernet = 2.

Processor/Ethernet Interface Count

D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Processor Count (See Table)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Ethernet Count (Based on Part Number Ethernet Options)

Maximum Module Slot Count/ARM Platform Type

Function: Specifies the Maximum Module Slot Count and ARM Platform Type.

Type: unsigned binary word (32-bit)

Data Range: See table below.

Read/Write: R

Operational Settings:

     Maximum Module Slot Count - Indicates the number of modules that can be installed on the product.

     ARM Platform - Altera = 1; Xilinx X1 = 2; Xilinx X2 = 3; UltraScale = 4

NAI BoardMaximum Module Slot CountARM Platform Type
cPCI75G53Xilinx X1 = 2; Xilinx X2 = 3

Maximum Module Slot Count / ARM Platform Type

D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Maximum Module Slot Count (See Table)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
ARM Platform Type (See Table)

Motherboard Firmware Information Registers

The registers in this section provide information on the revision of the firmware installed on the motherboard.

Motherboard Core (MBCore) Firmware Version
Function:Specifies the Version of the NAI factory provided Motherboard Core Application installed on the board.
Type:Two (2) unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Operational Settings:The motherboard firmware version consists of four components: Major, Minor, Minor 2 and Minor 3.
Motherboard Core Firmware Version (Note: little-endian order in register) (ex. 4.7.0.0)
Word 1 (Ex. 0007 0004 = 4.7 (Major.Minor)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Minor (ex: 0x0007 = 7)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Major (ex: 0x0004 = 4)
Word 2 (Ex. 0x0000 0000 = 0000 = 0.0 (Minor2.Minor3))
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Minor 3 (ex: 0x000 = 0)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Minor 2 (ex: 0x000 = 0)
Link to original

Motherboard Firmware Build Time/Date
Function:Specifies the Build Date/Time of the NAI factory provided Motherboard Core Application installed on the board.
Type:Two (2) unsigned binary word (32-bit)
Data Range:N/A
Read/Write:R
Operational Settings:The motherboard firmware time consists of the Build Date and Build Time. NOTE: On some builds the the Date/Time fields are fixed to 0000 0000 to maintain binary consistency across builds.
Motherboard Firmware Build Time (Note: little-endian order in register)
Word 1 - Build Date (ex. 0x030C 07E2 = 2018-12-03)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Day (ex: 0x03 = 3)Month (ex: 0x0C = 12)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Year (ex: 0x07E2 = 2018)
Word 2 - Build Time (ex. 0x001B 3B0A = 10:59:27)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
null (0x00)Seconds (ex: 0x1B = 27)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Minutes (ex: 0x3B = 59)Hours (ex: 0x0A = 10)
Link to original

Motherboard Monitoring Registers

The registers in this provide motherboard temperature measurement information.

Temperature Readings Register

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

These registers are only available on Xilinx Generation 5 platforms, and are periodically populated by the motherboard core application, which only runs in Petalinux and BareMetal. For other operating systems, refer to the naibrd Software Support Kit (SSK) naibsp_system_Monitor_Temperature_Get() routine to manually retrieve the temperature (NOTE: this feature is typically utilized for development/factory use only; contact the factory for additional details on potential use, if required).

Temperature Readings Register
Function:Specifies the Measured Temperatures on Motherboard.
Type:signed byte (8-bits) for each temperature reading - Six (6) 32-bit words
Data Range:0x0000 0000 to 0xFFFF 0000
Read/Write:R
Initialized Value:Value corresponding to the measured temperatures based on the table below.
Operational Settings:The 8-bit temperature readings are signed bytes. For example, if the following register contains the value 0x6955 0000:
Word 3 (Max Zynq Temperatures)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Max Zynq Core TemperatureMax Zynq PCB Temperature
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0x000x00

The values would represent the following temperatures:

Temperature MeasurementsData BitsValueTemperature (Celsius)
Max Zynq Core TemperatureD31:D240x69+105°
Max Zynq PCB TemperatureD23:D160x55+85°
Temperature Readings
Word 1 (Current Zynq Temperatures)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Zynq Core TemperatureZynq PCB Temperature
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0x000x00
Word 2 (Reserved)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0x000x00
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0x000x00
Word 3 (Max Zynq Temperatures)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Max Zynq Core TempMax Zynq PCB Temp
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0x000x00
Word 4 (Reserved)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0x000x00
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000000000000000
Word 5 (Min Zynq Temperatures)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Min Zynq Core TemperatureMin Zynq PCB Temperature
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000000000000000
Word 6 (Reserved)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0x000x00
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
0000000000000000
Link to original

Higher Precision Temperature Readings Registers

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

Higher Precision Zynq Core Temperature
Function:Specifies the 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
Link to original

Higher Precision Motherboard PCB Temperature
Function:Specifies the Higher Precision Measured Motherboard 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 Motherboard 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
Link to original

Motherboard Health Monitoring Registers

The registers in this section provide a summary of motherboard temperature sensors and their corresponding bits. Additionally, this section provides an overview of the registers allocated to those sensors, which are used to monitor current/minimum/maximum temperature readings, upper & lower critical/warning temperature thresholds, and whether or not a programmed temperature threshold has been exceeded.

These registers are only available on Xilinx Generation 5 platforms, and are periodically populated by the motherboard core application, which only runs in Petalinux and BareMetal. For other operating systems, refer to the naibrd Software Support Kit (SSK) naibsp_system_Monitor_Temperature_Get() routine to manually retrieve the temperature (NOTE: this feature is typically utilized for development/factory use only; contact the factory for additional details on potential use, if required).

Motherboard Sensor Summary Alarm
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 motherboard 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:D5Reserved
D4Motherboard PCB Temperature
D3Zynq Core Temperature
D2:D0Reserved
Link to original

Motherboard Sensor Registers

The registers listed in this section apply to each module sensor listed for the Motherboard Sensor Summary Status register. Each individual sensor register provides a group of registers for monitoring motherboard 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 Zynq Core Temperature sensor as an example.

Link to original

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
Link to original

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.
Link to original

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.
Link to original

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.
Link to original

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.
Link to original

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.
Link to original

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.
Link to original

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.
Link to original

Ethernet Configuration Registers

The registers in this section provide information about the Ethernet Configuration for the two ports on the board.

Important: Regardless if the board is configured for one or two Ethernet ports, the second IP address cannot be on the same Subnet as the First IP Address. The table below provides examples of valid and invalid IP Addresses and Subnet Mask Addresses.

First Port (A) IP AddressFirst Port (A) Subnet MaskSecond Port (B) IP AddressSecond Port (B) Subnet MaskResult
192.168.1.5255.255.255.0192.168.2.5255.255.255.0Good
192.168.1.5255.255.0.0192.168.2.5255.255.0.0Conflict
192.168.1.5255.255.0.0192.168.2.5255.255.255.0Conflict
10.0.0.15255.0.0.0192.168.1.5255.255.255.0Good
Link to original

Ethernet MAC Address and Ethernet Settings
Function:Specifies the Ethernet MAC Address and Ethernet Settings for the Ethernet port.
Type:Two (2) unsigned binary word (32-bit)
Data Range:See table.
Read/Write:R
Operational Settings:The Ethernet MAC Address consists of six octets. The Ethernet Settings are defined in table.
BitsDescriptionValues
D31:D23Reserved0
D22:D21Duplex00 = Not Specified, ` 01 = Half Duplex, ` 10 = Full Duplex, + 11 = Reserved
D20:D18Speed000 = Not Specified, ` 001 = 10 Mbps, ` 010 = 100 Mbps, ` 011 = 1000 Mbps, ` 100 = 2500 Mbps, ` 101 = 10000 Mbps, ` 110 = Reserved, + 111 = Reserved
D17Auto Negotiate0 = Enabled, + 1 = Disabled
D16Static IP Address0 = Enabled, + 1 = Disabled
Ethernet MAC Address and Ethernet Settings (Note: little-endian order in register)
Word 1 (Ethernet MAC Address (Octets 1-4)) (ex: aa:bb:cc:dd:ee:ff)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
MAC Address Octet 4 (ex: 0xDD)MAC Address Octet 3 (ex: 0xCC)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
MAC Address Octet 2 (ex: 0xBB)MAC Address Octet 1 (ex: 0xAA)
Word 2 (Ethernet MAC Address (Octets 5-6) and Ethernet Settings)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Ethernet Settings (See table)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
MAC Address Octet 6 (ex: 0xFF)MAC Address Octet 5 (ex: 0xEE)
Link to original

Ethernet Interface Name
Function:Specifies the Ethernet Interface Name for the Ethernet port.
Type:8-character ASCII string
Data Range:See table.
Read/Write:R
Operational Settings:The Ethernet Interface Name (eth0, eth1, etc) for the Ethernet port.
Ethernet Interface Name (Note: ascii string in register) (ex. “eth0”)
Word 1 (Bit 0-31) (ex: 0x3068 7465 = “0hte”)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
ASCII Character (ex: '0' - 0x30)ASCII Character (ex: 'h' - 0x68)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
ASCII Character (ex: 't' - 0x74)ASCII Character (ex: 'e' - 0x65)
Word 2 (Bit 32-63) (ex: 0x0000 0000)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
ASCII Character (ex: null - 0x00)ASCII Character (ex: null - 0x00)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
ASCII Character (ex: null - 0x00)ASCII Character (ex: null - 0x00)
Link to original

Ethernet IPv4 Address
Function:Specifies the Ethernet IPv4 Address for the Ethernet port.
Type:Three (3) unsigned binary word (32-bit)
Data Range:See table.
Read/Write:R
Operational Settings:The Ethernet IPv4 Address consists of three parts: IPv4 Address, IPv4 Subnet Mask and IPv4 Gateway.
Ethernet IPv4 Address (Note: little-endian order in register)
Word 1 (Ethernet IPv4 Address) (ex: 0x1001 A8C0 = 192.168.1.16)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
IPv4 Address Octet 4 (ex: 0x10 = 16)IPv4 Address Octet 3 (ex: 0x01 = 1)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
IPv4 Address Octet 2 (ex: 0xA8 = 168)IPv4 Address Octet 1 (ex: 0xC0 = 192)
Word 2 (Ethernet IPv4 Subnet) (ex: 0x00FF FFFF = 255.255.255.0)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
IPv4 Subnet Octet 4 (ex: 0x00 = 0)IPv4 Subnet Octet 3 (ex: 0xFF = 255)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
IPv4 Subnet Octet 2 (ex: 0xFF = 255)IPv4 Subnet Octet 1 (ex: 0xFF = 255)
Word 3 (Ethernet IPv4 Gateway) (ex: 0x0101 A8C0 = 192.168.1.1)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
IPv4 Gateway Octet 4 (ex: 0x01 = 1)IPv4 Gateway Octet 3 (ex: 0x01 = 1)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
IPv4 Gateway Octet 2 (ex: 0xA8 = 168)IPv4 Gateway Octet 1 (ex: 0xC0 = 192)
Link to original

Ethernet IPv6 Address
Function:Specifies the Ethernet IPv6 Address for the Ethernet port.
Type:Five (5) unsigned binary word (32-bit)
Data Range:See table.
Read/Write:R
Operational Settings:The IPv6 Prefix length indicates the network portion of an IPv6 address using the following format: IPv6 address/prefix length ` Prefix length can range from 0 to 128 ` * Typical prefix length is 64

The following is an illustration of IPv6 addressing with IPv6 Prefix length of 64.

64 bits64 bits
PrefixInterface ID
Prefix 1Prefix 2Prefix 3Subnet IDInterface ID 1Interface ID 2Interface ID 3Interface ID 4
Example: 2002:c0a8:101:0:7c99:d118:9058:1235/64
2002C0A8010100007C99D11890581235
Ethernet IPv6 Address (Note: little-endian order within 32-bit and 16-bit words in register) (ex. IPv6 Address: 2002:c0a8:201:0:7c99:d118:9058:1235 IPv6 Prefix: 64)
Word 1 (Ethernet IPv6 Address (Prefix 1-2)) (ex:0xA8C0 0220 = 2002 C0A8)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Prefix 2 (ex: 0xA8C0 = C0A8)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Prefix 1 (ex: 0x0220 = 2002)
Word 2 (Ethernet IPv6 Address (Prefix 3/Subnet ID)) + (ex:0x000 0101 = 0101 0000)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Subnet ID (ex: 0x0000 = 0000)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Prefix 3 (ex: 0x0101 = 0101)
Word 3 (Ethernet IPv6 Address (Interface ID 1-2)) + (ex: 0x18D1 997C = 7C99 D118)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Interface ID 2 (ex: 0x18D1 = D118)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Interface ID 1 (ex: 0x997C = 7C99)
Word 4 (Ethernet IPv6 Address (Interface ID 3-4)) + (ex: 0x3512 5890 = 9058 1235)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
Interface ID 4 (ex: 0x3512 = 1235)
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Interface ID 3 (ex: 0x5890 = 9058)
Word 5 (Ethernet IPv6 Prefix Length) + (ex:0x0000 0040)
D31D30D29D28D27D26D25D24D23D22D21D20D19D18D17D16
0000000000000000
D15D14D13D12D11D10D9D8D7D6D5D4D3D2D1D0
Prefix Length (ex: 0x0040 = 64)
Link to original

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
Link to original

Module Control Command Registers

Modules Control Command Requests
Function:Provides the ability to command individual Modules to Reset, Power-down, or Power-up.
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R/W
Operational Settings:The Module Control Commands registers provide the ability to request individual Modules to perform one of the following functions - Reset, Power-down, Power-up. Only one command can be requested at a time per Module. For example, one can't request a Reset and a Power-down at the same time for the same Module. Once the command is recognized and handled, the bit will be cleared.

Note

Clearing of the command request bit only indicates the command has been recognized and initiated, it does not indicate that the command action has been completed.

There is one Control Command Request register per Module. Each register is Bit-mapped as shown in the table below:

Bit(s)Description
D31:D3Reserved
D2Module Power-up
D1Module Power-down
D0Module Reset
Link to original

Module Health Monitoring Registers

Module Communications Status
Function:Provides the ability to monitor factors may effect communication status of a Module.
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Operational Settings:The Module Communications registers provide the ability to monitor factors that may effect the Communications Status of individual Modules. There is one register per Module. Each communication factor is bit mapped to the register as shown in the table below:
Bit(s)Description
D31:D5Reserved
D4Module Communications Error Detected
D3Module Firmware Not Ready
D2Module LinkInit Not Done
D1Module Not Detected
D0Module Powered-down

Module Powered-down: The user can request an individual Module be powered-down (see Module Control Command Requests). Once the request is detected and acted upon, this bit will be set. Once powered-down, you will not be able to communicate with the Module.

Module Not Detected: If a Module in this slot has not been detected, you will not be able to communicate with the Module.

Module LinkInit Not Done: Module communications is accomplished via SERDES. LinkInit is required to establish a connection to the Module. If the LinkInit has not been successfully completed, you will not be able to communicate with the Module.

Module Firmware Not Ready: Each Module has Firmware that is ready from Module QSPI and loaded for execution. If this Firmware was not loaded and started successfully, you may not be able to communicate with the Module.

Module Communications Error Detected: If at some point during run-time, communications with the Module has failed, this bit will be set.

Link to original

Module BIT Status

Function:Provides the ability to monitor the individual Module BIT Status.
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R
Operational Settings:The Module BIT Status registers provide the ability to monitor individual Module BIT results as Latched and current value. A 1 is any bit field indicates BIT failure for the Module in that slot.
Bit(s)Description
D31:D20Reserved
D19Module Slot 3 BIT Failure (current value)
D18Module Slot 2 BIT Failure (current value)
D17Module Slot 1 BIT Failure (current value)
D16Reserved
D15:D4Reserved
D3Module Slot 3 BIT Failure - Latched
D2Module Slot 2 BIT Failure - Latched
D1Module Slot 1 BIT Failure - Latched
D0Reserved
Link to original

Scratchpad Area

Scratchpad Area
Function:Registers reserved as scratch pad for customer use.
Type:unsigned binary word (32-bit)
Data Range:0x0000 0000 to 0xFFFF FFFF
Read/Write:R/W
Operational Settings:This area in memory is reserved for customer use.
Link to original

MOTHERBOARD REGISTER FUNCTION MAP

Key:

Bold Underline = Measurement/Status/Board Information

Bold Italic = Configuration/Control

Module Information Registers

0x03FCModule Slot Addressing ReadyR
0x0400Module Slot 1 AddressR
0x0404Module Slot 2 AddressR
0x0408Module Slot 3 AddressR
0x0430Module Slot 1 SizeR
0x0434Module Slot 2 SizeR
0x0438Module Slot 3 SizeR
0x0460Module Slot 1 IDR
0x0464Module Slot 2 IDR
0x0468Module Slot 3 IDR

Hardware Information Registers

0x0020Product Serial NumberR
0x0024PlatformR
0x0028ModelR
0x002CGenerationR
0x0030Processor Count/EthernetR
0x0034Maximum Module Slot Count/ARM Platform typeR

Motherboard Firmware Information Registers

0x0100MBCore Major/Minor VersionR
0x0104MBCore Minor 2/3 VersionR
0x0108MBCore Build DateR

Motherboard Measurement Registers

Temperature Readings

0x0200Current Zynq TemperaturesR
0x0204ReservedR
0x0208Max Zynq TemperaturesR
0x020CReservedR
0x0210Min Zynq TemperaturesR
0x0214ReservedR

Higher Precision Temperature Readings

0x0230Current Zynq Core TemperatureR
0x0234Current Motherboard PCB TemperatureR

Motherboard Health Monitoring Registers

0x20F8Motherboard Sensor Summary StatusR

Ethernet Configuration Registers

0x0070Ethernet A MAC (Octets 1-4)R
0x0074Ethernet A MAC (Octets 5-6)/Misc SettingsR
0x0078Ethernet A Interface Name (Bit 0-31)R
0x007CEthernet A Interface Name (Bit 32-63)R
0x0080Ethernet A IPv4 AddressR
0x0084Ethernet A IPv4 Subnet MaskR
0x0088Ethernet A IPv4 GatewayR
0x008CEthernet A IPv6 Address (Prefix 1-2)R
0x0090Ethernet A IPv6 Address (Prefix 3/Subnet ID)R
0x0094Ethernet A IPv6 Address (Interface ID 1-2)R
0x0098Ethernet A IPv6 Address (Interface ID 3-4)R
0x009CEthernet A IPv6 Prefix LengthR
0x00A0Ethernet B MAC (Octets 1-4)R
0x00A4Ethernet B MAC (Octets 5-6)/Misc SettingsR
0x00A8Ethernet B Interface Name (Bit 0-31)R
0x00ACEthernet B Interface Name (Bit 32-63)R
0x00B0Ethernet B IPv4 AddressR
0x00B4Ethernet B IPv4 Subnet MaskR
0x00B8Ethernet B IPv4 GatewayR
0x00BCEthernet B IPv6 Address (Prefix 1-2)R
0x00C0Ethernet B IPv6 Address (Prefix 3/Subnet ID)R
0x00C4Ethernet B IPv6 Address (Interface ID 1-2)R
0x00C8Ethernet B IPv6 Address (Interface ID 3-4)R
0x00CCEthernet B IPv6 Prefix LengthR

Interrupt Vector and Steering

0x0500 - 0x057CModule 1 Interrupt Vector 1 - 32R/W0x0600 - 0x067CModule 1 Interrupt Steering 1 - 32R/W
0x0700 - 0x077CModule 2 Interrupt Vector 1 - 32R/W0x0800 - 0x087CModule 2 Interrupt Steering 1 - 32R/W
0x0900 - 0x097CModule 3 Interrupt Vector 1 - 32R/W0x0A00 - 0x0A7CModule 3 Interrupt Steering 1 - 32R/W

Module Control Command Requests

0x01D8Module Slot 1 Command RequestR/W
0x01DCModule Slot 2 Command RequestR/W
0x01E0Module Slot 3 Command RequestR/W

Modules Health Monitoring Registers

Module Communications Status

0x01B8Module Slot 1 Communications StatusR
0x01BCModule Slot 2 Communications StatusR
0x01C0Module Slot 3 Communications StatusR

Module BIT Status

0x0128Module BIT Status (current and latched)R

Scratchpad Area

0x3800 - 0x3BFFScratchpad RegistersR/W

ETHERNET

(For detailed supplement, please visit the NAI web-site specific product page and refer to: Ethernet Interface for Generation 5 SBC and Embedded IO Boards Specification)

Note

For products capable of 10/100/1000Base-KX functionality - the product Ethernet PHY supports 1000BASE-X. Product interoperability with 10/100/1000BASE-KX is supported with 1000BASE-X (provided that auto-negotiation is disabled).

The Ethernet Interface Option allows communications and control access to all function modules either via the system BUS or Ethernet ports 1 or 2.

Ethernet 1Ethernet 2Ethernet 3*Ethernet 4*
(REF PORT A)(REF PORT B)(REF PORT C)(REF PORT D)
The default IP address:192.168.1.16192.168.2.16192.168.3.16192.168.4.16
The default subnet:255.255.255.0255.255.255.0255.255.255.0255.255.255.0
The default gateway:192.168.1.1192.168.2.1192.168.3.1192.168.4.1

*see Part Number Designation for applicability.

Note

Actual “as shipped” card Ethernet default IP addresses may vary based upon final ATP configuration(s).

The NAI interface supports IPv4 and IPv6 and both the TCP and UDP protocols. The Ethernet Operation Mode Command Listener application running on the motherboard host processor implements the operation interface. The listener is operational on startup through the nai_MBStartup process and listen on specific ports for commands to process. The default ports are listed below:

  • TCP1 - Port 52801
  • TCP2 - Port 52802
  • UDP1 - Port 52801
  • UDP2 - Port 52802

While the listener is active, note that interrupts from the motherboard do not trigger. The listener can be disabled by turning off the nai_MBStartup process through the Motherboard EEPROM. To turn off nai_MBStartup use the command mbeeprom_util set MBStartupInitOnlyFlag 1 in the console, either by serial port or telnet to the motherboard, and then reboot the system. To turn on the nai_MBStartup use the command mbeeprom_util set MBStartupInitOnlyFlag 0 in the console, either by serial port or telnet to the motherboard, and then reboot the system.

Ethernet Message Framework

The interface uses a specific message framework for all commands and responses. All messages begin with a Preamble code and end with a Postamble code. The message framework is shown below.

Preamble
2 bytes Always
0xD30F
SequenceNo
2 bytes
Type Code
2 byte
Message Length
(2 bytes)
Payload
(0..1414 bytes)
Postamble
2 bytes
Always
0xF03D

Message Elements

PreambleThe Preamble is used to delineate the beginning of a message frame.
The Preamble is always 0xD30F.
SequenceNoThe SequenceNo is used to associate Commands with Responses.
Type CodeType Codes are used to define the type of Command or Response the message contains.
Message LengthThe Message Length is the number of bytes in the complete message frame starting with and including the
Preamble and ending with and including the Postamble.
PayloadThe Payload contains the unique data that makes up the command or response.
Payloads vary based on command type.
PostambleThe Postamble is use to delineate the end of a message frame.
The Postamble is always 0xF03D.

Notes

  1. The messaging protocol applies only to card products.
  2. Messaging is managed by the connected (client) computer. The client computer will send a single message and wait for a reply from the card. Multiple cards may be managed from a single computer, subject to channel and computer capacity.

Board Addressing

The interface provides two main addressing areas: Onboard and Off-board.

Onboard addressing refers to accessing resources located on the board that is implementing the operation interface (including its modules).

Off-board addressing refers to accessing resources located on another board reachable via VME, PCI, or other bus. Off-board addressing requires a Master/Slave configuration.

The user must always specify if a particular address is Onboard or Off-board. See the command descriptions for the onboard and off-board flags.

Within a particular board (Onboard or Off-board), the address space is broken up into two areas: Motherboard Common Address Space and Module Address Space. All addresses are 32-bit.

Motherboard Common Address Space starts at 0x00000000 and ends at 0x00004000. This is a 4Kx32-bit address space (16 kbytes).

Module Address Space starts at 0x00004000. Module addressing is dynamically configured at startup. NAI boards support between 1 and 6 modules. The minimum module address space size is 4Kx32 (16 kbytes) and module sizes are always a multiple of 4Kx32.

Module addressing is dynamic and cumulative. The first detected module (starting with Slot 1) is given an address of 0x00004000. The 2nd detected Module is given an address of:

First_Detected_Module_Address + First_Detected_Module_Size

Note

Slots do not define addresses.

If no module is detected in a module slot, that slot is not given an address. Therefore, if the first detected Module is in Slot 2, then that module address will be 0x00004000. If the next detected module is in Slot 4, then the address of that Module will be:

Second_Detected_Module_Address = First_Detected_Module_Address + First_Detected_Module_Size

If a 3rd Module is detected in Slot 6, then the address of that Module will be:

Third_Detected_Module_Address = Second_Detected_Module_Address + Second_Detected_Module_Size

Note

Module addresses are calculated at each board startup when the modules are detected. Therefore, if a module should fail to be detected due to malfunction or because it was removed from the motherboard, the addresses of the modules that follow it in the slot sequence will be altered. This is important to note when programming to this interface.

Users can always retrieve the Module Addresses, Module Sizes and Module IDs from the fixed Motherboard Common address area. This data is set upon each board startup. While the Module Addressing is dynamic, the address where these addresses are stored is fixed. For example, to find the startup address of the module location in Slot 3, refer to the MB Common Address 0x00000408 from the Motherboard Common Addresses table that follows.

Ethernet Wiring Convention

RJ-45 PinT568A ColorT568B Color10/100Base-T1000BASE-TNAI wiring convention
1white/green stripewhite/orange stripeTX+DA+ETH-TP0+
2greenorangeTX-DA-ETH-TP0-
3white/orange stripewhite/green stripeRX+DB+ETH-TP1+
4blueblueDC+ETH-TP2+
5white/blue stripewhite/blue stripeDC-ETH-TP2-
6orangegreenRX-DB-ETH-TP1-
7white/brown stripewhite/brown stripeDD+ETH-TP3+
8brownbrownDD-ETH-TP3-
Link to original

CONNECTOR/PIN-OUT INFORMATION

Front and Rear Panel Connectors

Front Panel Connectors J3, J4

50-pin male connectors, 2 mm, Harwin P/N M80-5S25022M3

Mate kit: Harwin M80-486 product family (mating connector kit is available from Harwin as P/N M80-9415005). This mating connector may be purchased separately under NAI P/N 05-0118 (contact factory).

Rear Panel Connectors J1, J2

J1 - cPCI and Bus Controller interface only / 2mm 5x22 w/key, standard cPCI (AMP 352068-1 or equivalent). J2 - Bus Controller and configured I/O / 2mm 5x22 wo/key, standard cPCI (AMP 5352152-1 or equivalent). See mod slot pin-out.

Utility Connector J5

Industry standard mini-HDMI type (type-C receptacle).

Panel LEDs

Front Panel LEDs indications (only available on air-cooled units).

LEDILLUMINATEDEXTINGUISHED
GRN:Blinking: Initializing
Steady On: Power-On/Ready
Power off
RED:Module BIT faultNo BIT fault
YEL:(flash)Card access (bus or Gig-E activity)No card activity

Front Panel Chassis Ground

Front Panel: No dedicated pins - screw insert only.

Front Panel System (Power/Signal) Ground Reference

Front Panel: J3 pins 1, 26; J4 pins 25, 50 (Connected to cPCI system ground).

Front IO Utility Connector J5 (Convection and Conduction-Cooled)

The 75G5 utilizes a Mini-HDMI card edge connector J5, available on either convection or conduction cooled configurations, which provides the following signals:

  • Serial (port 1)
  • Ethernet port 1 (factory configuration option – Ethernet port1 may be redirected to rear I/O J2)

NAI also provides an optional “breakout” adapter board (NAI P/N 75SBC4-BB) with an HDMI cable. The “breakout” adapter board and a MicroHDMI cable (NAI P/N 75SBC4-BB) allow for standard I/O connections to Ethernet and asynchronous serial (DB9). Consult the factory for availability.

Signal Descriptions J5

Signal NameDescription
ETH1-TPxEthernet port 1 signals (4 pair) 10/100/1000 twisted pair signals (Optional)
SER1-TXDAsynchronous transmit serial data port 1 (out)
SER1-RXDAsynchronous received serial data port 1 (in)
GNDSystem Ground (return)

Compact PCI Interface

The 75G5 implements a 32-bit Compact PCI interface, conforming to the PICMG 2.0 R3.0 specification, and running at 33MHz. Hot Swap is NOT currently implemented on this card. The 75G5 card uses 3.3 V signaling voltage and is 5 V tolerant.

CAUTION The 75G5 is specifically designed for use with 32-bit Compact PCI backplanes and is not compatible with 64-bit backplanes. Plugging this card into a 64-bit backplane may cause permanent component damage.

Connector J1

Signal Descriptions J1

AD[31:0]PCI multiplexed Address/Data bits 31 to 0
C/BE[3:0]#PCI Command/Byte Enables for AD[31:24], AD[23:16], AD[15:8] and AD[7:0] respectively
INT[A:D]#PCI interrupts A, B, C and D respectively
REQ#Request indicates to the arbiter that the 75G5 is requesting the bus. This is a point-to-point signal. Every master has its own REQ#.
GNT#Grant indicates to access to the bus has been granted. This is a point-to-point signal. Every master has its own GNT#
LOCK#Bi-directional signal used to request Locked bus ownership
CLKOutput PCI clock signal (33 MHz)
DEVSEL#Device Select is an input. When actively driven, DEVSEL indicates that the driving device has decoded its address as the target of the current access
IRDY#Bi-directional signal indicating that the current bus master is driving a bus cycle. During a write, IRDY# asserted indicates that the initiator is driving valid data onto the data bus. During a read, IRDY# asserted indicates that the initiator is ready to accept data from the currently addressed slave.
TRDY#Target Ready indicates the target selected card’s ability to complete the current data phase of the transaction. TRDY# is used in conjunction with IRDY#.
FRAME#The current initiator drives Cycle Frame, which indicates the start (when first asserted) and duration (the duration of its assertion) of a transaction.
PARParity bit, parity is even parity across AD[31:0] and C/BE[3:0]#.
Parity generation is required by all PCI cards
PERR#Parity Error signal
SERR#System Error is for reporting address parity errors, data parity errors on the Special Cycle command, or any other system error
RST#Compact PCI backplane reset signal
STOP#Stop indicates the current target is requesting the master to stop the current transaction
IDSELInitialization Device Select is used as a chip select during an access to one of the device’s configuration registers
M66ENPCI 66 MHz operation signal
INTP, INTSLegacy interrupt input.
ENUM#Enumeration Interrupt
V_IOI/O selection for either 5V or 3.3V backplane signals.
5V+5V power connection
+12V+12V power connection
-12V-12V power connection
GNDDigital Ground and Power Supply return for (5, +12, -12)

Note

used after a signal name indicates that the signal in question is active low (or asserted low)

J2 Rear Connector Pinout/Option Mapping Summary

The following provides connector pin-out information for Rear Connector J2. Note that while there are several options for user input/output, there are also system dedicated pins that are reserved for specific motherboard functions. This provides 32 pins of available I/O. Dual Ethernet option for Module Slot 2 reduces available I/O to 24 pins. If the Rear Debug Port is selected, then Module Slot 3 is limited to 24-pins rear I/O availability

J3/J4 Front Panel Connector Pinout Mapping Summary

The following provides connector/pinout data for Front Panel connectors J3 and J4.

Connector J3

Connector J4

Front and Rear User I/O Mapping

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

Ethernet (Rear I/O)

Connector Signal/Pin-Out Notes

NAI Synchro/Resolver Naming Convention

SignalResolverSynchro
S1SIN(-)X
S2COS(+)Z
S3SIN(+)Y
S4COS(-)No connect

Additional Pin-Out Notes

1. Isolated Discrete Module (DT2)For ‘differential’ A/D; “P” designation considered ‘positive’ input pin, “N” pin designation considered ‘negative’ input pin.
2. Discrete I/O Module (DT1)All GND pins are common within the module, but, isolated from
system/power GND. Each pin should be individually wired for optimalpower current distribution.
3. TTL I/O Module (TL1)I/O referenced to system power GND.
4. CMRP - A/D Module(s) (ADx)The Common Mode Reference Point (CMRP) is an isolated reference connection for all the A/D channels. For expected high common mode voltage applications, it is recommended that the pin designated as CMRP be referenced (direct or resistor coupled) to the signal source GND reference (must have current path between CMRP and signal source generator) to minimize common mode voltage within the acceptable specification range. All channels within the module are independent but share a CMRP, which is isolated from system/power GND.

75G5 PART NUMBER DESIGNATION

Click here for the 75G5 part number designation

SYNCHRO/RESOLVER AND LVDT/RVDT SIMULATION MODULE CODE TABLES

Select the Digital-to-Synchro (DSx), Digital-to-Resolver (DRx) or Digital-to-LVDT/RVDT (DLx) module ID corresponding to the application operating parameters required from the following code table (where x = the specific module ID designator). Customer should indicate the actual frequency applicable the design to assure that the correct default band width is set at the factory. All Input and Reference voltages are auto ranging. Frequency/voltage band tolerances +/- 10%. For availability and ranges other than those listed contact the factory. Specifications may be subject to change.

  • Single Channel module pending availability (contact factory)
Module IDFormatChannel(s)Output Voltage VL-L (Vrms)Reference Voltage (Vrms)Frequency Range (Hz)Power / CH maximum (VA)Notes
DS1SYN1*2 - 282 - 11547 - 1 K3
DR1RSL
DL1LVDT/RVDT
DS2SYN1*2 - 282 - 1151 K - 5 K3
DR2RSL
DL2LVDT/RVDT
DS3SYN1*2 - 282 - 1155 K - 10 K3
DR3RSL
DL3LVDT/RVDT
DS4SYN1*2 - 282 - 11510 K - 20 K3
DR4RSL
DL4LVDT/RVDT
DS5SYN1*28 - 902 - 11547 - 1 K3
DR5RSL
DL5LVDT/RVDT
DSXSYN1*XXXXX = TBD; special configuration, requires special part number code designation, contact factory
DRXRSL
DLXLVDT/RVDT
DSASYN22 - 282 - 11547 - 1 K1.5
DRARSL
DLALVDT/RVDT
DSBSYN22 - 282 - 1151 K - 5 K1.5
DRBRSL
DLBLVDT/RVDT
DSCSYN22 - 282 - 1155 K - 10 K1.5
DRCRSL
DLCLVDT/RVDT
DSDSYN22 - 282 - 11510 K - 20 K1.5
DRDRSL
DLDLVDT/RVDT
DSESYN228 - 902 - 11547 - 1 K2.2
DRERSL
DLELVDT/RVDT
DSYSYN2YYYYY = TBD; special configuration, requires special part number code designation, contact factory
DRYRSL
DLYLVDT/RVDT
DSJSYN32 - 282 - 11547 - 1 K0.5
DRJRSL
DLJLVDT/RVDT
DSKSYN32 - 282 - 1151 K - 5 K0.5
DRKRSL
DLKLVDT/RVDT
DSLSYN32 - 282 - 1155 K - 10 K0.5
DRLRSL
DLLLVDT/RVDT
DSMSYN32 - 282 - 11510 K - 20 K0.5
DRMRSL
DLMLVDT/RVDT
DSNSYN328 - 902 - 11547 - 1 K0.5
DRNRSL
DLNLVDT/RVDT
DSZSYN3ZZZZZ = TBD; special configuration, requires special part number code designation, contact factory
DRZRSL
DLZLVDT/RVDT

SYNCHRO/RESOLVER AND LVDT/RVDT MEASUREMENT MODULE CODE TABLES

SYN/RSL Four-Channel Measurement (Field Programmable SYN/RSL)

Select the Synchro/Resolver-to-Digital (SDx) module ID corresponding to the application operating parameters required from the following code table (where x = the specific module ID designator). Customer should indicate the actual frequency applicable to the design to assure that the correct default band width is set at the factory. All Input and Reference voltages are auto ranging. For availability and ranges other than those listed contact the factory. Specifications may be subject to change.

Frequency/voltage band tolerances +/- 10%.

Module IDInput Voltage V (Vrms)Reference Voltage + (Vrms)Frequency Range + (Hz)Notes
SD12 - 282 - 11547 - 1 K
SD22 - 282 - 1151K - 5 K
SD32 - 282 - 1155K - 10 K
SD4*2 - 282 - 11510K - 20 K
SD528 - 902 - 11547 - 1 K
SDX*XXXX = TBD; special configuration, requires special part number code designation, contact factory

*Consult factory for availability

LVDT/RVDT Four-Channel Measurement (Field Programmable 2, 3 or 4-Wire)

Select the LVDT/RVDT-to-Digital (LDx) module ID corresponding to the application operating parameters required from the following code table (where x = the specific module ID designator). Customer should indicate the actual frequency applicable to the design to assure that the correct default band width is set at the factory. All Input and Excitation voltages are auto ranging. For availability and ranges other than those listed contact the factory. Specifications may be subject to change.

Frequency/voltage band tolerances +/- 10%.

Module IDInput Signal Voltage V + (Vrms)Excitation Voltage + (Vrms)Frequency Range + (Hz)Notes
LD12 - 282 - 11547 - 1 K
LD22 - 282 - 1151K - 5 K
LD32 - 282 - 1155K - 10 K
LD4*2 - 282 - 11510K - 20 K
LD528 - 902 - 11547 - 1 K
LDX*XXXX = TBD; special configuration, requires special part number code designation, contact factory

*Consult factory for availability

Link to original

Revision History

Motherboard Manual - 75G5 Revision History

RevisionRevision DateDescription
C2024-02-06ECO C11191, transition to docbuilder format. Pg.5, updated product image & description. Pg.6-7, updated available function modules table. Pg.7, updated from ‘Over 40…’ to ‘Over 100…‘. Pg.8, updated Introduction; added product overview section. Pg.9, changed ‘E’ to ‘H’ in “Temperature, Operating”. Pg.9, changed ‘E’ to ‘C’ in “Temperature Cycling”. Pg.11-36, reformatted Addressing/Register Descriptions/Function Map sections. Pg.40, changed Utility Connector to type-C. Pg.41, moved Panel LEDS before Chassis Ground. Pg.45, added two availability notations. Pg.49, removed module pinouts from Front and Rear User I/O Mapping section. Pg.50, added Ethernet details & additional notes. Pg.52, added Single Channel note. Pg.52, updated DSE/DRE/DLE Power/CH maximum (VA) to ‘2.2’.

DOCS.NAII REVISIONS

Revision DateDescription
2026-02-19Corrected Board Base Address table (Bus/MB & Module Register Access/MB & Module FW updates).

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