RZ/G2 BSP Information Page

From Renesas.info
Jump to navigation Jump to search

← RZ-G

Downloads

VLP64 v1.0.8 VLP64 v1.0.9-RT VLP64 v1.0.10
πŸ“¦ RZ/G2 Linux Package (Complete Download)
ZIP file containing Yocto BSP and all documentation
  • Yocto Recipe
    This is the actual BSP provided in a Yocto build package
  • Release Note for Linux Package
    Build instructions, start with this document
  • Reference Boards Linux Start-up Guide
    How to program the boot loaders into SPI flash
  • Release Note for HTML5 Linux Package
    Building the HTML5 browser using the BSP requires a different set of instructions
  • BSP Component list
    List of each package and version included in the default BSP build
πŸ’Ύ (link) πŸ’Ύ (link) πŸ’Ύ (link)
πŸ“¦ RZ/G2 Group BSP Manual Set
Detailed information about Device Drivers and Device Tree Settings
πŸ“„ (link) πŸ“„ (link) πŸ“„ (link)


BSP v1.3
πŸ“¦ RZ/G2L Linux Package
● Yocto BSP
● Release Note
  β—‹ Build instructions, start with this document
● RZ/G2L Reference Board Start-up Guide
  β—‹ How to program the boot loaders into SPI flash
● BSP Component list
  β—‹ List of each package and version included in the default BSP build
πŸ’Ύ (link)
πŸ“¦ RZ/G2L Mali Graphic Library (Evaluation Version)(Recommended)
● Files to be added to the Yocto BSP to enable Graphics
● Full function but 3-hour timeout limited. Download immediately.
v0.8
πŸ’Ύ (link)
πŸ“¦ RZ/G2L Mali Graphic Library (Unrestricted Version)
● Files to be added to the Yocto BSP to enable Graphics
● Due to license processing, requires 1 to 2 weeks before download.
v0.8
πŸ’Ύ (link)
πŸ“¦ RZ/G2L Video Codec Library
● Files to be added to the Yocto BSP to enable H.264 Video Encode/Decode
v0.53
πŸ’Ύ (link)
πŸ“¦ RZ/G2L Group BSP Manual Set
● Detailed information about Device Drivers and Device Tree Settings
πŸ“„ (link)
πŸ“¦ RZ/G2L Multi-OS Package (CM33)
● FreeRTOS for CM33 and OpenAMP comms between A55 and CM33
πŸ’Ύ (link)

This page discusses topics specific to the content and code released in the BSP. Information on using the BSP is found on other pages such as RZ-G/RZG_yocto.

BSP Differences Between renesas.com Download and Github Version

Below are the differences between BSP you download from renesas.com and what is available on public repositories.

Public Repository Clones

  • meta-gplv2/
  • meta-linaro/
  • meta-openembedded/
  • meta-qt5/
  • meta-rzg2/
  • meta-virtualization/
  • poky/

These directories are direct clones (no modifications) from public repositories. The repository URLs and commit IDs that were used are documented in the README.md file in the meta-rzg2 directory in the BSP.


Example Layers

  • meta-hmi-custom/
  • meta-userboard/

These directories do not have any functionally. They are simple example templates you can use to make your own customer layers. They are only included in the renesas.com package.


The RZ/G2 BSP

  • meta-rzg2/

Basically, all the customizations and patches are located in the directory 'meta-rzg2'.
This directory is a clone of the public repository is located here: https://github.com/renesas-rz/meta-rzg2.
There are git tags for BSP version that was release.
The only difference is that in the renesas.com version, the following lines were added to the local.conf files under docs/sample/conf

DL_DIR = "${TOPDIR}/oss_packages"
BB_NO_NETWORK = "0"

Additionally, other configuration files such as bblayers_gecko.conf and local_gecko.con are added to the renesas.com download that are not in the github version.


Non-public Patches

  • extra/

This directory is only in the package downloaded from renesas.com
It contains patches that are not included in the public the meta-rzg2 repository on github. For example, the patches to enable HDMI on the boards were not posted to github because of potential license issues.


Video and Multi-media Drivers

  • proprietary/

This directory is only in the package downloaded from renesas.com
This directory contains .zip files which are essentially the propriety closed source video and multimedia drivers. They used to be downloaded separately, but are now included when downloaded the BSP from renesas.com. When following the instructions in the "Renesas Note" that comes with the BSP, users will run the script copy_proprietary_softwares.sh which will unpack these zip files into various directories under meta-rzg2.

SPI Flash Driver for BSP 1.0.6

SPI flash write from Linux is not officially supported in V1.0.6 BSP. If you want SPI write enabled for BSP 1.0.6. Please follow the below steps:

1. Add kernel patches to BSP

1.a) Please get required patch files from https://github.com/seebe/rzg_stuff/tree/master/build_scripts/vlp64_patches/BSP-1.0.6-SPI-write/kernel

$ rzg2_bsp_eva_v106/recipes-kernel/linux/linux-renesas/patches
$ mkdir v1.0.6_spi_patch
$ cd v1.0.6_spi_patch #copy patch files here

1.b) Update patches.scc file:

Yocto uses .scc file to apply patches located in ~/rzg2_bsp_eva_v106/meta-rzg2/recipes-kernel/linux/linux-renesas/patches.scc. Get updated .scc file from https://github.com/seebe/rzg_stuff/tree/master/build_scripts/vlp64_patches/BSP-1.0.6-SPI-write/

$ cd ~/rzg2_bsp_eva_v106/meta-rzg2/recipes-kernel/linux/linux-renesas/
$ wget https://raw.githubusercontent.com/seebe/rzg_stuff/master/build_scripts/vlp64_patches/BSP-1.0.6-SPI-write/patches.scc

2. Configuring kernel using menuconfig

Configure the kernel to enable Renesas SPI driver and SPI memory. The following commands initialize the BitBake environment, run the do_kernel_configme task, and launch menuconfig. These commands assume the Source Directory's top-level folder is ~/rzg2_bsp_eva_v106:

$ cd rzg2_bsp_eva_v106
$ source poky/oe-init-build-env
$ bitbake linux-renesas -c kernel_configme -f
$ bitbake linux-renesas -c menuconfig

Once menuconfig comes up, configure below kernel configuration parameters.

2.a)Enable Renesa RPC-IF driver:

.config - Linux/arm64 4.19.140 Kernel Configuration
 > Device Drivers > Memory Controller drivers

2.b)Enable SPI memory (M25P80 ):

.config - Linux/arm64 4.19.140 Kernel Configuration
 > Device Drivers > Memory Technology Device (MTD) support > Self-contained MTD device drivers 

After making your changes, simply exit the tool and save your changes to create an updated version of the .config configuration file

3. Build the image using updated BSP