AKA, "High Resolution Embedded GUI Solution Kit for RZ/A1H" https://www.renesas.com/en-us/products/software-tools/boards-and-kits/renesas-demonstration-kits/ylcdrza1h.html
The "High Resolution Embedded GUI Solution Kit for RZ/A1H" is intended to showcase the graphics and image capture capabilities of the RZ/A1H as well as 3rd party middleware (non-OS and RTOS) using a 1280x800 LCD. However, the board can be used to run Linux as well.
- The board itself does not have a USB-to-Serial connection. Instead, you will have to use the PMOD connector that brings out SCIF3 and supply your own adapter.
- The Digilent PmodUSBUART module seems to work pretty good because all you have to do is plug it in and you're all set. ( https://www.digikey.com/products/en?keywords=1286-1097-ND )
Build Environment Setup
Install the RZ/A1 RSK BSP
- We will us the RSK BSP build environment even though we we will be using a YLCDRZA1H board. The reason is that the u-boot and Linux repositories on github also support YLCDRZA1H.
# Clone the BSP from github $ git clone https://github.com/renesas-rz/rza_linux-4.9_bsp.git $ cd rza_linux-4.9_bsp
Select YLCDRZA1H as the Target Board
- First enter the BSP configuration screen
$ ./build.sh config
- Then change the Target Board selection (the first item in list) from RSKRZA1 to YLCDRZA1H
- Select Save (the last item in the list)
- Now all your build defaults and J-Link programming examples will be specifically for YLCDRZA1H
Install Segger Jlink Drivers for Linux
- NOTE: This board has the JLINK HW already included on the board, so all you have to do is plug a USB cable into J17.
- Install the "J-Link Software and Documentation Pack" from Segger's website
- Hint: You need to click the "Click for downloads" to actually find the download links.
- The tested build environment was Ubuntu. If using another distribution, some changes might be needed (but I'm not sure what exactly).
- Lines that start with the symbol '$' are to be copy/pasted into the Linux PC terminal (without the $)
- Lines that start wit the symbol '=>' are u-boot commands
- Lines that start wit the symbol '#' are just comments
Build the File System
- We do this first because we need Buildroot to download the toolchain that we will use to build u-boot and the kernel.
- NOTE that I suggest the 'minimum' file system option when prompted becase it makes the build much quicker.
$ ./build.sh buildroot
$ ./build.sh u-boot
Build the Kernel and Device Tree
$ ./build.sh kernel xipImage $ ./build.sh kernel dtbs