• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 570 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.

Original question:

TDA4VM: TDA4VM WDR MERGE

TDA4VM: Details on WDR tuning block

Petr Nechaev
Prodigy 50 points

Part Number: TDA4VM
Other Parts Discussed in Thread: TDA4VL,

Hello,

after studying the TRM for TDA4VM an TDA4VL we cannot find much details on WDR motion-adaptive merge block, only register settings and some limited information in header files.

Could you please advise, where can we find more details on the operation of the block and meaning of parameters?  Thank you!

  • 0
    TI__Guru 67840 points

    Hi Petr,

    Unfortunately, I don't find more information available in any version of the TRM (public or NDA).

    What type of applications/sensors are you planning to use these blocks for?

  • 0 in reply to Gang Hua
    Prodigy 50 points

    Thank you for a quick reply!

    We need to provide an RFQ response so we are analyzing TDA4VM and TDA4VL capabilities for extending dynamic range for ox3a image sensor. It can do on-chip combination of  HCG + LCG to produce RAW12 image but VS/SPD exposures come in a different MIPI CSI virtual channel and must be combined with LPD on the SoC side. The RFQ is for a low-cost product, this is all I can tell on a public forum.
    We can figure out driver / capture / buffer management etc because they are well described and apparently mostly supported by drivers, but unfortunately there is nothing on meaning of WDR parameters in the documentation.

  • +1 in reply to Petr Nechaev
    TI__Guru 67840 points

    Hi Petr,

    Thank you very much for the background.
    I heard about similar situations for X3A a few times in the past.

    I have some TDA4 ISP training slides under NDA which include some more information about WDR merge.
    You may contact your local TI support and ask for the slides.

    In general, I would prefer WDR merge in sensor and don't recommend using the WDR merge in VISS as it is relatively simple merge logic and I am not sure how much motion artifacts there may be for a sensor.
    For ADAS applications, VISS WDR merge has not been widely used by customers.