REISZER OVERFLOW OCCURED

Hi, Zhuoran Dai

Thank you very much.

Now it is ok!

hi，Zhuoran Dai

If ispPrm.outQueuePrm[0].dataFormat  is SYSTEM_DF_YUV420SP_UV, should pitch be 2560 or 2560*1.5? Now I set pitch to 2560. There is a green line on image.

Hi,

I am experiencing a similar problem.

Where in the code do I need to change the pitch setting for the camera link?

Please check the function "CameraLink_drvAllocAndQueueFrames" in "cameraLink_drv.c", also in the same file make sure to pass the right pitch information to the driver and next link.

Hi Zhouran,

Thanks for your answer.

I am using 1920x1080 resolution. I have set the pitch to be 1920, but am still experiecing the same problem.

Shoud I increase the pitch further such as 1920 * 1.5 ?

Could you be more specific regarding the location where the pitch information is passed to the driver and next link?

Thanks,

eliba

Are you seeing RSZ overflow only with mirror/rotation? Or it happens even with a normal output?

Please check "CameraLink_drvCreateInst" (next link), "CameraLink_drvAllocAndQueueFrames" (allocation), "CameraLink_drvInitCreateArgs" (driver) for pitch information.

Hi Zhouran,

When using vertical mirroring and changing the sensor exposure, I get a resizer overflow and the image freezes and I can't see any video until I restart the usecase.

In normal display mode this doesn't happen, but I sometimes get a resizer overflow but I can still see captured video afterwards, but with green colors added to varous objects

Please double check the pitch setting at the three locations I indicated in my previous post.

If the pitch is not 128 bytes aligned, make it 128 bytes aligned may help you to avoid the overflow with mirror.

However, if you get an overflow when you change the sensor exposure, then it doesn't help. You need to verify your sensor output signal, especially HD/VD timing, our ISP doesn't support dynamic timing change on the input signal. What sensor do you use?

Hi Zhouran,

I have tried setting all the pitch variables to 1920. That still didn't solve the problem.

I am using CMOSIS CMV2000, this is a custom sensor I am integrating to work with the IPNC platform.

For some reason, when adjusting sensor exposure in response to 2A parameters, everything works well. This only happens when exposure is changed manually (through ITT server register write).

What could cause the difference? 

In the TI 2A case of adjusting exposure, this happens after sensor driver receives: IOCTL_ISS_SENSOR_UPDATE_EXP_GAIN

and if using ITT server, sensor driver receives: IOCTL_ISS_SENSOR_UPDATE_ITT

The code inside the sensor driver that handles both requests is the same.

I have done some further testing. I've connected the VSYNC and HSYNC signals to a logic analyzer and tested them at various frame rates. 

I've noticed there is indeed a difference in HS/VS timing when changing exposure manually, as opposed to changes resulting from TI 2A output parameters.

I've attached a comparison of both signals during AEWB mode, and with a manual change of exposure.

What could explain such findings? I am using the same implementation in the sensor driver for both commands.

Sorry I don't think I could help here as the problem seems to be in the sensor driver and we don't support that sensor in our RDK.

I think you need to double check the exact register write opeation.

Hi Zhouran,

Thanks to your advice of taking a look at HS/VS signals, I have managed to solve the problem.

When adjusting the exposure, I do so gradually with 500 microsecond steps, just like the TI 2A engine does. Now I see no resizer overflows in mirror mode, with default pitch settings.

We used to see that kind of line artifact on other sensors and I don't think it comes from mirror or pitch setting. You can capture a RAW frame and verify, that artifact should come from some improper sensor setting.

You're right, the line artifact is a known issue with this sensor in certain conditions.

Eliba,

Did you try increasing the ISS L3 priority when you got the ISS RESIZER overflows?

I think if you program the highest priority you can avoid overflow.

Regards

Rajat

Hi Rajat,

Thanks for your reply.

Where would I be able to change this setting?

Use following command:

./bin/sys_pri.out --L3-bw-reg-set ISS 3 3 100 2000&

And please replace the attached sys_pri folder with the corresponding folder in the RDK.

Regards

Rajat