Hi @ShaneCCC,
Suppose it depend on sensor.
No it doesn’t, the Jetson TX2 VI/CSI blocks should always follow the same working principle regardless the sensor.
You may reference to below for some Sony sensor’s case.
I already referenced that when I made the same sensor work on a Jetson Nano with the same custom baseboard.
Also you may need to check the trace log for the root cause of the PXL_SOF.
Kind of a pain in the ass but I may have no other choice since a lot of this things don’t go to dmesg.
Now, could yo please answer my original question?
I’d like to know whether the TX2 expects me to configure (for any possible sensor under the sky) the active image dimensions or the complete image dimensions (including blanks).
That very same parameters are used in the following piece of code extracted from vi4_fops.c
vi4_channel_write(chan, vnc_id, FRAME_X, width);
vi4_channel_write(chan, vnc_id, FRAME_Y, height);
vi4_channel_write(chan, vnc_id, SKIP_X, 0x0);
vi4_channel_write(chan, vnc_id, CROP_X, width);
vi4_channel_write(chan, vnc_id, OUT_X, width);
vi4_channel_write(chan, vnc_id, SKIP_Y, 0x0);
vi4_channel_write(chan, vnc_id, CROP_Y, height);
vi4_channel_write(chan, vnc_id, OUT_Y, height);
I already know the Nano expects the active image dimensions (or at least works fine with them).
That way doesn’t work on the TX2 NX right now and that’s why I’m asking.
I’d like to confirm if the configuration for those parameters should be the same.
Best Regards,
Juan Pablo.