R-Car/Boards/Spider

= Introduction =

This is the Wiki for the Renesas R-Car Spider board stack. It consists of: Refer to the R-Car page for information about Renesas' R-Car SoC family.
 * Spider CPU board equipped with R-Car S4-8 SoC (RTP8A779F0ASKB0SC2S),
 * Spider BreakOut board (RTP8A779F0ASKB0SB0S),
 * Spider Ethernet TSN sub-board (RTP8A779F0ASKB0ST0S).

= Hardware =

Type Name
RTP8A779F0ASKB0SP2SA080

Picture
The "Spider board" consists of a CPU board and a Breakout board. The CPU board is stuck on top of the Breakout board.

R-Car S4 SoC Documentation
https://www.renesas.com/us/en/products/automotive-products/automotive-system-chips-socs/r-car-s4-automotive-system-chip-soc-car-servercommunication-gateway#document
 * Soc

https://www.renesas.com/us/en/products/automotive-products/automotive-system-chips-socs/rtp8a779f0askb0sp2s-r-car-s4-reference-boardspider#document
 * Board documentation

= Quick Start How To = This sections describes steps that are necessary to boot Linux. And you will be able to run AWS IoT Greengrass and AWS IoT Fleetwise

Connect 12V Power supply to the board
Use 12 V power supply. There are sequences for turning on and off the power supply to the Spider board set. For the Spider board set, be sure to obey the notes below.

Note
 * When power is turned on
 * Be sure to confirm that the Power Switch (SW11) is off before plugging the AC adapter into the power source. It is prohibited to plug the AC adapter into a power source while the Power Switch (SW11) is on.
 * When power is shut off
 * Be sure to turn off the Power Switch (SW11) before unplugging the AC adapter from the power source. It is prohibited to unplug the AC adapter from the power source while the Power Switch (SW11) is on.

Connect to serial console
Use a microUSB cable to connect the PC to R-Car S4 Evaluation board(Spider) board. CN21 must be used on Spider side. It is routed to HSCIF0 in the R-Car S4 via a FT232 interface converter chip.

On Linux, FT232 driver is included with kernel versions >=2.6.12. Windows driver and sources can be found on FTDI Chip website.

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

On Linux:

picocom

sudo picocom -b 1843200 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   : 1843200 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.

Power on the board and go to U-Boot prompt
SW11 to switch the board on. Then you should see the following output in the terminal:

N:ICUMX Loader Rev.0.13.0 N:Built : 11:21:36, Aug 25 2022 N:PRR is R-Car S4 Ver1.1 N:Boot device is QSPI Flash(40MHz) N:LCM state is CM N:Normal boot(ICUMX) N:======== content cert info ======== destination address:0xfde30000 physical destination address:0xeb230000 source address:0x08240000 size:0x00001000 N:======== content of SA9 ======== address:0xeb231000 size:0x00009800 N:======== G4MH(1st) image load info ======== load address   = 0x10000000 image size     = 0x00100000 source address = 0x08900000 N:======== ICUMH image load info ======== load address   = 0x10500000 image size     = 0x00100000 source address = 0x08380000 N:======== G4MH(2nd) image load info ======== load address   = 0x10100000 image size     = 0x00100000 source address = 0x08a00000 N:BL2: DDR3200(rev.0.30rc7)N:BL2: [COLD_BOOT] N:..0 N:QoS setting(rev.0.02) N:DRAM refresh interval 1.91 usec N:Periodic Write DQ Training N:======== RTOS image load info ======== load address   = 0xe2100000 image size     = 0x00400000 source address = 0x08500000 N:======== Cx IPL image load info ======== load address   = 0xe6300000 image size     = 0x00030000 source address = 0x08480000 N:======== Secure FW image load info ======== load address   = 0xeb240000 image size     = 0x000bc000 source address = 0x08280000 N:CA55 Loader Program Rev.0.12.0 N:Built : 11:32:51, Aug 23 2022 N:PRR is R-Car S4 Ver.1.1 N:======== CA Program #1 image load info ======== N:load address = 0x46400000 image size     = 0x00022000 source address = (p:1)0x00e00000 N:======== CA Program #2 image load info ======== N:load address = 0x44100000 image size     = 0x00100000 source address = (p:1)0x00e80000 N:======== CA Program #3 image load info ======== N:load address = 0x50000000 image size     = 0x00200000 source address = (p:1)0x00f80000 N:Load finish.(CA55 Loader) N:Load finish. Dummy FW Program Dummy FW Program boot end U-Boot 2020.10 (Aug 29 2022 - 10:39:10 +0000) CPU: Renesas Electronics R8A779F0 rev 1.1 Model: Renesas Spider CPU and Breakout boards based on r8a779f0 DRAM: 3.4 GiB RAM Configuration: Bank #0: 0x048000000 - 0x09fffffff, 1.4 GiB Bank #1: 0x480000000 - 0x4ffffffff, 2 GiB MMC:  mmc@ee140000: 0 Loading Environment from SPIFlash... SF: Detected s25fs512s with page size 256 Bytes, erase size 256 KiB, total 64 MiB *** Warning - bad CRC, using default environment In:   serial@e6540000 Out:  serial@e6540000 Err:  serial@e6540000 Net: Dummy RTOS Program Dummy RTOS Program boot end Error: ethernet@e68c0000 address not set. No ethernet found. Hit any key to stop autoboot: 0

Quickly hit any key to get into U-boot command prompt. Use SW9 ("Reset") to reboot the board when necessary. You should see the following:

Hit any key to stop autoboot: 0 =>

= Booting Linux =


 * Kernel config: defconfig
 * Kernel image: arch/arm64/boot/Image
 * DTB: arch/arm64/boot/dts/renesas/r8a779f0-spider.dtb

U-Boot boot command: tftpboot 0x48080000 Image tftpboot 0x48000000 r8a779f0-spider.dtb booti 48080000 - 0x48000000

= After Boot Unix = Enjoy!!

AWS IoT Green Grass
Please refer to this page.

AWS IoT Fleetwise
Please refer to this page.