We are using the elinux yocto 2.0 build system, we would like to configure our display in RGB888 format, where we need to modify to make it work for RGB888 format?
Note : we are using the lvds display which support the RGB888 format.
In reply to Georgi:
In reply to Charan K S:
Hello Georgi, All the applications have the same issues, I attached the video captured from the display after runinng the 'weston-simple-egl' from the command line. drive.google.com/open The frame buffer configuration with 1280x800 have the issue. I tried both the configuration as you suggested but no improvements, Below is the bootargs command what i set during boot time setenv bootargs 'console=ttySC10,38400 ignore_loglevel rw root=/dev/nfs nfsroot=192.168.2.6:/nfs/skrzg1m,nfsvers=3 ip=192.168.2.10:192.168.2.6::255.255.255.0:skrzg1m vmalloc=384M video=LVDS-1:1280x800-32@60'
Hello georgi, we have improvements after made some modifications in the bootargs, that is video=LVDS-1:1280x800-16@60.
because of this change During the boot time we will get the yocto image that is coming good but after that when weston starts display again going to be blured as previous issue.
Hello Georgi, weston file which is present in the path /etc/xdg/weston/weston.ini does not contain any data, I added the below lines, after that i did the reset to check but no improvements(The changes we made in the weston.ini are not reflecting after reset, for example transform=180 should rotate the screen but its not happening). [output] name=LVDS1 mode=current transform=180 When i ran the command weston-info in command line, I got the below informations, weston-info interface: 'wl_compositor', version: 3, name: 1 interface: 'wl_subcompositor', version: 1, name: 2 interface: 'wl_scaler', version: 2, name: 3 interface: 'presentation', version: 1, name: 4 presentation clock id: 1 (CLOCK_MONOTONIC) interface: 'wl_data_device_manager', version: 2, name: 5 interface: 'wl_shm', version: 1, name: 6 formats: RGB565 XRGB8888 ARGB8888 interface: 'wl_kms', version: 2, name: 7 interface: 'wl_seat', version: 4, name: 8 name: default capabilities: pointer keyboard touch keyboard repeat rate: 40 keyboard repeat delay: 400 interface: 'wl_output', version: 2, name: 9 x: 0, y: 0, physical_width: 229 mm, physical_height: 149 mm, make: 'unknown', model: 'unknown', subpixel_orientation: unknown, output_transform: normal, mode: width: 1280 px, height: 800 px, refresh: 60 Hz, flags: mode: width: 1280 px, height: 800 px, refresh: 60 Hz, flags: mode: width: 1280 px, height: 800 px, refresh: 60 Hz, flags: current interface: 'wl_input_panel', version: 1, name: 10 interface: 'wl_input_method', version: 1, name: 11 interface: 'wl_text_input_manager', version: 1, name: 12 interface: 'wl_shell', version: 1, name: 13 interface: 'xdg_shell', version: 1, name: 14 interface: 'desktop_shell', version: 3, name: 15 interface: 'workspace_manager', version: 1, name: 16 interface: 'screenshooter', version: 1, name: 1
When i am trying to run the weston example application by executing the command weston-subsurfaces below are the config details visible.
weston-subsurfaces Chosen EGL config details: RGBA bits: 8 8 8 8 swap interval range: 0 - 1
But what we set in the boot args for display is video=LVDS-1:1280x800-16@60. (I think this RGB565).
As you suggested I tried it, Now display transformation is happening, but the display blurness still existed as mentioned in previous conversation, I am not sure why display is not coming properly once the weston starts.
Just to be in the track the issue we are facing is:
The lvds display not running properly after Weston starts [(some color are missing or wrong pixel format its referring not sure)] , but before Weston starts yocto image(Symbol) will come during boot it is displaying fine. Currently lvds is configured with pixel size 16(we tested 24 as well as 32 for these values even yocto symbol also will not display properly).
since lvds display is working fine with the yocto 1.6, We tried to understand what are the changes between the yocto 1.6 and yocto 2(We are having issue in display), we found following changes as seen the below diagram,
1. In yocto 2 default pixel size is 32(RGB888) whereas in yocto 1.6 its 24 (RGB666),
And also In yocto 2 we tried to change the pixel size to 16, 18, 24, 32 no improvements except the pixel size 16, where the yocto image during boot time coming properly as mentioned in previous mails but after Weston starts the display again not proper.
2. As you asked in previous mails which api you are using to communicate to display unit -> we didn't get how to check that, but when i checked the back-end which is used by Weston to run it looks like drm back-end.
Please suggest the ways to debug to get the useful information to solve the issue.
Hello Georgi, we tried to run an sample application that will display multiple colors by directly to the frame buffer. It worked perfectly. for testing the application I stopped the weston and run the sample application as you suggested it worked fine. please help us to resolve the weston issue. Regards, charan
yes we are specified 16-bit color in u-boot using the boot argument video=LVDS-1:1280x800-16@60.
Below is the screen shot for the img pix fmt value displaying during boot messages. It is showing value 1.
We are using the RZ/G1M starter kit same as image shown in the below link.
In the starter kit we have the HDMI port and we are not facing any issue with HDMI display, we are getting proper display output.