Jetson Nx adv7482 pal capture

Dear all.

I have modified adv7482 driver and port it to Jetson NX
It created /dev/video0 but when i read data from video link, i got capture failure Data(720*288)

Can some one help me. ?
Please …

hello hhami.2040,

this looks like alignment issue, VI should follow 64-alignment.
may I know what’s your test commands, could you please have a quick try to hack the active width as 768 for confirmation?

Hi …
Thank you for answering…
I got captured a frame in jetson Nano according below frame …

i have edited driver to 288*768
but dont change it.

hello hhami.2040,

are you using v4l2 or gst pipeline? may I know what’s your test commands, thanks

gst pipeline,
i have captured bot v4l2 command and gst pipline

when i captured v4l2 video link in Jetson nx
i have faced
[ 2.845815] tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 512
[ 2.865962] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 512
[ 2.885768] tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 512
[ 2.906243] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 512
[ 2.926057] tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 512

hello hhami.2040

you cannot capture the frame with v4l2 and Argus together,
please enable preferred_stride controls via v4l2 standard controls,
for example,
$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=2592,height=1944,pixelformat=RG10 --set-ctrl bypass_mode=0 --set-ctrl preferred_stride=64 --stream-mmap --stream-count=3 --stream-to=test.raw

hello dear
i have tested this command but it dosnt change
May you help me???

when i used this command in jetson nx
i could capture a raw frame and then i faced these errors:
res:720x288
720x288.raw (1.2 MB)

[ 91.994777] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 131072
[ 92.006317] tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 131072
[ 92.026107] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 131072
[ 92.040378] tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 131072
[ 92.066236] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 131072
[ 92.070812] tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 131072
[ 92.074956] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 131072
[ 92.094966] tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 131072
[ 92.130427] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 64
[ 92.150402] tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 131072
[ 92.170470] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 64
[ 92.190352] tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 131072
[ 92.210412] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 64
[ 92.230392] tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 131072
[ 92.250531] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 64
[ 92.270451] tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 131072
[ 92.290490] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 64
[ 92.310533] tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 64
<<<

but when i chenged driver resoulotion to 768x288
i couldnt capture a raw frame using
v4l2-ctl -d /dev/video0 --set-fmt-video=width=2592,height=1944,pixelformat=RG10 --set-ctrl bypass_mode=0 --set-ctrl preferred_stride=64 --stream-mmap --stream-count=3 --stream-to=test.raw

i faced this error
tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 512
tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 512
tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 512
tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 512
tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 512
tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 512
tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 512
tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 512
tegra194-vi5 15c10000.vi: corr_err: discarding frame 2, flags: 0, err_data 512
tegra194-vi5 15c10000.vi: corr_err: discarding frame 1, flags: 0, err_data 512

hello hhami.2040,

you have to revise the command-line to adapt your sensor capability, for example, width, height, pixel formats.

i thought i said clearly that,
i used the command according resolution of any driver for example
i changed the command to 720*288
$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=720,height=288,pixelformat=UYVY --set-ctrl bypass_mode=0 --set-ctrl preferred_stride=64 --stream-mmap --stream-count=3 --stream-to=test.raw

and used to the command for 768*288
$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=768,height=288,pixelformat=UYVY --set-ctrl bypass_mode=0 --set-ctrl preferred_stride=64 --stream-mmap --stream-count=3 --stream-to=test.raw

but i couldn’t capture no frame both of them
if you may see the raw file that i attached(720*288) in NX jetpack 4.6 of course we also tested that with jetpack 4.4.1
720x288.raw (1.2 MB)

hello hhami.2040,

please check the $ v4l2-ctl -d /dev/video0 --list-formats-ext for the reported available sensor modes, and please assign the exactly width/height values and pixel formats to the --set-fmt-video=width=<>,height=<>,pixelformat=<> settings.
the discarding frame failure there meant the channel encountered an uncorrectable error and it must be reset. could you please try toggle the reset of adv7482 before start streaming.

thank you,i do it and send you result of it defenitely

Hello JerryChang,again
thank you for answering
sorry repeat that, i asked you a question anytime ago, that why we could capture frame without any error in the jetson nano
but we have faced problem in the jetson NX
what is difference between them??
May you answer me really why??

hello hhami.2040,

Nano and Xavier NX having different architecture, they’re using different VI drivers, where Nano series using VI-2 and Xavier series having VI-5. in addition, Xavier series is more critical to the signal settings.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.