ADV8005 Hardware Reference Manual
UG-707
Packet Map Address
Access Type
Field Name
Default Value
Byte Name
1
0xF290
R/W
isrc2_pb13[7:0]
0b00000000
Data Byte 13
0xF291
R/W
isrc2_pb14[7:0]
0b00000000
Data Byte 14
0xF292
R/W
isrc2_pb15[7:0]
0b00000000
Data Byte 15
0xF293
R/W
isrc2_pb16[7:0]
0b00000000
Data Byte 16
0xF294
R/W
isrc2_pb17[7:0]
0b00000000
Data Byte 17
0xF295
R/W
isrc2_pb18[7:0]
0b00000000
Data Byte 18
0xF296
R/W
isrc2_pb19[7:0]
0b00000000
Data Byte 19
0xF297
R/W
isrc2_pb20[7:0]
0b00000000
Data Byte 20
0xF298
R/W
isrc2_pb21[7:0]
0b00000000
Data Byte 21
0xF299
R/W
isrc2_pb22[7:0]
0b00000000
Data Byte 22
0xF29A
R/W
isrc2_pb23[7:0]
0b00000000
Data Byte 23
0xF29B
R/W
isrc2_pb24[7:0]
0b00000000
Data Byte 24
0xF29C
R/W
isrc2_pb25[7:0]
0b00000000
Data Byte 25
0xF29D
R/W
isrc2_pb26[7:0]
0b00000000
Data Byte 26
0xF29E
R/W
isrc2_pb27[7:0]
0b00000000
Data Byte 27
1
As defined in the latest CEA 861 specification
6.12.
EDID HANDLING
6.12.1.
Reading the EDID
The Tx core of the
features an EDID/HDCP controller which can read the EDID content of the downstream sink through the DDC
lines, TXDDC_SCL and TXDDC_SDA. This EDID/HDCP controller begins buffering segment 0 of the downstream sink EDID once the sink
HPD is detected and the Tx core of the
is powered up. The system can request additional segments by programming the EDID
edid_ready_int
(refer to Section
) indicates that a 256-byte EDID read has been completed, and the
EDID content can be read from the EDID Map.
edid_segment[7:0]
, TX2 Main Map,
Address 0xF4C4[7:0]
This register is used to set the segment of the EDID read from the downstream receiver.
Function
edid_segment[7:0]
Description
xxxxxxxx
User programmed EDID segment value
6.12.2.
EDID Definitions
Extended EDID (E-EDID) supports up to 256 segments. A segment is a 256-byte segment of EDID data containing one or two 128-byte EDID
blocks. A typical HDMI sink will have only two EDID blocks and so will only use segment 0. The first EDID block is always a base EDID
structure defined in the VESA EDID specifications; the second EDID block is usually the CEA extension defined in the CEA-861 specification.
The
has a single memory location used to store EDID and HDCP information read from the downstream sink. During HDCP repeater
initialization, the EDID data read from the sink is overwritten with HDCP information which is also read from the sink. The sink EDID is not
reread after HDCP initialization. The user can request the
to rebuffer an EDID segment by using the
6.12.3.
Additional Segments
The EDID block 0 byte number 0x7E tells how many additional EDID blocks are available. If byte 0x7E is greater than 1, additional EDID
segments will need to be read. If there is more than one segment, the second block (that is, block 1) is required to be an EDID extension map.
This map should be parsed according to the VESA EDID specification to determine where additional EDID blocks are stored in the sink EDID
storage device such as EEPROM, RAM, and so on.
The
is capable of accessing up to 256 segments from EDID of the sink as allowed by the EDID specification. By writing the desired
segment number to the
field, the
will automatically access the correct portion of the sink EDID over the Tx DDC
lines and load the 256 bytes into the EDID/HDCP memory. When the action is complete, the
edid_ready_int
interrupt
). The EDID data read from the sink can then be accessed from the Tx EDID Map. If the host controller needs access to
previously requested EDID information, then it can be stored in its own memory.
Rev. A | Page 233 of 317
