On the HiHope-RZG2M board, the same error occurs when the following DIP SW settings are made.Ġ圆0018118 indicates the value of MODEMR. If the prohibition setting is made in the Boot Mode setting, it will be in No Boot state. If you have i2c-tools installed, you can use i2cdetect to confirm your device is accessible. Then you should see the device /dev/i2c-0ĥ. Now to repackage and copy the files into the 'deploy' directory, run this bitbake command:Ĥ. You can change the clock-frequency to 400000 if you like.Ģ. You need to add 2 new nodes in the Device Tree: One in the ‘pfc’ section to configure pin muxing, and another node at the global level to enable to I2C peripheral interface.īuild/tmp/work-shared/hihope-rzg2m/kernel-source/arch/arm64/boot/dts/renesas/r8a774a1-hihope-rzg2m-ex.dtsĪnd at the end of the file, add the following: If you are using an older V2 board, then you will need to use the "-rev2" Device Tree Files. You can find the version of your board printed on both the main board and sub-board. Starting with VLP64 v1.0.4, the default Device Tree file will be for HiHope boards HIHOPE_RZ/G2_V3 boards or later. If you have a sub-board attached (with the Ethernet connector), then you should use the "-ex" versions of the Device Tree. 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. HiHope Device Tree files are located in Yocto under:īuild/tmp/work-shared/hihope-rzg2m/kernel-source/arch/arm64/boot/dts/renesas/ NOTE: The same PCB board is used for RZ/G2M, RZ/G2N and RZ/G2H
0 kommentar(er)
