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

Compute Module • Re: Alternative to USB‑C for High-Speed Data & Video in a Small-Scale Custom Access System

$
0
0
When running without custom EDID settings, we get the top half of the screen flashing, bottom half is black.

This is the output from kmstest, kmsprint and dmesg | grep -i drm

Code:

kmstestConnector 0/@32: HDMI-A-1  Crtc 3/@101: 640x480@59.94 23.975 640/24/56/80/- 480/3/4/13/+ 60 (59.94) U   Plane 3/@90: 0,0-640x480    Fb 723 640x480-XR24press enter to exitkmsprintConnector 0 (32) HDMI-A-1 (connected)  Encoder 0 (31) TMDS    Crtc 3 (101) 640x480@59.94 23.975 640/24/56/80/- 480/3/4/13/+ 60 (59.94) U       Plane 3 (90) fb-id: 721 (crtcs: 3) 0,0 640x480 -> 0,0 640x480 (XR24 AR24 AB24 XB24 RG16 BG16 AR15 XR15 RG24 BG24 YU16 YV16 YU24 YV24 YU12 YV12 NV12 NV21 NV16 NV61 P030 XR30 AR30 AB30 XB30 RGB8 BGR8 XR12 AR12 XB12 AB12 BX12 BA12 RX12 RA12)        FB 721 640x480 RG16Connector 1 (42) HDMI-A-2 (disconnected)  Encoder 1 (41) TMDS      dmesg | grep -i drm[    2.302974] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0[    2.350433] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    2.356400] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    2.359153] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    3.050131] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    3.072056] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    3.074811] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    3.374839] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...[    3.435668] systemd[1]: modprobe@drm.service: Deactivated successfully.[    3.436039] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.[    4.084621] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.091408] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.144530] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.198515] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.222543] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.234391] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.239960] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.285172] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.300263] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops [vc4])[    4.310042] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops [vc4])[    4.310384] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops [vc4])[    4.310532] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4])[    4.310702] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4])[    4.310824] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4])[    4.310900] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4])[    4.311028] vc4-drm gpu: bound fec12000.pixelvalve (ops vc4_crtc_ops [vc4])[    4.313595] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1[    4.421622] vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device
I tried to convert the old timings from fkms, but clearly they must've been wrong. The reason i get horrid fps is because we get errors on our custom EDID:

Code:

kmsprintConnector 0 (32) HDMI-A-1 (connected)  Encoder 0 (31) TMDS    Crtc 3 (101) 2560x1600@50.37 220.430 2560/48/32/80/+ 1600/0/6/3/+ 50 (50.37) P|D       Plane 3 (90) fb-id: 723 (crtcs: 3) 0,0 2560x1600 -> 0,0 2560x1600 (XR24 AR24 AB24 XB24 RG16 BG16 AR15 XR15 RG24 BG24 YU16 YV16 YU24 YV24 YU12 YV12 NV12 NV21 NV16 NV61 P030 XR30 AR30 AB30 XB30 RGB8 BGR8 XR12 AR12 XB12 AB12 BX12 BA12 RX12 RA12)        FB 723 0x0 �1�Connector 1 (42) HDMI-A-2 (disconnected)  Encoder 1 (41) TMDS    dmesg | grep -i drm[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=HDMI-A-1:640x480M@60,margin_left=32,margin_right=32,margin_top=32,margin_bottom=32 smsc95xx.macaddr=D8:3A:DD:69:F4:13 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=tty1 root=PARTUUID=e5395574-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=SE drm.edid_firmware=HDMI-A-1:edid.bin video=HDMI-A-1:e[    2.316204] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0[    2.383751] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    2.391743] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    2.398363] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    3.069485] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    3.091460] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    3.446617] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...[    3.512430] systemd[1]: modprobe@drm.service: Deactivated successfully.[    3.512802] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.[    4.204099] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.206513] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.238158] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.316165] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.319672] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.324548] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.350823] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.381293] vc4-drm gpu: bound fe400000.hvs (ops vc4_hvs_ops [vc4])[    4.381528] [drm] forcing HDMI-A-1 connector on[    4.395249] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops [vc4])[    4.409775] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops [vc4])[    4.410029] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops [vc4])[    4.410160] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4])[    4.410288] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4])[    4.410395] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4])[    4.410480] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4])[    4.410582] vc4-drm gpu: bound fec12000.pixelvalve (ops vc4_crtc_ops [vc4])[    4.420753] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1[   14.556906] vc4-drm gpu: [drm] *ERROR* [CRTC:101:pixelvalve-2] flip_done timed out[   24.796899] vc4-drm gpu: [drm] *ERROR* flip_done timed out[   24.796910] vc4-drm gpu: [drm] *ERROR* [CRTC:101:pixelvalve-2] commit wait timed out[   35.036909] vc4-drm gpu: [drm] *ERROR* flip_done timed out[   35.036927] vc4-drm gpu: [drm] *ERROR* [CONNECTOR:32:HDMI-A-1] commit wait timed out[   45.276904] vc4-drm gpu: [drm] *ERROR* flip_done timed out[   45.276918] vc4-drm gpu: [drm] *ERROR* [PLANE:90:plane-3] commit wait timed out[   55.516899] vc4-drm gpu: [drm] *ERROR* flip_done timed out[   55.516908] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit[   65.756923] vc4-drm gpu: [drm] *ERROR* [CRTC:101:pixelvalve-2] flip_done timed out[   65.770077] vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device[   75.996918] vc4-drm gpu: [drm] *ERROR* flip_done timed out

The datasheet for the display is talking about mipi timings, so I emailed the manufacturer about the board timings and got this back. I will compare these board timings to my edid and see what went wrong.

Clock of Display
HDMI clock of board.png
Clock of Board
HDMI clock of display.png

Statistics: Posted by Jesper_ITOS — Wed Feb 05, 2025 10:37 am



Viewing all articles
Browse latest Browse all 8037

Trending Articles