
KTD-S0057-I Page 18 VESA® DisplayIDTM
KTAM3874/pITX Software Guide
The DisplayID
TM
Editor saves the parameters in a intermediate file format. The file extension is 'KDD' (Kon-
tron D
isplayID
TM
Data). This file format cannot be used to program the onboard EEPROM.
For transferring this file format into the binary file format for the EEPROM apply the Converter.
4.3.5 Building DisplayID
TM
File
Start the Windows
®
tool DisplayID.exe.
Use the Editor if you want to modify an existing DisplayID
TM
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 DisplayID
TM
Binary).
Program the onboard EEPROM using the board specific update tool.
4.3.6 Erasing DisplayID
TM
Record
Create a dummy file with a size of 128 bytes filled with the value 0xFFh and program this file using the U-
Boot update tool. This treatment deletes a valid DisplayID
TM
record.
4.3.7 U-Boot EEPROM Update Tool
The update tool is a new component of the U-Boot bootloader. You need two commands to program a
DisplayID
TM
file into the EEPROM:
ext2load, fatload, loadb or loady
writedid
File Operation
The following example gives an overview:
The storage medium is a microSD
TM
card formatted with a Linux
®
partition and the DisplayID
TM
file wvga.kdb
is located in the root directory. The file size of wvga.kdb amounts 81 bytes.
For loading the file into memory type the following standard U-Boot command lines
mmc rescan 0
ext2load mmc 0 81000000 wvga.kdb
The memory address (0x81000000) is free selectable. With the md command you can control the result
md.b 81000000 80
Now you can load the memory content into the EEPROM. Type the new KONTRON U-Boot command
writedid 81000000 51
The 'count' respectively the size argument is a very important parameter. Do not use another value as the
file size of your DisplayID
TM
file.
Kommentare zu diesen Handbüchern