AnsweredAssumed Answered

BF561 PPI Camera Input using ITU-656 codes

Question asked by Laz on May 19, 2010
Latest reply on Jul 27, 2010 by Laz

According to the HW Ref (11:15-17), the ITU 656 decoder expects the horizontal blanking to be before the active data.  My Aptina camera has the blank data after the active data.  Is this sufficient to prevent this mode from working?  The manual says:

"Note F and V are only allowed to change as part of EAV sequences (that is, transition from H = 0 to H = 1)."

 

The BF561 expects:

F/V/H

0/1/1 // horiz/vert blank data (start of frame)

0/1/0 // horiz active, vert blank

0/0/1 // horiz blank, vert active (end of vertical blank, start of first active line)

0/0/0 // horiz active, vert active (real data)

...

 

Where the Aptina does this:

F/V/H

0/1/0 // horiz active, vert blank (start of frame)

0/0/0 // horiz active, vert active (real data, start of line)

0/0/1 // horiz blank, vert active (horiz blanking region)

...

0/0/0 (start of line)

0/0/1 (blank end of line)

0/1/1 (end of frame)

 

The Aptina implementation is very similar to the hardware Frame/Line Valid PPI architecture.

 

The ADI camera code example only implements the Frame/Line valid method.

 

Anyone else played with ITU-656?

 

TIA

Dan

Outcomes