Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
en:general_information:tutorial:edid [2020/07/15 08:44] – [Requirements] weinholdoen:general_information:tutorial:edid [2023/06/13 13:24] (current) – removed HTML weinholdo
Line 1: Line 1:
 +<panel type="primary" title="EDID (Extended Display Identification Data)">
  
-===== EDID  ===== 
 ==== Basic Information about EDID ==== ==== Basic Information about EDID ====
  
-EDID (Extended Display Identification Data) is a data structure between the graphics unit and the connected monitor.  +EDID (Extended Display Identification Data) is a data structure 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. 
-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 ==== ==== Generate EDID data ====
  
Line 13: Line 13:
 === Prepare tool === === Prepare tool ===
  
-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. +Several EDID generators can be found on the internet, to name a few (in alphabetical order): 
-the wxEDID tool can be found **[[https://sourceforge.net/projects/wxedid/|Here]]** + 
 +  * [[https://ez.analog.com/video/w/documents/750/advantiv-edid-editor|Advantiv™ EDID Editor]] (Windows) 
 +  * [[https://www.analogway.com/emea/products/software-tools/aw-edid-editor/|AW EDID Editor]] (Windows, Mac OS) 
 +  * [[https://www.deltacast.tv/products/free-software/e-edid-editor|E-EDID Editor]] (Windows) 
 +  * [[https://sourceforge.net/projects/wxedid/|wxEDID]] (Linux, Windows; available as source code only) 
 + 
 +In this tutorial we will use the wxEDID editor (GPLv3) to explain the process. 
 ++++ GUI screenshot | ++++ GUI screenshot |
  
-<html> <span style="color:green;"><b>Block Tree</b></span></html>: Listing of the individual selectable EDID blocks for timings, customer info and color settings\\ +[color=green]Block Tree[/color]: Listing of the individual selectable EDID blocks for timings, customer info and color settings \\ [color=blue]Data Box[/color]: Used to view and edit the individual data of the selected EDID block \\ [color=red]Info Box[/color]: Displays information and descriptions for the currently selected entry in the Data box \\ {{:en:general_information:tutorial:wxedid_gui.png?nolink&}} 
-<html> <span style="color:blue;"><b>Data Box</b></span></html>: Used to view and edit the individual data of the selected EDID block\\ +
-<html> <span style="color:red;"><b>Info Box</b></span></html>: Displays information and descriptions for the currently selected entry in the Data box\\ +
-{{:en:general_information:tutorial:wxedid_gui.png?nolink|}}\\+
 ++++ ++++
  
 === Customize Data in Binary === === Customize Data in Binary ===
  
-  - load the Bin file which should be edited: **//File// > //Open EDID 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.   - 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. +  - 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//** +  - Once all changes have been entered into the tool, the binary file can be created: **//File//  > //Save EDID Binary// **
  
 ---- ----
  
 ==== Flash EDID Data ==== ==== Flash EDID Data ====
-<WRAP round important 55%> + 
-The following section only refers to the flash process for our TQ modules ! +<alert type="warning" icon="fa fa-warning"> The following section only refers to the flash process for our TQ modules ! </alert> 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.
-</WRAP> +
-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 === === Requirements ===
-The firmware can be requested via the [[support@tq-group.com?subject=Request: LVDS-Bridge Firmware Binaries |TQ-Support]].+ 
 +The firmware can be requested via the [[support@tq-group.com?subject=Request: LVDS-Bridge Firmware Binaries|TQ-Support]]. 
   * Firmware.bin (PTN3460)   * Firmware.bin (PTN3460)
   * new EDID Binary (128 Bytes)   * new EDID Binary (128 Bytes)
-  * Flash-Tool "PTN3460 Flash-over-AUX" (Distribution only by **[[https://www.nxp.com/support/support:SUPPORTHOME|NXP]]**) +  * Flash-Tool "PTN3460 Flash-over-AUX" (Distribution only by **[[https://www.nxp.com/support/support:SUPPORTHOME|NXP]]** ) 
-  * Hex file manipulation program (eg. **[[https://kde.org/applications/en/utilities/org.kde.okteta|okteta]]**)  +  * Hex file manipulation program (eg. **[[https://kde.org/applications/en/utilities/org.kde.okteta|okteta]]**)
  
 === Edit Firmware Binary === === Edit Firmware Binary ===
-{{ :en:general_information:tutorial:offsets_edid_index_full.png?300|}} + 
-to change the EDID data in the chip, the created EDID data must be written into the firmware at the appropriate location: +[[:en:general_information:tutorial:offsets_edid_index_full.png?id=en%3Ageneral_information%3Atutorial%3Aedid&media=en:general_information:tutorial:offsets_edid_index_full.png|{{  :en:general_information:tutorial:offsets_edid_index_full.png?300}}]] 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   * 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)+  * 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   * Copy the 128 bytes from the created EDID file and overwrite the existing values at the correct address
   * <wrap important> Make sure that the existing data is overwritten. The firmware binary must not contain more bytes than before! </wrap>   * <wrap important> Make sure that the existing data is overwritten. The firmware binary must not contain more bytes than before! </wrap>
-  * Save new Firmware.bin  +  * Save new Firmware.bin
 ++++ EDID addresses | ++++ EDID addresses |
  
-^  EDID Entry (Index)  ^  EDID Data Start Address  ^+^  EDID Entry (Index)  ^  EDID Data Start Address  |
 |  0  |  0x7000  | |  0  |  0x7000  |
 |  1  |  0x7080  | |  1  |  0x7080  |
Line 65: Line 69:
 |  5  |  0x7280  | |  5  |  0x7280  |
 |  6  |  0x7300  | |  6  |  0x7300  |
 +
 ++++ ++++
-\\ + 
-\\ + \\  \\  \\ 
-\\ +
-\\+
 === Flash Firmware Binary === === 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. 
  
 +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.
 <code> <code>
 +
 Example (windows): Example (windows):
  
Line 82: Line 86:
     |--- AuxDLL.dll     |--- AuxDLL.dll
     |--- PTN3460_FOA_App.exe     |--- PTN3460_FOA_App.exe
 +
 </code> </code>
 +
 Start flash process: Start flash process:
 +
   - Boot the module on which the LVDS bridge should be flashed <wrap important> use an operating system which is supported by the NXP tool </wrap>   - Boot the module on which the LVDS bridge should be flashed <wrap important> use an operating system which is supported by the NXP tool </wrap>
   - Start the Tool (PTN3460_FOA_App) and click on the button **DISPLAY**   - Start the Tool (PTN3460_FOA_App) and click on the button **DISPLAY**
-  - Select the Displaybridge in the dropdown-menu (//DP0// on the most modules) +  - Select the Displaybridge in the dropdown-menu (//DP0//  on the most modules) 
-  - Press the button **Flash** to start the flash process+  - 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. As soon as the process has been completed without errors, the text "//Programming complete//" should appear in the info window.
  
 ---- ----
 +
 ==== Use new Resolution ==== ==== Use new Resolution ====
 +
   - Reboot module and stop boot sequence in BIOS   - Reboot module and stop boot sequence in BIOS
   - From BIOS front page navigate to: **Device Management → SIO TQMx86**   - From BIOS front page navigate to: **Device Management → SIO TQMx86**
-  - Enable **Enable LVDS bridge** and **LVDS Configuration** +  - Enable **Enable LVDS bridge**  and **LVDS Configuration** 
-  - Set **LVDS EDID information** to **EDID Emulation on** +  - Set **LVDS EDID information**  to **EDID Emulation on** 
-  - Under **LVDS Resolution** select the entry that corresponds to the index selected in step "[[#edit_firmware_binary|Edit firmware binary]]"\\ see this ++ screenshot | +  - Under **LVDS Resolution**  select the entry that corresponds to the index selected in step "[[#edit_firmware_binary|Edit firmware binary]]" \\  see this ++ screenshot | {{:en:general_information:tutorial:lvds_config.png?nolink&900}} ++
-{{:en:general_information:tutorial:lvds_config.png?nolink&900|}} +
-+++
   - Press F10 to save changes and then reboot the system   - Press F10 to save changes and then reboot the system
-<wrap important> The resolutions listed under **LVDS Resolution** reflect the default resolutions as provided by the stock firmware binary. Please note that these are fixed strings, i.e. they are not dynamically created based on the resolution that is actually defined in the corresponding EDID index. An adjustment of these strings requires a custom specific BIOS! </wrap> 
  
-\\+<callout type="primary" icon="true"> The resolutions listed under **LVDS Resolution**  reflect the default resolutions as provided by the stock firmware binary. Please note that these are fixed strings, i.e. they are not dynamically created based on the resolution that is actually defined in the corresponding EDID index. An adjustment of these strings requires a custom specific BIOS! </callout> 
 ---- ----
 +
 +</panel>
 +
 +
  • Last modified: 2022/08/04 15:04