AIO-3568J Frame buffer and HDMI

Paquq

Hello, I launched the kernel from the sdk and busy box on this board, the frame buffer is created when the HDMI is connected, after which the backlight turns on. The problem is that writing random data to frame buffer (fb0) is not displayed on the monitor. Kernel config is firefly_linux_defconfig and device tree is rk3568-firefly-aioj.dtbI attach dmesg with drm debugging.
https://drive.google.com/file/d/ ... 4/view?usp=drivesdk

时间的蝴蝶

The display is managed by the windows system(X11/Wayland), you can try to close it or use /dev/dri/card0.

Paquq

I need to use the Frame buffer that is being created in /dev/fb0, is there any way I can do this?

Paquq

I built the sdk system and everything works fine, including the framebuffer and the console on the display, but when I try to build my system with my file system (kernel and u-boot from the sdk), the frame frame buffer does not work and there is no console on the display.

An attempt was also made to write a driver for the framebuffer using libdrm, but it does not work either, although it functions on other machines. What could be the problem?

Paquq

After a small reconciliation of the boot log, I noticed that the reason for the lack of communication between the frame buffer and the HDMI connector may be an incorrect vop2 driver bind. The output is made from the following lines of the boot log:

[    0.388660] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp0 assign plane mask: 0x0, primary plane phy id: -1
[    0.388721] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp1 assign plane mask: 0x0, primary plane phy id: -1
[    0.388773] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp2 assign plane mask: 0x0, primary plane phy id: -1
When the sdk assembly has a different line with vp0:
rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp0 assign plane mask: 0x3f, primary plane phy id: 4