Kontron pITX-SP User Manual

pITX-SP

KTD-S0003-C

User Information

Table of Contents

» Table of Contents «

1 User Information .............................................................................1

1.1 About This Document.................................................................................................... 1

1.2 Copyright Notice.......................................................................................................... 1

1.3 Trademarks................................................................................................................. 1

1.4 Standards................................................................................................................... 1

1.5 Warranty .................................................................................................................... 1

1.6 Life Support Policy ....................................................................................................... 2

1.7 Technical Support ........................................................................................................ 2

2 BIOS Update ...................................................................................3

2.1 AFUDOS (AMI) ............................................................................................................. 3

2.2 AFUWIN (AMI) ............................................................................................................. 3

2.3 BFLASH (KONTRON) ...................................................................................................... 3

3 Graphics Interface............................................................................4

3.1 LCD/LVDS Technology Overview ...................................................................................... 4

3.1.1 Detailed Timing Descriptor (EDID or DisplayIDTM) ............................................................................. 4

3.1.2 24 Bit Color Mapping Tips............................................................................................................6

3.2 EDID 1.3 Specification (VESA) ........................................................................................ 7

3.3 DisplayIDTM Specification (VESA) ..................................................................................... 7

3.3.1 DisplayIDTM Parameter Summary ...................................................................................................7

3.3.2 DisplayIDTM Restrictions ..............................................................................................................8

3.3.3 LCD Panel Selection ................................................................................................................... 8

3.3.4 DisplayID

3.3.5 Building DisplayIDTM File ........................................................................................................... 10

3.3.6 Erasing DisplayIDTM Record ........................................................................................................ 10

3.3.7 EEPROM Update Tool ................................................................................................................ 10

3.4 What means GMA and IEGD? ..........................................................................................11

3.4.1 The GMA Driver........................................................................................................................ 11

3.4.1.1 DVI Monitor Selection............................................................................................................... 12

3.4.2 The IEGD Driver ....................................................................................................................... 12

TM

Windows

®

Tool .......................................................................................................... 9

3.5 H.264 Support for Linux ...............................................................................................13

4 Serial-ATA Interface ....................................................................... 14

4.1 Native PCI IDE Controller ..............................................................................................14

4.2 RAID/AHCI Controller ..................................................................................................14

pITX-SP Software Guide

User Information

Table of Contents

5 SDIO/microSD Card Interface............................................................ 15

5.1 DOS Boot...................................................................................................................15

5.2 Linux Boot.................................................................................................................15

5.3 Windows

5.4 Windows

®

XP and Windows

®

XP Embedded or Windows

®

7 Boot.................................................................................16

®

7 Embedded Boot......................................................16

6 CPLD Interface............................................................................... 17

6.1 Special Hints..............................................................................................................18

6.1.1 Reserved Bits.......................................................................................................................... 18

6.1.2 GPIO Input Register ................................................................................................................. 18

6.1.3 Fan Divisor ............................................................................................................................. 18

6.2 Programming Examples................................................................................................19

6.2.1 Watchdog Example................................................................................................................... 19

6.2.2 Digital I/O Example.................................................................................................................. 20

6.2.3 I2C with GPIOs Example ............................................................................................................ 21

6.2.4 GPIO IRQ Example.................................................................................................................... 27

6.2.5 Fan Control Example ................................................................................................................ 30

6.2.6 Fan Speed Example .................................................................................................................. 31

7 Tri-Axis Accelerometer Example ........................................................ 33

8 DOS Problems................................................................................ 36

8.1 Keyboard Driver..........................................................................................................36

8.2 DR-DOS 7.03 ..............................................................................................................36

8.3 Gate A20 and LAN Boot ................................................................................................36

9 ACPI Thermal Management............................................................... 37

9.1 Passive Cooling ..........................................................................................................37

9.2 Active Cooling ............................................................................................................37

9.3 Temperature Limits .....................................................................................................37

9.4 Temperature Identifier.................................................................................................37

10 ACPI Wakeup ................................................................................. 38

10.1 Wake On USB..............................................................................................................38

10.1.1 Windows® XP .......................................................................................................................... 38

10.1.2 Linux .................................................................................................................................... 38

pITX-SP Software Guide

User Information

Table of Contents

11 JIDA32 Interface............................................................................ 39

11.1 Generic Part...............................................................................................................39

11.2 Display Part ...............................................................................................................39

11.3 I2C-Bus Part ..............................................................................................................39

11.3.1 Bus Number 0 (JIDA)................................................................................................................ 40

11.3.2 Bus Number 1 (Generic) ............................................................................................................ 40

11.3.3 BusNumber 2 (JILI) ................................................................................................................. 40

11.4 CPU Performance Part ..................................................................................................40

11.5 Hardware Monitor Part.................................................................................................41

11.5.1 Temperature........................................................................................................................... 41

11.6 Digital I/O Part...........................................................................................................41

11.7 Watchdog Part............................................................................................................41

11.8 JIDA32 Windows® Programming.....................................................................................42

11.8.1 Program Language C ................................................................................................................ 42

11.8.2 Program Language DELPHI ........................................................................................................ 43

11.8.3 Program Language VISUAL BASIC (VB.NET)................................................................................... 46

11.8.4 Module Definition File .............................................................................................................. 48

11.9 JIDA32 Linux Programming...........................................................................................50

12 Linux Support ............................................................................... 52

12.1 openSUSE® 11.1 .........................................................................................................52

12.2 Fedora® 11 ................................................................................................................52

12.3 Reboot Problem..........................................................................................................53

Appendix A: Reference Documents .............................................................. 54

Appendix B: Document Revision History .......................................................55

pITX-SP Software Guide

KTD-S0003-C Page 1 User Information

1 User Information

1.1 About This Document

This document provides information about products from KONTRON Technology A/S and/or its subsidiaries.
No warranty of suitability, purpose or fitness is implied. While every attempt has been made to ensure that
the information in this document is accurate the information contained within is supplied “as-is” - no
liability is taken for any inaccuracies. Manual is subject to change without prior notice.
KONTRON assumes no responsibility for the circuits, descriptions and tables indicated as far as patents or
other rights of third parties are concerned.

1.2 Copyright Notice

Copyright © 2009-2010, KONTRON Technology A/S, ALL RIGHTS RESERVED.
No part of this document may be reproduced or transmitted in any form or by any means, electronically or
mechanically, for any purpose without the express written permission of KONTRON Technology A/S.

1.3 Trademarks

Brand and product names are trademarks or registered trademarks of their respective owners.

1.4 Standards

KONTRON Technology A/S is certified to ISO 9000 standards.

1.5 Warranty

This product is warranted against defects in material and workmanship for the warranty period from the
date of shipment. During the warranty period KONTRON Technology A/S will at its discretion decide to
repair or replace defective products.
Within the warranty period the repair of products is free of charge as long as warranty conditions are
observed.
The warranty does not apply to defects resulting from improper or inadequate maintenance or handling by
the buyer, unauthorized modification or misuse, operation outside of the product’s environmental speci­fications or improper installation or maintenance.
KONTRON Technology A/S will not be responsible for any defects or damages to third party products that
are caused by a faulty KONTRON Technology A/S product.

pITX-SP Software Guide

KTD-S0003-C Page 2 User Information

1.6 Life Support Policy

KONTRON Technology's products are not for use as critical components in life support devices or systems
without express written approval of the general manager of KONTRON Technology A/S.
As used herein:
Life support devices or systems are devices or systems which
a) are intended for surgical implant into body or
b) support or sustain life and whose failure to perform, when properly used in accordance with instructions
for use provided in the labelling, can be reasonably expected to result in significant injury to the user.
A critical component is any component of a life support device or system whose failure to perform can be
reasonably expected to cause the failure of the life support device or system or to affect its safety or
effectiveness.

1.7 Technical Support

Please consult our web site at http://www.kontron.com/support for the latest product documentation,
utilities, drivers and support contacts

. In any case you can always contact your board supplier for technical
support.
Before contacting support please be prepared to provide as much information as possible:
Board identification:







Board configuration:







System environment:







Type
Part number (find PN on label)
Serial number (find SN on label)

DRAM type and size
BIOS revision (find in the BIOS Setup)
BIOS settings different than default settings (refer to the BIOS Setup section)

O/S type and version
Driver origin and version
Attached hardware (drives, USB devices, LCD panels ...)

pITX-SP Software Guide

KTD-S0003-C Page 3 BIOS Update

2 BIOS Update

The AMI and the KONTRON update tool is available for two operating systems: DOS and Windows® (e.g.

®

Windows
Software conditions:

2.1 AFUDOS (AMI)

Only the following combination of command line arguments has been tested and should be used for the
update process. The syntax of the DOS update tool is:

AFUDOS <BIOS filename> /X /P /B /N /C

/X = don't check ROM ID
/P = program main BIOS
/B = program boot block
/N = overwrite NVRAM (setup settings)
/C = destroy CMOS checksum

XP, Vista 32/64 or Windows® 7).

Operating System Tool Name Required Revision

DOS

Windows®

AFUWIN.EXE + UCORESYS.SYS (UCOREW64.SYS) 4.41 or greater

AFUDOS.EXE 4.23 or greater

BF.EXE 7.41 or greater

BF.EXE 7.41 or greater

2.2 AFUWIN (AMI)

For 32bit operating systems the file UCORESYS.SYS and for 64bit systems the file UCOREW64.SYS must be
used (located in the same folder as AFUWIN.EXE). AFUWIN can either be executed using the same command
line parameters as for AFUDOS or it can be executed in GUI mode by double klicking on it.

2.3 BFLASH (KONTRON)

In this manual the abbreviation BF is used for BFlash. This also matches with the actual name of the tool
(BF.EXE). BF can be used to read and write data to and from BIOS flash. With this tool it's possible to
update the BIOS, change DMI codes, setup vendor codes and save copies of all data. The copies can be used
as master data for mass production.
Type BF <ret> from DOS prompt to see the BFlash version number and the board version. Only the following
combination of command line arguments has been tested and should be used for the update process.

BF read <BIOS filename> 0 100000
BF write <BIOS filename> 0

pITX-SP Software Guide

KTD-S0003-C Page 4 Graphics Interface

3 Graphics Interface

3.1 LCD/LVDS Technology Overview

3.1.1 Detailed Timing Descriptor (EDID or DisplayIDTM)

The input fields Pixel Clock, Horizontal Active, Horizontal Blank, Horizontal Sync Offset, Horizontal Sync
Width, Vertical Active, Vertical Blank, Vertical Sync Offset and Vertical Sync Width must be filled in with the
correct values according to the panel’s data sheet. In many cases the value for Horizontal/Vertical Blank
cannot be read directly from the data sheet. Instead terms such as Display Period (active pixels/lines) or
Horizontal/Vertical Total appear.
In this case the following calculation can be made:

⇒ Blank Value = Total Value – Active Value.

Sometimes the datasheet does not specify Sync Offset and/or Sync Width. In this case the permissible
values can only be determined though testing. However the rule is:

⇒ The sum of Sync Offset and Sync Width must not exceed the value for Horizontal/Vertical Blank.

Also datasheets are often different for displays with double pixel clock. If Pixel Clock and Horizontal Values
seem to be halved this must be corrected for input:

⇒ The values must always be entered as though it were a panel with single pixel clock.

Example 1:

PRIMEVIEW PM070WL4 (single pixel clock)
Data sheet specifications:
Clock Frequency [typ.] 32 MHz
HSync Period [typ.] 1056 Clocks (equivalent to Horizontal Total)
HSync Display Period [typ.] 800 Clocks (equivalent to Horizontal Active)
HSync Pulse Width [typ.] 128 Clocks
HSync Front Porch [typ.] 42 Clocks
HSync Back Porch [typ.] 86 Clocks
VSync Period [typ.] 525 Lines (equivalent to Vertical Total)
VSync Display Period 480 Lines (equivalent to Vertical Active)
VSync Pulse Width [typ.] 2 Lines
VSync Front Porch [typ.] 10 Lines
VSync Back Porch [typ.] 33 Lines

Result:

Pixel Clock 32
Horizontal Active 800
Horizontal Blank 256 ((128 + 42 + 86) → H. Pulse Width + H. Front Porch + H.
Back Porch)
Horizontal Sync Offset 42 (H. Front Porch)
Horizontal Sync Width 128 (H. Pulse Width)
Vertical Active 480
Vertical Blank 45 ((2 + 10 + 33) → V. Pulse Width + V. Front Porch + V. Back
Porch)
Vertical Sync Offset 10 (V. Front Porch)
Vertical Sync Width 3 (V. Pulse Width)

pITX-SP Software Guide

KTD-S0003-C Page 5 Graphics Interface

Example 2 (not useable on pITX-SP):

SHARP LQ190E1LW01 (double pixel clock)
Data sheet specifications (no definition of Sync Offset and Sync Width):
Clock Frequency [typ.] 54 MHz
Horizontal Period (1) [typ.] 844 Clocks (equivalent to Horizontal Total)
Horizontal Display Period 640 Clocks (equivalent to Horizontal Active)
Vertical Period [typ.] 1066 Lines (equivalent to Vertical Total)
Vertical Display Period 1024 Lines (equivalent to Vertical Active)

Result:

Pixel Clock 108 (2 x 54 MHz)
Horizontal Active 1280 (2 x 640 Clocks)
Horizontal Blank 408 ((844 – 640) x 2 Clocks)
Horizontal Sync Offset 45 (normally approx. 10 – 15 % of Horizontal Blank)
Horizontal Sync Width 140 (normally approx. 30 – 70 % of Horizontal Blank)
Vertical Active 1024
Vertical Blank 42 (1066 – 1024 Lines)
Vertical Sync Offset 1 (normally approx. 1 – 3 Lines)
Vertical Sync Width 3 (normally approx. 1 – 15 Lines)

Example 3 (not useable on pITX-SP):

LG-PHILIPS LM170E01-TLA1 (double pixel clock)
Data sheet specifications:
Clock Frequency [typ.] 54 MHz
Hsync Period [typ.] 844 Clocks
Horiz. Valid [typ.] 640 Clocks
Horiz. Back Porch [typ.] 124 Clocks
Horiz. Front Porch [typ.] 24 Clocks
Vsync Period [typ.] 1066 Lines
Vert. Valid [typ.] 1024 Lines
Vert. Back Porch [typ.] 38 Lines
Vert. Front Porch [typ.] 1 Line

Result:

Pixel Clock 108 (2 x 54 MHz)
Horizontal Active 1280 (2 x 640 Clocks → Horizontal Addr. Time)
Horizontal Blank 408 ((844 – 640) x 2 Clocks)
Horizontal Sync Offset 48 (2 x 24 Clocks → Horizontal Front Porch)
Horizontal Sync Width 112 (((408/2 – 124 – 24) x 2) → H. Blank – H. Back Porch – H.
Front Porch)
Vertical Active 1024 (Vertical Addr. Time)
Vertical Blank 42 (1066 – 1024 Lines)
Vertical Sync Offset 1 (Vertical Front Porch)
Vertical Sync Width 3 (Vertical Blank – Vertical Back Porch – Vertical Front Porch)

The following picture shows the typical video timing.

Timing Parameter Definitions

Blanking

Active Part

Blanking

H-/V-Video

Front
Porch

H-/V-Sync

Sync
Pulse
Width

pos.
Sync

neg.
Sync

Back
Porch

Address Time

Total

pITX-SP Software Guide

Front
Porch

Sync
Pulse
Width

pos.
Sync

neg.
Sync

Back
Porch

KTD-S0003-C Page 6 Graphics Interface

ce

3.1.2 24 Bit Color Mapping Tips 3.1.2 24 Bit Color Mapping Tips

The double pixel clock or 24-bit color depth can generally be taken from the datasheet. There are two

The double pixel clock or 24-bit color depth can generally be taken from the datasheet. There are two
interface modes existing at 24-bit color depth: FPDI (F

interface modes existing at 24-bit color depth: FPDI (F
I

nterface). Some panels use the line SELL LVDS (SELect Lvds data order). The LVDS data assignment in the

lat Panel Display Interface) or LDI (LVDS Display

datasheet can give you an indication by the last channel (e.g. RX3/TX3 – SELL LVDS = low) wether it is a LDI
panel (contains the lowest bits). Most panels have a FPDI interface.

Example:

FPDI data assignment (LVDS channel 3 even or odd):
Tx/Rx27 Red 6 (e.g. even: RE6 or ER6)
Tx/Rx5 Red 7
Tx/Rx10 Green 6 (e.g. even: GE6 or EG6)
Tx/Rx11 Green 7
Tx/Rx16 Blue 6 (e.g. even: BE6 or EB6)
Tx/Rx17 Blue 7
Tx/Rx23 not used

LDI data assignment (LVDS channel 3 even or odd):
Tx/Rx27 Red 0 (e.g. even: RE0 or ER0)
Tx/Rx5 Red 1
Tx/Rx10 Green 0 (e.g. even: GE0 or EG0)
Tx/Rx11 Green 1
Tx/Rx16 Blue 0 (e.g. even: BE0 or EB0)
Tx/Rx17 Blue 1
Tx/Rx23 not used

TxClk

TxOut0

G0

R5

R4

R3

R2 R1

R0

FPDI

TxOut1

TxOut2

B1

DE

B0

VS

G5 G4 G3 G2 G1

HS

B5

B4

B3

B2

TxOut3

B7

B6

G7 G6 R7

R6

t

cycle

LDI

TxClk

TxOut0

TxOut1

G2 R7 R6 R5

B3

R4

R3

R2

G3G4G5G6G7B2

TxOut2

TxOut3

DE VS HS B7 B6 B5

B1

B0 G1 G0

R1

B4

R0

pITX-SP Software Guide

pITX-SP Software Guide

KTD-S0003-C Page 7 Graphics Interface

3.2 EDID 1.3 Specification (VESA)

The EDID (Extended Display Identification Data) record has a fixed structure. The first 8 bytes contain the
distinctive identification 00h, FFh, FFh, FFh, FFh, FFh, FFh, 00h. The end of the record is marked by the
checksum (1 byte). The result of the addition of all bytes including the checksum has to be zero.
For a comprehensive support of the majority of available panels you don't need all fields of the EDID
record. The Detailed Timing Descriptor (18 bytes) is the most important field. No 24bit panels (FPDI/LDI)
are supported though. This means EDID should only be used for 18bit panels.
For further information please consult the official EDID specification from the VESA comitee which has to be
payed.

3.3 DisplayID

TM

Specification (VESA)

Intended as a replacement for all previous EDID versions DisplayIDTM contains many new features. It's a
structure with several well defined elements (tags). Not every element that is listed in the specification has
to be part of the resulting data set (basic section).
KONTRON has decided to use this selection of tags (mandatory presence).

Tag Description

00h Product Identification Data Block (Vendor ID, Product Code, Manufacturing Date ...)

03h Type I Detailed Timing Data Block (Pixel Clock, Horizontal/Vertical Data ...)

0Ch Display Device Data Block (Device Technology, Operating Mode, Color Depth ...)

0Dh Interface Power Sequencing Data Block (Power On/Off Timing)

0Fh Display Interface Data Block (Interface Type, Interface Attribute ...)

3.3.1 DisplayIDTM Parameter Summary

Only a part of the parameters used in the DisplayIDTM Windows® tool are interpreted by a specific board. The
following table shows a summary of the used parameters (valid for pITX-SP).

Group Parameter Comment

Type I Timing Pixel Clock

Type I Timing Horizontal Active

Type I Timing Horizontal Blank

Type I Timing Horizontal Sync Offset Front porch

Type I Timing Horizontal Sync Width

Type I Timing Vertical Active

Type I Timing Vertical Blank

Type I Timing Vertical Sync Offset Front porch

Type I Timing Vertical Sync Width

Display Interface 1 Bits per Pixel Color depth (18 or 24bit)

Display Interface 2 Signal Polarity Only H-Sync and V-Sync

pITX-SP Software Guide

KTD-S0003-C Page 8 Graphics Interface

3.3.2 DisplayIDTM Restrictions

Depending on the graphic controller not all features can be used. The following table shows the most im­portant restrictions.

Restrictions for pITX-SP

Panels with dual or quad clock not supported (2 or 4 Pixel per Clock)

Panels with LDI 24bit color mapping not supported

Only normal DE mode possible

Variable power sequencing not supported

3.3.3 LCD Panel Selection

The choice of an LCD display is basically defined by two parameters.

Parameter Value

Pixel per Clock (Channels) 1

Maximum Pixel Clock 112 MHz

Currently this leads to a maximum resolution of

With the GMA driver (see details below) it is not guaranteed that every resolution can be achieved. There
can also be differences between the Windows
the correct function of the board for untypical resolution. In principal the use of DisplayID
lizing every special display resolution. For this a valid DisplayID
EEPROM. Additionally the BIOS Setup entry

must be set to Auto.
Many displays with a resolution up to XGA (1024 x 768) have a digital (TTL) interface. KONTRON offers a
special adapter to connect these displays to the LVDS interface (KAB-ADAPT-LVDStoTTL with part number

61029).

1366 x 768 Pixel (e.g. SHARP LK315T3LA31)

®

XP und Windows® Vista driver. KONTRON does not guarantee

TM

dataset must be written to the onboard

Advanced/Display Configuration/Flat Panel Type

TM

allows rea-

Note: The fact that a display is mentioned as an example does not mean that this display is approved by KONTRON.

pITX-SP Software Guide

KTD-S0003-C Page 9 Graphics Interface

3.3.4 DisplayIDTM Windows® Tool

The DisplayIDTM parameter can be modified with the DisplayIDTM Windows® tool.

For an example the following picture shows the input fields for the Detailed Timing parameters.

For more information see the documentation of the DisplayID

kontron.com).

pITX-SP Software Guide

TM

tool (software can be downloaded from

KTD-S0003-C Page 10 Graphics Interface

The DisplayIDTM Editor saves the parameters in a intermediate file format. The file extension is 'KDD' (Kon-

isplayIDTM Data). This file format cannot be used to program the onboard EEPROM.

tron D
For transfering this file format into the binary file format for the EEPROM apply the Converter.

3.3.5 Building DisplayIDTM File

Start the Windows® tool DisplayID.exe.



Use the Editor if you want to modify an existing DisplayIDTM file or select New to create a



complete new record.

Change respectively enter new parameters.



Save the parameters in a file with the extension 'KDD'.



Open the saved 'KDD'-file using the Converter.



Save the binary file with the extension 'KDB' (Kontron DisplayIDTM Binary).



Program the onboard EEPROM using the board specific DOS update tool.



3.3.6 Erasing DisplayIDTM Record

Programming the first 128 bytes in the EEPROM with the values 00h or FFh deletes a valid DisplayIDTM
record.

3.3.7 EEPROM Update Tool

The syntax of the DOS EEPROM update tool is:

PXSP-DID <option> <filename>

/W = read a file (must be KDB-format) and write the content to the EEPROM
/R = read the EEPROM and write the content to a file
/C = read a file and compare the content with the EEPROM
/D = clear the EEPROM content (without filename)

pITX-SP Software Guide

KTD-S0003-C Page 11 Graphics Interface

3.4 What means GMA and IEGD?

Intel® works with two different strategies for the VGA BIOS and the graphic drivers: GMA (Graphics Media

ccelerator) as the standard VGA BIOS for desktop PC´s and IEGD (Intel® Embedded Graphics Driver) for

A

®

special cases. The GMA VGA BIOS allows also the use of an IEGD graphic driver (Windows
Whereas the IEGD VGA BIOS should only be used with the corresponding graphic driver.
The GMA environment supports all available resolution within the operating system - the IEGD environment
particularly run with a discrete resolution (lower secondary resolutions can be used). However it is a big
benefit that the IEGD SDK is freely available and can be downloaded as freeware from the Intel
The following table shows a list of the most important parameters of the graphic controller which are
important for the driver performance respectively the applications based on it (valid for pITX-SP):

Parameter Value Comment

Max. Frame Buffer Size 8 MB Shared memory, DMA access

Max. Aperture Space 256 MB Untrusted buffer

No. of Pipes / Ports 2 Independent graphic engines

Graphics Clock 200 MHz

Integrated Codecs

DirectX Support 10.1

MPEG2, MPEG4,

H.264, VC1, WMV9

or Linux).

®

website.

3.4.1 The GMA Driver

The GMA driver from Intel® can only be used on Windows® operating systems.

Operating System Support Comment

Windows® XP SP2 and SP3

Windows® VISTA32

Windows® 7 (32 Bit)







The driver supports dual display support. For the synchronous use of both display interfaces in a Windows
operating system the BIOS Setup entry Boot Display Device must be set to LCD only. The BIOS respectively
the driver can't notice whether a LVDS display is connected but a DVI monitor can be detected through the
DDC interface and the hotplug pin.

Another driver as is used on VISTA32

®

pITX-SP Software Guide

KTD-S0003-C Page 12 Graphics Interface

3.4.1.1 DVI Monitor Selection

The following table gives an overview about the possible resolutions which can be displayed on a DVI moni­tor. Generally the best result can be achieved when the nominal resolution of the DVI-monitor is used.
ATTENTION: These resolutions are not valid for the LVDS interface of the pITX-SP (see chapter LCD Panel
Selection).

Resolution Aspect Ratio

1920 x 1200 16 : 10

1920 x 1080 16 : 9

1680 x 1050 16 : 10

1600 x 1200 4 : 3

1440 x 900 16 : 10

1366 x 768 16 : 9

1280 x 1024 5 : 4

1280 x 960 4 : 3

1152 x 864 4 : 3

1024 x 768 4 : 3

3.4.2 The IEGD Driver

The Intel® Embedded Graphics Drivers are developed specifically for embedded Intel® Architecture-based
platforms. IEGD offers embedded customers extended life support that correlates with the extended life

®

support of embedded silicon products. Intel

®

Linux distributions and Windows

operating systems. This package also contains a VGA-BIOS which can be

configured. What are the new enhancements added to the Intel

 OpenGL 2.0 support (Windows
 Improved 3D performance
 Hardware-enabled video decode
 Certified Output Protection Protocol (COPP) support on Windows

The IEGD driver supports a lot more operating system than the GMA driver.

Operating System Support

Windows® XP SP2 No

Windows® XP SP3

Windows® VISTA32 No

Windows® 7 (32 Bit) No

Windows® CE 5.0 / 6.0

Linux Fedora® Distribution

Linux Suse® Distribution No

Linux Ubuntu® Distribution

Linux Red Hat® Embedded

Linux Wind River®

Embedded Graphics Drivers have been validated on specific

®

Embedded Graphics Drivers?

®

and Linux)

®

XP













pITX-SP Software Guide

KTD-S0003-C Page 13 Graphics Interface

The IEGD package can be downloaded from the website http://edc.intel.com/Software/Downloads/IEGD
(KONTRON Technology A/S can't guarantee the availability of these internet address).

Note: The IEGD driver will not be developed any longer after version 10.3. Intel® plans to release a new version of the GMA driver

with several embedded features.

3.5 H.264 Support for Linux

KONTRON Technology A/S owns a Linux driver that support the H.264 codec.

®

This implementation has been tested with the Fedora
distributions is generally possible. The H.264 codec only supports video files but not the use of a blu-ray
drive.

Resolution Support Comment

1280 x 720

1440 x 1080 Not tested HDV2 (normally interlaced)

1920 x 1080

For further information please contact your local distributor or KONTRON for technical support

distribution (Core 11). The conversion to other linux





HDV1 (progressive)

Full HD (interlaced / progressive)

pITX-SP Software Guide

KTD-S0003-C Page 14 Serial-ATA Interface

4 Serial-ATA Interface

The Serial-ATA controller supports two operating modes: a native PCI IDE controller and a RAID/AHCI con­troller.

4.1 Native PCI IDE Controller

In this mode no drivers are needed for a Windows® installation. Interrupt and I/O-addresses can take any
value (except the known legacy settings 0x1F0/0x170 respectively IRQ14/15).
Diagnostic tools which bypass the INT13 and directly access registers may cause uncontrolled behaviors.
We strongly advise against the use of such tools.

Attention: For a bootable drive the Option ROM must be enabled.

4.2 RAID/AHCI Controller

The RAID functionality is not supported but the driver and Option ROM use this expression. A Windows®

®

installation without S-ATA drivers is not possible. To install Windows
TXTSETUP.OEM must be supplemented. Without any addition Windows
floppy drive. The following modifications allows the installation from a USB floppy drive.

;--The following lines give additional USB floppy support
id = "USB\VID_03F0&PID_2001", "usbstor" #--HP
id = "USB\VID_08BD&PID_1100", "usbstor" #--Iomega
id = "USB\VID_0409&PID_0040", "usbstor" #--NEC
id = "USB\VID_055D&PID_2020", "usbstor" #--Samsung
id = "USB\VID_0424&PID_0FDC", "usbstor" #--SMSC
id = "USB\VID_054C&PID_002C", "usbstor" #--Sony
id = "USB\VID_057B&PID_0001", "usbstor" #--Y-E Data

If a USB floppy drive is still not detected properly the parameters can be determined as follows:
Plugin the USB floppy drive on any Desktop PC running the Windows
device manager in the system control panel. The floppy drive should be listed below the entry Universal

Serial Bus Controller. Goto it's properties, select the details tab, then Hardware IDs where you can see

USB\VID_ ... &PID_ .... These values must be added as a new line to the file TXTSETUP.OEM.

Presumeably this addition must correspond with the file USBSTOR.INF. If the floppy drive identification is
not implemented in this file the installation might fail.

Manufacturer ID in USBSTOR.INF available

HP

Iomega Indefinite

NEC

Samsung Indefinite

SMSC

Sony

Y-E Data











XP on a Serial-ATA harddisk the file

®

expects the driver on a legacy

®

XP operating system and open the

pITX-SP Software Guide