This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

H3A AE/AWB Data Structure Mismatch

Hi,

in the TMS320DM814x Imaging Subsystem User's Guide is the H3A AE/AWB PacketFormat for several modes described.

I use this data to implement my own AutoExposure-Algorithm. But I have a mismatch in interpreting the data.

The documentation says there is new Window data every 32Bytes and the unsatured counters every 256Bytes. But if i'm examining the data i can't reconstruct this. Maybe I understood the documentation wrong, but I think there must be some different structure that I dont know.

I have access to the RDKs Source Code and indeed, the code handles the data differently than described. But even if i'm doing the same way, I get wrong results.

Can somebody help?

Thanks in advance, Thomas