Almost certainly you ignored my commentHi,
I have applied these commands as adviced. The result is as below :
1. ____ get-detected___ gives 0x000000ff PAL_B/B1.... etc
2. ------- set-standard PAL gives "standard set to 000000ff"
3. the final command : sudo gst-launch-1.0 v4l2src........ gives the result as below :
pi@raspberrypi:~ $ sudo gst-launch-1.0 v4l2src ! v4l2convert ! kmssink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstKMSSink:kmssink0: GStreamer encountered a general resource error.
Additional debug info:
../sys/kms/gstkmssink.c(2032): gst_kms_sink_show_frame (): /GstPipeline:pipeline0/GstKMSSink:kmssink0:
drmModeSetPlane failed: Permission denied (13)
Execution ended after 0:00:00.060099155
Setting pipeline to NULL ...
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error.
Additional debug info:
../libs/gst/base/gstbasesrc.c(3132): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
streaming stopped, reason error (-5)
Freeing pipeline ...
DRM/KMS only allows one master at a time to control what is on the screen. The framebuffer emulation doesn't count, but X11 or Wayland do.(must be booted to console, not X11 or Wayland)
Use raspi-config to select boot to "console", or use ctrl-alt-F2 to switch to an alternate TTY before running the gst-launch command. (Ctrl-alt-f1 to get back to X11/Wayland).
All CSI2 devices should be stopped when the V4L2 device is stopped.Observing output pins on the scope there is a short activity on D0P/N pins (starts and fails).
So the final result is as before. None.
I will try to change cabling between EVAL and RPi however the present are quite short so the propagation delay is rather beyond the importance. Anyway this is the last thing I can check and change.
The CSI2 receiver needs to see the D-PHY LP-11 to HS transition on the clock lane to synchronise properly, and it is powered down when not in use. That means that the CSI2 source has to be stopped and started in a controlled manner, not just left permanently streaming.
https://github.com/raspberrypi/linux/bl ... #L565-L567 does this (let's just use bare numbers even though we've defined ADV7180_CSI_REG_PWRDN and ADV7180_CSI_PWRDN
).I tested this yesterday, so I know it works. Admittedly that was with ADV7282-M, not ADV7282-MA, but I believe the only difference is RoHS compliance.
Statistics: Posted by 6by9 — Fri Jun 14, 2024 10:33 am
