EDID
EDID (Extended Display Identification Data) is an interface between the graphics unit and the connected monitor.
Via this the graphic unit receives the values of the display like timings, resolution, colors and further information about the used display.
mostly the EDID data is stored as 128 byte large binary in an EEPROM which is then read via an interface like I2C.
Generate EDID data
EDID generators and editors are mostly used to create and customize EDID binaries. After the necessary values are collected from the display data sheet, they can be inserted into the tool. The edid generator creates the required binary from the entered data like resolution, standard timings and other values.
Many EDID generators can be found on the internet. We use the wxEDID editor (GPLv3) to explain the process. Creating EDID data is similar for most programs and there is no need to use the same EDID generator as in this article.
the wxEDID tool can be found Here
GUI example
<html> <b>Block Tree</b></html>: Listing of the individual selectable EDID blocks for timings, customer info and color settings
<html> <b>Data Box</b></html>: Used to view and edit the individual data of the selected EDID block
<html> <b>Info Box</b></html>: Displays information and descriptions for the currently selected entry in the Data box

Customize Data in Binary
load the Bin file which should be edited: File > Open EDID Binary
change the values using the data sheet for the display. Information about the currently selected value is displayed in the info box below.
if the block DTD: Detailed Timing Descriptor is selected in the block tree, you can switch to the DTD Constructor tab at the top to set values like timing and resolution more easily and with graphical feedback regarding the display size.
Once all changes have been entered into the tool, the binary file can be created: File > Save EDID Binary
Flash EDID Data
The following section only refers to the flash process for our TQ modules !
To change the Edid data on the populated PTN3460 chip, its firmware must be adapted. The Edid data is located at certain addresses in the firmware and therefore the old 128 bytes must be overwritten with the new created bytes.
Requirements
Edit Firmware Binary
to change the EDID data in the chip, the created EDID data must be written into the firmware at the appropriate location:
Open the PTN3460.bin and the created EDID.bin in a Hex Editor
Search for the address of the Edid data in the firmware file, which should be replaced by the customized EDID data (use table –EDID addresses– below)
Copy the 128 bytes from the created EDID file and overwrite the existing values at the correct address
Make sure that the existing data is replaced and not inserted. The firmware binary must not contain more bytes than before!
Save new Firmware.bin
EDID addresses
EDID Entry | EDID Data Start Address |
1 | 0x7000 |
2 | 0x7080 |
3 | 0x7100 |
4 | 0x7180 |
5 | 0x7200 |
6 | 0x7280 |
7 | 0x7300 |
Flash Firmware Binary
After creating the edited firmware binaries the file can be written to the LVDS bridge.
Before the tool is started, the required files must be located in the same folder as the tool.
Example (windows):
<parent Folder>
|--- FLASH.bin
|--- PTN3460.bin (custom firmware binary)
|--- AuxDLL.dll
|--- PTN3460_FOA_App.exe
Start flash process:
Boot the module on which the LVDS bridge should be flashed use an operating system which is supported by the NXP tool
Start the Tool (PTN3460_FOA_App) and click on the button DISPLAY
Select the Displaybridge in the dropdown-menu (DP0 on the most modules)
Press the button Flash to start the flash process
As soon as the process has been completed without errors, the text “Programming complete” should appear in the info window.
Use new Resolution
Reboot module and stop boot sequence in BIOS
From BIOS front page navigate to: Device Management → SIO TQMx86
Enable Enable LVDS bridge and LVDS Configuration
Set LVDS EDID information to EDID Emulation on
Under LVDS Resolution select the index whose resolution was adjusted
Press F10 to save changes and then reboot the system
The displayed resolution is stored firmly in the BIOS and is not read from the chip. An adjustment of the LVDS resolution table requires a customer specific BIOS!
BIOS-Example