tm1300 NXP Semiconductors, tm1300 Datasheet - Page 113

• Manufacturer Part Number: tm1300
• Description: Tm-1300 Media Processor
• Manufacturer: NXP Semiconductors

Philips Semiconductors
Figure 7-18. Message-passing START and END signals.
data interpretation is done, and data is transferred at the
rate of one byte per VO_CLK. Data is clocked out on the
positive edge of VO_CLK.
When
EVO_ENABLE = 1 and SYNC_STREAMING = 1, the
VO_IO2 signal indicates a data-valid condition. This sig-
nal is asserted when the EVO starts outputting valid data
(that is, data-streaming mode is enabled and video out is
running), and is de-asserted when data-streaming mode
is disabled. As shown in
nal on VO_IO2 is asserted just before the first valid byte
is present on VO_DATA[7:0], and is de-asserted just af-
ter the last valid byte was sent, or if an HBE error is sig-
naled. All transitions of VO_IO2 occur on the rising edge
of VO_CLK. The VO_IO1 signal generates a pulse one
VO_CLK cycle before the first valid data is sent. The
transitions of VO_IO1 occur on the rising edge of
VO_CLK and last for one VO_CLK cycle.
In message-passing mode, the EVO issues signals on
VO_IO1 and VO_IO2 to indicate the start and end of
messages.
When
VO_CTL.VO_ENABLE, the EVO sends a Start condition
Figure 7-17. Data-streaming valid data signals.
Figure 7-16. Genlock mode.
VO_DATA[7:0]
Image Data
VO_DATA[7:0]
VO_CLK
message
VO_IO1
VO_IO2
data-streaming
VO_CLK
VO_IO2
VO_IO1
VO_IO2
Line 525/625
passing
message
Delay SLAVE_DLY in VO_CLK cycles
Start of
XX
Figure
mode
XX
is
D0
7-17, the data-valid sig-
started
EAV
XX
Line 1
is
D1
enabled
D0
by
D2
setting
D1
Line 2
and
One Frame
D3
DATA_VALID
D2
on VO_IO1. When the EVO has transferred the contents
of the buffer, it sends an End condition on VO_IO2, sets
BFR1_EMPTY, and interrupts the DSPCPU. The EVO
stops, and no further operation takes place until the
DSPCPU sets VO_ENABLE again to start another mes-
sage, or until the DSCPU initiates other EVO operation.
The timing for these signals is shown in
7.12
7.12.1
The EVO accepts memory-resident video image data in
three formats: YUV 4:2:2 co-sited, YUV 4:2:2 inter-
spersed, and YUV 4:2:0. These formats are shown in
Figure 7-19
7.12.2
Video image data is stored in memory with one table for
each of the Y, U and V components. This is called planar
format. This is shown in
data. The EVO merges bytes from each of the three ta-
PRODUCT SPECIFICATION
D4
Line counter loaded by FRAME_PRESET
Line FRAME_PRESET
EAV
D3
IMAGE DATA MEMORY FORMATS
D5
Video Image Formats
Planar Storage of Video Image Data in
Memory
through
D4
D6
Figure
D5
Line 525/625
message
End of
Figure 7-22
D7
7-21.
Dk
Enhanced Video Out
XX
EAV
Line 1
XX
for YUV 4:2:2 image
Figure
XX
XX
7-18.
7-9