Difference between revisions of "R-Car/Boards/SILK"

From eLinux.org
Jump to: navigation, search
m (Introduction)
(Quick Start How To: Added minicom)
Line 59: Line 59:
 
Refer to [[R-Car/Boards/Yocto]] for steps necessary for making a Yocto image.
 
Refer to [[R-Car/Boards/Yocto]] for steps necessary for making a Yocto image.
  
=== Connect 5 V power source to R-Car E2 SILK board ===
+
=== Connect 5 V power supply ===
 
Use 5 V power supply with a 5.5 mm barrel plug. The power supply should be able to provide '''TBD''' Amps.
 
Use 5 V power supply with a 5.5 mm barrel plug. The power supply should be able to provide '''TBD''' Amps.
  
=== Connect to serial console over microUSB ===
+
=== Connect to serial console ===
 
Use a microUSB cable to connect the PC to R-Car E2 SILK board. CN13 ("DEBUG") must be used on SILK side. It is routed to SCIF2 in the R-Car E2 via a CP2102 interface converter chip.
 
Use a microUSB cable to connect the PC to R-Car E2 SILK board. CN13 ("DEBUG") must be used on SILK side. It is routed to SCIF2 in the R-Car E2 via a CP2102 interface converter chip.
  
On Linux, CP2102 driver is included with kernel versions >=2.6.12. Windows driver and sources can be found at [http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Silicon Labs website].
+
On Linux, CP2102 driver is included with kernel versions >=2.6.12. Windows driver and sources can be found on [http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx Silicon Labs website].
  
Serial settings are 38400 8N1.
+
Serial settings are 38400 8N1. Any standard terminal emulator program can be used.  
  
On Linux, a popular terminal emulator program called [https://code.google.com/p/picocom/ picocom] can be used (or alternatives, like minicom)
+
On Linux:
 +
 
 +
===== [https://code.google.com/p/picocom/ picocom] =====
 
<pre>
 
<pre>
 
sudo picocom -b 38400 DEVICE
 
sudo picocom -b 38400 DEVICE
Line 98: Line 100:
 
</pre>
 
</pre>
 
Use Ctrl+A, Ctrl+Q to exit picocom.
 
Use Ctrl+A, Ctrl+Q to exit picocom.
 +
 +
===== [https://alioth.debian.org/projects/minicom/ minicom] =====
 +
<pre>
 +
sudo minicom -b 38400 -D DEVICE
 +
</pre>
 +
replace DEVICE with the proper tty device name, for example '''/dev/ttyUSB0'''. Running '''dmesg | tail''' can help locating proper device.<br/>
 +
After the successful connection, minicom should display:
 +
<pre class="bash">
 +
Welcome to minicom 2.6.2
 +
 +
OPTIONS: I18n
 +
Compiled on Aug  7 2013, 13:32:48.
 +
Port /dev/ttyUSB0
 +
 +
Press CTRL-A Z for help on special keys
 +
</pre>
 +
Use Ctrl+A, Q to exit minicom.
  
 
== Bootcode ==
 
== Bootcode ==

Revision as of 03:30, 3 February 2015

Introduction

This is the official Wiki for Renesas R-Car E2 SILK board.

Refer to R-Car page for Renesas R-Car SoC family. Information on Renesas R-Car M2 Porter board is on a separate page.

Hardware

Top view
For more information go to R-Car/Boards/SILK:Hardware

Hardware Features

  • R-Car E2 SoC
    • ARM®Cortex-A7 Dual Core
    • SH-4A core (optional)
    • GPU: PowerVR SGX540
    • Various hardware IP blocks for video and audio processing
  • 1 GB DDR3 memory
  • Two SPI flash memory chips (selected by SW9)
    • 4 MB
    • 64 MB
  • 8GB eMMC chip MTFC8GLWDQ-3M AIT Z
  • WiFi+Bluetooth module
  • Audio codec: AK4643EN
    • Line In 3.5 mm jack
    • LineOut 3.5 mm jack
  • HDMI type A output
    • Max. resolutions support TBD
  • LCD connector (bottom side)
  • VGA output (DB-15F)
  • Analog Video In: ADV7180WBCP32Z Video Decoder
    • RCA jack
    • NTSC/PAL/SECAM autodetection
  • Two USB 2.0 ports
    • One USB type A connector can be switched to Host or Function mode by SW10
  • I2C EEPROM (Renesas R1EX24002ATAS0)
  • Dialog Semiconductor DA9063 Power Regulator
  • Power supply: 5V, TBD Amps
  • Dimensions: 140x120 mm

Where to buy

TBD

List here distributors that sell SILK board

R-Car E2 SoC Documentation

TBD At the moment just block diagram reference is available http://am.renesas.com/applications/automotive/cis/cis_highend/rcar_e2/index.jsp

TBD Add here link to public R-Car E2 datasheet

Official SILK board documentation

The manual is available for download from File:R-Car E2 Application Development Board HardwareManual.pdf

Quick Start How To

This sections describes steps that are necessary to run a "Hello, World!" application using Yocto build. Both X11 and Wayland are supported.

Build Yocto image

Refer to R-Car/Boards/Yocto for steps necessary for making a Yocto image.

Connect 5 V power supply

Use 5 V power supply with a 5.5 mm barrel plug. The power supply should be able to provide TBD Amps.

Connect to serial console

Use a microUSB cable to connect the PC to R-Car E2 SILK board. CN13 ("DEBUG") must be used on SILK side. It is routed to SCIF2 in the R-Car E2 via a CP2102 interface converter chip.

On Linux, CP2102 driver is included with kernel versions >=2.6.12. Windows driver and sources can be found on Silicon Labs website.

Serial settings are 38400 8N1. Any standard terminal emulator program can be used.

On Linux:

picocom
sudo picocom -b 38400 DEVICE

replace DEVICE with the proper tty device name, for example /dev/ttyUSB0. Running dmesg | tail can help locating proper device.
After the successful connection, picocom should display:

picocom v1.7

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 38400
parity is      : none
databits are   : 8
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,

Terminal ready

Use Ctrl+A, Ctrl+Q to exit picocom.

minicom
sudo minicom -b 38400 -D DEVICE

replace DEVICE with the proper tty device name, for example /dev/ttyUSB0. Running dmesg | tail can help locating proper device.
After the successful connection, minicom should display:

Welcome to minicom 2.6.2

OPTIONS: I18n 
Compiled on Aug  7 2013, 13:32:48.
Port /dev/ttyUSB0

Press CTRL-A Z for help on special keys

Use Ctrl+A, Q to exit minicom.

Bootcode

R-Car E2 SoC can be booted various sources. SILK board is booted from QSPI Flash device. SILK has two SPI Flash memory chips selectable by SW9. In a standard configuration 4MB Flash S25FL032 stores original MiniMonitor firmware (for backup/rescue purposes) and 64 MB FLash S25FL512 stores MiniMonitor (QSPI Loader) and U-Boot (main storage).

Updating U-Boot using MiniMonitor

You may want to update U-Boot in case of upgrade or if the board you received does not have the U-Boot flashed. Follow these steps carefully to flash U-Boot:

  1. Set SW9 to 3 pin side. This selects 4MB SPI Flash with MiniMonitor as boot device/active QSPI flash
    Switch pin layout
    MiniMonitor is loaded via SPI boot interface of R-Car E2.
  2. Connect to serial console over microUSB. Start picocom with the following command line options:
    sudo picocom -b 38400 --send-cmd "ascii-xfr -vvs" /dev/ttyUSBnn
    
  3. Switch the board ON or reset it.
    You should see the following output on the console (version numbers can be different):
    SILK SPI_LOADER V0.05 2014.08.14
    DEVICE S25FL032
      
    SILK MiniMonitor SPI_BOOT
    Work memory DRAM (H'40200000-) 
    2014.08.15 Ver0.05 ** Program on DRAM (H'40000000-)  ** 
    
    >
    
  4. Execute the ls command:
    ls
    

    You should be able to see the following output:

    Load Program to Spiflash memory (U6:S25FL512S)
    SW9 1pin-Side! Setting OK? (Push Y key)
    

    MiniMonitor is asking to flip SW9 to 1 pin side.

  5. Switch SW9 to 1 pin side. This activates 64MB SPI Flash for U-Boot.
    Switch pin layout
  6. Enter y to confirm your setting.
  7. MiniMonitor should ask now:
    Select area(1-2)> 
    

    Answer 2 and Enter.

  8. Mini monitor should display:
    Please Input User Program Start Address :
    

    Enter e6304000 for R-Car E2 and hit Enter.

  9. MiniMonitor should now display:
    Please send ! ('.' & CR stop load)
    

    Use Ctrl+A, Ctrl+S, then select uboot.srec file and hit Enter.
    uboot.srec should be available in $WORK/build/tmp/deploy/images/silk/ folder which is generated by bitbake.

  10. Transmission should start immediately and the progress counter should be displayed:
    *** file: /data/Renesas/SILK/build/tmp/deploy/images/silk/u-boot.srec
    ascii-xfr -vvs /data/Renesas/SILK/build/tmp/deploy/images/silk/u-boot.srec 
    ASCII upload of "/data/Renesas/SILK/build/tmp/deploy/images/silk/u-boot.srec"
    
    15.0 Kbytes transferred at 3732 CPS...
    
  11. If there are some data in writing area, MiniMonitor will display:
    SPI Data Clear(H'FF) Check :H'0080000-00BFFFF Clear OK?(y/n)
    

    You can safely input "y" to override area 2 of 64MB SPI Flash.

  12. After writing is complete, MiniMonitor should display
    658.0 Kbytes transferred at 3850 CPS... Done.
    
    *** exit status: 0
    SPI Data Clear(H'FF) Check : OK 
    SAVE SPI-FLASH....... complete!
    -- Save (Program Start Address & Size ) -----
    SPI Data Clear(H'FF):H'040000-07FFFF Erasing..Erase Completed 
    SAVE SPI-FLASH....... complete!
    
    ==========  SPI Flash Sector1 Save Information  =========
     Program Start Address :  H'E6304000
     Program Size          :  H'00036D44
    =========================================================
    
  13. Reboot R-Car E2 SILK board by pressing SW5 "Reset" button. Leave SW9 on 1 pin side.
    You should see U-Boot prompt now.
    SILK SPI_LOADER V0.05 2014.08.14
    DEVICE S25FL512
    
    
    U-Boot 2013.01.01-g74b16ba-dirty (Dec 10 2014 - 16:16:57)
    
    CPU: Renesas Electronics R8A7794 rev 1.0
    Board: Silk Board
    
    DRAM:  1 GiB
    MMC:   sh_mmcif: 0, sh-sdhi: 1
    SF: Detected S25FL512S with page size 256 KiB, total 64 MiB
    In:    serial
    Out:   serial
    Err:   serial
    Net:   sh_eth
    Hit any key to stop autoboot: 3
    

Booting over TFTP from U-Boot

Linux Kernel can be booted over TFTP from U-Boot. You can specify kernel cmdline to mount rootfs image over NFS.

  1. Setup a tftp server.
    TBD. Instructions could be different for various host environments

    Fedora

  2. Make sure SW9 is on pin 1 side.
    Switch pin layout
  3. Connect to serial console over microUSB. Start picocom with the following command line options:
    sudo picocom -b 38400 /dev/ttyUSBnn
    
  4. Switch the board ON or reset it.
    You should see the following output on the console (version numbers can be different):
    >>>>>>>>>>>>>>>>>>TBD<<<<<<<<<<<<<<<<<<<<<<<<
    
  5. Type the following commands to prepare the environment:
    setenv ethaddr xx:xx:xx:xx:xx:xx
    setenv ipaddr 192.168.1.10
    setenv serverip 192.168.1.1
    

    Replace xx:xx:xx:xx:xx:xx with the MAC address of your board. It should be on the sticker on top of the Ethernet port.
    Set proper ip for the board and for the server. You can also use

    dhcp
    

    command to obtain information from DHCP server.

  6. Set Kernel cmdline to mount rootfs over NFS
    setenv bootargs root=/dev/nfs rw nfsroot=192.168.1.1:/opt/dev/silkrootfs ip=192.168.1.10
    TBD
    
  7. Load the kernel
    setenv bootcmd 'tftp 0x40007fc0 uImage; tftp 0x40f00000 r8a7794-silk.dtb; bootm 0x40007fc0 - 0x40f00000'
    
  8. Running Yocto

    Refer to R-Car/Boards/Yocto for making Yocto build

    FAQ

    Operating systems/distributions can be used on R-Car E2 SILK boards?

    It known to run

    • Yocto, Android, Tizen (supported)
    • Buildroot (experimental)
    • Ubuntu (unsupported)