Hi Dave,
Thank you for your prompt reply.
I confirm that when the anomalies occur, reading the SWFLAG the value is 0x6002 from the ADV for Luma,
the ADV for Chroma sometimes report 0x6002 other times 0xFF82.
This could be caused by time latency of register reading.
What is the meaning of 0x6002 ?
Concerning Compression parameter we use:
1920x540 raster size (Custom mode because we use either 1080i at 50Hz and at 59.94Hz)
irreversible 9/7 mode, 5 transform level, 8 or 10 bit precision, LRCP progression Style,
128x32 Code Block size, DMA used as DCS mode, rate control as Target size mode 1,
Pixel I/F using Embedded SAV/EAV.
The two ADV are read as soon as datas are available, in sequence Luma as first, then Chroma.
Thank you in advance for any advice.
Ciao Alfredo from Italy