Firefly Open Source Community

   Login   |   Register   |
New_Topic

AIO-3568J Frame buffer and HDMI

73

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
73
Posted at 7/19/2022 16:32:12     
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

Reply

Use props Report

365

Credits

20

Prestige

12

Contribution

intermediate

Rank: 3Rank: 3

Credits
365
Posted at 7/22/2022 09:17:04     
The display is managed by the windows system(X11/Wayland), you can try to close it or use /dev/dri/card0.
Reply

Use props Report

73

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
73
Posted at 7/30/2022 22:55:17     
I need to use the Frame buffer that is being created in /dev/fb0, is there any way I can do this?
Reply

Use props Report

73

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
73
Posted at 9/2/2022 14:25:40     
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?
Reply

Use props Report

73

Credits

0

Prestige

0

Contribution

registered members

Rank: 2

Credits
73
Posted at 9/5/2022 20:08:19     
Last edited by Paquq In 9/5/2022 20:09 Editor

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

Reply

Use props Report

You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list