![](http://datasheet.mmic.net.cn/Analog-Devices-Inc/ADV7188BSTZ_datasheet_96350/ADV7188BSTZ_58.png)
ADV7188
Rev. A | Page 58 of 112
Table 72. Ancillary Data in Byte Output Format1 Byte
B9
B8
B7
B6
B5
B4
B3
B2
B1
B0
Description
0
1
2
1
Ancillary data preamble.
3
EP
0
I2C_DID6_2 [4:0]
0
DID.
4
EP
I2C_SDID7_2 [5:0]
0
SDID.
5
EP
0
DC [4:0]
0
Data count.
6
EP
padding [1:0]
VBI_DATA_STD [3:0]
0
ID0 (User Data-Word 1).
7
EP
0
Line_number [9:5]
0
ID1 (User Data-Word 2).
8
EP
Even_Field
Line_number [4:0]
0
ID2 (User Data-Word 3).
9
EP
0
VDP_TTXT_TYPE [1:0]
0
ID3 (User Data-Word 4).
10
VBI_WORD_1 [7:0]
0
User Data-Word 5.
11
VBI_WORD_2 [7:0]
0
User Data-Word 6.
12
VBI_WORD_3 [7:0]
0
User Data-Word 7.
13
VBI_WORD_4 [7:0]
0
User Data-Word 8.
14
VBI_WORD_5 [7:0]
0
User Data-Word 9.
.
n 3
1
0
n 2
1
0
Pad 0x200. These padding
words may not be present
depending on ancillary data
type. User Data-Word XX.
n 1
B8
Checksum
0
CS (checksum word).
1 This mode does not fully comply with ITU-R BT.1364.
Structure of VBI Words in Ancillary Data Stream
Each VBI data standard has been split into a clock run-in (CRI),
a framing code (FC), and a number of data bytes (n). The data
packet in the ancillary stream includes only the FC and data
bytes. The VBI_WORD_X in the ancillary data stream has the
Table 73. Structure of VBI Data-Words in Ancillary Stream
Ancillary Data Byte Number
Byte
Type
Byte Description
VBI_WORD_1
FC0
Framing Code [23:16]
VBI_WORD_2
FC1
Framing Code [15:8]
VBI_WORD_3
FC2
Framing Code [7:0]
VBI_WORD_4
DB1
First data byte
…
VBI_WORD_N+3
DBn
Last (nth) data byte
VDP Framing Code
The length of the actual framing code depends on the VBI data
standard. For uniformity, the length of the framing code reported
in the ancillary data stream is always 24 bits. For standards with
a shorter framing code length, the extra LSB bits are set to 0.
The valid length of the framing code can be decoded from the
VBI_DATA_STD bit available in ID0 (UDW1).
The framing code is always reported in the reverse order of
transmission.
Table 74 shows the framing code and its valid
length for VBI data standards supported by VDP.
Example
For teletext (B-WST), the framing code byte is 11100100 (0xE4),
with bits shown in the order of transmission. Thus, VBI_WORD_1
= 0x27, VBI_WORD_2 = 0x00, and VBI_WORD_3 = 0x00.
Translating these into UDWs in the ancillary data stream, for
the nibble mode,
UDW5 [5:2] = 0010
UDW6 [5:2] = 0111
UDW7 [5:2] = 0000 (undefined bits, automatically set to 0)
UDW8 [5:2] = 0000 (undefined bits, automatically set to 0)
UDW9 [5:2] = 0000 (undefined bits, automatically set to 0)
UDW10 [5:2] = 0000 (undefined bits, automatically set to 0)
and for the byte mode,
UDW5 [9:2] = 0010_0111
UDW6 [9:2] = 0000_0000 (undefined bits, automatically set to 0)
UDW7 [9:2] = 0000_0000 (undefined bits, automatically set to 0)
Data Bytes
VBI_WORD_4 to VBI_WORD_N+3 contain the data-words that
were decoded by the VDP in the order of transmission. The position
of bits in bytes is in the reverse order of transmission. For example,
closed captioning has two user data bytes, as shown in
Table 80.
The data bytes in the ancillary data stream in this case are as follows:
VBI_WORD_4 = BYTE1 [7:0]
VBI_WORD_5 = BYTE2 [7:0]
The number of VBI_WORDS for each VBI data standard and
the total number of UDWs in the ancillary data stream are