JRexplus LX KTD-S0004-A
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...............................................................................
User Information Table of Contents 7.4 CPU Performance Part ..................................................................................................18 7.5 Hardware Monitor Part .................................................................................................19 7.5.1 7.5.2 Temperature........................................................................................................................... 19 Voltage.............................................................
KTD-S0004-A Page 1 1 User Information 1.1 About This Document User Information 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.
KTD-S0004-A 1.6 Page 2 User Information 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.
KTD-S0004-A 2 Page 3 BIOS Update BIOS Update The KONTRON update tool (based on the AMD utility 'FlashROM.com') is only available for the DOS operating system. First copy the files LX800UPD.EXE, UPDATE.EXT (absolutely essential) and the BIOS file to a directory. Only the following combination of command line arguments has been tested and should be used for the update process. Note: COMMAND.COM must reside in the same directory or alternatively there has to be a valid path in the variable COMSPEC.
KTD-S0004-A Page 4 3 Graphics Interface 3.1 LCD/LVDS Technology Overview 3.1.1 Detailed Timing Descriptor (EDID or DisplayIDTM) Graphics Interface 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.
KTD-S0004-A Page 5 Graphics Interface Example 2 (not useable on JRexplus LX): SHARP LQ190E1LW01 (double pixel clock) Data sheet specifications (no definition of Sync Offset Clock Frequency [typ.] 54 MHz Horizontal Period (1) [typ.] 844 Clocks Horizontal Display Period 640 Clocks Vertical Period [typ.
KTD-S0004-A 3.1.2 Page 6 Graphics Interfacee 24 Bit Color Mapping Tips 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 (Flat Panel Display Interface) or LDI (LVDS Display Interface). Some panels use the line SELL LVDS (SELect Lvds data order). The LVDS data assignment in the datasheet can give you an indication by the last channel (e.g.
KTD-S0004-A 3.2 Page 7 Graphics Interface 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.
KTD-S0004-A 3.3.2 Page 8 Graphics Interface DisplayIDTM Restrictions Depending on the graphic controller not all features can be used. The following table shows the most important restrictions. Restrictions for JRexplus LX Panels with dual or quad clock not supported (2 or 4 Pixel per Clock) Panels with LDI 24bit color mapping not supported Variable power sequencing not supported DisplayIDTM is not a solution for every LCD. Many displays center the picture automatically using the DEsignal.
KTD-S0004-A 3.3.4 Page 9 Graphics Interface 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 DisplayIDTM tool (software can be downloaded from kontron.com).
KTD-S0004-A Page 10 Graphics Interface The DisplayIDTM Editor saves the parameters in a intermediate file format. The file extension is 'KDD' (Kontron DisplayIDTM Data). This file format cannot be used to program the onboard EEPROM. For transfering this file format into the binary file format for the EEPROM apply the Converter. Building DisplayIDTM File 3.3.5 Start the Windows® tool DisplayID.exe.
KTD-S0004-A Page 11 4 Serial-ATA Interface 4.1 Windows® XP SP2 or SP3 Boot Serial-ATA Interface To install Windows® XP on a Serial-ATA harddisk without a legacy floppy drive the file TXTSETUP.OEM must be changed respectively recreated. The following modifications allows the installation from a USB floppy drive. Example for a new TXTSETUP.OEM file: [Disks] disk1 = "VIA_SCSI", viamraid.inf [Defaults] scsi = VCOMBORAID_I386 [scsi] VCOMBORAID_I386 = "VIA V-RAID Controller Series (Windows XP)" [Files.
KTD-S0004-A Page 12 Serial-ATA Interface 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® XP operating system and open the 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_ ....
KTD-S0004-A 5 Page 13 Watchdog, Digital I/O and Backlight Watchdog, Digital I/O and Backlight The following examples (DOS programs) show the access to these three system components (C compiler: BORLAND C++). Note: These examples can't be run on Linux and Windows®. 5.1 Watchdog Example #include #define #define #define #define #define JIDA16_INT WDT_INIT WDT_TRIGGER WDT_TIMEOUT WDT_DELAY 0x15 0xE000 0xE001 50 // timeout = 10 seconds (time base = 0.
KTD-S0004-A 5.2 Page 14 Watchdog, Digital I/O and Backlight Digital I/O Example #include #include #include #define #define #define #define #define #define JIDA16_INT GPIO_OUTPUT GPIO_INPUT JIDA_ID GPIO_MASK BOARD_NUM void WriteDigitalIO (unsigned char value) { union REGS regs; 0x15 0xEA51 0xEA52 0x4648 0x0F 1 // only lower nibble valid regs.x.ax = GPIO_OUTPUT; regs.x.dx = JIDA_ID; regs.h.cl = BOARD_NUM; regs.h.
KTD-S0004-A 5.3 Page 15 Backlight Example #include #include #include #define #define #define #define #define JIDA16_INT BACKL_OUT BACKL_IN JIDA_ID BOARD_NUM 0x15 0xEA29 0xEA28 0x4648 1 void WriteBacklight (unsigned char value) { union REGS regs; regs.x.ax = BACKL_OUT; regs.x.dx = JIDA_ID; regs.h.cl = BOARD_NUM; regs.h.ch = value; int86 (JIDA16_INT, ®s, ®s); } unsigned char ReadBacklight (void) { union REGS regs; regs.x.ax = BACKL_IN; regs.x.dx = JIDA_ID; regs.h.
KTD-S0004-A 6 Page 16 Remote Control (JRC) Remote Control (JRC) The Remote Control option provides a way to intercept and reroute certain BIOS functionality over a serial port at an early stage during the boot process. There are two distinct software components involved: the first component is part of the BIOS (client), the second component runs on a different device (host) that is connected using a serial cable to the client. This component is available as a WIN32 (JRC.EXE respectively jrc1i1xx.
KTD-S0004-A 7 Page 17 JIDA32 Interface JIDA32 Interface Most KONTRON single board computers (SBCs) are equipped with unique hardware features that cannot be accessed with standard API. The JIDA32 interface allows you to access this features in a hardware independent manner under popular 32-bit operating systems. Not mentioned parts of the JIDA32 interface are not supported and can lead to wrong results. 7.
KTD-S0004-A 7.3.1 Page 18 JIDA32 Interface Bus Number Technology Type Device Count 0 I2C (primary) JIDA 1 1 SMBus Generic 2 2 I2C JILI 1 Bus Number 0 (JIDA) This bus allows access to the JIDA EEPROM in which KONTRON specific manufacturing parameters are stored. A damage of these parameters leads to a loss of warranty. Due to this a write cycle may only be performed above a defined address. 7.3.
KTD-S0004-A 7.5 Page 19 JIDA32 Interface Hardware Monitor Part The hardware monitor part contains in most cases several subsections. 7.5.1 Section Sensor Count Temperature 2 Fan Not supported Voltage 6 Temperature The term On-Chip diode designates the chip temperature of the Super I/O temperature sensor (with no dependence to the CPU temperature). 7.5.2 Sensor Number On-Chip diode 0 CPU diode 1 Abs.
KTD-S0004-A 7.7 Page 20 JIDA32 Interface Watchdog Part The watchdog can be programmed with discrete timeout values on boards with CPLD implementation or in millisecond resolution with boards using a Super-I/O. In the discrete value scenario, if there is no exact match to the timeout value, the next higher one is used.
KTD-S0004-A 7.8 Page 21 JIDA32 Interface JIDA32 Windows® Programming For further information see the actual JIDA32 documentation (JIDA32.pdf). 7.8.1 Program Language C The demo program reads and shows the board name and the first 16 bytes of SPD EEPROM (SMBus). The program uses the static linked library JIDA.LIB. Example: #include #include "jida.
KTD-S0004-A 7.8.2 Page 22 JIDA32 Interface Program Language DELPHI The demo program activates the watchdog (timeout = 30 seconds). The keyword 'var' passes the argument by reference.
KTD-S0004-A Page 23 JIDA32 Interface procedure TForm1.Button1Click(Sender: TObject); begin {Method 1} if JidaDLLInitialize () then begin if JidaDllIsAvailable () then begin if JidaBoardOpen (JIDA_BOARD_CLASS_CPU, 0, JIDA_FLAGS_DEFAULT, hJida) then JidaWDogSetConfig (hJida, 0, JIDA_TIMEOUT_VALUE, JIDA_DELAY_VALUE, JIDA_REBOOT_MODE); end; JidaDllUninitialize (); end; end; end.
KTD-S0004-A Page 24 The associated DPR file: program Jidatest; uses Forms, mainU in 'mainU.pas' {Form1}; {$R *.res} begin Application.Initialize; Application.CreateForm (TForm1, Form1); Application.Run; end.
KTD-S0004-A 7.8.3 Page 25 JIDA32 Interface Program Language VISUAL BASIC (VB.NET) The demo program shows the board count value and activates the watchdog (timeout = 10 seconds). Example: Public Class JidaTest Declare Declare Declare Declare Auto Function JidaDllInitialize Lib "JIDA.DLL" () As Boolean Auto Function JidaDllUninitialize Lib "JIDA.DLL" () As Boolean Auto Function JidaDllIsAvailable Lib "JIDA.DLL" () As Boolean Auto Function JidaBoardCount Lib "JIDA.
KTD-S0004-A Page 26 JIDA32 Interface The associated Designer file: Partial Class JidaTest Inherits System.Windows.Forms.Form Protected Overrides Sub Dispose(ByVal disposing As Boolean) Try If disposing AndAlso components IsNot Nothing Then components.Dispose() End If Finally MyBase.Dispose(disposing) End Try End Sub Private components As System.ComponentModel.IContainer
KTD-S0004-A 7.8.4 Page 27 JIDA32 Interface Module Definition File The calling program can refer to the function by name or by ordinal value. The tool IMPDEF.EXE (e.g. BORLAND C++) make it possible to generate the DEF-file (from JIDA.DLL 06/07/2004, in newer DLLs the ordinal value can be changed).
KTD-S0004-A JidaIOIsAvailable JidaIORead JidaIOSetDirection JidaIOWrite JidaIOXorAndXor JidaJ32B JidaJ32BTransAddr JidaPerformanceGetCurrent JidaPerformanceGetPolicy JidaPerformanceGetPolicyCaps JidaPerformanceSetCurrent JidaPerformanceSetPolicy JidaStorageAreaBlockSize JidaStorageAreaCount JidaStorageAreaErase JidaStorageAreaEraseStatus JidaStorageAreaRead JidaStorageAreaSize JidaStorageAreaType JidaStorageAreaWrite JidaTemperatureCount JidaTemperatureGetCurrent JidaTemperatureGetInfo JidaTemperatureSetLi
KTD-S0004-A 7.9 Page 29 JIDA32 Interface JIDA32 Linux Programming Please note that the JIDA32 package does not include full sources. Instead precompiled objects are provided that can be used to build a JIDA32 package for a certain environment (GCC, kernel, libc). In order to handle GCC version incompatibilities and different kernel module build environments the package includes different branches (you can use the GCC_3.x.x subdirectory for GCC 4.x.x compiler versions). GCC_2.x.
KTD-S0004-A Page 30 JIDA32 Interface You can provide a prefix for the above named directories with the INSTALL_MOD_PATH environment variable if you want to install the files into an alternative root file system. (Note: kernel 2.6.x only) After successfull build and installation you should run the sample application jidatst which will display the following message: JIDA system driver is incompatible or not installed.
KTD-S0004-A Page 31 Appendix A: Reference Documents Appendix A: Reference Documents KONTRON Technology A/S can't guarantee the availability of internet addresses. Document Internet Address Advanced Configuration and Power Interface (ACPI) http://www.acpi.info/spec.htm AT Attachment Storage Interface Specification (ATA) http://t13.org Digital Visual Interface (DVI) http://www.ddwg.org High Definition Audio Specification (HD Audio) http://www.intel.
KTD-S0004-A Page 32 Appendix B: Document Revision History Appendix B: Document Revision History Revision Date Author S0004-A 11/04/10 M. Hüttmann Replaced the JIDA32 Delphi example Changes S0004-0 12/11/09 M. Hüttmann First release Corporate Offices Europe, Middle East & Africa North America Asia Pacific Oskar-von-Miller-Str. 1 85386 Eching/Munich Germany Tel.: +49 (0)8165/ 77 777 Fax: +49 (0)8165/ 77 219 info@kontron.com 14118 Stowe Drive Poway, CA 92064-7147 USA Tel.
