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.

dynamic capture resolution

Guru 20755 points

Hello,

In the MCFW training it is said that there is no support in Capture Link for dynamic resolution change, and also in VCAP MCFW API it is not described that there is such feature. But in the capture demo we can chose to change the resolution to one of the predefined resolutions(Vcap_setDynamicParamChn with VCAP_RESOLUTION). This will change DEI Link width, height. I would like to verify that this option enables dynamic resolution change of the captured video, i.e. if I change the input camera resolution the HDVPSS will be able to support the new resolution.

Any comment is appreciated,

Ran

  • Hello Ran,

    I'd also be interested in hearing about solutions for changing/adding a new resolution. We're working with the DM8127 - MT9J003 Aptina 10Mp sensor.

    At the moment everything is working well at 1920x1080 - but we need actual 1600x1200 ROI from camera.

    Thanks,

    Mechi

  • Hello,

    What is the software release that you are using IPNC or DVR RDK?

    Best Regards,

    Margarita

  • Hello Margarita,

    We're using the IPNC RDK. I'm familiar with the Aptina 10 Mp MT9J003 sensor - - and I know that it's not limited to any specific ROI - just maybe that the width and height should be multiples of 8.

    We need video streaming of 1600x1200 @ 30fps (or really 1632x1232 - since we use the SNF and TNF noise filters).

    We've set up a new usecase that combines Capture and Streaming.

    Any help would be appreciated.

    Thanks,

    Mechi

  • Hello,

    I notified the IPNC team for help or Contact your local FAE or TI Representative.

    Best Regards,

    Margarita

  • Hi Mechi,

    There is app note very detailed as to how to add new resolution, which is part of dvrrdk 4.0.1.2.

    There is also other very simpler way, which is to followoe (by search), another resolution and add the new resolution in a similar way. Don't forget to update the timing as required for the new reoslution in xx_timings.h file

    Thanks

    Ran

  • Hi Ran and Margarita,

    No one ever contacted me from the IPNC team.

    I built the new resolution based on the default (1920x1080 @ 30fps with binning). The problem is that even though I'm getting the resolution that I want with the correct frame rate, the AGC/AWB and SALDRE have stopped working.

    We now need a frame resolution of 1200x1200 @ 20fps (binning from 2400x2400) from the center of the sensor.

    When I made the changes gradually, I found that 1800x1200 (binning from 3600x2400) still gives me the correct AGC, AWB and SALDRE.

    Once I go down to 1600x1200, I lose all of the "automatic" frame processing functions.

    Ran - how can I get the app note you mentioned - maybe it can help me. Is it for the MT9J003 (Aptina 10Mp)?

    I'd appreciate any help you can offer,

    Thanks,

    Mechi

  • I think I may have found a link to the doc you mentioned - but it downloads as a blank page.

    http://processors.wiki.ti.com/images/f/fd/DVR_RDK_McFW_Link_API_Training.pdf

  • Hi,

    Maybe this app will help,

    Thanks,

    Ran

    DM81xx_DVR_RDK_Custom_Display_Resolution.pdf

  • Unfortunately this app note just discusses the Display resolution.
    I need something much more technical - how to change the sensor resolution.
    As I've mentioned, I changed it successfully, but the 2A functioning stopped working.
    Take care,
    Mechi
  • Hi, I'm not familiar with the 2A, but it sounds as if something in the sensors driver does not function as you expected. Did you get to check the driver code and add some printing maybe inside ? Also did you try to talk with Nissim ?
  • Is the driver of the sensor is in linux kernel ? Do you know which driver it is ? Thanks, Ran
  • I spoke to the TI FAE (Nissim) in Israel - he just said to post a message . He has no experience in changing resolutions on the driver level.
  • The "driver" is really just changing register settings. Since I'm familiar with this sensor (MT9J003), and I know which registers needed to be changed, I change the registers for the startup default to 1200x1200 (binning from 2400x2400). They are all in the file below.

    \ti_tools\iss_03_80_00_00\packages\ti\psp\devices\mt9j003\issdrv_mt9j003_config.h

    I've also found the files where the AEC/AWB are done and where the sizes are assumed fixed:

    \ti_tools\iss_03_80_00_00\packages\ti\psp\iss\drivers\alg\2A\src\issdrv_algTIaewb.c

    \ti_tools\iss_03_80_00_00\packages\ti\psp\iss\alg\aewb\ti2a\fd\inc\alg_ti_flicker_detect.h

    \ti_tools\iss_03_80_00_00\packages\ti\psp\iss\alg\aewb\ti2a\ae\src\ae_ti.c

    I'd rather not make the changes until I speak to someone in TI who is familiar with the 2A engine and can direct me to what exactly should be modified.

    Thanks,

    Mechi