• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 1348 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

High Dynamic Range problem for OPT9221

user4733815
Prodigy 60 points
Other Parts Discussed in Thread: OPT9221

After I setted hdr_frm_intg_scale to be 1 to start the HDR, according to the OPT9221 manual, the FLAG[2] of first pixel in the HDR frame is 1, but I didn't find FLAG[2] of any first pixel is 1. Did my operation have problem?

I think after starting the HDR, the output frame will be divided into normal frame and HDR frame. Am I right?

  • 0
    TI__Expert 3800 points
    Hi,

    Once you set the chipset in HDR mode, alternate frames are normal and HDR frames. FLAG[2] of the first pixel tells you if the frame is HDR frame or normal frame.
    Please let me know if this answers your question.

    Regards,
    Subhash
  • 0 in reply to Subhash Chandra Sadhu
    Prodigy 60 points
    Hi,
    I set the chipset in HDR mode. But when I read FLAG[2] of the first pixel, they are all 0 which means normal frame. I wonder wheather my chipset is wrong or my read way is wrong. I can read the correct phase from the chip.
  • 0 in reply to user4733815
    Intellectual 635 points

    Hi,

    Was there ever a solution for this? We seem to be seeing the same. Flag[2] is never set even when HDR is enabled. I can observe FLAG[3] being set (when I hold my hand over the lens), but we never see FLAG[2]. I can visually confirm that HDR is enabled as the frames start flickering as every second frame is now darker.

    I have checked the readout, and we seem to be seeing all the bytes in the image (not accidentally skipping the first byte/pel during capture); the image is nicely aligned, including the first line.

    We're capturing 8-bit parallel data and it seems that the data line that would carry the FLAG[2] bit is working for other parts of the pixel (so not a dodgy solder joint).

    Any thoughts welcome. 

    Thanks

    - Oliver 

  • 0 in reply to Oliver Lewis
    TI__Genius 15005 points
    Hi Oliver,

    This is a known issue in OPT9221 firmware 0.26 and below: when dealiasing is disabled, the HDR flag is not set as expected. This has been fixed in the upcoming firmware version 0.28.

    We will make an early release for you for testing.

    Best Regards,
    Anand
  • 0 in reply to Anand Gadiyar
    Intellectual 635 points
    Hi Anand,

    Thanks for the quick response. Any thoughts when this will be available? The pre-release of 0.27 didn't fix any of our issues and in fact added more. Will all the known 0.26 issues be addressed (stopping issue, setting modulation frequency only when camera is running, HDR flag)?

    Is there an errata/bug tracker anywhere for the opt9221 f/w releases (It's taken me the better part of a week to show that this fault was not due to something silly on my part)?

    Regards
    - Oliver
  • 0 in reply to Oliver Lewis
    TI__Genius 15005 points
    Hi Oliver,

    An updated firmware 0.29 has been released and can be accessed from here:
    www.ti.com/.../sbac142

    The package includes the original firmware 0.23 as well and a list of known issues.

    We are looking at setting up a public issue tracker for OPT9221 firmware releases.

    Best Regards,
    Anand