Analog.com Analog Dialogue Wiki 简体中文
EngineerZone
EngineerZone
  • Log In
  • Site
  • Search
  • User
  • Support

    Popular Forums

    • RF and Microwave
    • Power Management
    • Video
    • FPGA Reference Designs
    • Precision ADCs
    • Linux Software Drivers
    • SigmaDSP Processors & SigmaStudio Dev. Tool

    Product Forums

    • A2B
    • Amplifiers
    • Analog Microcontrollers
    • Clock and Timing
    • Data Converters
    • Direct Digital Synthesis (DDS)
    • Energy Monitoring and Metering
    • Interface and Isolation
    • MEMS Inertial Sensors
    • Processors and DSP
    • Switches/Multiplexers
    • Temperature Sensors
    • Voltage References
    View All

    Application Forums

    • Audio
    • Automated Test Equipment (ATE)
    • Condition-Based Monitoring
    • Depth, Perception & Ranging Technologies
    • Embedded Vision Sensing Library
    • Motor Control Hardware Platforms
    • Optical Sensing
    • Precision Technology Signal Chains Library
    • Video
    • Wireless Sensor Networks Reference Library

    Design Center Forums

    • ACE Evaluation Software
    • ADEF System Platforms
    • Design Tools and Calculators
    • FPGA Reference Designs
    • Linux Software Drivers
    • Microcontroller no-OS Drivers
    • Reference Designs
    • Signal Chain Power (SCP)
    • Software Interface Tools
    • System Demonstration Platform (SDP) Support
  • Learn

    Highlighted Webinar

    Multidimensional Simulations of Beamformers and other RF Integrated Circuits in Keysight SystemVue

    Recent Discussions

    • Issue running built programs on Pluto
    • Activity: Simple Op Amps, For ADALM1000 Fig. 1.3 Buffering example
    • ADALM-PLUTO [NETWORK] vs [USB_ETHERNET]
    • Using buffer size different from 2**n
    • ADALM1000 Pixelpulse feature Source Voltage / Measure Current explanation

    Places

    • ADI Education Home
    • ADI Education China
    • ADI Education India
    • ADI Education Philippines
    • StudentZone (Analog Dialogue)
    • Virtual Classroom

    Latest Webinars

    • Multidimensional Simulations of Beamformers and other RF Integrated Circuits in Keysight SystemVue
    • Improve Smart Building Energy Efficiency with Industrial Ethernet Controlled Air Conditioning (HVAC) Systems
    • Sustainable Motion Control Solutions for High Performance Servo Drives
    • Audio Design Solutions for Augmented and Virtual Reality (AR/VR) Glasses
    • Robust Industrial Motor Encoder Signal Chain Solutions
    View All Webinars
  • Community Hub

    Challenge Yourself!

      KCC's quizzes AQQ235 about a bipolar common emitter amplifier - a kind proposal from our colleague Martin Walker
    View All

    Places

    • Community Help
    • Logic Lounge

    Resources

    • EZ Code of Conduct
    • Getting Started Guide
    • ADI: Words Matter
    • Community Help Videos
    View All
  • Blogs

    Highlighted Blogs

    Crawl, Walk, And Run - The Journey To Create The Phaser

     

    Hardware Holds The Key To Making Industrial Systems IEC 62443 Compliant

    Latest Blogs

    • Behind the Scenes of DIYRadio Blogs: An Introduction
    • Empowering Surveillance Cameras To Capture A Scene Without Being Heard
    • Mastering The Metrics Makes Specifying Encoders Simpler
    • Understanding Secret Key Cryptography Without Formulas
    • 3 Reasons Why IO-Link is Changing Smart Factory Decision Making
    Read All Blogs

    ADI Blogs

    • EZ Spotlight
    • The Engineering Mind
  • Partners

    Electronic Design Services - PartnerZone

    • Boston Engineering
    • Calian, Advanced Technologies
    • Colorado Engineering Inc. (DBA CAES AT&E)
    • Clockworks Signal Processing
    • Epiq Solutions
    • Fidus
    • PalmSens
    • Richardson RFPD
    • Tri-Star Design, Inc.
    • VadaTech
    • Vanteon
    • X-Microwave
    View All
Video
Video
Documents EDID: Extended Display Identification Data
  • Q&A
  • File Uploads
  • Docs/ FAQs
  • Members
  • Tags
  • More
  • Cancel
  • FREE RUN
  • +AD724: FAQ
  • +AD725: FAQ
  • +AD7441A: FAQ
  • +AD8122: FAQ
  • +AD8380: FAQ
  • +AD8381: FAQ
  • +AD9388A: FAQ
  • +AD9389: FAQ
  • +AD9880: FAQ
  • +AD9882: FAQ
  • +AD9884A: FAQ
  • +AD9888: FAQ
  • +AD9889B: FAQ
  • +AD9978: FAQ
  • +AD9981: FAQ
  • +AD9984A: FAQ
  • +AD9985A: FAQ
  • +AD9994: FAQ
  • +ADA4891: FAQ
  • +ADDI7004: FAQ
  • +ADI Video Parts: FAQ
  • +ADV202: FAQ
  • +ADV212: FAQ
  • +ADV3002: FAQ
  • +ADV3224/25/28/29: FAQ
  • +ADV7123: FAQ
  • +ADV7125: FAQ
  • +ADV7128: FAQ
  • +ADV7171: FAQ
  • +ADV7174: FAQ
  • +ADV7179: FAQ
  • +ADV7180: FAQ
  • +ADV7180W: FAQ
  • +ADV7181C: FAQ
  • +ADV7181D: FAQ
  • +ADV7182: FAQ
  • +ADV7183B: FAQ
  • +ADV7184: FAQ
  • +ADV7185: FAQ
  • +ADV7188: FAQ
  • +ADV7202: FAQ
  • +ADV7280: FAQ
  • +ADV7281: FAQ
  • +ADV7282: FAQ
  • +ADV7283: FAQ
  • +ADV728x: FAQ
  • +ADV7341: FAQ
  • +ADV7343: FAQ
  • +ADV734X: FAQ
  • +ADV7390: FAQ
  • +ADV7393: FAQ
  • +ADV739x: FAQ
  • +ADV7401: FAQ
  • +ADV7403: FAQ
  • +ADV7441A: FAQ
  • +ADV7480: FAQ
  • +ADV7481: FAQ
  • +ADV7482: FAQ
  • +ADV749x: FAQ
  • +ADV7510: FAQ
  • +ADV7511: FAQ
  • +ADV7513: FAQ
  • +ADV7520: FAQ
  • +ADV7604: FAQ
  • +ADV7610: FAQ
  • +ADV7611: FAQ
  • +ADV7612: FAQ
  • +ADV7613: FAQ
  • +ADV7614: FAQ
  • +ADV7619: FAQ
  • +ADV7622: FAQ
  • +ADV7623: FAQ
  • +ADV7625: FAQ
  • +ADV7626: FAQ
  • +ADV7627: FAQ
  • +ADV7630: FAQ
  • +ADV7800: FAQ
  • +ADV7802: FAQ
  • +ADV7842: FAQ
  • +ADV7844: FAQ
  • +ADV7850: FAQ
  • +ADV78xx: FAQ
  • +adv8003: FAQ
  • +ADV8005: FAQ
  • +Advantiv: FAQ
  • +AN-1191: FAQ
  • +analog input muxing: FAQ
  • +Apple TV: FAQ
  • +Customer hardware validation scripts: FAQ
  • +CVBS: FAQ
  • +Decoder Product: FAQ
  • +DVP Evaluation Software: FAQ
  • +EVAL-MELODY: FAQ
  • +HDCP-Enabled Parts: FAQ
  • -HDMI: FAQ
    • ADI Recommended Setting
    • Chip-Set Differences
    • Common HDMI Transmitter Applications Issues
    • DVI Vs HDMI
    • EDID: Extended Display Identification Data
    • HDMI Initialization Sequence
    • HDMI Layout Guideline
    • How many KSV's can ADI HDMI Receivers support?
    • Queries and Primary Suggestions for our Video Customers!
    • Restrictions Relating to the Distribution of HDCP-Enabled Parts
    • What happens when I get the color space info incorrect?
  • +I2C: FAQ
  • +PCB Trace Impedance Calculator: FAQ
  • +VESA Standards: FAQ
  • +xtal Load Caps: FAQ

EDID: Extended Display Identification Data

Hi All,

      Here we described about "What is EDID and Its Terminologies". 

 EDID      -> Extended Display Identification Data

 Purpose -> Enable plug and play capabilities of the sink. It describes the video formats that are supported by the display device.

EDID is stored in:

                           1) PROM (Programmable ROM)

                           2) EEPROM (Electrically Erasable PROM)

 EDID is a standard published by the Video Electronics Standards Association (VESA). It is a data structure provided by displays to describe its capabilities to a video source. For EDID, the data includes:

  • Manufacturer name
  • Manufacturer serial numb
  • Product type
  • Phosphor of filter type
  • Timings supported by the display
  •  Display size
  •  Luminance data
  •  Pixel mapping data

Sink Device:

     All sink devices complaint to the HDMI specification must implement EDID.

Source Device:

    Source device checks the display’s DVI or HDMI port for the presence of an EDID PROM and uses the information inside to optimize the output video and/or audio format.

DDC Channel:

      DDC or Display Data Channel describes the protocol and physical path used by the source and display to communicate. It is typically assigned to a pin or pins on the interface, and carries the EDID/HDCP.

     Source should use the DDC to read the EDID data from Sink devices. If incase the DDC lines are not connected then source can send any specific format without knowing the Sink capability.

     Please note DDC uses a standard serial signaling scheme known as the I2C bus and it consists of three wires: SDA - data, SCL - clock, and a logic "high" DC pull-up voltage. For the DDC, the logic "high" voltage is specified to be +5V.

HPD (Hot Plug Detection):

   A pin on the HDMI connector that allows the source device to sense when a display device has been connected to it and its EDID is readable.

  Hot Plug detection is not supported for Analog interfaces, but it is supported in Digital interfaces including DVI, HDMI and Display Port.

  For these interfaces, the display device will supply a voltage on an HPD pin to signal to the video source device that it is connected So the video source device monitors the voltage on the HPD pin and then initiates EDID requests as it senses incoming voltage.

  The absences of a voltage on the HPD pin indicates disconnection.

Note: Generally, the connection process begins when the source outputs a +5V signal on Pin 18 to the sink, which sends back the +5V signal to the source on pin 19 which is the hot plug detect pin.

If the hot plug is asserted, then the source will read the capabilities of the sink device.

Internal EDID Vs External EDID:

        Generally, a legacy HDMI system will have only two EDID blocks(256 bytes) and will only use segment 0. The first EDID block is always a base EDID structure defined in VESA EDID specifications and the second EDID block is usually the CEA extension defined in the CEA-861D specification

Internal EDID – Volatile Memory:

       Internal EDID is volatile one So we need to re-program the internal EDID RAM every time during powerup.

       RAM SIZE: Internal E-EDID memory can store only upto 256 bytes.

       If the internal E-EDID RAM is enabled for one specific port , an external E-EDID storage device must not be connected on the DDC bus of that port.

External EDID – Non-Volatile Memory:

    External EDID EEPROM is one way of providing non volatile storage of EDID data and it would allow the DVI/HDMI source to detect the board even if the board is not powered.

    If customer is trying to use the External EDID and they need to ensure the below things,

    The external device should be connected to the DDC_SCL/DDC_SDA pins on the HDMI connector. If the external E-EDID is enabled for one specific port , an internal E-EDID must not be connected on the DDC bus of that port.

    Please note when an external storage device is used for storing the E-EDID data of a specific HDMI port, the storage device must be connected to the DDC lines of that HDMI port and also we need to ensure that internal E-EDID should not be enabled for such specific port.

How to determine the Source would read the EDID ?

   Best way is to monitor the DDC lines capture (i.e Capture the DDC lines with a I2C monitor).

Sequence needs to be followed while uploading the EDID into Source device:

1) HPA_MAN_VALUE_X =1

2) HPA_A pin active =0

3)  HPA_MAN_VALUE_A =0, Set HPA low

4)  Wait 100ms

4)  load up the EDID

5) HPA_MAN_VALUE_A =1, Set HPA high, forces source to reload EDID    

          Or

1) Set HPA_MAN_VALUE_A = 1 ; Set bit high

2) HPA_TRISTATE_A = 0 ;  Make HPA pin an output

3) Set HPA_MAN_VALUE = 0 ; Pulls HPA pin low

4) Wait 100ms ;

5) Set HPA_TRISTATE = 1 ; Makes HPA pin an input / Turn the HPA pin tri-state So the pull up resistor can pull HPA high (i.e External pull up resistor will create the rising edge on the HPD  causing the PC to re-read the EDID ).

Customer frequent issue when using the PC as source device:

   Customer need to take care while using the PC as source.

PC and Consumer sources(Player’s) are generally do not work unless they see a valid EDID. PC will only recognize a sink when they detect an valid EDID.

Customer need to make sure with below things when bringing up the board,
    1) Disconnect PC from the Part (Chipset)
    2) Run script
    3) Configure EDID
    4) Configure SPA registers (More than one Port)
    5) Plug PC into the Part. This should cause the PC to read the EDID

Below thread contains an EDID initialization script,
https://ez.analog.com/message/31879#31879

Advantiv EEditGold Tool:

The first 128 byte is only VESA block only.  The number of extensions are specified on the 'General' tab.  The extensions are CEA extensions.  The EDID data can be one or two or many blocks long.  Normally we see the EDID as 2 blocks totally 256 bytes. 

The last byte of each 128  block is the check sum for that block so byte 128 and 256 will change as you change the respective block.

Customer can use this EEdit tool to visualize and modification of EDID data blocks. 

 Download our EDID Editor here: (+) Advantiv EDID Editor - Documents - Video - EngineerZone (analog.com)

Thanks,

Poornima.S

  • edid
  • hdmi
  • Share
  • History
  • More
  • Cancel
Related
Recommended
Social
Quick Links
  • About ADI
  • ADI Signals+
  • Analog Dialogue
  • Careers
  • Contact us
  • Investor Relations
  • News Room
  • Quality & Reliability
  • Sales & Distribution
  • Incubators
Languages
  • English
  • 简体中文
  • 日本語
Newsletter

Interested in the latest news and articles about ADI products, design tools, training and events? Subscribe today!

Sign Up
Analog Logo
©1995 - 2023 Analog Devices, Inc. All Rights Reserved
沪ICP备09046653号-1
  • Sitemap
  • Legal
  • Privacy & Security
  • Privacy Settings
EngineerZone Uses cookies to ensure you get the best experience in our community. For more information on cookies, please read our Privacy & Security Statement.