phdm
January 21, 2021, 11:40am
1
Hello,
I have compiled successfully the oneshot example, called argus_oneshot, and I can run it successfully without option, thus using my first sensor. I have a second identical sensor on the same board, that works perfectly with v4l2, but running argus_oneshot with option ‘-d 1’ fails with the message
Failed to get IFrame interface
, while the kernel has issued a
fence timeout on [ffffffc1e6809c00] after 1500ms
message. Should argus_oneshot work with the second sensor or is that an expected behaviour ?
Thereafter, trying to use sensor 0 does not work anymore, until I reboot my board.
My two identical sensors are connected using 4 mipi lanes each, on csi 1 and csi 2.
Both of them are working by v4l2-ctl?
phdm
January 22, 2021, 5:50am
4
Yes :
nvidia@cam5-0000:~$ v4l2-ctl -d 0 --stream-mmap=3 --stream-count=256 --set-fmt-video=width=2464,height=2056,pixelformat=BG12
nvcamerasrc also works with both sensors; see attached log.nvcamerasrc.log (4.8 KB)
How about others sample APP?
phdm
January 22, 2021, 8:02am
6
I am on a custom board, using ssh. I have no display. Which samples are expected to work ?
I have also tested yuvJpeg (argus_yuv_jpeg). It works with the default option or ‘-d 0’. Like oneShot, it also fails with ‘-d 1’, and afterwards ‘-d 0’ does not work anymore.
How about the gst-launch-1.0?
export DISPLAY=:0
gst-launch-1.0 nvarguscamerasrc sensor-id=0 ! 'video/x-raw(memory:NVMM),width=1920,height=1080,format=NV12' ! nvvidconv ! fpsdisplaysink video-sink=fakesink --verbose
gst-launch-1.0 nvarguscamerasrc sensor-id=1 ! 'video/x-raw(memory:NVMM),width=1920,height=1080,format=NV12' ! nvvidconv ! fpsdisplaysink video-sink=fakesink --verbose
phdm
January 22, 2021, 8:47am
8
ShaneCCC:
gst-launch-1.0 nvarguscamerasrc sensor-id=0 ! 'video/x-raw(memory:NVMM),width=1920,height=1080,format=NV12' ! nvvidconv ! fpsdisplaysink video-sink=fakesink --verbose
gst-launch-1.0 nvarguscamerasrc sensor-id=1 ! 'video/x-raw(memory:NVMM),width=1920,height=1080,format=NV12' ! nvvidconv ! fpsdisplaysink video-sink=fakesink --verbose
That works with sensor-id=0, but fails with sensor-id=1.
CONSUMER: Producer has connected; continuing.
and the serial console shows
[ 166.806202] host1x 13e10000.host1x: CaptureSchedule: syncpoint id 19 (15600000.isp_nvargus-daemon_4) stuck waiting 753, timeout=-1
phdm
January 25, 2021, 8:46am
10
Sorry for the noise, ShaneCCC,
it works now; I had added printk’s to tegra_ivc_vi_notify_get_capture_status to ascertain that that function was used also when acquiring with argus (after I had already checked that it is used with v4l2). Those two added printk’s were enough to trigger a timeout for sensor 1, although they are innocuous for sensor 0. I didn’t check further. I only notice that without the printk’s, sensor 1 works again. I just must add that I managed to get UTC timestamps so the printk(ts) takes a little bit more time than with uptime timestamps.
static int tegra_ivc_vi_notify_get_capture_status(struct device *dev,
printk(“tivngcs(%u,%llu)\n”, ch, index);
if (ivn->adjust_ts_counter % ADJUST_TS_FREQUENCY == 0)
ivn->ts_adjustment = get_ts_adjustment(ivn->ts_res_ns);
if (status->sof_ts != 0) {
s64 ts = (s64)status->sof_ts;
ts += ivn->ts_adjustment;
status->sof_ts = (u64)ts;
printk(“-> %llu\n”, (u64)ts);
if (status->eof_ts != 0) {
s64 ts = (s64)status->eof_ts;
ts += ivn->ts_adjustment;
status->eof_ts = (u64)ts;
}
ivn->adjust_ts_counter++;
} else {
err = -ENOTSUPP;
}
return err;
}
I don’t have idea for it now. Could you check if add some delay help on it?