Hi Rama,
You can find the demo to reproduce the issue by the following URL:
https://drive.google.com/file/d/0Byw88ezNrM71SmJPOWVwNDJBR0U/edit?usp=sharing
Details about the demo:
- It runs H.264 decoder on cores 0-3
- Decoder reads H.264 elementary input from addres 0x90000000 (13 MiB) in infinite loop. Demo input is attached (stream.264). You should load the file by the address above before starting demo using Load Memory tool.
- Decoder sends frames to H.264 encoder
- H.264 encoder runs on cores 4-7
- Encoder outpus data by 0x98000000 address
- After encoding reasonable number of frames you can pause demo and save generated H.264 elementary stream using Save Memory tool
- Demo informs how many 32 bit words of H.264 data were generated in console:
[C66xx_4] Writing 673 bytes total 824820 words
- You can see artifacts in generated output
- If you uncomment the following line in TranscodeComponent.c artifacts will gone:
//Cache_inv((void*)0x0C000000, 1, Cache_Type_L1D, FALSE); // TODO: temporary fix - barrier should invalidate something
I use the following components:
- XDCtools 3.30.3.47
- EDMALLD 2.11.11
- FC 3.30.0.06
- IPC 3.22.2.11
- SYS/BIOS 6.40.2.27
- H.264 decoder 01.01.04.00
- H.264 encoder 01.00.02.00
Feel free to ask any questions.
Regards,
Andrey Lisnevich