Difference between revisions of "RZ-G/Boards/EK874"

From eLinux.org
Jump to: navigation, search
(initial page)
 
(add u-boot Configuration Files)
(2 intermediate revisions by the same user not shown)
Line 23: Line 23:
 
Therefore, iWave is distributing the the Silicon linux RZ/G2E board using their channel.
 
Therefore, iWave is distributing the the Silicon linux RZ/G2E board using their channel.
  
 +
= Max Monitor Resolution of 1080p@30fps =
 +
 +
The RZ/G2E has two types of display outputs - LVDS and parallel (RGB888). On the RZ/G2E evaluation board the HDMI output is connected to the parallel RGB interface. That interface has a maximum pixel clock of 75MHz which is not enough to support 1080p at 60fps, the maximum that can be supported is 1080p 30fps, or 1080i 60 fps or lower. 
 +
 
 +
The problem is that most desktop displays support 1080p 60fps and that gets auto negotiated over the HDMI connection. And since the board doesn't actually support that mode, there are visual artifacts on the display. 
 +
Because of that RVC have put specific display configuration settings in the BSP that set the mode to 1080p 30 fps. However, it turns out those settings work for the specific display that they have used but don't work for many other displays, e.g. the typical Dell displays that we have here. 
 +
The reason they don't work is because these displays don't actually support 30fps, they only support 60 fps. 
 +
 +
So, one solution is to use a display that supports 1080p 30fps but I am not sure how common those are. The other option is to use a display that support lower resolutions. E.g. I use a portable touch display called GeChic 1002 which has a native resolution of 1280x800 and works fine with the RZ/G2E board.
  
 
= No HDMI output for Weston =
 
= No HDMI output for Weston =
Line 48: Line 57:
 
  mode=current  
 
  mode=current  
 
Then in u-boot, change the boot args to specify the resolution you want:  
 
Then in u-boot, change the boot args to specify the resolution you want:  
  => setenv bootargs 'root=/dev/mmcblk0p2 rootwait video=HDMI-A-1:1280x720-32  
+
  => setenv bootargs 'root=/dev/mmcblk0p2 rootwait video=HDMI-A-1:1280x720-32'
  => saveenv  
+
  => saveenv
 
 
= Changing the Video Mode for Weston =
 
 
 
The display configuration for RZ/G2 is controlled by a file named 'weston.ini' located in the folder /etc/xdg/weston. Currently there is this section in it that sets some specific display timings.
 
In order to make a display work with the RZ/G2E board, the 'mode' settings need to be change to something that the display supports. In order to find those settings, run the 'cvt' command providing it the desired mode as parameters, e.g. like this - 
 
 
 
cvt 1920 1080 30 
 
 
 
This should give you the proper display timings for running your display at 1080p 30fps. After modifying the configuration and saving the file, restart the Weston desktop using this command - 
 
 
 
systemctl restart weston 
 
  
To edit the file weston.ini you can use the 'vi' editor that is in the BSP, or you can connect the board remotely using WinSCP and do it that way. Please let me know if you need any instructions regarding this.   
+
NOTE: The '''GeChic 1002''' portable touchscreen monitor (used by many Renesas people) has a native resolution of 1280x800, so you should use that instead of 720p.
 +
=> setenv bootargs 'root=/dev/mmcblk0p2 rootwait video=HDMI-A-1:1280x800-32'
 +
  => saveenv
  
= Max Monitor Resolution of 1080p@30fps =
+
= u-boot Configuration Files =
 +
The u-boot for the RZ/G2 configures the HW (peripherals and drivers) in multiple locations.
  
The RZ/G2E has two types of display outputs - LVDS and parallel (RGB888). On the RZ/G2E evaluation board the HDMI output is connected to the parallel RGB interface. That interface has a maximum pixel clock of 75MHz which is not enough to support 1080p at 60fps, the maximum that can be supported is 1080p 30fps, or 1080i 60 fps or lower. 
+
{| class="wikitable"
 
+
|-
The problem is that most desktop displays support 1080p 60fps and that gets auto negotiated over the HDMI connection. And since the board doesn't actually support that mode, there are visual artifacts on the display. 
+
|'''Board'''
Because of that RVC have put specific display configuration settings in the BSP that set the mode to 1080p 30 fps. However, it turns out those settings work for the specific display that they have used but don't work for many other displays, e.g. the typical Dell displays that we have here. 
+
|'''Device Tree '''
The reason they don't work is because these displays don't actually support 30fps, they only support 60 fps. 
+
|'''Header '''
 
+
|'''Code '''
So, one solution is to use a display that supports 1080p 30fps but I am not sure how common those are. The other option is to use a display that support lower resolutions. E.g. I use a portable touch display called GeChic 1002 which has a native resolution of 1280x800 and works fine with the RZ/G2E board.
+
|-
 +
|RZ/G2E EK874
 +
|arch/arm/dts/r8a774c0-u-boot.dtsi <br> arch/arm/dts/r8a774c0-ek874.dts <br> arch/arm/dts/r8a774c0-ek874-u-boot.dts
 +
|include/configs/ek874.h
 +
|board/renesas/ek874/ek874.c
 +
|}

Revision as of 13:46, 22 October 2020

Silicon Linux RZ/G2E evaluation kit (EK874)

Template:TOC

General Information

You can make sure you have all the supporting hardware and are able to connect and talk to the board. There is no manual for the board yet, so here is what you need:

Power supply – 12V, 2.5A or more, with a center positive plug, 4.7x1.7mm in size HDMI display, preferable with touch. If it doesn’t have touch you will need a USB mouse Drivers for the serial-to-USB converter used on the board - https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers Tera Term or other terminal emulator software - https://osdn.net/projects/ttssh2/

There is an add-on micro USB cable that you need to plug into the board (in CN1). That provides console access to the board. After you install the drivers and connect to the micro USB port from your PC, you should see a new virtual COM port being created. Launch Tera Term, create a serial connection to the new COM port, set the baud rate to 115200. Turn on the board (the On/Off switch is next to the power plug) and you should see some boot messages in Tera Term and you should get to the u-boot command line where you can type.

Turning off the board - with any of the RZ/G boards it is recommended to turn off the board using the switch before unplugging the power supply.

"Silicon Linux" vs "iWave"

The RZ/G2E eval board is design/manufactured by Silicon Linux and distributed by iWave. So it sometimes refereed to as the “iWave board” or “Silicon Linux board”. Silicon linux is small company and does not have have distribution channel. Therefore, iWave is distributing the the Silicon linux RZ/G2E board using their channel.

Max Monitor Resolution of 1080p@30fps

The RZ/G2E has two types of display outputs - LVDS and parallel (RGB888). On the RZ/G2E evaluation board the HDMI output is connected to the parallel RGB interface. That interface has a maximum pixel clock of 75MHz which is not enough to support 1080p at 60fps, the maximum that can be supported is 1080p 30fps, or 1080i 60 fps or lower.

The problem is that most desktop displays support 1080p 60fps and that gets auto negotiated over the HDMI connection. And since the board doesn't actually support that mode, there are visual artifacts on the display. Because of that RVC have put specific display configuration settings in the BSP that set the mode to 1080p 30 fps. However, it turns out those settings work for the specific display that they have used but don't work for many other displays, e.g. the typical Dell displays that we have here. The reason they don't work is because these displays don't actually support 30fps, they only support 60 fps.

So, one solution is to use a display that supports 1080p 30fps but I am not sure how common those are. The other option is to use a display that support lower resolutions. E.g. I use a portable touch display called GeChic 1002 which has a native resolution of 1280x800 and works fine with the RZ/G2E board.

No HDMI output for Weston

The display configuration for RZ/G2 is controlled by a file named 'weston.ini' located in the folder /etc/xdg/weston. Currently there is a section in it that sets some specific display timings. Please note, that board can only display a maximum of 1920x1080 @ 30Hz, so by default, the timing has been fixed to that.

When using the HDMI connector, you may have to edit the file /etc/xdg/weston/weston.ini on your target board and remove the "mode" line if not video shows up. This is always the case with the small 1280x800 monitors. You can just comment it out by putting a # sign at the beginning of the line.

[output]
name=HDMI-A-1  
#mode=79.75 1920 1976 2168 2416 1080 1083 1088 1102 -hsync +vsync

These timings force the output to be 1920x1080 30Hz. The reason we add this setting is to prevent monitor from displaying in 1920x1080 60Hz. Without this setting, the board always run in 1920x1080 60Hz (if supported by the monitor, because it will pick the highest resolution). In that case, system still work, but users will see many noise on the screen. Not all monitors support 30Hz at 1920x1080. You can use the command 'cvt 1920 1080' to see what refresh rates are supported.

Possible solutions are to change the mode line to:

mode=138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync 

or By just specifying 'mode=1920x1080' in weston.ini, which is the same as not specifying anything and letting the timings be auto negotiated.

Another option is to set mode to "current" and then set the resolution the kernel command line:

[output]  
name=HDMI-A-1  
mode=current 

Then in u-boot, change the boot args to specify the resolution you want:

=> setenv bootargs 'root=/dev/mmcblk0p2 rootwait video=HDMI-A-1:1280x720-32'
=> saveenv

NOTE: The GeChic 1002 portable touchscreen monitor (used by many Renesas people) has a native resolution of 1280x800, so you should use that instead of 720p.

=> setenv bootargs 'root=/dev/mmcblk0p2 rootwait video=HDMI-A-1:1280x800-32'
=> saveenv

u-boot Configuration Files

The u-boot for the RZ/G2 configures the HW (peripherals and drivers) in multiple locations.

Board Device Tree Header Code
RZ/G2E EK874 arch/arm/dts/r8a774c0-u-boot.dtsi
arch/arm/dts/r8a774c0-ek874.dts
arch/arm/dts/r8a774c0-ek874-u-boot.dts
include/configs/ek874.h board/renesas/ek874/ek874.c