1 # Building for Supported Renesas Boards
3 AGL supports building for several automotive
4 [Renesas](https://www.renesas.com/us/en/solutions/automotive.html) board kits.
5 Renesas is the number one supplier of vehicle control microcontrollers and
6 System on a Chip (SoC) products for the automotive industry.
8 This section provides the build and deploy steps you need to create an
9 image for the following Renesas platforms:
11 * [Renesas R-Car Starter Kit Pro Board](https://www.elinux.org/R-Car/Boards/M3SK)
12 * [Renesas R-Car Starter Kit Premier Board](https://www.elinux.org/R-Car/Boards/H3SK)
13 * [Renesas Salvator-X Board](https://www.elinux.org/R-Car/Boards/Salvator-X)
14 * [Renesas Kingfisher Infotainment Board](https://elinux.org/R-Car/Boards/Kingfisher)
16 **NOTE:** You can find similar information for the Pro and Premier board kits on the
17 [R-Car/Boards/Yocto-Gen3](https://elinux.org/R-Car/Boards/Yocto-Gen3) page.
18 The information on this page describes setup and build procedures for both these
19 Renesas development kits.
21 ## 1. Downloading Proprietary Drivers
23 Before setting up the build environment, you need to download proprietary drivers from the
24 [R-Car H3/M3 Software library and Technical document](https://www.renesas.com/us/en/solutions/automotive/rcar-download/rcar-demoboard-2.html)
27 Follow these steps to download the drivers you need:
29 1. **Determine the Files You Need:**
31 Run the ``setup_mm_packages.sh`` script as follows to
32 display the list of ZIP files containing the drivers you need.
33 Following is an example:
36 grep -rn ZIP_.= $AGL_TOP/meta-agl/meta-agl-bsp/meta-rcar-gen3/scripts/setup_mm_packages.sh
39 The script's output identifies the files you need to download from the page.
41 2. **Get Your Board Support Package (BSP) Version:**
43 Be sure to have the correct BSP version of the R-Car Starter Kit
44 based on the version of the AGL software you are using.
45 Find the appropriate download links on the
46 [R-Car H3/M3 Software library and Technical document](https://www.renesas.com/us/en/solutions/automotive/rcar-download/rcar-demoboard-2.html)
48 The file pairs are grouped according to the Yocto Project version you are
49 using with the AGL software.
50 Use the following table to map the Renesas version to your AGL software:
52 | AGL Version | Renesas version |
54 | AGL jellyfish 10.0.0 | 3.21.0 |
57 3. **Download the Files:**
59 Start the download process by clicking the download link.
60 If you do not have an account with Renesas, you will be asked to register a free account.
61 You must register and follow the "Click Through" licensing process
62 in order to download these proprietary files.
64 If needed, follow the instructions to create the free account by providing the required
66 Once the account is registered and you are logged in, you can download the files.
69 You might have to re-access the
70 [original page](https://www.renesas.com/us/en/solutions/automotive/rcar-download/rcar-demoboard-2.html)
71 that contains the download links you need after creating the account and logging in.
73 4. **Create an Environment Variable to Point to Your Download Area:**
75 Create and export an environment variable named `XDG_DOWNLOAD_DIR` that points to
76 your download directory.
80 $ export XDG_DOWNLOAD_DIR=$HOME/Downloads
83 5. **Be Sure the Files Have Rights:**
85 Be sure you have the necessary rights for the files you downloaded.
86 You can use the following command:
89 chmod a+x $XDG_DOWNLOAD_DIR/*.zip
92 6. **Check to be Sure the Files are Downloaded and Have the Correct Rights:**
94 Do a quick listing of the files to ensure they are in the download directory and
95 they have the correct access rights.
99 $ ls -l $XDG_DOWNLOAD_DIR/*.zip
100 -rw-rw-r-- 1 scottrif scottrif 4662080 Nov 19 14:48 /home/scottrif/Downloads/R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-weston8-20191206.zip
101 -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-20191021.zip
104 ## 2. Getting More Software
106 1. **Get the `bmaptool`:**
108 Download this tool from the
109 [bmap-tools](https://build.opensuse.org/package/show/isv:LinuxAutomotive:AGL_Master/bmap-tools)
111 The site has pre-built packages (DEB or RPM) for the supported host
114 ## 3. Getting Your Hardware Together
116 Gather together this list of hardware items, which is not exhaustive.
117 Having these items ahead of time saves you from having to try and
118 collect hardware during development:
120 * Supported Starter Kit Gen3 board with its 5V power supply.
121 * Micro USB-A cable for serial console.
122 This cable is optional if you are using Ethernet and an SSH connection.
123 * USB 2.0 Hub. The hub is optional but makes it easy to connect multiple USB devices.
124 * Ethernet cable. The cable is optional if you are using a serial console.
125 * HDMI type D (Micro connector) cable and an associated display.
126 * 4 Gbyte minimum MicroSD Card. It is recommended that you use a class 10 type.
127 * USB touch screen device such as the GeChic 1502i/1503i. A touch screen device is optional.
129 **NOTE:** The Salvator-X Board has NDA restrictions.
130 Consequently, less documentation is available for this board both here and across the
134 ## 4. Making Sure Your Build Environment is Correct
137 "[Initializing Your Build Environment](./3_Initializing_Your_Build_Environment.md)"
138 section presented generic information for setting up your build environment
139 using the `aglsetup.sh` script.
140 If you are building an image for a supported Renesas board,
141 you need to take steps to make sure your build host is set up correctly.
143 1. **Define Your Board:**
145 Depending on your Renesas board, define and export a `MACHINE` variable as follows:
147 | Board| `MACHINE` Setting |
149 | Starter Kit Pro/M3 | `MACHINE`=m3ulcb |
150 | Starter Kit Pro/M3 + kingfisher support | `MACHINE`=m3ulcb-kf |
151 | Starter Kit Pro/M3 whithout graphic | `MACHINE`=m3ulcb-nogfx |
152 | Starter Kit Premier/H3 | `MACHINE`=h3ulcb |
153 | Starter Kit Premier/H3 + kingfisher support | `MACHINE`=h3ulcb-kf |
154 | Starter Kit Premier/H3 whithout graphic | `MACHINE`=h3ulcb-nogfx |
155 | Salvator-X | `MACHINE`=h3-salvator-x |
157 For example, the following command defines and exports the `MACHINE` variable
158 for the Starter Kit Pro/M3 Board:
161 $ export MACHINE=m3ulcb
164 2. **Run the `aglsetup.sh` Script:**
166 Use the following commands to run the AGL Setup script:
170 $ source meta-agl/scripts/aglsetup.sh -m $MACHINE -b build agl-devel agl-demo
174 Running the `aglsetup.sh` script automatically places you in the
175 working directory (i.e. `$AGL_TOP/build`).
176 You can change this default behavior by adding the "-f" option to the
177 script's command line.
179 In the previous command, the "-m" option sets your machine to the previously
180 defined `MACHINE` variable.
181 The "-b" option defines your Build Directory, which is the
182 default `$AGL_TOP/build`.
183 Finally, the AGL features are provided to support building the AGL Demo image
184 for the Renesas board.
186 You can learn more about the AGL Features in the
187 "[Initializing Your Build Environment](./3_Initializing_Your_Build_Environment.md)"
190 3. **Examine the Script's Log:**
192 Running the `aglsetup.sh` script creates the `setup.log` file, which is in
193 the `build/conf` folder.
194 You can examine this log to see the results of the script.
195 For example, suppose the graphics drivers were missing or could not be extracted
196 when you ran the script.
199 <summary> In case of missing graphics drivers, you could notice an error message
200 similar to the following:</summary>
204 --- fragment /home/working/workspace_agl_master/meta-agl/templates/machine/h3ulcb/50_setup.sh
205 /home/working/workspace_agl_master /home/working/workspace_agl_master/build_gen3
206 The graphics and multimedia acceleration packages for
207 the R-Car Gen3 board can be downloaded from:
208 https://www.renesas.com/en-us/solutions/automotive/rcar-demoboard-2.html
210 These 2 files from there should be store in your'/home/devel/Downloads' directory.
211 R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-weston5-20190802.zip
212 R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-weston5-20190802.zip
213 /home/working/workspace_agl_master/build_gen3
214 --- fragment /home/working/workspace_agl_master/meta-agl/templates/base/99_setup_EULAconf.sh
215 --- end of setup script
217 Generating setup file: /home/working/workspace_agl_master/build_gen3/agl-init-build-env ... OK
218 ------------ aglsetup.sh: Done
224 If you encounter this issue, or any other unwanted behavior, you can fix the error
225 mentioned, remove the `$AGL_TOP/build` directory, and then re-launch the
229 <summary>Here is another example that indicates the driver files could not be extracted from the downloads directory:</summary>
234 ~/workspace_agl/build/conf $ cat setup.log
235 --- beginning of setup script
236 --- fragment /home/iotbzh/workspace_agl/meta-agl/templates/base/01_setup_EULAfunc.sh
237 --- fragment /home/iotbzh/workspace_agl/meta-agl/templates/machine/m3ulcb/50_setup.sh
238 ~/workspace_agl ~/workspace_agl/build
239 ERROR: FILES "+/home/iotbzh/Downloads/R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-weston5-20190802.zip+" NOT EXTRACTING CORRECTLY
240 ERROR: FILES "+/home/iotbzh/Downloads/R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-weston5-20190802.zip+" NOT EXTRACTING CORRECTLY
241 The graphics and multimedia acceleration packages for
242 the R-Car Gen3 board BSP can be downloaded from:
243 <https://www.renesas.com/us/en/solutions/automotive/rcar-download/rcar-demoboard-2.html>
245 These 2 files from there should be stored in your
246 '/home/iotbzh/Downloads' directory.
247 R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-weston5-20190802.zip
248 R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-weston5-20190802.zip
249 ERROR: Script /home/iotbzh/workspace_agl/build/conf/setup.sh failed
255 ## 5. Checking Your Configuration
257 Aside from environment variables and parameters you establish through
258 running the `aglsetup.sh` script, you can ensure your build's configuration
259 is just how you want it by examining the `local.conf` configuration file.
261 You can find this configuration file in the Build Directory (e.g.
262 "$TOP_DIR/build/conf/local.conf").
264 In general, the defaults along with the configuration fragments the
265 `aglsetup.sh` script applies in the `local.conf` file are good enough.
266 However, you can customize aspects by editing the `local.conf` file.
268 "[Customizing Your Build](../image-workflow-cust-build.html)"
269 section for common configurations you might want to consider.
271 **NOTE:** For detailed explanations of the configurations you can make
272 in the ``local.conf`` file, consult the
273 [Yocto Project Documentation](https://www.yoctoproject.org/docs/).
275 A quick way to see if you have the `$MACHINE` variable set correctly
276 is to use the following command:
279 grep -w -e "^MACHINE =" $AGL_TOP/build/conf/local.conf
282 Depending on the Renesas board you are using, you should see output
294 MACHINE = "h3-salvator-x"
297 If you ran the `aglsetup.sh` script as described in the
298 "[Making Sure Your Build Environment is Correct](./renesas.html#4-making-sure-your-build-environment-is-correct)"
299 section earlier, the "agl-devel", "agl-demo" AGL features will be in effect.
300 These features provide the following:
303 * Some tweaks, including a disabled root password
305 * The TCF Agent for easier application deployment and remote debugging
306 * Some extra system tools such as USB and bluetooth
307 * Support for the AGL demo platform
308 * [IoT.bzh](https://iot.bzh/en/) Application Framework plus
309 [SMACK](https://en.wikipedia.org/wiki/Smack_(software)) and
310 [Cynara](https://wiki.tizen.org/Security:Cynara)
314 This section shows the `bitbake` command used to build the AGL image.
315 Before running BitBake to start your build, it is good to be reminded that AGL
316 does provide pre-built images for developers that work with supported hardware.
317 You can find these pre-built images on the
318 [AGL Download web site](https://download.automotivelinux.org/AGL/release).
320 Start the build using the `bitbake` command.
322 **NOTE:** An initial build can take many hours depending on your
323 CPU and and Internet connection speeds.
324 The build also takes approximately 100G-bytes of free disk space.
326 For this example, the target is "agl-demo-platform":
329 bitbake agl-demo-platform
332 The build process puts the resulting image in the Build Directory:
335 <build_directory>/tmp/deploy/images/$MACHINE
338 ## 7. Booting the Image Using a MicroSD Card
340 To boot your image on the Renesas board, you need to do three things:
342 1. Update all firmware on the board.
343 2. Prepare the MicroSD card to you can boot from it.
346 **NOTE:** For subsequent builds, you only have to re-write the MicroSD
347 card with a new image.
349 ### Updating the Board's Firmware
351 Follow these steps to update the firmware:
353 1. **Update the Sample Loader and MiniMonitor:**
355 You only need to make these updates one time per device.
357 Follow the procedure found on the
358 eLinux.org wiki to update to at least version 3.02,
359 which is mandatory to run the AGL image ([R-car loader update](https://elinux.org/R-Car/Boards/Kingfisher#How_to_update_of_Sample_Loader_and_MiniMonitor)).
361 2. **Update the Firmware Stack:**
363 You only need to update the firmware stack if you are
364 using the Eel or later (5.0) version of AGL software.
366 M3 and H3 Renesas board are AArch64 platforms.
367 As such, they have a firmware stack that is divided across: **ARM Trusted Firmware**, **OP-Tee** and **U-Boot**.
369 If you are using the Eel (5.0) version or later of the AGL software, you must update
370 the firmware using the **[h3ulcb][R-car h3ulcb firmware update](http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware)**
371 or **[m3ulcb][R-car m3ulcb firmware update](https://elinux.org/R-Car/Boards/M3SK#Flashing_firmware)** links from the
372 [Embedded Linux Wiki](https://www.elinux.org/Main_Page) (i.e. `elinux.org`).
374 The table in the wiki lists the files you need to flash the firmware.
375 You can find these files in the following directory:
378 $AGL_TOP/build/tmp/deploy/images/$MACHINE
381 **NOTE:** The Salvator-X firmware update process is not documented on eLinux.
383 ### Preparing the MicroSD Card
387 Plug the MicroSD card into your Build Host.
388 After plugging in the device, use the `dmesg` command as follows to
389 discover the device name:
394 [ 1971.462160] sd 6:0:0:0: [sdc] Mode Sense: 03 00 00 00
395 [ 1971.462277] sd 6:0:0:0: [sdc] No Caching mode page found
396 [ 1971.462278] sd 6:0:0:0: [sdc] Assuming drive cache: write through
397 [ 1971.463870] sdc: sdc1 sdc2
402 In the previous example, the MicroSD card is attached to the device `/dev/sdc`.
406 You can also use the `lsblk` command to show all your devices.
407 Here is an example that shows the MicroSD card as `/dev/sdc`:
412 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
413 sda 8:0 0 167,7G 0 disk
414 ├─sda1 8:1 0 512M 0 part /boot/efi
415 ├─sda2 8:2 0 159,3G 0 part /
416 └─sda3 8:3 0 7,9G 0 part [SWAP]
417 sdb 8:16 0 931,5G 0 disk
418 └─sdb1 8:17 0 931,5G 0 part /media/storage
419 sdc 8:32 1 14,9G 0 disk
420 ├─sdc1 8:33 1 40M 0 part
421 └─sdc2 8:34 1 788M 0 part
426 **IMPORTANT NOTE:** Before re-writing any device on your Build Host, you need to
427 be sure you are actually writing to the removable MicroSD card and not some other
429 Each computer is different and removable devices can change from time to time.
430 Consequently, you should repeat the previous operation with the MicroSD card to
431 confirm the device name every time you write to the card.
433 To summarize this example so far, we have the following:
435 * The first SATA drive is `/dev/sda`.
437 * `/dev/sdc` corresponds to the MicroSD card, and is also marked as a removable device.
438 You can see this in the output of the `lsblk` command where "1" appears in the "RM" column
441 Now that you have identified the device you are going to be writing the image on,
442 you can use the `bmaptool` to copy the image to the MicroSD card.
444 Your desktop system might offer a choice to mount the MicroSD automatically
446 For this example, assume that the MicroSD card mount directory is stored in the
449 Following are example commands that write the image to the MicroSD card:
452 cd $AGL_TOP/build/tmp/deploy/images/$MACHINE
453 bmaptool copy ./agl-demo-platform-$MACHINE.wic.xz <boot_device_name>
456 Alternatively, you can leave the image in an uncompressed state and write it
460 sudo umount <boot_device_name>
461 xzcat ./agl-demo-platform-$MACHINE.wic.xz | sudo dd of=<boot_device_name> bs=4M
465 ### Booting the Board
467 Follow these steps to boot the board:
469 1. Use the board's power switch to turn off the board.
471 2. Insert the MicroSD card into the board.
473 3. Verify that you have plugged in the following:
475 * An external monitor into the board's HDMI port
477 * An input device (e.g. keyboard, mouse, touchscreen, and so forth) into the board's USB ports.
479 4. Use the board's power switch to turn on the board.
481 After a few seconds, you will see the AGL splash screen on the display and you
482 will be able to log in at the console's terminal or using the graphic screen.
484 ## 8. Setting Up the Serial Console
486 Setting up the Serial Console involves the following:
488 * Installing a serial client on your build host
489 * Connecting your build host to your Renesas board's serial port
490 * Powering on the board to get a shell at the console
491 * Configuring U-Boot parameters
492 * Logging into the console
493 * Determining the board's IP address
495 ### Installing a Serial Client on Your Build Host
497 You need to install a serial client on your build host.
499 [GNU Screen](https://en.wikipedia.org/wiki/GNU_Screen),
500 [picocom](https://linux.die.net/man/8/picocom),
502 [Minicom](https://en.wikipedia.org/wiki/Minicom).
504 Of these three, "picocom" has less dependencies and is therefore
505 considered the "lightest" solution.
507 ### Connecting Your Build Host to Your Renesas Board's Serial Port
509 You need to physically connect your build host to the Renesas board using
510 a USB cable from the host to the serial CP2102 USP port (i.e. Micro USB-A port)
511 on the Renesas board.
515 Once you connect the board, determine the device created for the serial link.
516 Use the ``dmesg`` command on your build host.
522 [2097783.287091] usb 2-1.5.3: new full-speed USB device number 24 using ehci-pci
523 [2097783.385857] usb 2-1.5.3: New USB device found, idVendor=0403, idProduct=6001
524 [2097783.385862] usb 2-1.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
525 [2097783.385864] usb 2-1.5.3: Product: FT232R USB UART
526 [2097783.385866] usb 2-1.5.3: Manufacturer: FTDI
527 [2097783.385867] usb 2-1.5.3: SerialNumber: AK04WWCE
528 [2097783.388288] ftdi_sio 2-1.5.3:1.0: FTDI USB Serial Device converter detected
529 [2097783.388330] usb 2-1.5.3: Detected FT232RL
530 [2097783.388658] usb 2-1.5.3: FTDI USB Serial Device converter now attached to ttyUSB0
535 The device created is usually "/dev/ttyUSB0".
536 However, the number might vary depending on other USB serial ports connected to the host.
538 To use the link, you need to launch the client.
539 Here are three commands, which vary based on the serial client, that show
540 how to launch the client:
544 $ picocom -b 115200 /dev/ttyUSB0
550 $ minicom -b 115200 -D /dev/ttyUSB0
556 $ screen /dev/ttyUSB0 115200
559 ### Powering on the Board to Get a Shell at the Console
561 Both the Pro and Premier kits (e.g.
562 [m3ulcb](https://elinux.org/R-Car/Boards/M3SK) and
563 [h3ulcb](https://elinux.org/R-Car/Boards/H3SK#Hardware)) have nine
564 switches (SW1 through SW9).
565 To power on the board, "short-press" SW8, which is the power switch.
567 Following, is console output for the power on process for each kit:
576 NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.7
577 NOTICE: BL2: PRR is R-Car H3 ES1.1
578 NOTICE: BL2: LCM state is CM
579 NOTICE: BL2: DDR1600(rev.0.15)
580 NOTICE: BL2: DRAM Split is 4ch
581 NOTICE: BL2: QoS is Gfx Oriented(rev.0.30)
582 NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x52
583 NOTICE: BL2: Lossy Decomp areas
584 NOTICE: Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
585 NOTICE: Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
586 NOTICE: Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
587 NOTICE: BL2: v1.1(release):41099f4
588 NOTICE: BL2: Built : 19:20:52, Jun 9 2016
589 NOTICE: BL2: Normal boot
590 NOTICE: BL2: dst=0xe63150c8 src=0x8180000 len=36(0x24)
591 NOTICE: BL2: dst=0x43f00000 src=0x8180400 len=3072(0xc00)
592 NOTICE: BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
593 NOTICE: BL2: dst=0x44100000 src=0x8200000 len=524288(0x80000)
594 NOTICE: BL2: dst=0x49000000 src=0x8640000 len=1048576(0x100000)
597 U-Boot 2015.04 (Jun 09 2016 - 19:21:52)
599 CPU: Renesas Electronics R8A7795 rev 1.1
603 MMC: sh-sdhi: 0, sh-sdhi: 1
607 Net: Board Net Initialization Failed
609 Hit any key to stop autoboot: 0
621 NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.14
622 NOTICE: BL2: PRR is R-Car M3 Ver1.0
623 NOTICE: BL2: Board is Starter Kit Rev1.0
624 NOTICE: BL2: Boot device is HyperFlash(80MHz)
625 NOTICE: BL2: LCM state is CM
626 NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x52
627 NOTICE: BL2: DDR1600(rev.0.22)NOTICE: [COLD_BOOT]NOTICE: ..0
628 NOTICE: BL2: DRAM Split is 2ch
629 NOTICE: BL2: QoS is default setting(rev.0.17)
630 NOTICE: BL2: Lossy Decomp areas
631 NOTICE: Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
632 NOTICE: Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
633 NOTICE: Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
634 NOTICE: BL2: v1.3(release):4eef9a2
635 NOTICE: BL2: Built : 00:25:19, Aug 25 2017
636 NOTICE: BL2: Normal boot
637 NOTICE: BL2: dst=0xe631e188 src=0x8180000 len=512(0x200)
638 NOTICE: BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)
639 NOTICE: BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
640 NOTICE: BL2: dst=0x44100000 src=0x8200000 len=524288(0x80000)
641 NOTICE: BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)
644 U-Boot 2015.04-dirty (Aug 25 2017 - 10:55:49)
646 CPU: Renesas Electronics R8A7796 rev 1.0
650 MMC: sh-sdhi: 0, sh-sdhi: 1
655 Hit any key to stop autoboot: 0
661 ## 9. Setting-up U-boot
662 ### Configuring U-Boot Parameters
664 Follow these steps to configure the board to use the MicroSD card as the
665 boot device and also to set the screen resolution:
667 1. As the board is powering up, press any key to stop the autoboot process.
668 You need to press a key quickly as you have just a few seconds in which to
671 2. Once the autoboot process is interrupted, use the board's serial console to
672 enter <b>printenv</b> to check if you have correct parameters for booting your board:
675 Here is an example using the <b>h3ulcb</b> board:
682 bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro rootfstype=ext4
683 bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000
685 fdt_high=0xffffffffffffffff
686 initrd_high=0xffffffffffffffff
687 load_dtb=ext4load mmc 0:1 0x48000000 /boot/r8a7795-h3ulcb.dtb
688 load_ker=ext4load mmc 0:1 0x48080000 /boot/Image
692 ver=U-Boot 2015.04 (Jun 09 2016 - 19:21:52)
694 Environment size: 648/131068 bytes
700 Here is a second example using the <b>m3ulcb</b> board:
706 bootargs=console=ttySC0,115200 root=/dev/mmcblk1p1 rootwait ro rootfstype=ext4
707 bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000
709 fdt_high=0xffffffffffffffff
711 initrd_high=0xffffffffffffffff
712 load_dtb=ext4load mmc 0:1 0x48000000 /boot/r8a7796-m3ulcb.dtb
713 load_ker=ext4load mmc 0:1 0x48080000 /boot/Image
717 ver=U-Boot 2015.04 (Nov 30 2016 - 18:25:18)
719 Environment size: 557/131068 bytes
724 3. To boot your board using the MicroSD card, be sure your environment is set up
728 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
729 setenv bootcmd run load_ker\; run load_dtb\; booti 0x48080000 - 0x48000000
730 setenv load_ker ext4load mmc 0:1 0x48080000 /boot/Image
735 **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.
737 Make sure your ``load_dtb`` is set as follows :
739 * **H3SK v2.0(DDR 4GB)** : `$ setenv load_dtb ext4load mmc 0:1 0x48000000 /boot/r8a7795-h3ulcb.dtb`
741 * **H3SK v2.0(DDR 8GB)/v3.0(DDR 8GB)** : `$ setenv load_dtb ext4load mmc 0:1 0x48000000 /boot/r8a7795-h3ulcb-4x2g.dtb`
743 * **M3SK v1.0** : `$ setenv load_dtb ext4load mmc 0:1 0x48000000 /boot/r8a7796-m3ulcb.dtb`
745 * **M3SK v3.0** : `$ setenv load_dtb ext4load mmc 0:1 0x48000000 /boot/r8a7796-m3ulcb-2x4g.dtb`
747 * **H3SK with a Kingfisher board** : `$ setenv load_dtb ext4load mmc 0:1 0x48000000 /boot/r8a7795-h3ulcb-kf.dtb`
749 * **M3SK with a Kingfisher board** : `$ setenv load_dtb ext4load mmc 0:1 0x48000000 /boot/r8a7796-m3ulcb-kf.dtb`
751 5. Save the boot environment:
764 ## 10. Troubleshooting
765 ### Logging Into the Console
767 Once the board boots, you should see the
768 [Wayland display](https://en.wikipedia.org/wiki/Wayland_(display_server_protocol))
769 on the external monitor.
770 A login prompt should appear as follows depending on your board:
775 Automotive Grade Linux ${AGL_VERSION} h3ulcb ttySC0
783 Automotive Grade Linux ${AGL_VERSION} m3ulcb ttySC0
788 At the prompt, login by using `root` as the login.
789 The password is "empty" so you should not be prompted for the password.
791 ### Determining the Board's IP Address
793 If your board is connected to a local network using Ethernet and
794 if a DHCP server is able to distribute IP addresses,
795 you can determine the board's IP address and log in using `ssh`.
799 Here is an example for the m3ulcb board:
804 Last login: Tue Dec 6 09:55:15 UTC 2016 on tty2
805 root@m3ulcb:~# ip -4 a
806 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
807 inet 127.0.0.1/8 scope host lo
808 valid_lft forever preferred_lft forever
809 3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
810 inet 10.0.0.27/24 brd 10.0.0.255 scope global eth0
811 valid_lft forever preferred_lft forever
819 In the previous example, IP address is 10.0.0.27.
820 Once you know the address, you can use `ssh` to login.
821 Following is an example that shows logging into SSH and then
822 displaying the contents of the `/etc/os-release` file:
827 Last login: Tue Dec 6 10:01:11 2016 from 10.0.0.13
828 root@m3ulcb:~# cat /etc/os-release
830 NAME="Automotive Grade Linux"
831 VERSION="3.0.0+snapshot-20161202 (chinook)"
832 VERSION_ID="3.0.0-snapshot-20161202"
833 PRETTY_NAME="Automotive Grade Linux 3.0.0+snapshot-20161202 (chinook)"
838 **NOTE:** More generics troubleshooting can be found here : [Generic issues](../troubleshooting.html)
840 ## 11. Supplementary Information
842 * R-Car Generation 3 Information
844 Refer to the following for more information from [eLinux website](https://elinux.org/R-Car).
846 * Proprietary libraries for meta-rcar-gen3
848 The meta-rcar-gen3 layer of meta-renesas is supported Graphic GLES(GSX)
849 libraries, proprietary library of multimedia, and ICCOM software.
851 1. Build with Renesas multimedia libraries
853 Multimedia portions depend on GLES portions.
855 * A. Configuration for Multimedia features
857 * Please copy proprietary libraries to the directory of recipes.
859 * Please set local.conf the following.
860 **Enable multimedia features. This provides package group of plug-ins of the GStreamer, multimedia libraries and kernel drivers.**
863 MACHINE_FEATURES_append = " multimedia"
866 * B. Configuration for optional codecs and middleware
868 * Please copy proprietary libraries to the directory of recipes.
870 * Add features to DISTRO_FEATURES_append to local.conf
874 **Additional configuration in OMX module**
878 " h263dec_lib" - for OMX Media Component H263 Decoder Library
879 " h264dec_lib" - for OMX Media Component H264 Decoder Library
880 " h264enc_lib" - for OMX Media Component H.264 Encoder Library
881 " h265dec_lib" - for OMX Media Component H265 Decoder Library
882 " mpeg2dec_lib" - for OMX Media Component MPEG2 Decoder Library
883 " mpeg4dec_lib" - for OMX Media Component MPEG4 Decoder Library
884 " vc1dec_lib" - for OMX Media Component VC-1 Decoder Library
885 " divxdec_lib" - for OMX Media Component DivX Decoder Library
886 " rvdec_lib" - for OMX Media Component RealVideo Decoder Library
887 " alacdec_lib" - for OMX Media Component ALAC Decoder Library
888 " flacdec_lib" - for OMX Media Component FLAC Decoder Library
889 " aaclcdec_lib" - for OMX Media Component AAC-LC Decoder Library
890 " aaclcdec_mdw" - for AAC-LC 2ch Decoder Middleware for Linux
891 " aacpv2dec_lib" - for OMX Media Component aacPlus V2 Decoder Library
892 " aacpv2dec_mdw" - for aacPlus V2 Decoder Middleware for Linux
893 " mp3dec_lib" - for OMX Media Component MP3 Decoder Library
894 " mp3dec_mdw" - for MP3 Decoder Middleware for Linux
895 " wmadec_lib" - for OMX Media Component WMA Standard Decoder Library
896 " wmadec_mdw" - for WMA Standard Decoder Middleware for Linux
897 " dddec_lib" - for OMX Media Component Dolby(R) Digital Decoder Library
898 " dddec_mdw" - for Dolby(R) Digital Decoder Middleware for Linux
899 " aaclcenc_lib" - for OMX Media Component AAC-LC Encoder Library
900 " vp8dec_lib" - for OMX Media Component VP8 Decoder Library for Linux
901 " vp8enc_lib" - for OMX Media Component VP8 Encoder Library for Linux
902 " vp9dec_lib" - for OMX Media Component VP9 Decoder Library for Linux
903 " aaclcenc_mdw" - for AAC-LC Encoder Middleware for Linux
904 " cmsbcm" - for CMS Basic Color Management Middleware for Linux
905 " cmsblc" - for CMS CMM3 Backlight Control Middleware for Linux
906 " cmsdgc" - for CMS VSP2 Dynamic Gamma Correction Middleware for Linux
907 " dtv" - for ISDB-T DTV Software Package for Linux
908 " dvd" - for DVD Core-Middleware for Linux
909 " adsp" - for ADSP driver, ADSP interface and ADSP framework for Linux
910 " avb" - for AVB Software Package for Linux
919 DISTRO_FEATURES_append = " h264dec_lib h265dec_lib mpeg2dec_lib aaclcdec_lib aaclcdec_mdw"
922 * C. Configuration for test packages
924 Must ensure that Multimedia features have been enabled.
925 (Please refer to III/A to enable Multimedia.)
927 * Please add feature to DISTRO_FEATURES_append to local.conf.
929 **Configuration for multimedia test package**
931 DISTRO_FEATURES_append = "mm-test"
934 2. Enable Linux ICCOM driver and Linux ICCOM library
937 For Linux ICCOM driver and Linux ICCOM library
939 * Please copy proprietary libraries to the directory of recipes.
941 * Please set local.conf the following.
944 DISTRO_FEATURES_append = "iccom"