RZ-G/Boards/HiHope
HiHope RZ/G2M,N,H board
NOTE: The same PCB board is used for RZ/G2M, RZ/G2N and RZ/G2H
Device Tree Rev2 Files
HiHope Device Tree files are located in Yocto under:
build/tmp/work-shared/hihope-rzg2m/kernel-source/arch/arm64/boot/dts/renesas/
NOTE: The file names below are for RZ/G2M (r8a774a1-hihope-rzg2m.dts), but the same applies for RZ/G2N and RZ/G2H Device Tree files.
If you have a sub-board attached (with the Ethernet connector), then you should use the "-ex" versions of the Device Tree.
Starting with VLP64 v1.0.4, the default Device Tree file will be for HiHope boards HIHOPE_RZ/G2_V3 boards or later.
You can find the version of your board printed on both the main board and sub-board.
Boards V3 or later
- hihope-common.dtsi
- r8a774a1-hihope-rzg2m.dts
- r8a774a1-hihope-rzg2m-ex.dts
If you are using an older V2 board, then you will need to use the "-rev2" Device Tree Files.
Board V2 only
- hihope-common-rev2.dtsi
- r8a774a1-hihope-rzg2m-rev2.dts
- r8a774a1-hihope-rzg2m-rev2-ex.dts
Enable I2C-0 on header
Directions on adding I2C-0
You need two nodes in the device tree – one in the ‘pfc’ section to configure pin muxing, and another node at the global level to enable to interface. This is what was added under the ‘pfc’ section –
i2c0_pins: i2c0 { groups = "i2c0"; function = "i2c2"; };
And this is at the global level –
&i2c0 { pinctrl-0 = <&i2c0_pins>; pinctrl-names = "default"; status = "okay"; clock-frequency = <400000>; };
You can change the clock frequency to 100000 if you like. I haven’t found a good method for building the device tree using just Yocto commands. So, this is the method that I use –
1. Run this bitbake command -
bitbake -c devshell linux-renesas
2. This will open a new window. In the new window, run –
make dtbs exit
The generated device tree binaries are in this folder –
build/tmp/work/hihope_rzg2m-poky-linux/linux-renesas/4.19.56-cip5+gitAUTOINC+5b7dee96a2-r1/linux-hihope_rzg2m-standard-build/arch/arm64/boot/dts/renesas
Note that this is in a different folder tree (build/tmp/work) from the device tree source files (buid/tmp/work-shared). Also, the filenames are a little different, e.g. ‘r8a774a1-hihope-rzg2m-ex.dtb’. So, you need to rename that to ‘Image-r8a774a1-hihope-rzg2m-ex.dtb’ before transferring it to the board.
"No Boot" Message
When you get the message:
No Boot 0x00000010 0x60018118 0x00000008
If the prohibition setting is made in the Boot Mode setting, it will be in No Boot state.
On the HiHope-RZG2M board, the same error occurs when the following DIP SW settings are made.
0x60018118 indicates the value of MODEMR.
MD8 MD7 MD6 MD5 MD4 MD3 MD2 MD1 MD0 1 0 0 0 1 1 0 0 0
Since MD5=0 is prohibited, it must be changed to MD5=1.
For eMMC Boot operation, it is necessary to change to MD1=1.