We use UB964 connect with TX2. Our sensor frame rate is 25 fps. But after TX2 CSI interface, our test result is 12.5 fps. We have mereament MIPI clk rate is 25 fps. We use v4l-ctl & yavta to do testing. Both return frame rate is 12.5 fps. How could cause this problem?

hello 53216142, actually, you should configure the signal properties settings correctly, since kernel drivers refer to these and configure the clock rates dynamically. thanks

If you boost the clock still can’t get improve, then I think the problem is the sensor output problem.

@ShaneCCC As mentioned before, we have did measurement MIPI CLK (Discontinuous mode). The interval time is actually 40ms, not 80ms. We have SCOPE picture, you can get it from #5 attachment 671900850.jpg.

hello 53216142, you might dig into the VI driver to check the capture events trigger timing. could you please add debug messages to check each syncpt wait period. for example, /kernel_src/kernel/kernel-4.4/drivers/media/platform/tegra/camera/vi/vi4_fops.c /* * Wait for PXL_SOF syncpt …

Does this scope is between UB964 and Tegra CSI? Could you also probe the MIPI data and clock.

@JerryChang Do you mean this? /* * Wait for PXL_SOF syncpt * * Use the syncpt max value we just set as threshold */ for (i = 0; i < chan->valid_ports; i++) { ts_a …

hello 53216142, yes, sync-point of PXL_SOF is sending, and waiting for each frame start. this function timing roughly close to frame processing time of your sensor hardware. since your sensor frame rate is 25-fps, you should expect nvhost_syncpt_wait_timeout_ext() taking ~40ms here. looking forw…

@JerryChange Here is the reuslts. Any useful info. Or if you have any concern I can insert more debug info as needed. [ 56.758696] video4linux video0: fun vi_notify_wait line 217 port 0 period 43ms [ 56.838789] video4linux video0: fun vi_notify_wait line 217 port 0 period 39ms [ 56.918872…

hello 53216142, it surprise me that your syncpt wait returning within 1/fps, could you please share more details about what’s your environment settings, for example, which JetPack release you’re working with. what’s additional patches you had applied. below function indicate the actual frame b…

JerryChange, My JetPack tag is tegra-l4t-r28.2.1. For now I didn’t apply any patch. And sure I will apply Jul26_topic1037809.tar.gz laster as you mentioned. My result is within 1/fps, I guess it maybe caused by compiler FP issue. After test point an function start and end, the period roughly like …

MIPI CSi frame rate issue

Robotics & Edge Computing Jetson Systems Jetson TX2

53216142 January 10, 2019, 8:11am 11

@ShaneCCC Yes, the scope between UB964 and Tegra CSI.

I have only take picture of MIPI clock as 671900850.jpg showing.
About MIPI data I remember the frequency is correct(18KHZ the line frequency of 1280*720?). Because I can download correct image picture. Except frame rate is half now!

Topic		Replies	Views
About the frame rate reduction problem of capture processing using CSI of Jetson TX2 Jetson TX2 camera	53	2842	May 7, 2021
Only each of the second frame is captured on the CSI bus Jetson TX2 camera	20	2541	May 18, 2021
TX2 EMV ov5693 trace issue Jetson TX2	4	547	February 25, 2019
Jetpack3.2.1, TX2 CSI-MIPI can only get the the first frame of image, but TX1 works fine. Jetson TX2	9	3390	July 30, 2018
Mipi camera sometimes cannot get frame Jetson TX2 camera	17	1145	November 29, 2022
Problem of getting data from MIPI CSI Jetson TX2 Jetson TX2	39	4242	September 6, 2019
About TX2 MIPI CSI error message : rtos_queue_peek_from_isr_failed Jetson TX2	1	765	February 21, 2020
Got "PXL_SOF syncpt timeout! err " Jetson TX2	7	2060	October 12, 2020
Questions about MIPI recievement on TX2 side Jetson TX2	8	1316	January 17, 2019
CSI camera driver syncpt timeout error Jetson TX2	7	3027	February 15, 2018

MIPI CSi frame rate issue

Related topics