Renesas Koelsch Hardware Setup and Software Installation

Transcription

1 Renesas Koelsch Hardware Setup and Software Installation Table of content Introduction Master GDP-ivi10 GDP-ivi9 GDP-ivi7 Software setup Pre-built binaries Quick Start Obtain and Install Renesas Graphics Drivers M2 Porter low cost board M2 Koelsch evaluation board Equipment Setup Software prerequisites Hardware prerequisites Connect Devices Connecting the PC and the Koelsch Porter Board To access the shell (serial) Peripherals Deployment Deployment (SDCARD) On the host On the target board Change U-Boot parameters to boot from SD card Boot from SD card Use Last User Mode Deployment (TFTP) Network Setup On the Board On the Host PC To access the shell (ssh) Automated test Limitations and Known Issues 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.

2 R-Car M2 Koelsch System Evaluation Board: Please refer link for detailed hardware specifications. Master Please follow the Koelsch instructions in the GDP Master page to build the GDP-ivi10 tag of the Master branch on the Renesas M2 Koelsch board. GDP-ivi10 Please follow the Koelsch instructions in the GDP Master page to build GDP-ivi10 on the Renesas M2 Koelsch board. GDP-ivi9 Renesas Koelsch is currently unsupported in GDP-ivi9 If you are interested in contributing to support it, please contact the GDP Delivery team. GDP-ivi7 Software setup Pre-built binaries Renesas partners can obtain pre-built binaries from the Renesas Genivi BSP Maintainer Stephen Lawrence

3 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 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 libsdl2-dev xterm Create a directory for the GDP sources $ mkdir GDP $ cd GDP Clone genivi demo platform using the recursion on Koelsh / Porter branch (specifiy with -b) $ git clone --recursive -b koelsch Obtain and Install Renesas Graphics Drivers (see below) Initialise build environment $ cd $HOME/GDP/genivi-demo-platform $ source init.sh Bitbake the image $ bitbake genivi-demo-platform 7. Once built, Setup Hardware & Deploy (see 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 zip (MD5 Sum: bcca2517afdd2c3bd8bf4c2cb0a64d06) r-car_series_evaluation_software_package_of_linux_drivers zip (MD5 Sum: e1e83ce1882c48faedcc02adc9853e17) Follow the following steps to integrate the drivers into the Renesas BSP Yocto layers: 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 Populate meta-renesas with the graphics acceleration drivers. cd $HOME/GDP/meta-renesas/meta-rcar-gen2./copy_gfx_software_<board>.sh../../binary-tmp Populate meta-renesas with the multimedia acceleration drivers. cd $HOME/GDP/meta-renesas/meta-rcar-gen2./copy_mm_software_lcb.sh../../binary-tmp 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. Alternatively the drivers can be copied manually 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.

4 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. 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 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 Optionally remove the temporary directory $ rm -r binary-tmp Alternatively the drivers can be copied manually Equipment Setup Software prerequisites Binary GENIVI Demo Platform image 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 Renesas Koelsch or Porter Board AC adapter USB Cable (A-microB Cable) LAN Cable Stereo speaker with 5 stereo connector ( known to work reference) USB hub ( known to work reference) Touchscreen monitor with HDMI connector ( known to work reference) (A non touchscreen monitor paired with a USB mouse can also be used) Ethernet switch ( known to work reference) LAN cable (2) Keyboard ( known to work reference) 16GB SD-card Second 16GB (or less) SD-card for Last User Mode feature HDMI Cable ( known to work reference) You also need a Personal Computer running Ubuntu Linux 104 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 0 compatible port. Connect Devices Follow these images

5 Example of device connection

6 Focus on Koelsch board connection

7 Connecting the PC and the Koelsch Porter Board To access the shell (serial) 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. 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)_Rev01_e.pdf (CD contents of Development KIT) for detailed descriptions. 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 10 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.

8 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 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 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. 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 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 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 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. To login use these credentials: User - root / Password - root 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.

9 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: /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 Connect the Board with serial line, Please refer To access the shell (Serial) Edit '/var/lib/connman/ethernet_<mac_address>_cable/settings' ( <MAC_Address> will be different ) In this case, The Board's Static IP address is , and Gateway (HOST PC) IP address is , You can change dnsserver to other public Nameserver instead of Please add following lines IPvmethod=manual IPvnetmask_prefixlen=24 IPvlocal_address= IPvgateway= Nameservers= ; For example, 'settings' file will be root@koelsch:~# cat /var/lib/connman/ethernet_ _cable/settings [ethernet_ _cable] Name=Wired AutoConnect=true Modified= T00:00: Z IPvmethod=manual IPvnetmask_prefixlen=24 IPvlocal_address= IPvgateway= Nameservers= ; IPv6.method=off IPv6.privacy=disabled Reboot board root@koelsch:~# shutdown -r now You can use the 'ifconfig' command to get IP information. [inet addr] - indicates the Board's IP address, in this example IP address is root@koelsch:~# ifconfig eth0 Link encap:ethernet HWaddr 01:02:03:04:05:06 inet addr: Bcast: Mask: 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: (5 MiB) TX bytes:10636 (10.3 KiB) Interrupt:194 DMA chan:ff lo Link encap:local Loopback inet addr: Mask: 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

10 Configuration 'eth0' Network Interface 5. If you are using Ubuntu Desktop edition, Please enter [System Setting] - [Network] - [Wired connection] - [Options] Go to 'IPv4 Settings' tab Change Address to these value 'IP: / netmask: / Gateway ' Enable IP forwarding Open /etc/sysctl.conf file, and uncomment following line. # net.ipvip forward=1 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 Save IP tables rules $ iptables-save > /etc/iptables.rules 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 is your Board's IP address and to login use this credential : Password - root $ ssh root@ 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: Ensure the GDP HMI is running - this will most likely be a simple matter of turning on the device. Ensure uinput is working by checking whether '/dev/uinput' or '/dev/input/uinput' exist. From a shell, run gdp-hmi-mouse-test.py 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 [Instability] HMI sometimes has input issues. Cursor is displayed badly and can't select controls. Details in Bugzilla Bug 349 [Limitation] FSA not yet integrated. Details in Bugzilla Bug 355