2 title: Building for Supported Renesas Boards
5 AGL supports building for several automotive
6 [Renesas](https://www.renesas.com/us/en/solutions/automotive.html) board kits.
7 Renesas is the number one supplier of vehicle control microcontrollers and
8 System on a Chip (SoC) products for the automotive industry.
10 This section provides the build and deploy steps you need to create an
11 image for the following Renesas platforms:
13 * [Renesas R-Car Starter Kit Pro Board](https://www.elinux.org/R-Car/Boards/M3SK)
14 * [Renesas R-Car Starter Kit Premier Board](https://www.elinux.org/R-Car/Boards/H3SK)
15 * [Renesas Salvator-X Board](https://www.elinux.org/R-Car/Boards/Salvator-X)
16 * [Renesas Kingfisher Infotainment Board](https://elinux.org/R-Car/Boards/Kingfisher)
18 **NOTE:** You can find similar information for the Pro and Premier board kits on the
19 [R-Car/Boards/Yocto-Gen3](https://elinux.org/R-Car/Boards/Yocto-Gen3) page on [elinux.org](https://elinux.org).
20 The information on this page describes setup and build procedures for both of these
21 Renesas development kits.
23 Additionally, the AGL Reference Hardware platform is based on the same Renesas
24 H3 processor used on the Renesas R-Car Starter Kit Premier and Salvator-X boards,
25 so support for it leverages the Starter Kit Premier (also known as "h3ulcb")
27 For more information on the AGL reference hardware platform, please refer to its
28 [manual](https://wiki.automotivelinux.org/_media/eg-rhsa/rh_manual_ver.1.0.pdf),
29 or the Reference Hardware System Architecture Expert Group
30 [wiki page](https://wiki.automotivelinux.org/eg-rhsa).
32 ## 1. Prepare your build
34 ### 1.1 Downloading Proprietary Drivers
36 Before setting up the build environment, you need to download proprietary drivers from the
37 [R-Car H3/M3 Software library and Technical document](https://www.renesas.com/us/en/application/automotive/r-car-h3-m3-documents-software)
40 Follow these steps to download the drivers you need:
42 1. **Determine the Files You Need:**
44 Run the ``setup_mm_packages.sh`` script as follows to
45 display the list of ZIP files containing the drivers you need.
46 Following is an example:
49 grep -rn ZIP_.= $AGL_TOP/meta-agl/meta-agl-bsp/meta-rcar-gen3/scripts/setup_mm_packages.sh
52 The script's output identifies the files you need to download from the page.
54 2. **Get Your Board Support Package (BSP) Version:**
56 Be sure to have the correct BSP version of the R-Car Starter Kit
57 based on the version of the AGL software you are using.
58 Find the appropriate download links on the
59 [R-Car H3/M3 Software library and Technical document](https://www.renesas.com/us/en/application/automotive/r-car-h3-m3-documents-software)
61 The file pairs are grouped according to the Yocto Project version you are
62 using with the AGL software.
64 Use the following table to map the Renesas version to your AGL software:
66 | AGL Version | Renesas version |
68 | AGL master | 4.7.0 |
70 3. **Download the Files:**
72 Start the download process by clicking the download link.
73 If you do not have an account with Renesas, you will be asked to register a free account.
74 You must register and follow the "Click Through" licensing process
75 in order to download these proprietary files.
77 If needed, follow the instructions to create the free account by providing the required
79 Once the account is registered and you are logged in, you can download the files.
81 **NOTE:** You might have to re-access the
82 [original page](https://www.renesas.com/us/en/application/automotive/r-car-h3-m3-documents-software)
83 that contains the download links you need after creating the account and logging in.
85 4. **Create an Environment Variable to Point to Your Download Area:**
87 Create and export an environment variable named `XDG_DOWNLOAD_DIR` that points to
88 your download directory.
92 export XDG_DOWNLOAD_DIR=$HOME/Downloads
95 5. **Be Sure the Files Have Rights:**
97 Be sure you have the necessary rights for the files you downloaded.
98 You can use the following command:
101 chmod a+rw $XDG_DOWNLOAD_DIR/*.zip
104 6. **Check to be Sure the Files are Downloaded and Have the Correct Rights:**
106 Do a quick listing of the files to ensure they are in the download directory and
107 they have the correct access rights.
111 $ ls -l $XDG_DOWNLOAD_DIR/*.zip
112 -rw-rw-r-- 1 scottrif scottrif 4662080 Nov 19 14:48 /home/scottrif/Downloads/R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-weston8-20200923.zip
113 -rw-rw-r-- 1 scottrif scottrif 3137626 Nov 19 14:49 /home/scottrif/Downloads/R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-weston8-20200923.zip
116 ### 1.2. Getting More Software
118 1. **Get the `bmaptool`:**
120 Download this tool from the
121 [bmap-tools](https://build.opensuse.org/package/show/isv:LinuxAutomotive:AGL_Master/bmap-tools)
123 The site has pre-built packages (DEB or RPM) for the supported host
126 ### 1.3. Getting Your Hardware Together
128 Gather together this list of hardware items, which is not exhaustive.
129 Having these items ahead of time saves you from having to try and
130 collect hardware during development:
132 * Supported Starter Kit Gen3 board with its 5V power supply.
133 * Micro USB-A cable for serial console.
134 This cable is optional if you are using Ethernet and an SSH connection.
135 * USB 2.0 Hub. The hub is optional but makes it easy to connect multiple USB devices.
136 * Ethernet cable. The cable is optional if you are using a serial console.
137 * HDMI type D (Micro connector) cable and an associated display.
138 * 4 Gbyte minimum MicroSD Card. It is recommended that you use a class 10 type.
139 * USB touch screen device such as the GeChic 1502i/1503i. A touch screen device is optional.
141 **NOTE:** The Salvator-X Board has NDA restrictions.
142 Consequently, less documentation is available for this board both here and across the
145 ### 1.4. Making Sure Your Build Environment is Correct
148 "[Initializing Your Build Environment](./3_Initializing_Your_Build_Environment.md)"
149 section presented generic information for setting up your build environment
150 using the `aglsetup.sh` script.
151 If you are building an image for a supported Renesas board,
152 you need to take steps to make sure your build host is set up correctly.
154 1. **Define Your Board:**
156 Depending on your Renesas board, define and export a `MACHINE` variable as follows:
158 | Board | `MACHINE` Setting |
160 | Starter Kit Pro/M3 | `MACHINE`=m3ulcb |
161 | Starter Kit Pro/M3 + kingfisher support | `MACHINE`=m3ulcb-kf |
162 | Starter Kit Pro/M3 without graphic driver (using pixman) | `MACHINE`=m3ulcb-nogfx |
163 | Starter Kit Premier/H3 | `MACHINE`=h3ulcb |
164 | Starter Kit Premier/H3 + kingfisher support | `MACHINE`=h3ulcb-kf |
165 | Starter Kit Premier/H3 without graphic driver (using pixman) | `MACHINE`=h3ulcb-nogfx |
166 | Salvator-X | `MACHINE`=h3-salvator-x |
167 | AGL Reference Hardware | `MACHINE`=h3ulcb |
168 | AGL Reference Hardware without graphic driver (using pixman) | `MACHINE`=h3ulcb-nogfx |
170 For example, the following command defines and exports the `MACHINE` variable
171 for the Starter Kit Premier/H3 Board:
174 export MACHINE=h3ulcb
177 ### 1.5. **Run the `aglsetup.sh` Script:**
179 Use the following commands to run the AGL Setup script:
183 source meta-agl/scripts/aglsetup.sh -m $MACHINE -b build agl-devel agl-demo
187 To avoid useless download and rebuild, it's important to set the variable DL_DIR and SSTATE_DIR in your configuration.
190 echo '# reuse download directories' >> $AGL_TOP/site.conf
191 echo 'DL_DIR = "$HOME/downloads/"' >> $AGL_TOP/site.conf
192 echo 'SSTATE_DIR = "$AGL_TOP/sstate-cache/"' >> $AGL_TOP/site.conf
193 ln -sf $AGL_TOP/site.conf conf/
196 **Reference Hardware :**
198 If building for the AGL Reference Hardware (with `MACHINE` set to "h3ulcb" or
199 "h3ulcb-nogfx"), add `agl-refhw-h3`, for example:
203 source meta-agl/scripts/aglsetup.sh -m $MACHINE -b build agl-devel agl-demo agl-refhw-h3
206 **HTML5 based IVI demo :**
208 For HTML5 based IVI demo the feature "agl-profile-graphical-html5" is needed.
211 $ source meta-agl/scripts/aglsetup.sh -f -m $MACHINE -b $MACHINE agl-demo agl-devel agl-profile-graphical-html5
214 **Instrument Cluster with Container isolation demo :**
217 $ source meta-agl/scripts/aglsetup.sh -f -m $MACHINE -b $MACHINE agl-lxc
221 You can check if your logs match what is expected in the [troubleshooting section](#4-troubleshooting).
223 Running the `aglsetup.sh` script automatically places you in the
224 working directory (i.e. `$AGL_TOP/build`).
225 You can change this default behavior by adding the "-f" option to the
226 script's command line.
228 In the previous command, the "-m" option sets your machine to the previously
229 defined `MACHINE` variable.
230 The "-b" option defines your Build Directory, which is the
231 default `$AGL_TOP/build`.
232 Finally, the AGL features are provided to support building the AGL Demo image
233 for the Renesas board.
235 You can learn more about the AGL Features in the
236 "[Initializing Your Build Environment](./3_Initializing_Your_Build_Environment.md)"
241 This section shows the `bitbake` command used to build the AGL image.
242 Before running BitBake to start your build, it is good to be reminded that AGL
243 does provide pre-built images for developers that work with supported hardware.
244 You can find these pre-built images on the
245 [AGL Download web site](https://download.automotivelinux.org/AGL/release).
247 Start the build using the `bitbake` command.
249 **NOTE:** An initial build can take many hours depending on your
250 CPU and and Internet connection speeds.
251 The build also takes approximately 100G-bytes of free disk space.
253 For this example, the target is "agl-demo-platform":
256 bitbake agl-demo-platform
259 The build process puts the resulting image in the Build Directory:
262 <build_directory>/tmp/deploy/images/$MACHINE
265 ## 3. Deploying the AGL Demo Image
267 To boot your image on the Renesas board, you need to do three things:
269 1. [Update all firmware on the board.](#4-troubleshooting)
270 2. Prepare the MicroSD card to you can boot from it.
273 **NOTE:** For subsequent builds, you only have to re-write the MicroSD
274 card with a new image.
276 ### 3.1. Booting the Image Using a MicroSD Card
278 1. Preparing the MicroSD Card
280 Plug the MicroSD card into your Build Host.
281 After plugging in the device, use the `dmesg` command as follows to
282 discover the device name:
286 [ 1971.462160] sd 6:0:0:0: [sdc] Mode Sense: 03 00 00 00
287 [ 1971.462277] sd 6:0:0:0: [sdc] No Caching mode page found
288 [ 1971.462278] sd 6:0:0:0: [sdc] Assuming drive cache: write through
289 [ 1971.463870] sdc: sdc1 sdc2
292 In the previous example, the MicroSD card is attached to the device `/dev/sdc`.
293 You can also use the `lsblk` command to show all your devices.
294 Here is an example that shows the MicroSD card as `/dev/sdc`:
298 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
299 sda 8:0 0 167,7G 0 disk
300 ├─sda1 8:1 0 512M 0 part /boot/efi
301 ├─sda2 8:2 0 159,3G 0 part /
302 └─sda3 8:3 0 7,9G 0 part [SWAP]
303 sdb 8:16 0 931,5G 0 disk
304 └─sdb1 8:17 0 931,5G 0 part /media/storage
305 sdc 8:32 1 14,9G 0 disk
306 ├─sdc1 8:33 1 40M 0 part
307 └─sdc2 8:34 1 788M 0 part
310 **IMPORTANT NOTE:** Before re-writing any device on your Build Host, you need to
311 be sure you are actually writing to the removable MicroSD card and not some other
313 Each computer is different and removable devices can change from time to time.
314 Consequently, you should repeat the previous operation with the MicroSD card to
315 confirm the device name every time you write to the card.
317 To summarize this example so far, we have the following:
319 * The first SATA drive is `/dev/sda`.
321 * `/dev/sdc` corresponds to the MicroSD card, and is also marked as a removable device.
322 You can see this in the output of the `lsblk` command where "1" appears in the "RM" column
325 Now that you have identified the device you are going to be writing the image on,
326 you can use the `bmaptool` to copy the image to the MicroSD card.
328 Your desktop system might offer a choice to mount the MicroSD automatically
330 For this example, assume that the MicroSD card mount directory is stored in the
333 Following are example commands that write the image to the MicroSD card:
336 cd $AGL_TOP/build/tmp/deploy/images/$MACHINE
337 bmaptool copy ./agl-demo-platform-$MACHINE.wic.xz <boot_device_name>
340 Alternatively, you can leave the image in an uncompressed state and write it
344 sudo umount <boot_device_name>
345 xzcat ./agl-demo-platform-$MACHINE.wic.xz | sudo dd of=<boot_device_name> bs=4M
351 Follow these steps to boot the board:
353 1. Use the board's power switch to turn off the board.
355 2. Insert the MicroSD card into the board.
357 3. Verify that you have plugged in the following:
359 * An external monitor into the board's HDMI port
361 * An input device (e.g. keyboard, mouse, touchscreen, and so forth) into the board's USB ports.
363 4. Use the board's power switch to turn on the board.
365 After a few seconds, you will see the AGL splash screen on the display and you
366 will be able to log in at the console's terminal or using the graphic screen.
368 ### 3.2. Setting Up the Serial Console
370 Setting up the Serial Console involves the following:
372 * Installing a serial client on your build host
373 * Connecting your build host to your Renesas board's serial port
374 * Powering on the board to get a shell at the console
375 * Configuring U-Boot parameters
376 * Logging into the console
377 * Determining the board's IP address
379 1. Installing a Serial Client on Your Build Host
381 You need to install a serial client on your build host.
384 * [GNU Screen](https://en.wikipedia.org/wiki/GNU_Screen)
385 * [picocom](https://linux.die.net/man/8/picocom)
386 * [Minicom](https://en.wikipedia.org/wiki/Minicom)
388 Of these three, "picocom" has the least dependencies and is therefore
389 considered the "lightest" solution.
391 2. Connecting Your Build Host to Your Renesas Board's Serial Port
393 You need to physically connect your build host to the Renesas board using
394 a USB cable from the host to the serial CP2102 USP port (i.e. Micro USB-A port)
395 on the Renesas board.
397 Once you connect the board, determine the device created for the serial link.
398 Use the ``dmesg`` command on your build host.
403 [2097783.287091] usb 2-1.5.3: new full-speed USB device number 24 using ehci-pci
404 [2097783.385857] usb 2-1.5.3: New USB device found, idVendor=0403, idProduct=6001
405 [2097783.385862] usb 2-1.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
406 [2097783.385864] usb 2-1.5.3: Product: FT232R USB UART
407 [2097783.385866] usb 2-1.5.3: Manufacturer: FTDI
408 [2097783.385867] usb 2-1.5.3: SerialNumber: AK04WWCE
409 [2097783.388288] ftdi_sio 2-1.5.3:1.0: FTDI USB Serial Device converter detected
410 [2097783.388330] usb 2-1.5.3: Detected FT232RL
411 [2097783.388658] usb 2-1.5.3: FTDI USB Serial Device converter now attached to ttyUSB0
414 The device created is usually "/dev/ttyUSB0".
415 However, the number might vary depending on other USB serial ports connected to the host.
417 To use the link, you need to launch the client.
418 Here are three commands, which vary based on the serial client, that show
419 how to launch the client:
422 picocom -b 115200 /dev/ttyUSB0
428 minicom -b 115200 -D /dev/ttyUSB0
434 screen /dev/ttyUSB0 115200
437 3. Powering on the Board to Get a Shell at the Console
439 Both the Pro and Premier kits (e.g.
440 [m3ulcb](https://elinux.org/R-Car/Boards/M3SK) and
441 [h3ulcb](https://elinux.org/R-Car/Boards/H3SK#Hardware)) have nine
442 switches (SW1 through SW9).
443 To power on the board, "short-press" SW8, which is the power switch.
445 Following, is console output for the power on process for each kit:
450 NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.7
451 NOTICE: BL2: PRR is R-Car H3 ES1.1
452 NOTICE: BL2: LCM state is CM
453 NOTICE: BL2: DDR1600(rev.0.15)
454 NOTICE: BL2: DRAM Split is 4ch
455 NOTICE: BL2: QoS is Gfx Oriented(rev.0.30)
456 NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x52
457 NOTICE: BL2: Lossy Decomp areas
458 NOTICE: Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
459 NOTICE: Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
460 NOTICE: Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
461 NOTICE: BL2: v1.1(release):41099f4
462 NOTICE: BL2: Built : 19:20:52, Jun 9 2016
463 NOTICE: BL2: Normal boot
464 NOTICE: BL2: dst=0xe63150c8 src=0x8180000 len=36(0x24)
465 NOTICE: BL2: dst=0x43f00000 src=0x8180400 len=3072(0xc00)
466 NOTICE: BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
467 NOTICE: BL2: dst=0x44100000 src=0x8200000 len=524288(0x80000)
468 NOTICE: BL2: dst=0x49000000 src=0x8640000 len=1048576(0x100000)
471 U-Boot 2015.04 (Jun 09 2016 - 19:21:52)
473 CPU: Renesas Electronics R8A7795 rev 1.1
477 MMC: sh-sdhi: 0, sh-sdhi: 1
481 Net: Board Net Initialization Failed
483 Hit any key to stop autoboot: 0
487 ### 3.3. Setting-up U-boot
489 Configuring U-Boot Parameters
491 Follow these steps to configure the board to use the MicroSD card as the
492 boot device and also to set the screen resolution:
494 1. As the board is powering up, press any key to stop the autoboot process.
495 You need to press a key quickly as you have just a few seconds in which to
498 2. Once the autoboot process is interrupted, use the board's serial console to
499 enter `printenv` to check if you have correct parameters for booting your board:
501 Here is an example using the **h3ulcb** board:
506 bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro rootfstype=ext4
507 bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000
509 fdt_high=0xffffffffffffffff
510 initrd_high=0xffffffffffffffff
511 load_dtb=ext4load mmc 0:1 0x48000000 /boot/r8a7795-h3ulcb.dtb
512 load_ker=ext4load mmc 0:1 0x48080000 /boot/Image
516 ver=U-Boot 2015.04 (Jun 09 2016 - 19:21:52)
518 Environment size: 648/131068 bytes
521 3. To boot your board using the MicroSD card, be sure your environment is set up
525 setenv bootargs console=ttySC0,115200 ignore_loglevel vmalloc=384M video=HDMI-A-1:1920x1080-32@60 root=/dev/mmcblk1p1 rw rootfstype=ext4 rootwait rootdelay=2
526 setenv bootcmd run load_ker\; run load_dtb\; booti 0x48080000 - 0x48000000
527 setenv load_ker ext4load mmc 0:1 0x48080000 /boot/Image
532 **NOTE** : Refer [here](https://elinux.org/R-Car/Boards/Yocto-Gen3-CommonFAQ/Which_dtb_file_is_required_to_boot_linux_on_the_R-Car_Starter_Kit_board_%3F) for more information.
534 Make sure your ``load_dtb`` is set as follows :
536 | Renesas Boards | DTB Name |
538 | **H3SK v2.0(DDR 4GB)** | r8a7795-h3ulcb.dtb |
539 | **H3SK v2.0(DDR 8GB)/v3.0(DDR 8GB)** | r8a7795-h3ulcb-4x2g.dtb |
540 | **M3SK v1.0** | r8a7796-m3ulcb.dtb |
541 | **M3SK v3.0** | r8a7796-m3ulcb-2x4g.dtb |
542 | **H3SK with a Kingfisher board** | r8a7795-h3ulcb-kf.dtb |
543 | **M3SK with a Kingfisher board** | r8a7796-m3ulcb-kf.dtb |
544 | **AGL Reference Hardware board** | r8a7795-agl-refhw.dtb |
547 setenv load_dtb ext4load mmc 0:1 0x48000000 /boot/r8a7795-h3ulcb-kf.dtb
550 5. Save the boot environment:
562 ## 4. Troubleshooting
564 ### 4.1. Checking Your Configuration
566 Aside from environment variables and parameters you establish through
567 running the `aglsetup.sh` script, you can ensure your build's configuration
568 is just how you want it by examining the `local.conf` configuration file.
570 You can find this configuration file in the Build Directory (e.g.
571 `$TOP_DIR/build/conf/local.conf`).
573 In general, the defaults along with the configuration fragments the
574 `aglsetup.sh` script applies in the `local.conf` file are good enough.
575 However, you can customize aspects by editing the `local.conf` file.
577 "[Customizing Your Build](4_Customizing_Your_Build.md)"
578 section for common configurations you might want to consider.
580 **NOTE:** For detailed explanations of the configurations you can make
581 in the ``local.conf`` file, consult the
582 [Yocto Project Documentation](https://www.yoctoproject.org/docs/).
584 A quick way to see if you have the `$MACHINE` variable set correctly
585 is to use the following command:
588 grep -w -e "^MACHINE =" $AGL_TOP/build/conf/local.conf
591 Depending on the Renesas board you are using, you should see output
607 MACHINE = "h3-salvator-x"
610 If you ran the `aglsetup.sh` script as described in the
611 "[Making Sure Your Build Environment is Correct](./5_3_RCar_Gen_3.md#4-making-sure-your-build-environment-is-correct)"
612 section earlier, the "agl-devel", "agl-demo", "agl-netboot", "agl-appfw-smack", and
613 "agl-localdev" AGL features will be in effect.
614 These features provide the following:
617 * Some tweaks, including a disabled root password
619 * The TCF Agent for easier application deployment and remote debugging
620 * Some extra system tools such as USB and bluetooth
621 * Support for the AGL demo platform
622 * Network boot support through TFTP and NBD protocols
623 * [IoT.bzh](https://iot.bzh/en/) Application Framework plus
624 [SMACK](https://en.wikipedia.org/wiki/Smack_(software)) and
625 [Cynara](https://wiki.tizen.org/Security:Cynara)
626 * Support for local development including `localdev.inc` when present
628 ### 4.2. Check the Script's Log:
630 Running the `aglsetup.sh` script creates the `setup.log` file, which is in
631 the `build/conf` folder.
632 You can examine this log to see the results of the script.
633 For example, suppose the graphics drivers were missing or could not be extracted
634 when you ran the script.
635 In case of missing graphics drivers, you could notice an error message
636 similar to the following:
640 --- fragment /home/working/workspace_agl_master/meta-agl/templates/machine/h3ulcb/50_setup.sh
641 /home/working/workspace_agl_master /home/working/workspace_agl_master/build_gen3
642 The graphics and multimedia acceleration packages for
643 the R-Car Gen3 board can be downloaded from:
644 https://www.renesas.com/en-us/solutions/automotive/rcar-demoboard-2.html
646 These 2 files from there should be store in your'/home/devel/Downloads' directory.
647 R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-weston8-20200923.zip
648 R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-weston8-20200923.zip
649 /home/working/workspace_agl_master/build_gen3
650 --- fragment /home/working/workspace_agl_master/meta-agl/templates/base/99_setup_EULAconf.sh
651 --- end of setup script
653 Generating setup file: /home/working/workspace_agl_master/build_gen3/agl-init-build-env ... OK
654 ------------ aglsetup.sh: Done
658 If you encounter this issue, or any other unwanted behavior, you can fix the error
659 mentioned, remove the `$AGL_TOP/build` directory, and then re-launch the
662 Here is another example that indicates the driver files could not be extracted from the downloads directory:
665 ~/workspace_agl/build/conf $ cat setup.log
666 --- beginning of setup script
667 --- fragment /home/working/workspace_agl/meta-agl/templates/base/01_setup_EULAfunc.sh
668 --- fragment /home/working/workspace_agl/meta-agl/templates/machine/h3ulcb/50_setup.sh
669 ~/workspace_agl ~/workspace_agl/build
670 ERROR: FILES "+/home/working/Downloads/R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-weston8-20200923.zip+" NOT EXTRACTING CORRECTLY
671 ERROR: FILES "+/home/working/Downloads/R-car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-weston8-20200923.zip+" NOT EXTRACTING CORRECTLY
672 The graphics and multimedia acceleration packages for
673 the R-Car Gen3 board BSP can be downloaded from:
674 <https://www.renesas.com/us/en/application/automotive/r-car-h3-m3-documents-software>
676 These 2 files from there should be stored in your
677 '/home/working/Downloads' directory.
678 R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-weston8-20200923.zip
679 R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-weston8-20200923.zip
680 ERROR: Script /home/working/workspace_agl/build/conf/setup.sh failed
684 ### 4.3. Updating the Board's Firmware
686 Follow these steps to update the firmware:
688 1. **Update the Sample Loader and MiniMonitor:**
690 You only need to make these updates one time per device.
692 Follow the procedure found on the
693 eLinux.org wiki to update to at least version 3.02,
694 which is mandatory to run the AGL image
695 ([R-car loader update](https://elinux.org/R-Car/Boards/Kingfisher#How_to_update_of_Sample_Loader_and_MiniMonitor)).
697 2. **Update the Firmware Stack:**
699 You only need to update the firmware stack if you are
700 using the Eel or later (5.0) version of AGL software.
702 M3 and H3 Renesas board are AArch64 platforms.
703 As such, they have a firmware stack that is divided across: **ARM Trusted Firmware**, **OP-Tee** and **U-Boot**.
705 If you are using the Eel (5.0) version or later of the AGL software, you must update
706 the firmware using the **[h3ulcb] [R-car h3ulcb firmware update](http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware)**
707 or **[m3ulcb] [R-car m3ulcb firmware update](https://elinux.org/R-Car/Boards/M3SK#Flashing_firmware)** links from the
708 [Embedded Linux Wiki](https://www.elinux.org/Main_Page) (i.e. `elinux.org`).
710 The table in the wiki lists the files you need to flash the firmware.
711 You can find these files in the following directory:
714 $AGL_TOP/build/tmp/deploy/images/$MACHINE
717 **NOTE:** The Salvator-X firmware update process is not documented on eLinux.
718 **NOTE:** The AGL Reference Hardware board generally should not require a
719 firmware update to be usable, and has a slightly different update procedure.
720 If you do need to update the firmware, the procedure is documented
721 [here](https://git.automotivelinux.org/AGL/meta-agl-refhw/tree/meta-agl-refhw-gen3/docs/ReferenceHW_Rcar_gen3.md).
723 ### 4.4. Logging Into the Console
725 Once the board boots, you should see the
726 [Wayland display](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol))
727 on the external monitor.
728 A login prompt should appear as follows depending on your board:
730 **h3ulcb** or **AGL Reference Hardware**:
733 Automotive Grade Linux ${AGL_VERSION} h3ulcb ttySC0
738 At the prompt, login by using `root` as the login.
739 The password is "empty" so you should not be prompted for the password.
741 ### 4.5. Determining the Board's IP Address
743 If your board is connected to a local network using Ethernet and
744 if a DHCP server is able to distribute IP addresses,
745 you can determine the board's IP address and log in using `ssh`.
747 Here is an example for the **h3ulcb** board:
751 Last login: Tue Dec 6 09:55:15 UTC 2016 on tty2
752 root@h3ulcb:~# ip -4 a
753 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
754 inet 127.0.0.1/8 scope host lo
755 valid_lft forever preferred_lft forever
756 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
757 inet 10.0.0.27/24 brd 10.0.0.255 scope global eth0
758 valid_lft forever preferred_lft forever
762 In the previous example, IP address is 10.0.0.27.
763 Once you know the address, you can use `ssh` to login.
764 Following is an example that shows logging into SSH and then
765 displaying the contents of the `/etc/os-release` file:
769 Last login: Tue Dec 6 10:01:11 2016 from 10.0.0.13
770 root@h3ulcb:~# cat /etc/os-release
772 NAME="Automotive Grade Linux"
773 VERSION="11.0.0+snapshot-20210128 (koi)"
774 VERSION_ID="11.0.0-snapshot-20210128"
775 PRETTY_NAME="Automotive Grade Linux 11.0.0+snapshot-20210128 (koi)"
778 ## 5. Supplementary Information
780 ### 5.1. R-Car Generation 3 Information
782 Refer to the [R-Car](https://elinux.org/R-Car) page on the
783 [elinux.org](https://elinux.org) website for more information.
785 ### 5.2. Proprietary libraries for meta-rcar-gen3
787 The meta-rcar-gen3 layer of meta-renesas supports Graphic GLES(GSX)
788 libraries, proprietary multimedia libraries, and ICCOM software.
790 ### 5.3. Build with Renesas multimedia libraries
792 Multimedia portions depend on GLES portions.
794 * A. Configuration for Multimedia features
796 * Please copy proprietary libraries to the directory of recipes.
798 * Please set local.conf the following.
800 **Enable multimedia features. This provides package group of plug-ins of the GStreamer, multimedia libraries and kernel drivers.**
803 MACHINE_FEATURES:append = " multimedia"
806 * B. Configuration for optional codecs and middleware
808 * Please copy proprietary libraries to the directory of recipes.
810 * Add features to `DISTRO_FEATURES:append` to local.conf
812 **Additional configuration in OMX module**:
815 " h263dec_lib" - for OMX Media Component H263 Decoder Library
816 " h264dec_lib" - for OMX Media Component H264 Decoder Library
817 " h264enc_lib" - for OMX Media Component H.264 Encoder Library
818 " h265dec_lib" - for OMX Media Component H265 Decoder Library
819 " mpeg2dec_lib" - for OMX Media Component MPEG2 Decoder Library
820 " mpeg4dec_lib" - for OMX Media Component MPEG4 Decoder Library
821 " vc1dec_lib" - for OMX Media Component VC-1 Decoder Library
822 " divxdec_lib" - for OMX Media Component DivX Decoder Library
823 " rvdec_lib" - for OMX Media Component RealVideo Decoder Library
824 " alacdec_lib" - for OMX Media Component ALAC Decoder Library
825 " flacdec_lib" - for OMX Media Component FLAC Decoder Library
826 " aaclcdec_lib" - for OMX Media Component AAC-LC Decoder Library
827 " aaclcdec_mdw" - for AAC-LC 2ch Decoder Middleware for Linux
828 " aacpv2dec_lib" - for OMX Media Component aacPlus V2 Decoder Library
829 " aacpv2dec_mdw" - for aacPlus V2 Decoder Middleware for Linux
830 " mp3dec_lib" - for OMX Media Component MP3 Decoder Library
831 " mp3dec_mdw" - for MP3 Decoder Middleware for Linux
832 " wmadec_lib" - for OMX Media Component WMA Standard Decoder Library
833 " wmadec_mdw" - for WMA Standard Decoder Middleware for Linux
834 " dddec_lib" - for OMX Media Component Dolby(R) Digital Decoder Library
835 " dddec_mdw" - for Dolby(R) Digital Decoder Middleware for Linux
836 " aaclcenc_lib" - for OMX Media Component AAC-LC Encoder Library
837 " vp8dec_lib" - for OMX Media Component VP8 Decoder Library for Linux
838 " vp8enc_lib" - for OMX Media Component VP8 Encoder Library for Linux
839 " vp9dec_lib" - for OMX Media Component VP9 Decoder Library for Linux
840 " aaclcenc_mdw" - for AAC-LC Encoder Middleware for Linux
841 " cmsbcm" - for CMS Basic Color Management Middleware for Linux
842 " cmsblc" - for CMS CMM3 Backlight Control Middleware for Linux
843 " cmsdgc" - for CMS VSP2 Dynamic Gamma Correction Middleware for Linux
844 " dtv" - for ISDB-T DTV Software Package for Linux
845 " dvd" - for DVD Core-Middleware for Linux
846 " adsp" - for ADSP driver, ADSP interface and ADSP framework for Linux
847 " avb" - for AVB Software Package for Linux
853 DISTRO_FEATURES:append = " h264dec_lib h265dec_lib mpeg2dec_lib aaclcdec_lib aaclcdec_mdw"
856 * C. Configuration for test packages
858 Must ensure that Multimedia features have been enabled.
859 (Please refer to III/A to enable Multimedia.)
861 * Please add feature to `DISTRO_FEATURES:append` to local.conf.
863 **Configuration for multimedia test package**
866 DISTRO_FEATURES:append = " mm-test"
869 ### 5.4. Enable Linux ICCOM driver and Linux ICCOM library
871 For Linux ICCOM driver and Linux ICCOM library
873 * Please copy proprietary libraries to the directory of recipes.
875 * Please set the following in local.conf:
878 DISTRO_FEATURES:append = "iccom"