GDP-ivi8

Historical information, may be outdated & incorrect

Quick Start

The Genivi Demo Platform repo utilises git-submodules and source scripts to automate the configuration of the required repository build layers. Although this does not fully automate the process, the use of it is advised especially for those wanting to get up and running quickly.

GDP-ivi7

Historical information, may be outdated & incorrect

Introduction

The purpose of this document is to explain how to quickly setup the hardware and install the GENIVI Demo Platform (GDP) on the Renesas R-Car M2 Koelsch Board. Since the Renesas R-Car M2 Porter Board (low cost board) is very similar, these instructions apply to the Porter board as well.

R-Car M2 Koelsch System Evaluation Board

Please refer link for detailed hardware specifications.

Software setup

Pre-built binaries

Renesas partners can obtain pre-built binaries from the Renesas Genivi BSP Maintainer Stephen Lawrence

Quick Start

The Genivi Demo Platform repo utilises git-submodules and source scripts to automate the configuration of the required repository build layers. Allthough this does not fully automate the process, the use of it is advised especially for those wanting to get up and running quickly.

1. Install the required development tools on the host by executing the following command.

   $ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-dev xterm

2. Create a directoy for the GDP sources

   $ mkdir GDP
   $ cd GDP
   

3. Clone genivi demo platform using the recursion on Koelsh / Porter branch (specifiy with -b)

   $ git clone --recursive http://git.projects.genivi.org/genivi-demo-platform.git -b koelsch

4. Obtain and Install Renesas Graphics Drivers (section header below)
5. Initialise build environment

   $ cd $HOME/GDP/genivi-demo-platform
   $ source init.sh
   

6. Bitbake the image

   $ bitbake genivi-demo-platform

7. Once built, Setup Hardware & Deploy (section header below)

Obtain and Install Renesas Graphics Drivers

M2 Porter low cost board

The graphics and multimedia acceleration packages for the M2 Porter and E2 Silk low cost boards can be downloaded directly from here via a "click through" license. Note that these easy access drivers have a time limit- the OpenGL and H.264 codec library stop drawing after 3 hours uptime, which freezes the system. Drivers without this limit are available from Renesas marketing.

The download consists of the following two ZIP files, which can be found under the links for "download Multimedia and Graphics library" and "download related Linux drivers":

• r-car_series_evaluation_software_package_for_linux-20150515.zip (MD5 Sum: bcca2517afdd2c3bd8bf4c2cb0a64d06)
• r-car_series_evaluation_software_package_of_linux_drivers-20150515.zip (MD5 Sum: e1e83ce1882c48faedcc02adc9853e17)

Follow the following steps to integrate the drivers into the Renesas BSP Yocto layers:

1. Unzip the two downloads into a folder. In this example a temporary directory is used.

   $ cd $HOME/GDP
   $ mkdir binary-tmp
   $ <unzip the two downloads into binary-tmp>
   

   After this step there should be two files in binary-tmp:

   R-Car_Series_Evaluation_Software_Package_for_Linux-*.tar.gz
   R-Car_Series_Evaluation_Software_Package_of_Linux_Drivers-*.tar.gz
   

2. Populate meta-renesas with the graphics acceleration drivers.

   cd $HOME/GDP/meta-renesas/meta-rcar-gen2
   ./copy_gfx_software_<board>.sh ../../binary-tmp
   

3. Populate meta-renesas with the multimedia acceleration drivers.

   cd $HOME/GDP/meta-renesas/meta-rcar-gen2
   ./copy_mm_software_lcb.sh ../../binary-tmp
   

4. Optionally remove the temporary directory

   $ rm -r ../../binary-tmp
   

   The copy scripts locate the needed parts from the archives in the temporary directory and copies them into the required location in the BSP layers.

M2 Koelsch evaluation board

If you do not already have it as part of a working relationship with Renesas, the R-Car M2 graphics driver can be obtained by contacting Renesas.

Integration of the driver into the Renesas BSP Yocto layers is described in step 5, "copy proprietary software into recipe directory structure", of section 3, "Building Instructions" of the BSP Yocto Start-Up Guide. The Start-Up Guide can be found in the root of the BSP delivery.

For simplicity the steps are summarised here.

• Using the copy script provided in the BSP delivery.

1. Copy the graphics driver deliverables into a folder. In this example a temporary directory is used.

   $ cd $HOME/GDP
   $ mkdir binary-tmp
   $ cp <storage media>/<binary deliverables> binary-tmp
   

2. The copy script locates the needed parts from the directory and copies them into the required location in the BSP layers.

   $ sh <path to Renesas BSP>/copy_proprietary_softwares-v1*.sh binary-tmp
   

3. Optionally remove the temporary directory

   $ rm -r binary-tmp
   

Equipment Setup

Software prerequisites

Binary GENIVI Demo Platform image

1. In case you build from source, you should find the binaries in the following directory.
   • for koelsch board:

   $ cd $HOME/GDP/gdp-src-build/tmp/deploy/images/koelsch/
   

   • for porter board:

   $ cd $HOME/GDP/gdp-src-build/tmp/deploy/images/porter/
   

Hardware prerequisites

1. Renesas Koelsch or Porter Board
2. AC adapter
3. USB Cable (A-microB Cable)
4. LAN Cable
5. Stereo speaker with 3.5 stereo connector (known to work reference)
6. USB hub (known to work reference)
7. Touchscreen monitor with HDMI connector (known to work reference) (A non touchscreen monitor paired with a USB mouse can also be used)
8. Ethernet switch (known to work reference)
9. LAN cable (2)
10. Keyboard (known to work reference)
11. 16GB SD-card
12. Second 16GB (or less) SD-card for Last User Mode feature
13. HDMI Cable (known to work reference)

You also need a Personal Computer running Ubuntu Linux 14.04 LTS (x86_64). The computer should be capable to format, read, write and erase SD-Cards, connect to the wired and the wireless local area network and has at least one free USB 2.0 compatible port.

Connect Devices

• Follow these images

• Example of device connection

• Focus on Koelsch board connection

Connecting the PC and the Koelsch|Porter Board

To access the shell (serial)

1. With the Koelsch board powered off, connect the 'Debug Serial 0' port on the board (for Porter mini-USB port close to on/off switch) with the host PC using the USB cable.
2. Start a terminal emulator, such as 'minicom' or 'picocom', on the host, connecting to the USB serial port (/dev/ttyUSB0) with 38400, 8n1 settings.
   Please refer KOELSCH_MiniMonitor_Manual(SPI_Boot)_Rev2.01_e.pdf (CD contents of Development KIT) for detailed descriptions.
3. Power on the Koelsch|Porter board to see a shell on the console.

Peripherals

• Plugin one end of the LAN cable into the Ethernet switch
• Plugin the other end of the same LAN cable into the Renesas Koelsch|Porter board.
• Plugin one end of a second LAN cable into the Ethernet switch
• Plugin the other end of the same LAN cable into the Personal Computer running Ubuntu Linux 14.04.
• Switch off the power for the Koelsch|Porter board and connect the remaining peripherals using common sense.

Deployment

Deployment (SDCARD)

On the host

• Create EXT3 partition on the SD-card.

• Mount the SD-Card partition under /media/$SDCARD_LABEL.
  Note: Please replace $SDCARD_LABEL with the path to where the SD-card was mounted.
• Copy the GENIVI Demo Platform files onto the SD-card.

1. Go to your build directory or go to directory for downloaded images If you build from source code, for koelsch:

   $ cd $BUILDDIR/tmp/deploy/images/koelsch 
   

   If you build from source code, for porter:

   $ cd $BUILDDIR/tmp/deploy/images/porter 
   

2. Extract the root file system archive into the SD-card.
   • For Koelsch board:

   $ sudo tar --extract --numeric-owner --preserve-permissions --preserve-order --totals \
              --directory=/media/$SDCARD_LABEL --file=genivi-demo-platform-koelsch.tar.bz2 

   • For Porter board:

   $ sudo tar --extract --numeric-owner --preserve-permissions --preserve-order --totals \
              --directory=/media/$SDCARD_LABEL --file=genivi-demo-platform-porter.tar.bz2 

3. Copy Kernel Image and Device Tree Blob file into the /boot directory of the SD-card.
   • For Koelsch board:

   $ sudo cp uImage uImage-r8a7791-koelsch.dtb /media/$SDCARD_LABEL/boot 

   • For Porter board:

   $ sudo cp uImage uImage-r8a7791-porter.dtb /media/$SDCARD_LABEL/boot 

   Note: you may need to execute rm /media/$SDCARD_LABEL/boot/uImage* before this.

4. After the copy finished, unmount the SD-Card and insert the card into the SD0 slot of the Renesas board.

On the target board

It is assumed that the Renesas Koelsch|Porter board already running u-boot as second stage boot loader.

Change U-Boot parameters to boot from SD card

1. Power up the board and, using your preferred terminal emulator, stop the board's autoboot and run the following 'print' commands to check environment.

   => print 

   Please check if you have environment variables called baudrate and ethaddr.
   In case not, a baud rate that is known to work is 38400.
2. Then set the follow environment variables and save them
   • For koelsch board:

   => setenv bootargs_console 'console=ttySC6,${baudrate}'
   => setenv bootargs_video 'vmalloc=384M video=HDMI-A-1:1024x768-32@60'
   => setenv bootcmd_sd 'ext4load mmc 0:1 0x40007fc0 boot/uImage;ext4load mmc 0:1 0x40f00000 boot/uImage-r8a7791-koelsch.dtb'
   => setenv bootcmd 'setenv bootargs ${bootargs_console} ${bootargs_video} root=/dev/mmcblk0p1 rw rootfstype=ext3;run bootcmd_sd;bootm 0x40007fc0 - 0x40f00000'
   => saveenv
   

   • For porter board:

   => setenv bootargs_console console=ttySC6,${baudrate}
   => setenv bootargs_video vmalloc=384M video=HDMI-A-1:1024x768-32@60
   => setenv bootcmd_sd 'ext4load mmc 0:1 0x40007fc0 boot/uImage;ext4load mmc 0:1 0x40f00000 boot/uImage-r8a7791-porter.dtb'
   => setenv bootcmd 'setenv bootargs ${bootargs_console} ${bootargs_video} root=/dev/mmcblk0p1 rw rootfstype=ext3;run bootcmd_sd;bootm 0x40007fc0 - 0x40f00000'
   => saveenv
   

Boot from SD card

1. After board reset, U-Boot is started and after a countdown, ...
   Linux boot messages should be displayed. Please login after the Linux boot messages passed.
2. To login use these credentials: User - root / Password - root
3. After boot, the launcher will start automatically the Genivi Demo Platform via HDMI on the Touchscreen monitor.

Use Last User Mode

• By using Last User Mode feature, the Genivi Demo Platform state will be saved on reboot or shutdown and after boot, the demo will return to the stored state.
• To use this feature you need to create an EXT3 partition on a second SD-card (or micro-SD for Porter board) and insert it in SD1 slot of the Renesas board.
• To remove this feature, you simply need to unplug this second SD card from the slot.

Deployment (TFTP)

Loading kernel via TFTP and rootfs via NFS Follow these steps to setup working TFTP and NFS server: http://www.elinux.org/R-Car/Boards/Yocto#Running_Yocto_image

Network Setup

This section describes how to set the Board can access the internet via the development host.

On the Board

• Assume your board is connected to an isolated network without DHCP,
  Please refer 'Network Environment' of Connect Devices

1. Connect the Board with serial line, Please refer To access the shell (Serial)
2. Edit '/var/lib/connman/ethernet_<MAC_Address>_cable/settings' ( <MAC_Address> will be different )
   • In this case, The Board's Static IP address is 192.168.1.2, and Gateway (HOST PC) IP address is 192.168.1.1, You can change dnsserver to other public Nameserver instead of 8.8.8.8
   • Please add following lines

   IPv4.method=manual
   IPv4.netmask_prefixlen=24
   IPv4.local_address=192.168.1.2
   IPv4.gateway=192.168.1.1
   Nameservers=8.8.8.8;
   

   • For example, 'settings' file will be

   root@koelsch:~# cat /var/lib/connman/ethernet_010203040506_cable/settings 
   [ethernet_010203040506_cable]
   Name=Wired
   AutoConnect=true
   Modified=1970-01-01T00:00:12.002051Z
   IPv4.method=manual
   IPv4.netmask_prefixlen=24
   IPv4.local_address=192.168.1.2
   IPv4.gateway=192.168.1.1
   Nameservers=8.8.8.8;
   IPv6.method=off
   IPv6.privacy=disabled
   

3. Reboot board

   root@koelsch:~# shutdown -r now
   

4. You can use the 'ifconfig' command to get IP information.
   • [inet addr] - indicates the Board's IP address, in this example IP address is 192.168.1.2

   root@koelsch:~# ifconfig
   eth0      Link encap:Ethernet  HWaddr 01:02:03:04:05:06  
             inet addr:192.168.1.2  Bcast:192.168.0.255  Mask:255.255.255.0
             UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
             RX packets:36867 errors:0 dropped:5407 overruns:0 frame:0
             TX packets:73 errors:0 dropped:0 overruns:0 carrier:0
             collisions:0 txqueuelen:1000 
             RX bytes:3731515 (3.5 MiB)  TX bytes:10636 (10.3 KiB)
             Interrupt:194 DMA chan:ff 
   
   lo        Link encap:Local Loopback  
             inet addr:127.0.0.1  Mask:255.0.0.0
             UP LOOPBACK RUNNING  MTU:65536  Metric:1
             RX packets:0 errors:0 dropped:0 overruns:0 frame:0
             TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
             collisions:0 txqueuelen:0 
             RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
   

On the Host PC

You will need two network connections.
One network connects to the Internet(WAN). In this example this network is WLAN.
The other network (eth0) connects to switch (internal network). Please refer Connect Devices

1. Configuration 'eth0' Network Interface
   1. If you are using Ubuntu Desktop edition, Please enter [System Setting] - [Network] - [Wired connection] - [Options]
   2. Go to 'IPv4 Settings' tab
   3. Change Address to these value 'IP: 192.168.1.1 / netmask: 255.255.255.0 / Gateway 192.168.1.1'
2. Enable IP forwarding
   Open /etc/sysctl.conf file, and uncomment following line.

   # net.ipv4.ip forward=1

3. Enable IP Masquerading
   Enter following commands on the shell.

   $ sudo iptables -t nat -A POSTROUTING -o wlan -j MASQUERADE
   $ sudo iptables -A FORWARD -i wlan -o eth0 -m state -–state RELATED,ESTABLISHED -j ACCEPT
   $ sudo iptables -A FORWARD -i eth0 -o wlan -j ACCEPT
   

4. Save IP tables rules

   $ iptables-save > /etc/iptables.rules 

5. Run ping command on the Board

   root@koelsch:~# ping -c 3 genivi.org

To access the shell (ssh)

• Please run following command on your HOST PC.

192.168.1.2 is your Board's IP address and to login use this credential : Password - root

$ ssh root@192.168.1.2

Automated test

The Renesas GDP build contains a small python-uinput based script used for testing stability over long periods of time. The script uses a virtual mouse to click parts of the screen in sequence, on a loop.

To use this test:

1. Ensure the GDP HMI is running - this will most likely be a simple matter of turning on the device.
2. Ensure uinput is working by checking whether '/dev/uinput' or '/dev/input/uinput' exist.
3. From a shell, run

   gdp-hmi-mouse-test.py

4. If you would like it running in the background, so you can log out of the shell, you can instead run

   nohup gdp-hmi-mouse-test.py> mouse-test.log 2>&1 &

Limitations and Known Issues

1. [Instability] HMI sometimes has input issues. Cursor is displayed badly and can't select controls.
   • Details in Bugzilla – Bug 349
2. [Limitation] FSA not yet integrated.
   • Details in Bugzilla – Bug 355