Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 8609

Troubleshooting • HDMI does not work after vc4-kms-v3d started (CM3)

$
0
0
Hi, All!

Please help! There is a board based on CM3+. There are two displays connected - DPI and HDMI. When booting (OS is the latest 19.11.2024 RaspiOS Bookworm Lite) the HDMI display shows booting process until vc4-kms-v3d driver starts, then HDMI output turns off and DPI display turns on.

Tried with two monitors and one TV with the same result. Tried to add/remove hdmi_force_hotplug.

The confusing thing - several days ago I made a fresh install of the same image and configured it (I had to tweak several device tree overlays because my project moved from the old system/legacy driver to the new one with kms driver). Everything worked well - the system output was cloned across two displays, kmsprint shows both displays active. Unfortunately the card died yesterday and I did not save all configuration.

I think the following information may help.
kmsprint output:

Code:

Connector 0 (32) HDMI-A-1 (disconnected)  Encoder 0 (31) TMDSConnector 1 (42) DPI-1 (connected)  Encoder 1 (41) DPI    Crtc 1 (73) 1280x800@60.00 71.107 1280/70/10/80/+ 800/10/3/10/+ 60 (60.00) P|D      Plane 1 (62) fb-id: 318 (crtcs: 1) 0,0 1280x800 -> 0,0 1280x800 (XR24 AR24 AB24 XB24 RG16 BG16 AR15 XR15 RG24 BG24 YU16 YV16 YU24 YV24 YU12 YV12 NV12 NV21 NV16 NV61 RGB8 BGR8 XR12 AR12 XB12 AB12 BX12 BA12 RX12 RA12)        FB 318 1280x800 RG16        
ddcutil output
Note: I see monitor on the i2c2 bus and ddcutil can read EDID

Code:

root@raspberrypi:/share/OGL# ddcutil detect --verboseInvalid display   I2C bus:  /dev/i2c-2      DRM connector:                      card0-HDMI-A-1      Driver:                             Unknown      I2C address 0x50 (EDID) responsive: true      Is eDP device:                      false      Is LVDS device:                     false      /sys/bus/i2c/devices/i2c-2/name     bcm2835 (i2c@7e805000)      PCI device path:                    /sys/devices/platform/soc/3f805000.i2c/i2c-2   EDID synopsis:      Mfg id:               NEC - NEC Corporation      Model:                LCD2490WUXi2      Product code:         26509  (0x678d)      Serial number:      Binary serial number: 16843009 (0x01010101)      Manufacture year:     2010,  Week: 17      EDID version:         1.3      Extra descriptor:      Video input definition:    0x80 - Digital Input      Supported features:         DPMS active-off         Digital display type: RGB 4:4:4 + YCrCb 4:4:4         Standard sRGB color space: False      White x,y:        0.313, 0.329      Red   x,y:        0.644, 0.335      Green x,y:        0.304, 0.613      Blue  x,y:        0.146, 0.070      Extension blocks: 1   EDID source: I2C   EDID hex dump:              +0          +4          +8          +c            0   4   8   c      +0000   00 ff ff ff ff ff ff 00 38 a3 8d 67 01 01 01 01   ........8..g....      +0010   11 14 01 03 80 34 20 78 2a fc 85 a4 55 4d 9d 25   .....4 x*...UM.%      +0020   12 50 54 20 00 00 01 01 01 01 01 01 01 01 01 01   .PT ............      +0030   01 01 01 01 01 01 01 1d 00 72 51 d0 1e 20 6e 28   .........rQ.. n(      +0040   55 00 06 44 21 00 00 1e 01 1d 00 bc 52 d0 1e 20   U..D!.......R..      +0050   b8 28 55 40 06 44 21 00 00 1e 00 00 00 fd 00 31   .(U@.D!........1      +0060   3d 1b 46 0f 00 0a 20 20 20 20 20 20 00 00 00 fc   =.F...      ....      +0070   00 4c 43 44 32 34 39 30 57 55 58 69 32 0a 01 9d   .LCD2490WUXi2...   DDC communication failed
dmesg output:

Code:

root@raspberrypi:/share/OGL# dmesg | grep vc4[   15.508728] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])[   15.511131] rc rc0: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0[   15.511450] input: vc4-hdmi as /devices/platform/soc/3f902000.hdmi/rc/rc0/input1[   15.563365] input: vc4-hdmi HDMI Jack as /devices/platform/soc/3f902000.hdmi/sound/card1/input2[   15.564325] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])[   15.564779] vc4-drm soc:gpu: bound 3f208000.dpi (ops vc4_dpi_ops [vc4])[   15.565253] vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops [vc4])[   15.565670] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])[   15.566093] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])[   15.566485] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])[   15.566782] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])[   15.605038] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0[   15.693704] vc4-drm soc:gpu: [drm] fb0: vc4drmfb frame buffer device
Part of the config.txt with display configuration

Code:

# Enable DRM VC4 V3D driverdtoverlay=vc4-kms-v3dmax_framebuffers=2# DPI TFT LCDdtoverlay=vc4-kms-dpi-genericdtparam=hactive=1280,hfp=70,hsync=10,hbp=80dtparam=vactive=800,vfp=10,vsync=3,vbp=10dtparam=clock-frequency=71107200,pixclk-invert=1# Free gpio2 & gpio3 (VSYNC/HSYNC)# NOTE: the followin line should be below vc4-kms-dpi-generic!dtoverlay=dpi18_1# DPI Backlight PWM Control#dtoverlay=pwm_blgpio=40=op,dh###############################################################################hdmi_force_hotplug=1config_hdmi_boost=6hdmi_blanking=1# Disable compensation for displays with overscandisable_overscan=1

Statistics: Posted by oleg11 — Mon Feb 03, 2025 7:26 pm



Viewing all articles
Browse latest Browse all 8609

Trending Articles