apexvx - rtsoftapexvx getting started apexvx concept and usage sd.dt.-g01-0e page 1 chapter 1 -...

ApexVX

Getting Started

SD.DT.G01-0e - May 2012

If it's embedded, it's Kontron.

ApexVX Getting StartedPreface

Page i SD.DT.G01-0e

Revision History

Publication Title: ApexVX Getting Started

Doc. ID: SD.DT.G01-0e

Rev. Brief Description of Changes Date of Issue

0e Initial Version 05-2012

Copyright © 2012 Kontron AG. All rights reserved. All data is for information purposes only and not guaranteedfor legal purposes. Information has been carefully checked and is believed to be accurate; however, noresponsibility is assumed for inaccuracies. Kontron and the Kontron logo and all other trademarks or registeredtrademarks are the property of their respective owners and are recognized. Specifications are subject to changewithout notice.

ApexVX Getting Started Preface

SD.DT.G01-0e Page ii

Proprietary Note

This document contains information proprietary to Kontron. It may not be copied or transmitted by any means,disclosed to others, or stored in any retrieval system or media without the prior written consent of Kontron or oneof its authorized agents.

The information contained in this document is, to the best of our knowledge, entirely correct. However, Kontroncannot accept liability for any inaccuracies or the consequences thereof, or for any liability arising from the useor application of any circuit, product, or example shown in this document.

Kontron reserves the right to change, modify, or improve this document or the product described herein, as seenfit by Kontron without further notice.

Trademarks

This document may include names, company logos and trademarks, which are registered trademarks and,therefore, proprietary to their respective owners.

Environmental Protection Statement

This product has been manufactured to satisfy environmental protection requirements where possible. Manyof the components used (structural parts, printed circuit boards, connectors, batteries, etc.) are capable of beingrecycled.

Final disposition of this product after its service life must be accomplished in accordance with applicable country,state, or local laws or regulations.

The Waste Electrical and Electronic Equipment (WEEE) Directive aims to:

> reduce waste arising from electrical and electronic equipment (EEE)

> make producers of EEE responsible for the environmental impact of their products, especially when they

become waste

> encourage separate collection and subsequent treatment, reuse, recovery, recycling and sound

environmental disposal of EEE

> improve the environmental performance of all those involved during the lifecycle of EEE

ApexVX Getting StartedPreface

Page iii SD.DT.G01-0e

Conventions

This guide uses several types of notice: Note, Caution, ESD.

Note: this notice calls attention to important features or instructions.

Caution: this notice alert you to system damage, loss of data, or risk of personal injury.

ESD: This banner indicates an Electrostatic Sensitive Device.

All numbers are expressed in decimal, except addresses and memory or register data, which are expressed inhexadecimal. The prefix `0x' shows a hexadecimal number, following the `C' programming language convention.

The multipliers `k', `M' and `G' have their conventional scientific and engineering meanings of *103, *106 and *109

respectively. The only exception to this is in the description of the size of memory areas, when `K', `M' and `G'mean *210, *220 and *230 respectively.

When describing transfer rates, `k' `M' and `G' mean *103, *106 and *109 not *210 *220 and *230.

In PowerPC terminology, multiple bit fields are numbered from 0 to n, where 0 is the MSB and n is the LSB. PCIand CompactPCI terminology follows the more familiar convention that bit 0 is the LSB and n is the MSB.

Signal names ending with an asterisk (*) or a hash (#) denote active low signals; all other signals are active high.

Signal names follow the PICMG 2.0 R3.0 CompactPCI Specification and the PCI Local Bus 2.3 Specification.

For Your Safety

Your new Kontron product was developed and tested carefully to provide all features necessary to ensure itscompliance with electrical safety requirements. It was also designed for a long fault-free life. However, the lifeexpectancy of your product can be drastically reduced by improper treatment during unpacking and installation.Therefore, in the interest of your own safety and of the correct operation of your new Kontron product, you arerequested to conform with the following guidelines.

High Voltage Safety Instructions

Warning!

All operations on this device must be carried out by sufficiently skilled personnel only.

Caution, Electric Shock!

Before installing a not hot-swappable Kontron product into a system always ensure that your mains power

is switched off. This applies also to the installation of piggybacks. Serious electrical shock hazards can

exist during all installation, repair and maintenance operations with this product. Therefore, always unplug

the power cable and any other cables which provide external voltages before performing work.

ApexVX Getting Started Preface

SD.DT.G01-0e Page iv

Special Handling and Unpacking Instructions

ESD Sensitive Device!

Electronic boards and their components are sensitive to static electricity. Therefore, care must be taken

during all handling operations and inspections of this product, in order to ensure product integrity at all

times

Do not handle this product out of its protective enclosure while it is not used for operational purposes unless itis otherwise protected.

Whenever possible, unpack or pack this product only at EOS/ESD safe work stations. Where a safe work stationis not guaranteed, it is important for the user to be electrically discharged before touching the product with his/herhands or tools. This is most easily done by touching a metal part of your system housing.

It is particularly important to observe standard anti-static precautions when changing piggybacks, ROM devices,jumper settings etc. If the product contains batteries for RTC or memory backup, ensure that the board is notplaced on conductive surfaces, including anti-static plastics or sponges. They can cause short circuits anddamage the batteries or conductive circuits on the board.

General Instructions on Usage

In order to maintain Kontron’s product warranty, this product must not be altered or modified in any way. Changesor modifications to the device, which are not explicitly approved by Kontron and described in this manual orreceived from Kontron’s Technical Support as a special handling instruction, will void your warranty.

This device should only be installed in or connected to systems that fulfill all necessary technical and specificenvironmental requirements. This applies also to the operational temperature range of the specific boardversion, which must not be exceeded. If batteries are present, their temperature restrictions must be taken intoaccount.

In performing all necessary installation and application operations, please follow only the instructions suppliedby the present manual.

Keep all the original packaging material for future storage or warranty shipments. If it is necessary to store or

ship the board, please re-pack it as nearly as possible in the manner in which it was delivered.

Special care is necessary when handling or unpacking the product. Please consult the special handling andunpacking instruction on the previous page of this manual.

ApexVX Getting StartedTable Of Contents

Page v SD.DT.G01-0e

Table Of Contents

Chapter 1 - ApexVX Concept and Usage 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 Unique Asset for Agile Procurement 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 A Two-Step Approach 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Pre-Configured Computer 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2 - ApexVX Evaluation 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 ApexVX Demo Overview 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2 Test Setup Overview 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 Start Demo 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3 - Demo Software Descritpion 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 System Monitoring 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Temperature Monitoring 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Performance and Unit tests 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.1 Data Plane: VXFabric™ on PCIe 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.2 Integrated GPU: Video Test 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.3 OPENGL 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.4 Network 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.5 GPIO (RX/TX 1&2) 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 4 - System Hardware Configuration 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 VX3030: Core i7 CPU Boards 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 VX3830: Custom I/O FPGA Board 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3 VX3905: PCie and GETH Switch Board 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4 IFDPC5-3U-VPXV1SI: Open VPX Backplane 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.5 PB-IOBRK/APEX : I/O Break Out Board 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.6 Internal Cabling 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 5 - System Software Configuration 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 Pre-Configured User Accounts 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2 Network Configuration 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.3 OS and Storage Configuration 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.4 PCIe Configuration and VXFabric™ 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.5 Display 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.6 Serial Terminal 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.7 GPIO 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ApexVX Getting Started Table Of Contents

SD.DT.G01-0e Page vi

Chapter 6 - Troubles Shooting 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1 Restoring ApexVX Entire Software Content 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2 VX3030 Boot Server/Diskless (RE) Configuration 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 7 - Customizing ApexVX 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1 AP-5985-01010101 Parts List 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2 Assembling VX3830 and FMC Mezzanine 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3 FMC-SER0 to VX3830 Rear VPX GPIO Pin Assignment 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ApexVX Getting StartedTable Of Contents

Page vii SD.DT.G01-0e

List Of Figures

Figure 1: ApexVX Overview 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2: gnome-system-monitor GUI 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3: OpenGL Sample 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4: VX3030 Functional Description 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 6: FMC-SER0 Functional Description 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 8: ApexVX OpenVPX Backplane 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 9: BreakOut Board 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 10: Internal Cabling 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 11: VX3030 (Board 1 & Board 2) 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12: VPX Backplane (A1) 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13: FMC-SER0 (Board 7) 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 14: VX3905 (Board 5) 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 15: Break-Out Board (Board 8) 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 16: VX3830 (Board 3) 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ApexVX Getting Started ApexVX Concept and Usage

SD.DT.-G01-0e Page 1

Chapter 1 - ApexVX Concept and Usage

ApexVX is a pre-qualified Rugged Embedded computer baseline which has been designed to be easily customized. Our customers start from an existing ApexVX computer configuration and customize it to match their application needs.

Figure 1: ApexVX Overview

1.1 Unique Asset for Agile Procurement

ApexVX is a new generation of turnkey rugged computers aiming at rapid prototyping of multiple applicationprofiles for military and transportation customers.

ApexVX integrated hardware and software, based on COTS elements from Kontron, demonstrate theperformance of the combined new cutting edge technology improvements provided by conduction cooled 3UVPX cards mounted into a ½ ATR style small form factor chassis.

Any computer workload based on Linux and TCP/IP will run unmodified on ApexVX. ApexVX pre-configuredsoftware includes VXFabric™ (TCP/IP on PCIe backplane, 10 GETH class bandwidth) for the data planebetween CPUs. A system wide PBIT solution with auto learning mode is also part of the system.

ApexVX specifically aims at fulfilling the AGILE PROCUREMENT trend which promotes the use of very earlyfield trials of new concepts. To allow this, ApexVX has been designed to be used in the lab and then directlytransferred into harsh environment for real scale field trials.

ApexVX Getting StartedApexVX Concept and Usage

Page 2 SD.DT.-G01-0e

1.2 A Two-Step Approach

Be the First with ApexVX: choose from a pre-qualified ApexVX configuration to run your application prototypeand be the first to complete field trials. Contact [email protected] for all required configuration changes.

Finalize with ApexVX by introducing final configuration for deployments: I/O panel, filtering, complete healthmanagement solution for the deployed equipment.

At any time, [email protected] helps you design your application-dependent elements: custom I/O boards,cabling, information security solutions. All that you need to cover 100% of your customer requirements and saveon recurring computer cost.

1.3 Pre-Configured Computer

ApexVX is the union of battle-proven enclosure technology and leading edge 3U VPX computing infrasctructure.

ApexVX is delivered fully functional and will run most Linux based application without require code change

The specific version of ApexVX hardware and software described in this manual is only an example of

what Kontron ApexVX technology can bring to its customers. More 3U VPX hardware is constantly being

introduced in the ecosystem by Kontron and provided as additional ApexVX computer profiles Be sure to

contact [email protected].

mailto:[email protected]



ApexVX Getting Started ApexVX Evaluation


Chapter 2 - ApexVX Evaluation

The ApexVX is ready to use out-of-the-box. ApexVX model AP-5985-01010101 described here includes a preinstalled Linux distribution which manages multiple SBCs and customizable I/O boards.This turnkey computeralso contains demo and test software.

It is delivered with a software recovery tool to restore the system to its pristine delivery status (see section 6.1page 18 )

2.1 ApexVX Demo Overview

> 3U VPX Environmentally Sealed computer

> Power dissipation < 150W

> 2 Multiple CPU Core i7 @ 2GHz

> 2GB SDRAM per CPU

> Preloaded Linux Fedora 12

> I/O preset:

> 1 x Display Port

� 1 x Ethernet 10/100

� 2 x FPGA GPIO rear

� 1 x USB

� 1 x RS232

> Conduction-Cooled + Fan-Assist

> Weight < 6kg

> RTCA DO160F compliant

> MIL-STD-810E Shock & Vibration

According to demonstration purpose and location, the base configuration will have to be completed with:

� DP Display port adaptor to graphics display

� AC Mains to 28V PSU converter

� USB Keyboard

� Set of cables (GPIO loopback. HDMI, ETHERNET and SERIAL generic cables)

ApexVX Getting StartedApexVX Evaluation


2.2 Test Setup Overview

1. Plug the unit with the accessories as follows

Label Interface Equipment

J1 Power Kontron Cable + PSU

J3 Display Port eDP Display (not included)

J5 USB USB keyboard + mouse (not included (USB hub needed)

J6 GPIO GPIO loopback cable

2. Power On the ApexVX device: Plug PSU cable on J1.

3. Wait for the Gnome login screen

4. Login as user “Kontron”. (password is “powermp”)

ApexVX Getting Started ApexVX Evaluation


2.3 Start Demo

1. Start Demo by clicking on the « Demo » icon

A terminal windows appears and displays the test sequence in progress.

Please allow 1 minute wait for all test, movies and other monitoring windows to appear.

2. Stop Demo by clicking on « STOP DEMO »

ApexVX Getting StartedDemo Software Descritpion


Chapter 3 - Demo Software Descritpion

What happens when you power on the ApexVX, log into the system and hit the test and demo icon?

The demo software starts performance and unit tests (see section 3.3 page 7) using dedicated scripts withparallel python threads to exercise the complete computer simultaneously with CPU and I/O loads.

While test is running, monitoring of the system behavior is possible in specific windows.

3.1 System Monitoring

The test software monitors temperatures, performances (Ethernet, VxFabric, CPU) thanks to the two followingcommands:

gnome-system-monitor

Figure 2: gnome-system-monitor GUI

Threads results are displayed into a terminal in ASCII text and also in a friendly GUI. �

ApexVX Getting Started Demo Software Descritpion


3.2 Temperature Monitoring

Temperatures are monitored every second trough the following command:

Sensors

‘sensors’ command is used to show the current readings of all sensor chips, and to signal values which are

reaching min/max values (as specified in the configuration file /etc/sensors.conf).

3.3 Performance and Unit tests

3.3.1 Data Plane: VXFabric™ on PCIe

The VXFabric tools and kernel modules are pre-installed and provide high bandwidth communication over thePCIe between CPU nodes. The following command creates PCI heavy loads between the two VX3030 boards:

vxfabric -n [node_src] -N [node_dst] -B 0x400000 -L 0x100

3.3.2 Integrated GPU: Video Test

VX3030 Core i7 CPU includes a powerful GPU inside the main processor chip. In this test, rendering a videosample demonstrates the absence of lag during whole computer stress tests.

vlc --noaudio --loop --width 100 --height 100

/home/kontron/TESTS/MOVIES/kontron_0.mov -I dummy

ApexVX Getting StartedDemo Software Descritpion


3.3.3 OPENGL

Launches a script that display a rotating cube using OPENGL library (run on the on the CPU integrated GPU)

python /home/kontron/TESTS/OPENGL/Cube_kontron.py

Figure 3: OpenGL Sample

3.3.4 Network

The second VX3030 is diskless system. Command iperf allow heavy loads over the ETHERNET between the2 VX3030

iperf -c [IP address]

3.3.5 GPIO (RX/TX 1&2)

Launch script to manage somes of GPIO levels of FMC-SER0

sh /home/kontron/TESTS/APEX_HANDLER/fmc_fp_io_test.sh B

ApexVX Getting Started System Hardware Configuration


Chapter 4 - System Hardware Configuration

In this AP-5985-01010101 sample version, ApexVX is composed of 2 Core i7 CPU boards (VX3030) plus oneFPGA I/O board with FMC (VX3830) and a PCie and GETH switch board (VX3905).

ApexVX has also a spare 3U VPX Slot.

A small breakout board located at the back of the VPX backplane allows to route selected SBC I/O to the ApexVXI/O panel.

From the outside, the I/O panel of AP-5985-01010101 is organized like this:

Label Interface Equipment

J1 Power Specific cable

J2 ETH0 or ETH1 RJ45 socket

J3 Display Port eDP socket

J4 Serial RJ11 socket

J5 USB USB 1/2 Socket

J6 GPIO Specific cable

Inside the AP-5985-01010101, the board layout look like this

Slot Equipment

PSU ApexVX Power Supply

S5 PCIe / GETH switch

S4 Empty

S3 FPGA Board w. FMC

S2 Core i7 SBC (1)

S1 Core i7 SBC (0)

ApexVX Getting StartedSystem Hardware Configuration


4.1 VX3030: Core i7 CPU Boards

Figure 4: VX3030 Functional Description

The Kontron VX3030 is an innovative VPX computing blade for parallel data and signal processing applicationsin the communications, military, aerospace, medical, industrial, and infotainment markets. The Kontron VPXblade VX3030 is the ideal building block for intensive parallel computing workloads where a cluster of KontronVX3030s can be used in full mesh VPX or switched OpenVPX environments. The VX3030 implements Intel'snext generation high performance embedded processor with integrated memory controller and Intel HD graphics- the Intel Core i7 processor - coupled with the highly integrated Intel Platform Controller Hub (PCH) QM57 withnumerous Gigabit Ethernet, SATA, USB 2.0 and PCIe channels.

The VX3030 board comes with EFI BIOS and supports Linux. It is covered by Kontron's long term supplyprogram, which guarantees customers multi-year supply of the product beyond its active life.

VX3030 is a member of compatible Core i7 SBCs from Kontron. This family includes:

� VX3030: Core i7 SBC

� VX3035: 2nd Gen Core i7 SBC (supports AVX signal processing extensions)

� VX304x: 3rd Gen Core i7 SBC (supports 10G I/O, XMC slot and Quad Core Cpus)



4.2 VX3830: Custom I/O FPGA Board

The VX3830 is a member of the Kontron's VITA 46 VPX range of products. The VX3830 is designed to operatein a 3U VPX peripheral slot and provides the resources of a Xilinx Virtex-5 FPGA and VITA57 FPGA MezzanineCard (FMC) slot for designing versatile I/O interface.

The VITA57 FMC standard provides an industry standard mezzanine form factor in support of a flexible, modularI/O interface to an FPGA located on a baseboard or carrier card, the VX3830. It allows the physical I/O interfaceto be physically separated from the FPGA design while maintaining a close coupling between a physical I/O interface and an FPGA through a single connector.


An external loopback implemented on connector JX on the ApexVX I/O Panel. This connector is internally linkedto the FMC-SER0 board sitting on top of the VX3830 carrier card.

Figure 6: FMC-SER0 Functional Description



4.3 VX3905: PCie and GETH Switch Board


The VX3905 is a standard 3U OpenVPX Fabric featuring PCI Express switching and unmanaged GigabitEthernet switching. It is compliant with OpenVPX slot profile SLT3-SWH-6F6U-14.4.1 and module profileMOD3-SWH-6F6U-16.4.1-3 while offering additional configuration options.



4.4 IFDPC5-3U-VPXV1SI: Open VPX Backplane

ApexVX backplane is an OpenVPX Centralised backplane with 4 payload slots and 1 switch slot.

When used with VX3905 PCie and GETH switch board, multiple combinations of payload boards can be usedwith this backplane.

In the typical use, one controlling SBC in slot 0 is the PCIe main root and manages all other boards in payloadslots. Such boards can be XMC, PMC carriers, or FPGA (FMC) boards or even sibling SBC boards accessedas peripherals (thanks to their Non Transparent port)

VX3905 also permits the implementation of multiple independent PCIe domains, allowing two SBCs to managetheir own PCIe peripherals independently. This use allows to implement INDEPENDENT COMPUTERS insidea single case and on a single backplane.

Figure 8: ApexVX OpenVPX Backplane



4.5 PB-IOBRK/APEX : I/O Break Out Board

ApexVX includes a reduced form factor break out board. It is compatible with OpenVPX backplane RTM connectors and has been designed to match Kontron 3U VPX CPU boards I/O routing.

Figure 9: BreakOut Board

BreakOut Board is reduced classical RTM with minimal footprint that allows integration in small chassis.



4.6 Internal Cabling

The sample Kontron baseline computer is made with a generic backplane and discrete cabling from the boardsor break out board to the enclosure external connectors.

ApexVX philosophy is to change this cabling scheme for the deployment phase.

When the application is completely defined and field proven, this I/O cabling can be replaced with a dedicatedVPX backplane and I/O panel. This is the recommended solution for medium to large deployments as it reducesthe integration and maintenance costs. �

The turn-key software and benchmarks delivered with this computer expects AP-5985-01010101 internal signalrouting to be configured as described below:

Figure 10: Internal Cabling

ApexVX Getting StartedSystem Software Configuration


Chapter 5 - System Software Configuration

ApexVX comes with a pre-configured Linux distribution. This configuration manages the two SBCs and theFPGA board. Demos and test programs are provided to exercise the hardware.

5.1 Pre-Configured User Accounts

When ApexVX is powered on, log on as “kontron” user for demos, as “root” for maintenance.

User: kontron

Password: kontron

User: root

Password: powermp

5.2 Network Configuration

Each VX3030 implements 3 GETH channels. One is a BASE-T Ethernet available at the back thanks to thebreak out board, the other two are BASE-BX Ethernet channels and are routed inside the backplane to the switchslot and into VX3905. The expected use of the delivered configuration is as follows:

� VX3030 (1) BASE-T Ethernet port is connected to the external network through the connector XX. It can beused as the ApexVX mainmonitoring link.

Network: 172.20.xxx.xxx

� Both BASE-BX Ethernet ports are connected to the internal computer network via the VX3905

Networks: 192.168.1.0 / 192.168.2.0. These channels implement the DATA PLANE for the ApexVX, allowingbulk data transfer between SBCs.

5.3 OS and Storage Configuration

The first VX3030 (1) boots from a SATA FLash mezzanine. It is directly connected on the CPU base board.

The second VX3030 (2) operates as a linux diskless client and boots from the internal computer network. PXEand NFS servers run on the first VX3030 board.

ApexVX Getting Started System Software Configuration


5.4 PCIe Configuration and VXFabric™

The first VX3030(1) is able to access all other boards in the computer via theVX3905 switch. All other boards are accessed by the first board as PCieperipheral boards. This is also true for the second VX3030(2) thanks to its nontransparent (NT) PCIe port feature (this feature is controlled by the BIOS. Whenthe board is NOT in the first slot, it becomes a PCIe peripheral).

In this multiple SBC setting Kontron VXFabric can be used. VXFabric is aTCP/IP implementation on top of PCIe. Implemented as a linux kernel module,it can provide another internal network between several SBCs running Linux inKontron VPX computers. VXFabric use is recommended whenever the PCIe x4bandwidth is available while the GETH internal network, implemented onBaseBX channels, is saturated by external data in or out.

5.5 Display

Display port screen available on connector J3 is connected on the first VX3030 through the breakout board. Itcan support Screen definitions up to 1920 x 1080.

The graphics engine is the Intel HD Graphics which is part of the Core I7 CPU chips.

5.6 Serial Terminal

A serial terminal is connected to both VX3030 on connector J4. It allows to interact with Linux but also with eachSBC EFI BIOS serial line console. Thanks to VX3030 EFI BIOS, which implement BIOS console redirect, thecomplete BIOS configuration can be done without any graphics screen or nor USB keyboard. �

5.7 GPIO

An external loopback cable is provided to run the test suite. The GPIO test suite is a series of GPIO assertionand detection of changes. It is using Linux standard GPIO device drivers.

ApexVX Getting StartedTroubles Shooting


Chapter 6 - Troubles Shooting

The following sections explain how to recover from various problems or maintenance issues.

6.1 Restoring ApexVX Entire Software Content

The system is delivered with a software recovery tool (USB stick). It can be used to restore the complete Apexsoftware to its original content.

This USB stick is referenced TTK (Target Tool Kit) and is built from Red Hat Fedora 16 live CD

technology.

From this point on, the operation takes XX mn.

How to Proceed:

1. Plug the usual ApexVX peripherals as explained in section 2.2 page 4 (USB Keyboard, Screen)

2. Plug the USB stick in connector (JXXX)

3. Boot ApexVX using the USB stick as the boot device.

(press <F7> during the BIOS startup to select USB as the first boot media).

4. Let Grub Main Menu automatically starts

5. Let the system boot into graphics mode

6. From the Gnome Desktop, open a "gnome terminal" to enter the following commands.

7. Switch to root mode:

[liveuser@localhost ~]$ su - [root@localhost ~]#

8. Go to IMG Folder:

[root@localhost ~]# cd /mnt/live/IMG

9. Start restore script:

[root@localhost ~]# ./build_flash.sh /dev/sda /mnt/live/IMG/

10.Wait until the end of the install process (“Image generation ended. Please restart.”).

11.Halt ApexVX

[root@localhost ~]# halt

12.Wait until complete power down sequence

13.Unplug the USB key

ApexVX Getting Started Troubles Shooting


6.2 VX3030 Boot Server/Diskless (RE) Configuration

The operation described here is required in two situations:

� After a fresh (re)installation of the software (see section 6.1 page 18)

� After a change in the SBC boards, creating a change in MAC addresses,

The VX3030 (location 1) and VX3030 (location 2) are connected through the VX3905 Ethernet switch . A networkboot (through BIOS PXE) is set up to get a diskless Linux system on the VX3030 (location 2) with the disklessservices running from VX3030 (location 1).

1. Power On ApexVX device. With keyboard and screen attached

2. Wait for the login screen

3. Login as kontron user . Gnome session starts

4. Select « Demo » icon

If something goes wrong, please check following points.

� Open a gnome Shell Terminal

The package multinodes-diskless is available and is used to setup and configure a NFS exportable root

filesystem and to provide a kernel and an initrd filesystem for PXE boot.

� Edit the file /etc/diskless/image.xml and modify the MAC adresses according to the MAC address of the

second SBC (location 1): enter the following linux command:

Cat /proc/net/arp | grep eth1

� Set this address in the file /etc/diskless/image.xml:

#<nodemap id=”diskless-cluster_A” clients=”diskless_A” default=”1”> # <match criterium=”macaddress”> # <value>00:00:DE:40:36:F9</value> # </match> # <ip>192.168.1.%(1+order.value)</ip>

� Set this address in the file /etc/diskless/image.xml:

� Configure the exportable root file system on the server

# diskless -B

This re-builds the filesystem used by the nfs server in /diskless/layers/

This process takes a few minutes.

ApexVX Getting StartedCustomizing ApexVX


Chapter 7 - Customizing ApexVX

When you need to design your own version of ApexVX to match your application requirements, the followinginformation will help you find the various components, how they look like and what is their order code.

7.1 AP-5985-01010101 Parts List

ItemType

Designation Part NumberEngineering

Level

BIOS /FirmwareRevision

Level

Chassis Chassis FS-5985-xxxxx

Backplane Backplane IFDPC5-3U-VPXV1SI

PSU PSU 28V 200W xxx

SBC VX3030 VX3030-RC22-0S000

SBC VX3030 VX3030-RC22-0S000

Carrier VX3830 VX3830-RC-0N000

Switch VX3905 VX3905-RC-0N000

RTM Break Out Board for VX3030 PB-IOBRK/APEX

Flash Storage

SATA FLASH mezzanine forVX3030

FDM-SATA-32GB-C0V

BIOS BIOS Firmware for VX3030 board 11328

OS Fedora 12 ki7 BSP 11245

Demo/TestSoftware

ApexVX Demo 1.0

ApexVX Getting Started Customizing ApexVX


ApexVX is built using standard Kontron parts. Learn to recognize them :

Figure 11: VX3030 (Board 1 & Board 2) Figure 12: VPX Backplane (A1)

Figure 13: FMC-SER0 (Board 7) Figure 14: VX3905 (Board 5)

Figure 15: Break-Out Board (Board 8) Figure 16: VX3830 (Board 3)



7.2 Assembling VX3830 and FMC Mezzanine

Kontron VX3830 is a Customisable I/O board. It features a Xilinx VIRTEX 5 FPGA board with a FMC I/O module.In ApexVX all boards are conduction-cooled and the FPGA I/O are routed to the backplane as follow:

VX3830 Board is coupled with a GPIO FMC IO board.

Fit the FMC board as described:

ApexVX Getting Started Customizing ApexVX


7.3 FMC-SER0 to VX3830 Rear VPX GPIO Pin Assignment

This table allows the customization of ApexVX I/Os. Thanks to the Virtex5 onboard the VX3830, many I/Ointerfaces can be implemented using XILINX development tools. The following table indicates the mapping fromFMC I/Os to the backplane wafers. From the backplane to the I/O panel of VXFabric, two solutions exist: customdiscrete cabling (low rate deployments) or Specific Backplane + I/O board (high runners)

P0 Wafer Assignment

Wafer ROW G ROW F ROW E ROW D ROW C ROW B ROW A

1 +12V +12V +12V N.C.

2 +12V +12V +12V N.C. . .

3 +5V +5V +5V N.C. +5V +5V +5V

4 GND -12V_AUX GND SYSRESET* NVMRO

5 GAP* GA4* GND 3V3_AUX GND

6 GA3* GA2* GND GND GA1* GA0*

7 GND P0_CLK0- P0_CLK0+ GND

8 GND REF_CLK- REF_CLK+ GND N.C.(RFU) N.C.(RFU) GND

CASE GND

P1 Wafer Assignment


1 GPIO0 GND PCIE0_TX- PCIE0_TX+ GND PCIE0_RX- PCIE0_RX+Date

Plane

Port1

2 GND PCIE1_TX- PCIE1_TX+ GND PCIE1_RX- PCIE1_RX+ GND

3 NC GND PCIE2_TX- PCIE2_TX+ GND PCIE2_RX- PCIE2_RX+

4 GND PCIE3_TX- PCIE3_TX+ GND PCIE3_RX- PCIE3_RX+ GND

5 SYS_CON* GND (PCIE0_TX) (PCIE0_TX) GND (PCIE0_RX) (PCIE0_RX)Date

Plane

Port 2

6 GND (PCIE1_TX) (PCIE1_TX) GND (PCIE1_RX) (PCIE1_RX) GND

7 NC GND (PCIE2_TX) (PCIE2_TX) GND (PCIE2_RX) (PCIE2_RX)

8 GND (PCIE3_TX) (PCIE3_TX) GND (PCIE3_RX) (PCIE3_RX) GND

9 NC GND NC NC GND NC NCExpan

sion

Plane

10 GND NC NC GND NC NC GND

11 NC GND NC NC GND NC NC

12 GND NC NC GND NC NC GND

13 GPIO1 GND NC NC GND NC NC User

Defined14 GND NC NC GND NC NC GND

15 MASKEABLE

_RST#

GND NC- NC GND NC NCControl

Plane16 GND NC NC GND NC NC GND

Case GND



P2 Wafer Assignment


1 GND RX_1 RX_2 GND TX_1 TX_2

FMC

2 GND GND GND GNDHA20P_GPI

O_1/GND

HA20N_GPI

O_2/GNDGND


4 GND RX_5 RX_6 GND TX_5 TX_6 GND

5 GND GND GND GNDHB3P_GPIO

_3/GND

HB3N_GPIO

_4/GND

6 GND RX_7 RX_8 GND TX_7 RX_16 GND


8 GND GND GND GNDHB13P_GPI

O_5/GND

HB13N_GPI

O_6/GNDGND



11 GND GND GND GNDHB2P_GPIO

_7/GND

HB2N_GPIO

_8/GND


13 GNDHB10P_GPI

O_9/GNDGPIO11 GND

HB8P_GPIO

_10/GNDGPIO12

14 GND GPIO13 GPIO14 GND GPIO15 GPIO16 GND

15 GND GPIO17 GPIO18 GND GPIO19 GPIO20

16 GND GPIO21 GPIO22 GND GPIO23 GPIO24 GND

Europe, Middle East & Africa North America Asia Pacific

Kontron Modular Computers S.A.S.150 rue Marcelin Berthelot - BP 244ZI TOULON EST83078 TOULON CEDEX - FranceTel.: +33 (0) 4 98 16 34 00

14118 Stowe DrivePoway, CA 92064-7147USATel.: +1 888 294 4558Fax: +1 858 677 0898

17 Building,Block #1,ABP.188 Southern West 4th Ring RoadBeijing 100070, P.R.ChinaTel.: + 86 10 63751188Fax: + 86 10 83682438

[email protected] [email protected] [email protected]

If it's embedded, it's Kontron.




apexvx - rtsoftapexvx getting started apexvx concept and usage sd.dt.-g01-0e page 1 chapter 1 -...

Documents