TDA3MV: Is it possible that data of the video port can be written in the buffer logic?

Hi YR,

Sorry did not get your question, why do you want video port to go to SD RAM and then read in buffer login..

Buffer logic ie path to write to memory is supported in ISIF, Resizer and H3A modules.. So we need to pass through these modules in order to write data to memory..

Regards,

Brijesh

Hi,

Thank you for sharing.

I want that the format of video port is YUV422 because when 12bit raw bayer data pass through the CFA interpolation module, 12 bit raw bayer data is lost(CFA interpolation RGB4:4:4)

When the format of video port is YUV422, there is other problem.

The problem is that when the Y data of the video port increases by 1 to 0, 1, 2, 3, ..., the output of IPIPEIF is 0, 14, 29, 45, ..., which increases by 14-15.

I don't know the reason.

Regards,

Hi YR,

Do you want to read YUV422 data over Video port? But what processing do you want to enabled? CFA module can be bypassed for YUV422 mode. 

Please refer to ISS Resizer link in the vision sdk. This link uses only resizer in the ISS for YUV input data.. We can optionally enable Edge Enhancer for YUV data. 

Regards,

Brijesh

Hi,

Thank you for reply.

1. Do you want to read YUV422 data over Video port?

   --> Yes. 

2. What processing do you want to enabled?

 --> GLBCE, NSF3V,, Gamma, Edge Enhancer, RSZ, CNF, VTNF, DPC, white balance, 

      Could I use all these modules?

3. CFA module can be bypassed for YUV422 mode.

 --> That is what i want because when the raw data pass through the CFA, the data loss is occurred.(Is this right?)

      So i want to use the YUV422 instead of Raw Bayer data format.

4. Please refer to ISS Resizer link in the vision sdk. This link uses only resizer in the ISS for YUV input data.. We can optionally enable Edge Enhancer for YUV data. 

 --> I will check it.

5. Below my question.

------------------------------------------------------------------------------------

When the YUV422 data format pass through IPIPEIF --> ISIF --> RSZ, YUV422 data format is changed to be weird.

The input data of IPIPEIF is 0 at 0 pixel position.

The input data of IPIPEIF is 1 at 1 pixel position.

The input data of IPIPEIF is 2 at 2 pixel position.

The input data of IPIPEIF is 3 at 3 pixel position.

...

The output data of RSZ is about 0 at 0 pixel position

The output data of RSZ is about 14 at 1 pixel position

The output data of RSZ is about 28 at 2 pixel position.

The output data of RSZ is about 43 at 3 pixel position.

...

I don't know why the output data of IPIPEIF is getting bigger than the value that I expect.

So when I use the YUV422 data format, I couldn't get the correct image data.

Thanks for reading.

I'm not good at English, so if there are you don't understand, then please tell me.

Regards,

Hi

#2, please check IPIPE documentation, many of these modules are supported only for RAW data. Only few modules can be enabled for YUV data.

#4 Please go through the link mentioned above, it will give idea about how to bypass CFA module. 

#5, please complete above two and it will give correct at the resizer output. There is also a way to bypass resizer..

Rgds,

Brijesh

Thanks for reply.

#2, please check IPIPE documentation, many of these modules are supported only for RAW data. Only few modules can be enabled for YUV data.

 --> Okay, I will check. I want to use DPC, Edge enhancer only in IPIPE module.

 --> I have a question about the format settings for IPIPE_SRC_FMT.

      The settings, 0x2 for FMT2 and 0x3 for FMT, is not possible, so I have to set 0x0 for FMT2 and 0x03 for FMT,

      Is it right?

#4 Please go through the link mentioned above, it will give idea about how to bypass CFA module. 

 --> You mentioned the link about RSZ module. Is it right?
      (ISS Resizer link in the vision sdk)

      I think CFA module is before RGB2RGB blending in IPIPE. Could Resizer module affect CFA module?

     Or do you mean that the raw bayer data can bypass CFA module, if I refer the ISS Resizer link?

#5, please complete above two and it will give correct at the resizer output. There is also a way to bypass resizer..

 --> Actually, i think there are problems in ISIF. I will check first to do #2, #4.

Thank you for 

Hi,

Please find answers to your questions below.

#1, Yes that's correct

#2, Yes, that's correct, please refer to ISP resizer link in vision sdk.

Resizer comes after IPIPE, so it does not affect CFA module.

CFA is bypassed when FMT is set to 3

Regards,

Brijesh

Hello. I have the same type of question, so I want to check it.

I'm having trouble using the YUV422 input and I'm checking it out.

The path is as follows: IssCapture-> customAlgo-> ISP-> customAlgo2-> Display

The ISP path is as follows:
IPIPEIF-> ISIF-> RSZ

If CustomAlgo's output is RAW_BGGR, the video is fine.
However, if i change it to YUV422_UYVY output, the problem occurs that the output value increases by 14 ~ 15 as in the above question. Also, the video does not display normally.

So I want to know the ISP settings when the ISP input is YUV422.
So I would like to see which module is causing the problem.

Here are the settings I have set up:
-------------------- ISP ----------------------------- -----------------------
isp operating mode = 12 bit linear mode;

-------------------- IPIPEIF ----------------------------- -----------------------
IPIPEIF_CFG1 [15:14] INPSRC1 = 0;
IPIPEIF_CFG1 [15:14] INPSRC2 = 0;
DECOMPAND from Vport = disabled;
Averaging filter = disabled;
Horizontal pixel decimator = disabled;

-------------------- ISIF ----------------------------- -----------------------
ISIF_MODESET [6] DPOL = 0;
ISIIF_LINCFG [0] LINEN = 0;
ISIFFMTCFG [0] = 0;
ISIF_CSCCTL [0] CSCEN = 0;
BLACK CLAMP = disabled;
VDFC = disabled;
2D-LSC = disabled;
ISIF_MODESET [14] HLPF = 0;
ISIF_CGAMMAWD [0] CCDTBL = 0;
ISIF_MISC [12] DPCMEN = 0;
DATA SHIFHT = No data movement;

-------------------- Resize ---------------------------- ------------------------
opmode resize = resize

overrideincfg = true;
yuvrszmode = chroma only;

Resize outfmt = YUV420SP_UV;
Resize infmt = YUV420SP_UV;
oufmt.bpp = 12 bits;
scalemode = normal mode;

Hi sdi,

Are you using vision sdk or pdk drivers?

for vision sdk, please use iss_resizer link, implemented in the file vision_sdk\links_fw\src\rtos\links_ipu\iss_m2mresizer\issResizer_drv.c. This link support YUV422 input format and using resizer, it can be uesd to convert format to YUV420..

For PDK driver, please refer to driver example in vision_sdk\ti_components\drivers\pdk_01_10_02_07\packages\ti\drv\vps\examples\iss\m2mIss\src\M2mIss_main.c file..

Regards,

Brijesh

Hi,

issm2mlink uses all components of the isp, whereas issm2mresizer just uses resizer. 

It is ok, even if you are using resizer in the issm2mlink, you could use both the links in the single usecase. The framework will take care of protecting resizer in both the links.

Rgds,

Brijesh