Difference between revisions of "R-Car/Boards/V3HSK"
(→For Yocto v3.9.0 and later:) |
|||
(25 intermediate revisions by the same user not shown) | |||
Line 10: | Line 10: | ||
===Board Layout=== | ===Board Layout=== | ||
− | + | ||
+ | [[File:V3h_board_markings_top.png|801px]] | ||
+ | <br> <br> | ||
+ | [[File:V3h_board_markings_bot.png|801px]] | ||
=== Hardware Features === | === Hardware Features === | ||
Line 19: | Line 22: | ||
== V3H Starter Kit Board Documentation == | == V3H Starter Kit Board Documentation == | ||
− | + | [https://www.renesas.com/en-eu/doc/products/rcar/R20UT4302ED0100.pdf Official Renesas documentation] | |
== Quick Start == | == Quick Start == | ||
+ | This board is supported in both Yocto v2.23.1, v3.9.0 and later. | ||
+ | Yocto v3.21.0 is preferred option. | ||
+ | |||
=== Build BSP images === | === Build BSP images === | ||
Please follow these instruction to build BSP http://elinux.org/R-Car/Boards/Yocto-Gen3-ADAS#Building_the_BSP_for_Renesas_ADAS_boards: | Please follow these instruction to build BSP http://elinux.org/R-Car/Boards/Yocto-Gen3-ADAS#Building_the_BSP_for_Renesas_ADAS_boards: | ||
Skip steps 5 and 6 (These steps are for GPU and multimedia libraries-only)<br/> | Skip steps 5 and 6 (These steps are for GPU and multimedia libraries-only)<br/> | ||
− | Replace step 8 with the following: | + | Replace step 8 with the following: <br/> |
+ | For Yocto v2.23.1: | ||
<pre> | <pre> | ||
cp $WORK/meta-rcar/meta-rcar-gen3-adas/docs/sample/conf/v3hsk/linaro-gcc/bsp/*.conf ./conf/ | cp $WORK/meta-rcar/meta-rcar-gen3-adas/docs/sample/conf/v3hsk/linaro-gcc/bsp/*.conf ./conf/ | ||
+ | </pre> | ||
+ | For Yocto v3.9.0 and later: | ||
+ | <pre> | ||
+ | cp $WORK/meta-rcar/meta-rcar-gen3-adas/docs/sample/conf/v3hsk/poky-gcc/bsp/*.conf ./conf/ | ||
</pre> | </pre> | ||
Skip steps 9,10 and 11 (specific for multimedia packages only)<br/> | Skip steps 9,10 and 11 (specific for multimedia packages only)<br/> | ||
Line 35: | Line 46: | ||
bitbake core-image-minimal | bitbake core-image-minimal | ||
</pre> | </pre> | ||
− | + | ||
+ | At step 16 use images depending on board: | ||
+ | <ol> | ||
+ | ===== For Yocto v2.23.1: ===== | ||
+ | for V3H Starter Kit board: | ||
<pre> | <pre> | ||
Image-r8a7798-v3hsk.dtb | Image-r8a7798-v3hsk.dtb | ||
</pre> | </pre> | ||
− | + | for V3H Starter Kit expansion board VideoBox Mini: | |
− | NOTE: you can refer to http://elinux.org/R-Car/Boards/Yocto-Gen3-ADAS#Build_scripts_examples section and use scripts after adding replacement accordingly to steps | + | <pre> |
+ | Image-r8a7798-v3hsk-vbm.dtb | ||
+ | Image-r8a7798-v3hsk-vbm-v2.dtb | ||
+ | </pre> | ||
+ | for ULCB expansion board Kingfisher: | ||
+ | <pre> | ||
+ | Image-r8a7798-v3hsk-kf.dtb | ||
+ | </pre> | ||
+ | ===== For Yocto v3.9.0 and later: ===== | ||
+ | for V3H Starter Kit board: | ||
+ | <pre> | ||
+ | Image-r8a77980-v3hsk.dtb | ||
+ | </pre> | ||
+ | for V3H Starter Kit expansion board VideoBox Mini: | ||
+ | <pre> | ||
+ | Image-r8a77980-v3hsk-vbm.dtb | ||
+ | Image-r8a77980-v3hsk-vbm-v2.dtb | ||
+ | Image-r8a77980-es2-v3hsk-vbm.dtb | ||
+ | Image-r8a77980-es2-v3hsk-vbm-v2.dtb | ||
+ | </pre> | ||
+ | for ULCB expansion board Kingfisher: | ||
+ | <pre> | ||
+ | Image-r8a77980-v3hsk-kf.dtb | ||
+ | </pre> | ||
+ | </ol> | ||
+ | NOTE: prefix -es2- is a blob to be used with ws2.0 silicon. The blob without prefix is for ws1.0 and ws1.1 silicon. | ||
+ | NOTE: you can refer to http://elinux.org/R-Car/Boards/Yocto-Gen3-ADAS#Build_scripts_examples section and use scripts after adding replacement accordingly to steps 9,14 | ||
=== Build SDK === | === Build SDK === | ||
Line 46: | Line 87: | ||
== Flashing firmware == | == Flashing firmware == | ||
+ | The firmware files are generated during BSP build procedure and are located in the deploy directory. <br/> | ||
+ | You can verify its content: | ||
+ | <pre class="bash"> | ||
+ | $ ls -1 ./tmp/deploy/images/v3hsk/*.srec | ||
+ | ./tmp/deploy/images/v3hsk/bl2-v3hsk.srec | ||
+ | ./tmp/deploy/images/v3hsk/bl31-v3hsk.srec | ||
+ | ./tmp/deploy/images/v3hsk/bootparam_sa0.srec | ||
+ | ./tmp/deploy/images/v3hsk/cr7-v3hsk.srec | ||
+ | ./tmp/deploy/images/v3hsk/cert_header_sa3.srec | ||
+ | ./tmp/deploy/images/v3hsk/cert_header_sa6.srec | ||
+ | ./tmp/deploy/images/v3hsk/u-boot-elf-v3hsk.srec | ||
+ | </pre> | ||
+ | |||
{| class="wikitable" | {| class="wikitable" | ||
− | |+ Writing data (Yocto v2.23.1) | + | |+ Writing data (Yocto v2.23.1 and later) |
|- | |- | ||
! Filename !! Program Top Address !! Flash Save Address !! Description | ! Filename !! Program Top Address !! Flash Save Address !! Description | ||
Line 71: | Line 125: | ||
</li> | </li> | ||
<pre> | <pre> | ||
− | Use | + | Use SW1 |
</pre> | </pre> | ||
<li> Set SW as follows: | <li> Set SW as follows: | ||
</li> | </li> | ||
<pre> | <pre> | ||
− | + | SW4[1]=OFF, SW4[2]=OFF, SW4[3]=OFF, SW4[4]=OFF, SW4[5]=OFF, SW4[6]=OFF, SW4[7]=OFF, SW4[8]=OFF | |
− | |||
− | |||
</pre> | </pre> | ||
<li> Power on the board | <li> Power on the board | ||
</li> | </li> | ||
<pre> | <pre> | ||
− | Use | + | Use SW1 |
Boot ROM start and provides input | Boot ROM start and provides input | ||
</pre> | </pre> | ||
</li> | </li> | ||
− | <li> Load [[File:AArch32_Gen3_H3_M3_V3H_Scif_MiniMon_develop_V3H_V0.05.mot.zip]]. In console provide the following inputs: | + | <li> Load [[File:AArch32_Gen3_H3_M3_V3H_Scif_MiniMon_develop_V3H_V0.05.mot.zip]] ('''[[File:AArch32_Gen3_V3H_Scif_MiniMon_V5.04C.MOT.zip]] for V3H 1.1'''). In console provide the following inputs: |
</li> | </li> | ||
<pre> | <pre> | ||
Line 98: | Line 150: | ||
</li> | </li> | ||
<pre> | <pre> | ||
− | + | SW4[1]=ON, SW4[2]=ON, SW4[3]=OFF, SW4[4]=ON, SW4[5]=OFF, SW4[6]=OFF, SW4[7]=OFF, SW4[8]=OFF | |
</pre> | </pre> | ||
Line 120: | Line 172: | ||
</pre> | </pre> | ||
− | <li> Flash cr7-v3hsk.srec. In console execute xls2 command (load program to qspi flash) and provide the following inputs: | + | <li> Flash cr7-v3hsk.srec ('''For v2.23.1 only: Please use [[File:cr7-v3h-1.1.srec.zip]] for V3H 1.1 instead of one available in the build'''). In console execute xls2 command (load program to qspi flash) and provide the following inputs: |
</li> | </li> | ||
<pre> | <pre> | ||
Line 189: | Line 241: | ||
</li> | </li> | ||
<pre> | <pre> | ||
− | Press | + | Press SW3 |
</pre> | </pre> | ||
Line 198: | Line 250: | ||
Please follow these instruction to boot from network http://elinux.org/R-Car/Boards/Yocto-Gen3-ADAS#Loading_kernel_via_TFTP_and_rootfs_via_NFS <br/> | Please follow these instruction to boot from network http://elinux.org/R-Car/Boards/Yocto-Gen3-ADAS#Loading_kernel_via_TFTP_and_rootfs_via_NFS <br/> | ||
− | For V3H Starter Kit board you must use the following dtb file: | + | For V3H Starter Kit board you must use the following dtb file: <br/> |
+ | For Yocto v2.23.1: | ||
<pre> | <pre> | ||
Image-r8a7798-v3hsk.dtb | Image-r8a7798-v3hsk.dtb | ||
+ | Image-r8a7798-v3hsk-vbm.dtb | ||
+ | Image-r8a7798-v3hsk-vbm-v2.dtb | ||
+ | Image-r8a7798-v3hsk-kf.dtb | ||
+ | </pre> | ||
+ | For Yocto v3.9.0 and later: | ||
+ | <pre> | ||
+ | Image-r8a77980-v3hsk.dtb | ||
+ | Image-r8a77980-v3hsk-vbm.dtb | ||
+ | Image-r8a77980-v3hsk-vbm-v2.dtb | ||
+ | Image-r8a77980-v3hsk-kf.dtb | ||
</pre> | </pre> | ||
== ADAS test applications == | == ADAS test applications == | ||
TBD | TBD | ||
+ | |||
+ | == Installing V3H Starter Kit Expansion Board == | ||
+ | Use the following procedure to install Expansion Board to the V3HSK Board: | ||
+ | https://elinux.org/R-Car/Boards/V3MSK#Installing_V3M_Starter_Kit_Expansion_Board <br/> <br/> | ||
+ | |||
+ | Update VI and DU power domains to 3.3V using CPLD Configuration tool. <br/> | ||
+ | Please contact Renesas to obtain this tool. |
Revision as of 15:59, 23 October 2020
Introduction
This is the official Wiki for V3H Starter Kit Board. Refer to the R-Car page for information about Renesas' R-Car SoC family.
Hardware
This section contains information about Starter Kit Board hardware.
Board Layout
Hardware Features
TBD
Where to buy
Contact Renesas representatives
V3H Starter Kit Board Documentation
Official Renesas documentation
Quick Start
This board is supported in both Yocto v2.23.1, v3.9.0 and later. Yocto v3.21.0 is preferred option.
Build BSP images
Please follow these instruction to build BSP http://elinux.org/R-Car/Boards/Yocto-Gen3-ADAS#Building_the_BSP_for_Renesas_ADAS_boards:
Skip steps 5 and 6 (These steps are for GPU and multimedia libraries-only)
Replace step 8 with the following:
For Yocto v2.23.1:
cp $WORK/meta-rcar/meta-rcar-gen3-adas/docs/sample/conf/v3hsk/linaro-gcc/bsp/*.conf ./conf/
For Yocto v3.9.0 and later:
cp $WORK/meta-rcar/meta-rcar-gen3-adas/docs/sample/conf/v3hsk/poky-gcc/bsp/*.conf ./conf/
Skip steps 9,10 and 11 (specific for multimedia packages only)
As step 13 use (weston window manager is not supported for V3M/V3H):
bitbake core-image-minimal
At step 16 use images depending on board:
For Yocto v2.23.1:
for V3H Starter Kit board:
Image-r8a7798-v3hsk.dtb
for V3H Starter Kit expansion board VideoBox Mini:
Image-r8a7798-v3hsk-vbm.dtb Image-r8a7798-v3hsk-vbm-v2.dtb
for ULCB expansion board Kingfisher:
Image-r8a7798-v3hsk-kf.dtb
For Yocto v3.9.0 and later:
for V3H Starter Kit board:
Image-r8a77980-v3hsk.dtb
for V3H Starter Kit expansion board VideoBox Mini:
Image-r8a77980-v3hsk-vbm.dtb Image-r8a77980-v3hsk-vbm-v2.dtb Image-r8a77980-es2-v3hsk-vbm.dtb Image-r8a77980-es2-v3hsk-vbm-v2.dtb
for ULCB expansion board Kingfisher:
Image-r8a77980-v3hsk-kf.dtb
NOTE: prefix -es2- is a blob to be used with ws2.0 silicon. The blob without prefix is for ws1.0 and ws1.1 silicon. NOTE: you can refer to http://elinux.org/R-Car/Boards/Yocto-Gen3-ADAS#Build_scripts_examples section and use scripts after adding replacement accordingly to steps 9,14
Build SDK
Please follow these instruction to build SDK http://elinux.org/R-Car/Boards/Yocto-Gen3-ADAS#Build_SDK
Flashing firmware
The firmware files are generated during BSP build procedure and are located in the deploy directory.
You can verify its content:
$ ls -1 ./tmp/deploy/images/v3hsk/*.srec ./tmp/deploy/images/v3hsk/bl2-v3hsk.srec ./tmp/deploy/images/v3hsk/bl31-v3hsk.srec ./tmp/deploy/images/v3hsk/bootparam_sa0.srec ./tmp/deploy/images/v3hsk/cr7-v3hsk.srec ./tmp/deploy/images/v3hsk/cert_header_sa3.srec ./tmp/deploy/images/v3hsk/cert_header_sa6.srec ./tmp/deploy/images/v3hsk/u-boot-elf-v3hsk.srec
Filename | Program Top Address | Flash Save Address | Description |
---|---|---|---|
bootparam_sa0.srec | 0xEB220000 | 0x000000 | Loader(Boot parameter) |
cr7-v3hsk.srec | 0xEB204000 | 0x040000 | CR7 Loader |
cert_header_sa3.srec | 0xEB220000 | 0x0C0000 | Loader(Certification) |
bl2-v3hsk.srec | 0xEB244000 | 0x140000 | CA53 Loader |
cert_header_sa6.srec | 0xEB220000 | 0x180000 | Loader(Certification) |
bl31-v3hsk.srec | 0x44000000 | 0x1C0000 | ARM Trusted Firmware |
u-boot-elf-v3hsk.srec | 0x50000000 | 0x640000 | U-Boot |
- Power off the board
- Set SW as follows:
- Power on the board
- Load File:AArch32 Gen3 H3 M3 V3H Scif MiniMon develop V3H V0.05.mot.zip (File:AArch32 Gen3 V3H Scif MiniMon V5.04C.MOT.zip for V3H 1.1). In console provide the following inputs:
- Change SW as follows:
- Erase flash. In console execute xcs command and provide the following inputs:
- Flash bootparam_sa0.srec. In console execute xls2 command (load program to qspi flash) and provide the following inputs:
- Flash cr7-v3hsk.srec (For v2.23.1 only: Please use File:Cr7-v3h-1.1.srec.zip for V3H 1.1 instead of one available in the build). In console execute xls2 command (load program to qspi flash) and provide the following inputs:
- Flash cert_header_sa3.srec. In console execute xls2 command (load program to qspi flash) and provide the following inputs:
- Flash bl2-v3hsk.srec. In console execute xls2 command (load program to qspi flash) and provide the following inputs:
- Flash cert_header_sa6.srec. In console execute xls2 command (load program to qspi flash) and provide the following inputs:
- Flash bl31-v3hsk.srec. In console execute xls2 command (load program to qspi flash) and provide the following inputs:
- Flash u-boot-elf-v3hsk.srec. In console execute xls2 command (load program to qspi flash) and provide the following inputs:
- Reset the board
Use SW1
SW4[1]=OFF, SW4[2]=OFF, SW4[3]=OFF, SW4[4]=OFF, SW4[5]=OFF, SW4[6]=OFF, SW4[7]=OFF, SW4[8]=OFF
Use SW1 Boot ROM start and provides input
type "ctrl+A S" and select upload method "ascii", then choose file for uploading "AArch32_Gen3_H3_M3_V3H_Scif_MiniMon_develop_V3H_V0.05.mot", after upload finished press any key. Minimonitor starts and provides prompts on console
SW4[1]=ON, SW4[2]=ON, SW4[3]=OFF, SW4[4]=ON, SW4[5]=OFF, SW4[6]=OFF, SW4[7]=OFF, SW4[8]=OFF
3 y y
3 y eb220000 0 type "ctrl+A S" and select upload method "ascii", then choose file for uploading "bootparam_sa0.srec", after upload finished press any key y
3 y eb204000 40000 type "ctrl+A S" and select upload method "ascii", then choose file for uploading "cr7-v3hsk.srec", after upload finished press any key y
3 y eb220000 c0000 type "ctrl+A S" and select upload method "ascii", then choose file for uploading "cert_header_sa3.srec", after upload finished press any key y
3 y eb244000 140000 type "ctrl+A S" and select upload method "ascii", then choose file for uploading "bl2-v3hsk.srec", after upload finished press any key y
3 y eb220000 180000 type "ctrl+A S" and select upload method "ascii", then choose file for uploading "cert_header_sa6.srec", after upload finished press any key y
3 y 44000000 1C0000 type "ctrl+A S" and select upload method "ascii", then choose file for uploading "bl31-v3hsk.srec", after upload finished press any key y
3 y 50000000 640000 type "ctrl+A S" and select upload method "ascii", then choose file for uploading "u-boot-elf-v3hsk.srec", after upload finished press any key y
Press SW3
U-Boot Environment
Please follow these instruction to boot from network http://elinux.org/R-Car/Boards/Yocto-Gen3-ADAS#Loading_kernel_via_TFTP_and_rootfs_via_NFS
For V3H Starter Kit board you must use the following dtb file:
For Yocto v2.23.1:
Image-r8a7798-v3hsk.dtb Image-r8a7798-v3hsk-vbm.dtb Image-r8a7798-v3hsk-vbm-v2.dtb Image-r8a7798-v3hsk-kf.dtb
For Yocto v3.9.0 and later:
Image-r8a77980-v3hsk.dtb Image-r8a77980-v3hsk-vbm.dtb Image-r8a77980-v3hsk-vbm-v2.dtb Image-r8a77980-v3hsk-kf.dtb
ADAS test applications
TBD
Installing V3H Starter Kit Expansion Board
Use the following procedure to install Expansion Board to the V3HSK Board:
https://elinux.org/R-Car/Boards/V3MSK#Installing_V3M_Starter_Kit_Expansion_Board
Update VI and DU power domains to 3.3V using CPLD Configuration tool.
Please contact Renesas to obtain this tool.