Talk:R-Car/Boards/Yocto-Gen3

From eLinux.org
Jump to: navigation, search

AGL7.0 Home screen NOT displayed

Hello.

I have encountered a problem with running AGL7.0 Guppy on R-Car Starter Kit Premier.
Although Linux is successfully booted up and I can login to the shell, the home screen is not displayed on the monitor which is connected to SK's micro HDMI port. (the monitor does not receive any signal at all from its HDMI input port)

I basically followed the instructions below and added agl-html5-framework feature in addition to agl-devel agl-demo agl-netboot agl-appfw-smack agl-localdev which are listed in the instruction.
And I also made changes in U-Boot environment as this page's thread "AGL 6.0.0 booting on R-Car H3 not completed". (bootargs and load_dtb).

http://docs.automotivelinux.org/next/docs/en/guppy/getting_started/reference/getting-started/machines/renesas.html

I will really appreciate it if anyone give me advises for solving this problem.

Boot log is shown below.

 [    0.000161] NOTICE:  BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.21
 [    0.005726] NOTICE:  BL2: PRR is R-Car H3 Ver.2.0
 [    0.010395] NOTICE:  BL2: Board is Starter Kit Rev.1.0
 [    0.015507] NOTICE:  BL2: Boot device is HyperFlash(80MHz)
 [    0.020932] NOTICE:  BL2: LCM state is CM
 [    0.024972] NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x53
 [    0.030962] NOTICE:  BL2: DDR3200(rev.0.33)NOTICE:  [COLD_BOOT]NOTICE:  ..0
 [    0.067520] NOTICE:  BL2: DRAM Split is 4ch
 [    0.071402] NOTICE:  BL2: QoS is default setting(rev.0.19)
 [    0.076845] NOTICE:  BL2: DRAM refresh interval 1.95 usec
 [    0.082263] NOTICE:  BL2: Lossy Decomp areas
 [    0.086436] NOTICE:       Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
 [    0.093521] NOTICE:       Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
 [    0.100433] NOTICE:       Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
 [    0.107347] NOTICE:  BL2: v1.4(release):15dba6b-dirty
 [    0.112356] NOTICE:  BL2: Built : 10:37:56, Apr  8 2019
 [    0.117543] NOTICE:  BL2: Normal boot
 [    0.121189] NOTICE:  BL2: dst=0xe6322300 src=0x8180000 len=512(0x200)
 [    0.127572] NOTICE:  BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)
 [    0.134192] NOTICE:  BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
 [    0.141422] NOTICE:  BL2: dst=0x44100000 src=0x8200000 len=1048576(0x100000)
 [    0.156245] NOTICE:  BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)
 
 
 U-Boot 2015.04 (Apr 08 2019 - 09:51:12)
 
 CPU: Renesas Electronics R8A7795 rev 2.0
 Board: H3ULCB
 I2C:   ready
 DRAM:  3.9 GiB
 Bank #0: 0x048000000 - 0x07fffffff, 896 MiB
 Bank #1: 0x500000000 - 0x53fffffff, 1 GiB
 Bank #2: 0x600000000 - 0x63fffffff, 1 GiB
 Bank #3: 0x700000000 - 0x73fffffff, 1 GiB
 
 Flash: 64 MiB
 MMC:   sh-sdhi: 0, sh-sdhi: 1
 In:    serial
 Out:   serial
 Err:   serial
 Net:   Board Net Initialization Failed
 No ethernet found.
 Hit any key to stop autoboot:  0
 19558912 bytes read in 4620 ms (4 MiB/s)
 71610 bytes read in 23 ms (3 MiB/s)
 ## Flattened Device Tree blob at 48000000
    Booting using the fdt blob at 0x48000000
    Using Device Tree in place at 0000000048000000, end 00000000480147b9
 
 Starting kernel ...
 
 [    0.000000] Booting Linux on physical CPU 0x0
 [    0.000000] Linux version 4.14.35-yocto-standard (oe-user@oe-host) (gcc version 7.3.0 (GCC)) #1 SMP PREEMPT Mon Apr 8 06:29:46 UTC 2019
 [    0.000000] Boot CPU: AArch64 Processor [411fd073]
 [    0.000000] Machine model: Renesas H3ULCB board based on r8a7795 ES1.x
 [    0.000000] debug: ignoring loglevel setting.
 [    0.000000] efi: Getting EFI parameters from FDT:
 [    0.000000] efi: UEFI not found.
 [    0.000000] Reserved memory: created CMA memory pool at 0x0000000057000000, size 400 MiB
 [    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
 [    0.000000] Reserved memory: created CMA memory pool at 0x0000000070000000, size 256 MiB
 [    0.000000] OF: reserved mem: initialized node linux,multimedia, compatible id shared-dma-pool
 [    0.000000] NUMA: No NUMA configuration found
 [    0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x000000073fffffff]
 [    0.000000] NUMA: NODE_DATA [mem 0x73ff94b80-0x73ff9667f]
 [    0.000000] Zone ranges:
 [    0.000000]   DMA      [mem 0x0000000048000000-0x00000000ffffffff]
 [    0.000000]   Normal   [mem 0x0000000100000000-0x000000073fffffff]
 [    0.000000] Movable zone start for each node
 [    0.000000] Early memory node ranges
 [    0.000000]   node   0: [mem 0x0000000048000000-0x0000000053ffffff]
 [    0.000000]   node   0: [mem 0x0000000057000000-0x000000007fffffff]
 [    0.000000]   node   0: [mem 0x0000000500000000-0x000000053fffffff]
 [    0.000000]   node   0: [mem 0x0000000600000000-0x000000063fffffff]
 [    0.000000]   node   0: [mem 0x0000000700000000-0x000000073fffffff]
 [    0.000000] Initmem setup node 0 [mem 0x0000000048000000-0x000000073fffffff]
 [    0.000000] On node 0 totalpages: 1003520
 [    0.000000]   DMA zone: 3392 pages used for memmap
 [    0.000000]   DMA zone: 0 pages reserved
 [    0.000000]   DMA zone: 217088 pages, LIFO batch:31
 [    0.000000]   Normal zone: 12288 pages used for memmap
 [    0.000000]   Normal zone: 786432 pages, LIFO batch:31
 [    0.000000] psci: probing for conduit method from DT.
 [    0.000000] psci: PSCIv1.0 detected in firmware.
 [    0.000000] psci: Using standard PSCI v0.2 function IDs
 [    0.000000] psci: Trusted OS resident on physical CPU 0x0
 [    0.000000] psci: SMC Calling Convention v1.1
 [    0.000000] random: fast init done
 [    0.000000] percpu: Embedded 23 pages/cpu @ffff8006ffed7000 s55576 r8192 d30440 u94208
 [    0.000000] pcpu-alloc: s55576 r8192 d30440 u94208 alloc=23*4096
 [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
 [    0.000000] Detected PIPT I-cache on CPU0
 [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 987840
 [    0.000000] Policy zone: Normal
 [    0.000000] Kernel command line: console=ttySC0,115200 ignore_loglevel vmalloc=384M video=HDMI-A-1:1920x1080-32@60 root=/dev/mmcblk0p1 rw rootfstype=ext4 rootwait rootdelay=2
 [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
 [    0.000000] software IO TLB [mem 0x4ffff000-0x53fff000] (64MB) mapped at [ffff80000ffff000-ffff800013ffefff]
 [    0.000000] Memory: 3190004K/4014080K available (11324K kernel code, 1244K rwdata, 5332K rodata, 1152K init, 422K bss, 152332K reserved, 671744K cma-reserved)
 [    0.000000] Virtual kernel memory layout:
 [    0.000000]     modules : 0xffff000000000000 - 0xffff000008000000   (   128 MB)
 [    0.000000]     vmalloc : 0xffff000008000000 - 0xffff7dffbfff0000   (129022 GB)
 [    0.000000]       .text : 0xffff000008080000 - 0xffff000008b90000   ( 11328 KB)
 [    0.000000]     .rodata : 0xffff000008b90000 - 0xffff0000090d0000   (  5376 KB)
 [    0.000000]       .init : 0xffff0000090d0000 - 0xffff0000091f0000   (  1152 KB)
 [    0.000000]       .data : 0xffff0000091f0000 - 0xffff000009327200   (  1245 KB)
 [    0.000000]        .bss : 0xffff000009327200 - 0xffff000009390b50   (   423 KB)
 [    0.000000]     fixed   : 0xffff7dfffe7f9000 - 0xffff7dfffec00000   (  4124 KB)
 [    0.000000]     PCI I/O : 0xffff7dfffee00000 - 0xffff7dffffe00000   (    16 MB)
 [    0.000000]     vmemmap : 0xffff7e0000000000 - 0xffff800000000000   (  2048 GB maximum)
 [    0.000000]               0xffff7e0000200000 - 0xffff7e001c000000   (   446 MB actual)
 [    0.000000]     memory  : 0xffff800008000000 - 0xffff800700000000   ( 28544 MB)
 [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
 [    0.000000] Preemptible hierarchical RCU implementation.
 [    0.000000]  RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=8.
 [    0.000000]  Tasks RCU enabled.
 [    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
 [    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
 [    0.000000] GIC: Adjusting CPU interface base to 0x00000000f102f000
 [    0.000000] GIC: Using split EOI/Deactivate mode
 [    0.000000] arch_timer: cp15 timer(s) running at 8.33MHz (phys).
 [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1ec02923e, max_idle_ns: 440795202125 ns
 [    0.000003] sched_clock: 56 bits at 8MHz, resolution 120ns, wraps every 2199023255496ns
 [    0.000339] Console: colour dummy device 80x25
 [    0.000378] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.66 BogoMIPS (lpj=33333)
 [    0.000387] pid_max: default: 32768 minimum: 301
 [    0.000430] Security Framework initialized
 [    0.000440] Smack:  Initializing.
 [    0.000443] Smack:  IPv6 port labeling enabled.
 [    0.002001] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
 [    0.002792] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
 [    0.002836] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
 [    0.002866] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
 [    0.015958] ASID allocator initialised with 32768 entries
 [    0.023951] Hierarchical SRCU implementation.
 [    0.032423] Detected Renesas R-Car Gen3 r8a7795 ES2.0
 [    0.033545] EFI services will not be available.
 [    0.039974] smp: Bringing up secondary CPUs ...
 [    0.068145] Detected PIPT I-cache on CPU1
 [    0.068183] CPU1: Booted secondary processor [411fd073]
 [    0.096158] Detected PIPT I-cache on CPU2
 [    0.096176] CPU2: Booted secondary processor [411fd073]
 [    0.124190] Detected PIPT I-cache on CPU3
 [    0.124208] CPU3: Booted secondary processor [411fd073]
 [    0.152231] CPU features: enabling workaround for ARM erratum 845719
 [    0.152238] Detected VIPT I-cache on CPU4
 [    0.152273] CPU4: Booted secondary processor [410fd034]
 [    0.180252] Detected VIPT I-cache on CPU5
 [    0.180274] CPU5: Booted secondary processor [410fd034]
 [    0.208283] Detected VIPT I-cache on CPU6
 [    0.208304] CPU6: Booted secondary processor [410fd034]
 [    0.236316] Detected VIPT I-cache on CPU7
 [    0.236337] CPU7: Booted secondary processor [410fd034]
 [    0.236407] smp: Brought up 1 node, 8 CPUs
 [    0.236429] SMP: Total of 8 processors activated.
 [    0.236435] CPU features: detected feature: 32-bit EL0 Support
 [    0.236439] CPU features: detected feature: Kernel page table isolation (KPTI)
 [    0.242529] CPU: All CPU(s) started at EL2
 [    0.242550] alternatives: patching kernel code
 [    0.243108] devtmpfs: initialized
 [    0.248109] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
 [    0.248163] futex hash table entries: 2048 (order: 6, 262144 bytes)
 [    0.256042] pinctrl core: initialized pinctrl subsystem
 [    0.257385] DMI not present or invalid.
 [    0.257631] NET: Registered protocol family 16
 [    0.258973] cpuidle: using governor menu
 [    0.259164] vdso: 2 pages (1 code @ ffff000008b96000, 1 data @ ffff0000091f5000)
 [    0.259175] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
 [    0.259791] DMA: preallocated 256 KiB pool for atomic allocations
 [    0.260017] Serial: AMBA PL011 UART driver
 [    0.263521] sh-pfc e6060000.pin-controller: r8a77951_pfc support registered
 [    0.280499] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
 [    0.281488] ACPI: Interpreter disabled.
 [    0.283467] rcar-avs: use avs value: 0
 [    0.283531] rcar-avs: /cpus/cpu@0 is running with: /opp_table0
 [    0.283540] rcar-avs: /cpus/cpu@1 is running with: /opp_table0
 [    0.283547] rcar-avs: /cpus/cpu@2 is running with: /opp_table0
 [    0.283554] rcar-avs: /cpus/cpu@3 is running with: /opp_table0
 [    0.283569] rcar-avs: /soc/gsx@fd000000 is running with: /gsx_opp_table0
 [    0.284815] vgaarb: loaded
 [    0.284972] SCSI subsystem initialized
 [    0.285092] libata version 3.00 loaded.
 [    0.285262] usbcore: registered new interface driver usbfs
 [    0.285290] usbcore: registered new interface driver hub
 [    0.285339] usbcore: registered new device driver usb
 [    0.286212] i2c-sh_mobile e60b0000.i2c: I2C adapter 7, bus speed 400000 Hz
 [    0.286525] media: Linux media interface: v0.10
 [    0.286549] Linux video capture interface: v2.00
 [    0.286609] pps_core: LinuxPPS API ver. 1 registered
 [    0.286612] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
 [    0.286624] PTP clock support registered
 [    0.286857] EDAC MC: Ver: 3.0.0
 [    0.287021] dmi: Firmware registration failed.
 [    0.287822] Advanced Linux Sound Architecture Driver Initialized.
 [    0.288076] NetLabel: Initializing
 [    0.288082] NetLabel:  domain hash size = 128
 [    0.288085] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
 [    0.288122] NetLabel:  unlabeled traffic allowed by default
 [    0.288389] clocksource: Switched to clocksource arch_sys_counter
 [    0.288492] VFS: Disk quotas dquot_6.6.0
 [    0.288526] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
 [    0.288624] pnp: PnP ACPI: disabled
 [    0.292639] NET: Registered protocol family 2
 [    0.293103] TCP established hash table entries: 32768 (order: 6, 262144 bytes)
 [    0.293323] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
 [    0.293600] TCP: Hash tables configured (established 32768 bind 32768)
 [    0.293720] UDP hash table entries: 2048 (order: 4, 65536 bytes)
 [    0.293786] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
 [    0.293945] NET: Registered protocol family 1
 [    0.294173] RPC: Registered named UNIX socket transport module.
 [    0.294179] RPC: Registered udp transport module.
 [    0.294182] RPC: Registered tcp transport module.
 [    0.294186] RPC: Registered tcp NFSv4.1 backchannel transport module.
 [    0.294194] PCI: CLS 0 bytes, default 128
 [    0.295066] hw perfevents: enabled with armv8_cortex_a57 PMU driver, 7 counters available
 [    0.295311] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
 [    0.295611] kvm [1]: 8-bit VMID
 [    0.296481] kvm [1]: vgic interrupt IRQ1
 [    0.296594] kvm [1]: Hyp mode initialized successfully
 [    0.298243] audit: initializing netlink subsys (disabled)
 [    0.298320] audit: type=2000 audit(0.291:1): state=initialized audit_enabled=0 res=1
 [    0.298579] workingset: timestamp_bits=44 max_order=20 bucket_order=0
 [    0.301676] squashfs: version 4.0 (2009/01/31) Phillip Lougher
 [    0.302008] NFS: Registering the id_resolver key type
 [    0.302027] Key type id_resolver registered
 [    0.302030] Key type id_legacy registered
 [    0.302039] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
 [    0.302153] 9p: Installing v9fs 9p2000 file system support
 [    0.303592] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
 [    0.303600] io scheduler noop registered
 [    0.303701] io scheduler cfq registered (default)
 [    0.303706] io scheduler mq-deadline registered
 [    0.303710] io scheduler kyber registered
 [    0.309980] gpio_rcar e6050000.gpio: driving 16 GPIOs
 [    0.310196] gpio_rcar e6051000.gpio: driving 28 GPIOs
 [    0.310399] gpio_rcar e6052000.gpio: driving 15 GPIOs
 [    0.310612] gpio_rcar e6053000.gpio: driving 16 GPIOs
 [    0.310813] gpio_rcar e6054000.gpio: driving 18 GPIOs
 [    0.311007] gpio_rcar e6055000.gpio: driving 26 GPIOs
 [    0.311208] gpio_rcar e6055400.gpio: driving 32 GPIOs
 [    0.311403] gpio_rcar e6055800.gpio: driving 4 GPIOs
 [    0.330185] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
 [    0.331737] SuperH (H)SCI(F) driver initialized
 [    0.332150] e6e88000.serial: ttySC0 at MMIO 0xe6e88000 (irq = 139, base_baud = 0) is a scif
 [    1.421607] console [ttySC0] enabled
 [    1.425906] msm_serial: driver initialized
 [    1.431015] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    1.437635] [drm] No driver support for vblank timestamp query.
 [    1.444070] rcar-dw-hdmi fead0000.hdmi: Detected HDMI TX controller v2.01a with HDCP (DWC HDMI 2.0 TX PHY)
 [    1.453906] rcar-dw-hdmi fead0000.hdmi: registered DesignWare HDMI I2C bus driver
 [    1.467965] brd: module loaded
 [    1.475104] loop: module loaded
 [    1.490544] libphy: Fixed MDIO Bus: probed
 [    1.494893] tun: Universal TUN/TAP device driver, 1.6
 [    1.500977] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
 [    1.506814] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
 [    1.512762] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
 [    1.519722] igb: Copyright (c) 2007-2014 Intel Corporation.
 [    1.525314] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k
 [    1.533142] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
 [    1.539375] sky2: driver version 1.30
 [    1.543779] ravb e6800000.ethernet: no valid MAC address supplied, using a random one
 [    1.551668] libphy: ravb_mii: probed
 [    1.556513] ravb e6800000.ethernet eth0: Base address at 0xe6800000, 16:20:6c:d7:26:9c, IRQ 136.
 [    1.565824] VFIO - User Level meta-driver version: 0.3
 [    1.572018] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
 [    1.578550] ehci-pci: EHCI PCI platform driver
 [    1.583016] ehci-platform: EHCI generic platform driver
 [    1.588514] ehci-platform ee0a0100.usb: EHCI Host Controller
 [    1.594186] ehci-platform ee0a0100.usb: new USB bus registered, assigned bus number 1
 [    1.602151] ehci-platform ee0a0100.usb: irq 146, io mem 0xee0a0100
 [    1.620397] ehci-platform ee0a0100.usb: USB 2.0 started, EHCI 1.10
 [    1.626919] hub 1-0:1.0: USB hub found
 [    1.630684] hub 1-0:1.0: 1 port detected
 [    1.634869] ehci-orion: EHCI orion driver
 [    1.639021] ehci-exynos: EHCI EXYNOS driver
 [    1.643290] ehci-msm: Qualcomm On-Chip EHCI Host Controller
 [    1.648938] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
 [    1.655131] ohci-pci: OHCI PCI platform driver
 [    1.659612] ohci-platform: OHCI generic platform driver
 [    1.665006] ohci-platform ee0a0000.usb: Generic Platform OHCI controller
 [    1.671716] ohci-platform ee0a0000.usb: new USB bus registered, assigned bus number 2
 [    1.679616] ohci-platform ee0a0000.usb: irq 146, io mem 0xee0a0000
 [    1.774650] hub 2-0:1.0: USB hub found
 [    1.778413] hub 2-0:1.0: 1 port detected
 [    1.782540] ohci-exynos: OHCI EXYNOS driver
 [    1.787219] usbcore: registered new interface driver usb-storage
 [    1.793280] usbcore: registered new interface driver usbserial
 [    1.799131] usbcore: registered new interface driver usbserial_generic
 [    1.805672] usbserial: USB Serial support registered for generic
 [    1.814089] i2c /dev entries driver
 [    1.824815] cs2000-cp 2-004f: revision - C1
 [    1.829065] i2c-rcar e6510000.i2c: probed
 [    1.837639] i2c-rcar e66d8000.i2c: probed
 [    1.842151] usbcore: registered new interface driver i2c-tiny-usb
 [    1.849517] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    1.857531] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    1.864808] imr fe860000.imr0: IMR device (pdev: -1) registered as /dev/video0
 [    1.872241] imr fe870000.imr1: IMR device (pdev: -1) registered as /dev/video1
 [    1.879686] imr fe880000.imr2: IMR device (pdev: -1) registered as /dev/video2
 [    1.887103] imr fe890000.imr3: IMR device (pdev: -1) registered as /dev/video3
 [    1.896853] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    1.904865] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    1.912480] rcar_gen3_thermal e6198000.thermal: is using pseudo fixed FUSE values
 [    1.924605] rcar_gen3_thermal e6198000.thermal: TSC0: Loaded 1 trip points
 [    1.935724] rcar_gen3_thermal e6198000.thermal: TSC1: Loaded 1 trip points
 [    1.946786] rcar_gen3_thermal e6198000.thermal: TSC2: Loaded 3 trip points
 [    1.955932] sdhci: Secure Digital Host Controller Interface driver
 [    1.962119] sdhci: Copyright(c) Pierre Ossman
 [    1.966966] renesas_sdhi_internal_dmac ee100000.sd: Got CD GPIO
 [    1.973104] Synopsys Designware Multimedia Card Interface Driver
 [    1.979860] sdhci-pltfm: SDHCI platform and OF driver helper
 [    1.986901] ledtrig-cpu: registered to indicate activity on CPUs
 [    1.993872] usbcore: registered new interface driver usbhid
 [    1.999448] usbhid: USB HID core driver
 [    2.004160] optee: probing for conduit method from DT.
 [    2.009504] R-Car Rev.1.0.8
 [    2.012585] optee: initialized driver
 [    2.017494] usbcore: registered new interface driver snd-usb-audio
 [    2.032174] rcar_sound ec500000.sound: probed
 [    2.036828] NET: Registered protocol family 17
 [    2.041351] 9pnet: Installing 9P2000 support
 [    2.045664] Key type dns_resolver registered
 [    2.050389] registered taskstats version 1
 [    2.059274] thermal emergency: set temperature to 110 celsius
 [    2.065132] thermal emergency: shutdown target cpus 1-7
 [    2.070360] thermal emergency: freq scaled target cpus 0
 [    2.075951] renesas_irqc e61c0000.interrupt-controller: driving 6 irqs
 [    2.083667] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    2.090288] [drm] No driver support for vblank timestamp query.
 [    2.097834] bd9571mwv 7-0030: Device: BD9571MWV rev. 4
 [    2.106501] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    2.114514] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    2.121858] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    2.129875] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    2.138130] renesas_sdhi_internal_dmac ee100000.sd: Got CD GPIO
 [    2.204556] renesas_sdhi_internal_dmac ee100000.sd: mmc0 base at 0xee100000 max clock rate 200 MHz
 [    2.214922] asoc-simple-card sound: ak4613-hifi <-> ec500000.sound mapping ok
 [    2.222069] asoc-simple-card sound: ASoC: no DMI vendor name!
 [    2.230113] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    2.236736] [drm] No driver support for vblank timestamp query.
 [    2.243646] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    2.251676] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    2.259979] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    2.269020] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    2.277828] input: keyboard as /devices/platform/keyboard/input/input0
 [    2.285064] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    2.288475] hctosys: unable to open rtc device (rtc0)
 [    2.288885] ALSA device list:
 [    2.288887]   #0: Loopback 1
 [    2.288888]   #1: ak4613
 [    2.302593] usb 2-1: new full-speed USB device number 2 using ohci-platform
 [    2.312156] [drm] No driver support for vblank timestamp query.
 [    2.313147] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    2.313153] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    2.313413] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    2.313416] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    2.347893] Waiting 2 sec before mounting root device...
 [    2.557972] mmc0: new ultra high speed SDR104 SDHC card at address aaaa
 [    2.562026] input: ILITEK Multi-Touch-V3004 as /devices/platform/soc/ee0a0000.usb/usb2/2-1/2-1:1.0/0003:222A:0088.0001/input/input1
 [    2.562124] hid-multitouch 0003:222A:0088.0001: input: USB HID v1.10 Device [ILITEK Multi-Touch-V3004] on usb-ee0a0000.usb-1/input0
 [    2.562830] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    2.562832] [drm] No driver support for vblank timestamp query.
 [    2.563731] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    2.563738] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    2.563992] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    2.563996] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    2.568435] hid-generic 0003:222A:0088.0002: device has no listeners, quitting
 [    2.568966] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    2.568967] [drm] No driver support for vblank timestamp query.
 [    2.569661] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    2.569666] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    2.569910] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    2.569913] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    2.679926] mmcblk0: mmc0:aaaa SM32G 29.7 GiB
 [    2.686201]  mmcblk0: p1
 [    2.689480] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    2.696097] [drm] No driver support for vblank timestamp query.
 [    2.702853] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    2.710866] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    2.718094] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    2.726101] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    4.384422] md: Skipping autodetection of RAID arrays. (raid=autodetect will force)
 [    4.419655] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
 [    4.427773] VFS: Mounted root (ext4 filesystem) on device 179:1.
 [    4.434544] devtmpfs: mounted
 [    4.438086] Freeing unused kernel memory: 1152K
 [    4.819530] systemd[1]: Successfully loaded Smack policies.
 [    4.828363] systemd[1]: Successfully loaded Smack/CIPSO policies.
 [    4.835877] systemd[1]: System time before build time, advancing clock.
 [    4.875296] NET: Registered protocol family 10
 [    4.880426] Segment Routing with IPv6
 [    4.888486] systemd[1]: Relabelled /dev and /run in 2.512ms.
 [    4.933639] systemd[1]: systemd 234 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN default-hierarchy=hybrid)
 [    4.954674] systemd[1]: Detected architecture arm64.
 
 Welcome to Automotive Grade Linux 7.0.0+snapshot-20190409 (guppy)!
 
 [    4.977001] systemd[1]: Set hostname to <h3ulcb>.
 [    5.270305] systemd[1]: Reached target Swap.
 [  OK  ] Reached target Swap.
 [    5.288655] systemd[1]: Listening on Network Service Netlink Socket.
 [  OK  ] Listening on Network Service Netlink Socket.
 [    5.308544] systemd[1]: Listening on Journal Audit Socket.
 [  OK  ] Listening on Journal Audit Socket.
 [    5.328491] systemd[1]: Listening on udev Kernel Socket.
 [  OK  ] Listening on udev Kernel Socket.
 [    5.348533] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
 [  OK  ] Started Forward Password Requests to Wall Directory Watch.
 [    5.372541] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
 [  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
 [    5.400431] systemd[1]: Listening on Process Core Dump Socket.
 [  OK  ] Listening on Process Core Dump Socket.
 [  OK  ] Started Dispatch Password Requests to Console Directory Watch.
 [  OK  ] Reached target Paths.
 [  OK  ] Listening on Journal Socket (/dev/log).
 [  OK  ] Listening on Journal Socket.
 [  OK  ] Reached target Remote File Systems.
 [  OK  ] Created slice User and Session Slice.
 [  OK  ] Listening on udev Control Socket.
 [  OK  ] Created slice System Slice.
 [  OK  ] Reached target Slices.
          Starting Load Kernel Modules...
 [  OK      5.565412] mostcore: loading out-of-tree module taints kernel.
 0m] Created slic[    5.573039] mostcore: init()
 e system-getty.slice.
 [    5.578681] aim_cdev: init()
 [    5.581895] mostcore: registered new application interfacing module cdev
 [    5.590559] mostcore: registered new application interfacing module networking
 [    5.599450] aim_sound: init()
 [    5.602471] mostcore: registered new application interfacing module sound
 [    5.611614] mostcore: registered new application interfacing module v4l
 [  OK  ] Created slice system-afm\x2duser\x2dsession.slice.
 [    5.627757] usbcore: registered new interface driver hdm_usb
 [    5.636541] rgnmm_drv mmngr: assigned reserved memory node linux,multimedia
 [  OK  ] Created slice system-serial\x2dgetty.slice.
          Mounting Kernel Debug File System...
          Starting Remount Root and Kernel File Systems...
 [    5.697788] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
          Mounting POSIX Message Queue File System...
 [  OK  ] Listening on Syslog Socket.
          Starting Journal Service...
 [    5.737606] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    5.744239] [drm] No driver support for vblank timestamp query.
 [    5.751646] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    5.759717] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    5.767561] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    5.775582] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    5.783176] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    5.789825] [drm] No driver support for vblank timestamp query.
 [    5.791274] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    5.791282] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
          Starting Create list of required st…ce nodes for the current kernel...
          Starting Setup Virtual Console...
          Mounting Temporary Directory (/tmp)...
          Mounting Huge Pages File System...
 [  OK  ] Mounted Kernel Debug File System.
 [  OK  ] Mounted POSIX Message Queue File System.
 [    5.903129] pvrsrvkm fd000000.gsx: opp[1/4]: (200000000 Hz, 830000 uV)
 [    5.909701] pvrsrvkm fd000000.gsx: opp[2/4]: (300000000 Hz, 830000 uV)
 [    5.916277] pvrsrvkm fd000000.gsx: opp[3/4]: (400000000 Hz, 830000 uV)
 [    5.922851] pvrsrvkm fd000000.gsx: opp[4/4]: (600000000 Hz, 830000 uV)
 [    5.930165] [drm] Initialized pvr 1.9.4991288 20110701 for fd000000.gsx on minor 0
 [    5.938515] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    5.946541] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [  OK      5.953880] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 0m] Mounted Huge[    5.961589] [drm] No driver support for vblank timestamp query.
  Pages File System.
 [    5.969902] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    5.978717] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [  OK  ] Mounted Temporary Directory (/tmp).
 [    6.001392] AVIRT: core: Alsa Virtual Sound Driver avirt-0.0.1
 [    6.008368] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    6.013705] AVIRT: core: Registered new Audio Path: Loopback Audio Path
 [    6.023021] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    6.030490] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    6.031089] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 617: -2
 [    6.031095] uvcs fe8df000.vcp4: failed to add to PM domain a3vc: -2
 [    6.031127] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 616: -2
 [    6.031131] uvcs fe8ff000.vcp4: failed to add to PM domain a3vc: -2
 [    6.065800] [drm] No driver support for vblank timestamp query.
 [    6.066949] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    6.066955] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    6.067239] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    6.067242] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    6.068363] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    6.068364] [drm] No driver support for vblank timestamp query.
 [  OK  ] Started Journal Service.
 [  OK  ] Started Remount Root and Kernel File Systems.
 [  OK  ] Started Create list [    6.148424] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 of required sta瞼    6.157470] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 ・ice nodes for[    6.157714] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 629: -2
  the current ker[    6.157719] vspm-vsp fe9c0000.vspm: failed to add to PM domain a3vp: -2
 nel.
 [    6.158107] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 117: -2
 [    6.158111] vspm-fdp fe948000.fdpm: failed to add to PM domain a3vp: -2
 [    6.199034] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    6.207050] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    6.214396] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    6.221021] [drm] No driver support for vblank timestamp query.
 [    6.227880] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 629: -2
 [    6.235904] vspm-vsp fe9c0000.vspm: failed to add to PM domain a3vp: -2
 [  OK      6.243182] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 117: -2
 0m] Started Setu[    6.251977] vspm-fdp fe948000.fdpm: failed to add to PM domain a3vp: -2
 p Virtual Consol[    6.260291] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 e.
 [    6.269367] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
          Starting udev Coldplug all Devices...
 [    6.294904] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    6.302951] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
          Starting Create Static D[    6.311183] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 evice Nodes in /[    6.319270] [drm] No driver support for vblank timestamp query.
 dev...
 [    6.327985] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 629: -2
 [    6.336024] vspm-vsp fe9c0000.vspm: failed to add to PM domain a3vp: -2
 [    6.343466] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 117: -2
 [    6.351503] vspm-fdp fe948000.fdpm: failed to add to PM domain a3vp: -2
 [    6.358828] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    6.366858] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    6.374520] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    6.382563] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    6.383676] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    6.383678] [drm] No driver support for vblank timestamp query.
 [    6.384988] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 629: -2
 [    6.384995] vspm-vsp fe9c0000.vspm: failed to add to PM domain a3vp: -2
 [    6.385359] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 117: -2
 [    6.385364] vspm-fdp fe948000.fdpm: failed to add to PM domain a3vp: -2
 [    6.385631] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    6.385635] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    6.385928] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    6.385931] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
          Starting Flush Journal to Persistent Storage...
 [FAILED] Failed to start Load Kernel Modules.
 See 'systemctl status systemd-modules-load.service' for details.
 [DEPEND] Dependency failed for Driver configuration for Unicens2.
 [  OK  ] Started Create Static Device Nodes in /dev.
 [  OK  ] Reached target Local File Systems (Pre).
          Mounting /var/volatile...
          Starting udev Kernel Device Manager...
          Mounting Kernel Configuration File System...
          Starting Apply Kernel Variables...
 [  OK  ] Mounted Kernel Configuration File System.
 [  OK  ] Mounted /var/volatile.
 [    6.671222] systemd-journald[1983]: Received request to flush runtime journal from PID 1
          Starting Load/Save Random Seed...
 [  OK  ] Reached target Local File Systems.
 [  OK  ] Started Flush Journal to Persistent Storage.
 [  OK  ] Started udev Coldplug all Devices.
 [  OK  ] Started Apply Kernel Variables.
 [  OK  ] Started Load/Save Random Seed.
 [  OK  ] Started udev Kernel Device Manager.
 [  OK  ] Found device /dev/ttySC0.
          Starting Setup Virtual Console...
          Starting Load Kernel Modules...
 [    7.222742] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 617: -2
 [    7.231662] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    7.231665] [drm] No driver support for vblank timestamp query.
 [    7.244962] uvcs fe8df000.vcp4: failed to add to PM domain a3vc: -2
 [    7.244976] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 629: -2
 [    7.244981] vspm-vsp fe9c0000.vspm: failed to add to PM domain a3vp: -2
 [    7.245765] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 117: -2
 [    7.245769] vspm-fdp fe948000.fdpm: failed to add to PM domain a3vp: -2
 [    7.246057] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    7.246061] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    7.246341] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    7.246345] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    7.310250] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 616: -2
 [    7.318275] uvcs fe8ff000.vcp4: failed to add to PM domain a3vc: -2
          Starting Create Volatile Files and Directories...
 [  OK  ] Started Setup Virtual Console.
 [FAILED] Failed to start Load Kernel Modules.
 See 'systemctl status systemd-modules-load.service' for details.
 [    7.438340] random: crng init done
          Starting Load Kernel Modules...
 [    7.457284] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    7.457454] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 617: -2
 [    7.457462] uvcs fe8df000.vcp4: failed to add to PM domain a3vc: -2
 [    7.457498] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 616: -2
 [    7.457502] uvcs fe8ff000.vcp4: failed to add to PM domain a3vc: -2
 [    7.492658] [drm] No driver support for vblank timestamp query.
 [    7.494214] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 629: -2
 [    7.494222] vspm-vsp fe9c0000.vspm: failed to add to PM domain a3vp: -2
 [    7.494741] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 117: -2
 [    7.494746] vspm-fdp fe948000.fdpm: failed to add to PM domain a3vp: -2
 [    7.495060] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 600: -2
 [    7.495065] rcar-fcp fea3f000.fcp: failed to add to PM domain always-on: -2
 [    7.495451] renesas-cpg-mssr e6150000.clock-controller: Cannot get module clock 620: -2
 [    7.495456] vsp1 fea38000.vsp: failed to add to PM domain always-on: -2
 [    7.497747] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
 [    7.497749] [drm] No driver support for vblank timestamp query.
          Starting Setup Virtual Console...
 [  OK  ] Started Create Volatile Files and Directories.
 [FAILED] Failed to start Load Kernel Modules.
 See 'systemctl status systemd-modules-load.service' for details.
 [  OK  ] Started Setup Virtual Console.
          Starting Start Psplash Boot Screen...
          Starting Update UTMP about System Boot/Shutdown...
 [  OK  ] Started Start Psplash Boot Screen.
 [  OK  ] Started Update UTMP about System Boot/Shutdown.
 [  OK  ] Reached target System Initialization.
 [  OK  ] Listening on GPS (Global Positioning System) Daemon Sockets.
 [  OK  ] Listening on D-Bus System Message Bus Socket.
          Starting sshd.socket.
 [  OK  ] Started Daily Cleanup of Temporary Directories.
          Starting cynara-monitor-get.socket.
 [  OK  ] Started dnf makecache timer.
 [  OK  ] Started dnf-automatic-download timer.
 [  OK  ] Listening on security-manager.socket.
 [  OK  ] Listening on cynara.socket.
 [  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
 [  OK  ] Listening on cynara-admin.socket.
          Starting cynara-agent.socket.
          Starting Network Service...
 [  OK  ] Started dnf-automatic-install timer.
 [  OK  ] Listening on afm-system-daemon.socket.
 [  OK  ] Started dnf-automatic-notifyonly timer.
 [  OK  ] Reached target Timers.
 [  OK  ] Listening on sshd.socket.
 [  OK  ] Listening on cynara-monitor-get.socket.
 [  OK  ] Listening on cynara-agent.socket.
 [  OK  ] Reached target cynara sockets.
 [  OK  ] Reached target Sockets.
 [  OK  ] Reached target Basic System.
          Starting Terminate Psplash Boot Screen...
          Starting Save/Restore Sound Card State...
          Starting User Mode Init Manager for TI shared transport...
 [  OK  ] Started D-Bus System Message Bus.
 [    8.282253] Bluetooth: Core ver 2.22
 [    8.285923] NET: Registered protocol family 31
 [    8.290386] Bluetooth: HCI device and connection manager initialized
 [    8.296758] Bluetooth: HCI socket layer initialized
 [    8.301650] Bluetooth: L2CAP socket layer initialized
 [    8.306726] Bluetooth: SCO socket layer initialized
          Starting Connection service...
          Starting Cynara service...
 [  OK  ] Started Hardware RNG Entropy Gatherer Daemon.
          Starting PowerVR consumer services...
          Starting neard service...
          Starting Avahi mDNS/DNS-SD Stack...
 [  OK  ] Reached target Containers.
          Starting Login Service...
          Starting Initiate afm-system-setup...
          Starting Telephony service...
 [  OK  ] Started System Logging Service.
 [  OK  ] Started Kernel Logging Service.
          Starting Start the security manager...
          Starting Disk Manager (legacy version)...
 [  OK  ] Started Network Service.
 [FAILED] Failed to start Terminate Psplash Boot Screen.
 See 'systemctl status psplash-quit.service' for details.
 [  OK  ] Started Save/Restore Sound Card State.
 [  OK  ] Started User Mode Init Manager for TI shared transport.
 [  OK  ] Started PowerVR consumer services.
 [  OK  ] Started Cynara service.
 [    9.028788] nfc: nfc_init: NFC Core ver 0.1
 [    9.033101] NET: Registered protocol family 39
 [  OK  ] Started neard service.
 [  OK  ] Started Initiate afm-system-setup.
 [  OK  ] Started Telephony service.
 [  OK  ] Started Login Service.
 [  OK  ] Started Avahi mDNS/DNS-SD Stack.
 [  OK  ] Started Application Framework Supervisor.
 [  OK  ] Started Application Framework Master, system side.
 [  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
          Starting Bluetooth service...
 [  OK  ] Reached target Sound Card.
 [  OK  ] Started Start the security manager.
 [  OK  ] Started Connection service.
 [  OK  ] Reached target Network.
          Starting Target Communication Framework agent...
          Starting Berkeley Internet Name Domain (DNS)...
          Starting Permit User Sessions...
 [  OK  ] Started Disk Manager (legacy version).
 [  OK  ] Started Automount Disk Manager.
 [  OK  ] Started Permit User Sessions.
          Starting Hostname Service...
 [  OK  ] Started Serial Getty on ttySC0.
 [  OK  ] Reached target Login Prompts.
 [  OK  ] Started Initiate afm[    9.771720] Micrel KSZ9031 Gigabit PHY e6800000.ethernet-ffffffff:00: attached PHY driver [Micrel KSZ9031 Gigabit PHY] (mii_bus:phy_addr=e6800000.ethernet-ffffffff:00, irq=184)
 -user-session 0.
 [    9.789428] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
          Starting WPA supplicant...
 [  OK  ] Started Bluetooth service.
 [  OK  ] Started Bluetooth Audio ALSA Backend.
          Starting Authorization Manager...
 [    9.964662] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
 [    9.969995] Bluetooth: BNEP filters: protocol multicast
 [    9.975257] Bluetooth: BNEP socket layer initialized
 [  OK  ] Started Target Communication Framework agent.
 [  OK  ] Started Hostname Service.
 [  OK  ] Started WPA supplicant.
 [   10.374665] audit: type=1006 audit(1554702896.535:2): pid=3745 uid=0 subj=System old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=1 res=1
 [  OK  ] Created slice User Slice of root.
          Starting User Manager for UID 0...
 [   10.441290] audit: type=1006 audit(1554702896.603:3): pid=3776 uid=0 subj=System old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=2 res=1
 [  OK  ] Started Session 1 of user root.
 [   10.492970] audit: type=1400 audit(1554702896.655:4): lsm=SMACK fn=smack_inode_permission action=denied subject="System" object="_" requested=w pid=3762 comm="named" name="bind" dev="mmcblk0p1" ino=30115
 [   10.511216] audit: type=1300 audit(1554702896.655:4): arch=c00000b7 syscall=48 success=no exit=-13 a0=ffffffffffffff9c a1=aaaaaec33698 a2=2 a3=aaaaaec33698 items=0 ppid=3739 pid=3762 auid=4294967295 uid=987 gid=987 euid=987 suid=987 fsuid=987 egid=987 sgid=987 fsgid=987 tty=(none) ses=4294967295 comm="named" exe="/usr/sbin/named" subj=System key=(null)
 [   10.544424] audit: type=1327 audit(1554702896.655:4): proctitle=2F7573722F7362696E2F6E616D6564002D750062696E64
 [  OK  ] Started Authorization Manager.
 [  OK  ] Started Berkeley Internet Name Domain (DNS).
 [  OK  ] Reached target Host and Network Name Lookups.
 [  OK  ] Reached target Multi-User System.
          Starting Weston Wayland compositor...
          Starting Update UTMP about System Runlevel Changes...
 [  OK  ] Started Update UTMP about System Runlevel Changes.
 [  OK  ] Started Weston Wayland compositor.
 [  OK  ] Started User Manager for UID 0.
 [   11.958499] can: controller area network core (rev 20170425 abi 9)
 [   11.964822] NET: Registered protocol family 29
 [   12.148666] can: broadcast manager protocol (rev 20170425 t)
 
 Automotive Grade Linux 7.0.0+snapshot h3ulcb ttySC0
 
 h3ulcb login: root
 h3ulcb:~#
20:03, 11 April 2019

Hello.

Is the penguin and AGL logo displayed on the monitor during startup?

23:24, 14 April 2019

Hello,

Thank you very much for your reply.

No, there is nothing displayed on the monitor during startup and even after Linux login prompt is shown on serial console which is running on other PC. The monitor says that no signal input.

23:51, 14 April 2019

Hi OK, please paste the result of the "printenv" command.

17:46, 15 April 2019

Hello,

Here is the results of printenv command.

 baudrate=115200
 bootargs=console=ttySC0,115200 ignore_loglevel vmalloc=384M video=HDMI-A-1:1920x1080-32@60 root=/dev/mmcblk0p1 rw rootfstype=ext4 rootwait rootdelay=2
 bootcmd=run load_ker; run load_dtb; booti 0x48080000 - 0x48000000
 bootdelay=3
 fdt_high=0xffffffffffffffff
 filesize=12a7200
 initrd_high=0xffffffffffffffff
 load_dtb=ext4load mmc 0:1 0x48000000 /boot/r8a7795-es1-h3ulcb.dtb
 load_ker=ext4load mmc 0:1 0x48080000 /boot/Image
 stderr=serial
 stdin=serial
 stdout=serial
 ver=U-Boot 2015.04 (Apr 08 2019 - 09:51:12)
 
 Environment size: 547/131068 bytes
19:35, 15 April 2019

> load_dtb=ext4load mmc 0:1 0x48000000 /boot/r8a7795-es1-h3ulcb.dtb

This device tree is for the H3 v1.1 SK(RTP0RC7795SKBX0010SA00).

> [ 0.005726] NOTICE: BL2: PRR is R-Car H3 Ver.2.0

According to the above log you are using H3 v2.0 SK.

Please use the "r8a7795-h3ulcb.dtb".

20:40, 15 April 2019
 
 
 
 
 

I2C errors appeared with multiple usb devices

With multiple USB devices connected environment, I2C bus error occur when operating I2C device. We observed the following two patterns.

Pattern 1: [ 133.082741] i2c-rcar e66d8000.i2c: error -11 : f

Arbitration lost occurs on the I2C bus, and rcar_i2c_master_xfer() fails with EAGAIN. When an I2C interrupt occurs, bit 5 (Master Arbitration Lost) of the Master Status Register (ICMSR) is set.


Pattern 2: [ 183.453555] i2c-rcar e66d8000.i2c: error -110 : 13

I2C device access timeout occurs and rcar_i2c_master_xfer () fails with ETIMEDOUT. Timeout occurs because the Master Stop Transmitted bit of the Master Status Register (ICMSR) is not set.

Although the causal relationship between the USB devices and the I2C bus is unclear, it seems that the hardware is detecting an abnormality. (From Master Status Register (ICMSR))


[ Reproduce environment ] Renesas bsp 3.15 Rcar M3 StarterKit + KF-M06

M3 USB2.0(CN 5) <-------> USBHUB <----> USB WIFI

                                                           <----> USB MEMORY * 2
                                                           <----> USB mouse dongle

KF-M06(CN 29) <--------> CMOS Camera

When CMOS camera is operated (capture), I2C bus error occurs probability as below. pattern1: 1/10. pattern2: 1/2.

Thanks, WN

00:03, 7 March 2019

Hi Can we reproduce this phenomenon if we don't use USB Wifi? M3 USB2.0(CN5) <---> USB HUB <---> USB MEMORY * 2 and USB mouse dongle KF-M06(CN29) <---> CMOS camera(ov5642)

I cannot reproduce.(0/20) Could you try it on another KF board?

18:42, 13 March 2019

As a result of our confirmation again, it can be reproduced, even if the USB device is not connected. Let me share the reproduction the scenario below. In addition, I used another board butI2C error is still reproduced.

[ Reproduce environment ]

- Renesas bsp 3.15 - Rcar M3 StarterKit + KF-M06 - CMOS Camera OV5642

 https://
    www.aliexpress.com/item/OV5642-5-Million-High-Sensitivity-Camera-Module-Image-Sensor-Module-Manual-Fine-tuning-with-JPEG-Interface/32909308847.html
 Connected CMOS Camera to CN 29 on KF-M06.

- capture command

 Customized based on V4L2 video capture example in here.
 https://
    linuxtv.org/downloads/v4l-dvb-apis-new/uapi/v4l/capture.c.html
 please see the attached file.
 
 # capture -d /dev/video0 -F -f rgb32 -L 0 -T 0 -W 12800 -H 720 -c 1000 -t 60 -z

[pattern1]

[ 1491.549362] i2c-rcar e66d8000.i2c: error -11 : f

[pattern2]

[ 1443.614690] i2c-rcar e66d8000.i2c: error -110 : 3

When capture command was executed, I2C bus error occurs probability as below. pattern1: 3/10. pattern2: 4/10.

Your feedback would be welcome. Thanks

05:07, 1 April 2019

I confirmed but did not reproduce.(0/20)

root@m3ulcb:~# dmesg|grep ov5642
[    2.583901] ov5642 22-003c: Chip ID 0x5642 detected
root@m3ulcb:~# capture -d /dev/video0 -F -f rgb32 -L 0 -T 0 -W 1280 -H 720 -c 1000 -t 60 -z
fb0 Fixed Info:
     @ 0x57400000, len=8294400, line=7680 bytes,
   Geometry - 1280 x 800, 32 bpp
/dev/video0 FPS:  29.1
(snip)
/dev/video0 FPS:  29.1
root@m3ulcb:~#

My environments:
- M3 SK (Connected: HDMI, Serial(cn12), Ether(cn7))
- KF M06(Connected: CMOS camera(cn29))

02:09, 2 April 2019

Thank you for the confirmation. Let me re-check with another camera module.

03:01, 11 April 2019
 
 
 
 

I would like to introduce NTL library to R-CarH3

Hello.

I wanted to use the NTL library with R-CarH3, but I tried to introduce it, but I am in trouble because it does not work well.

Would you please point out any problems with the environment or procedures?

I would be pleased if you could lend us your wisdom.

【usage environment】

ubuntu 18.04 (LTS)

【compiler】

gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu 1 ~ 18.04)

aarch64-linux-gnu-gcc (gcc version 7.3.0 (Ubuntu / Linaro 7.3.0-27ubuntu 1 to 18.04))

aarch64-linux-gnu-g ++


【Library and version you want to install】

gmp-6.1.2

ntl - 10.5.0

【procedure】

① Get gcc cross compiler with apt install (aarch64-linux-gnu-gcc, aarch64-linux-gnu-g ++)


② Create working directory, get gmp inside ~ install (gmp introduction succeeded)

mkdir / home / user / work

cd / home / user / work

sudo wget ftp://ftp.gnu.org/gnu/gmp/gmp-6.1.2.tar.xz

tar xvf gmp - 6.1.2.tar.xz

cd gmp - 6.1.2

./configure - prefix = / home / user / work / gmp --build = x86_64 - linux - gnu - host = aarch64 - linux - gnu - disable - shared

make

make check

make install


③ Obtaining ~ ntnt

cd / home / user / work

sudo wget http://www.shoup.net/ntl/ntl-10.5.0.tar.gz

tar xvf ntl-10.5.0.tar.gz

cd ntl - 10.5.0 / src

CXX = aarch64 - linux - gnu - g ++ "CXXFLAGS = - O 2 - march = armv 8 - a"

make



make setup1

make [1]: Enter directory '/usr/aarch64-linux-gnu/src/ntl-10.5.0/src'

aarch64 - linux - gnu - g ++ - I .. / include - I. - g - O 2 - march = armv 8 - a - c MakeDescAux.cpp

aarch64 - linux - gnu - g ++ - I .. / include - I. - g - O 2 - march = armv 8 - a - o MakeDesc MakeDesc.cpp MakeDescAux.o - lm

./MakeDesc

./MakeDesc: 1: ./MakeDesc: Syntax error: word unexpected (expecting ")")

makefile: 309: recipe for target 'setup1' failed

make [1]: *** [setup1] Error 2

make [1]: Exit the directory '/usr/aarch64-linux-gnu/src/ntl-10.5.0/src'

makefile: 298: recipe for target 'all' failed

make: *** [all] Error 2


21:16, 28 January 2019

The latest version of NTL seems to be 11.3.2. Could you try it?

17:39, 30 January 2019

Thank you. Sorry for the late reply. I tried it, but the same error came out.

20:32, 5 February 2019
 
 

AGL 6.0.0 booting on R-Car H3 not completed

Hello.
I built AGL 6.0.0 for the R-Car Starter Kit Premier/H3 according to the AGL guide, and tried booting AGL on the R-Car H3. [See "Steps to reproduce"]

But I can not see completing of AGL boot on R-Car H3.
The kernel does not proceed from message of "Waiting for root device /dev/mmcblk1p1...". [See attached "Booting log"]

Please tell me how to solve it.
In case of AGL 6.0.0 booting on M3, I can see completing of AGL boot[the shell is launched and home-screen is shown at hdmi-display].

Steps to reproduce:

1) Download all layers for the for Flounder 6.0.0
 I have performed according to below page:
 https://wiki.automotivelinux.org/agl-distro/release-notes#funky_flounder
 
 $ repo init -b flounder -m flounder_6.0.0.xml -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
 $ repo sync
2) Building and Booting the AGL for R-Car Starter Kit Premier/H3
 I have performed for machine h3ulcb according to below page:
 http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/machines/R-Car-Starter-Kit-gen3.html
 
 Note) I set "/boot/r8a7795-es1-h3ulcb.dtb" is instead of "/boot/Image-r8a7795-es1-h3ulcb.dtb" becaseu I cannot find "Image-r8a7795-es1-h3ulcb.dtb" on "/boot/".


Booting log:

[    0.000295] NOTICE:  BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.16
[    0.005858] NOTICE:  BL2: PRR is R-Car H3 Ver1.1
[    0.010440] NOTICE:  BL2: Board is Starter Kit Rev1.0
[    0.015468] NOTICE:  BL2: Boot device is HyperFlash(80MHz)
[    0.020893] NOTICE:  BL2: LCM state is CM
[    0.024936] NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x53
[    0.030919] NOTICE:  BL2: DDR2800(rev.0.27)NOTICE:  [COLD_BOOT]NOTICE:  ..0
[    0.065554] NOTICE:  BL2: DRAM Split is 4ch
[    0.069438] NOTICE:  BL2: QoS is default setting(rev.0.37)
[    0.074939] NOTICE:  BL2: Lossy Decomp areas
[    0.079114] NOTICE:       Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
[    0.086199] NOTICE:       Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
[    0.093111] NOTICE:       Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
[    0.100027] NOTICE:  BL2: v1.3(release):b330e0e
[    0.104516] NOTICE:  BL2: Built : 01:25:08, Jan 24 2018
[    0.109703] NOTICE:  BL2: Normal boot
[    0.113345] NOTICE:  BL2: dst=0xe6320208 src=0x8180000 len=512(0x200)
[    0.119894] NOTICE:  BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)
[    0.126352] NOTICE:  BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
[    0.133577] NOTICE:  BL2: dst=0x44100000 src=0x8200000 len=524288(0x80000)
[    0.144057] NOTICE:  BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)

U-Boot 2015.04 (Jan 24 2018 - 10:25:14)

CPU: Renesas Electronics R8A7795 rev 1.1
Board: H3ULCB
I2C:   ready
DRAM:  3.9 GiB
Flash: 64 MiB
MMC:   sh-sdhi: 0, sh-sdhi: 1
In:    serial
Out:   serial
Err:   serial
Net:   Board Net Initialization Failed
No ethernet found.
Hit any key to stop autoboot:  0
19347968 bytes read in 3092 ms (6 MiB/s)
69134 bytes read in 14 ms (4.7 MiB/s)
## Flattened Device Tree blob at 48000000
   Booting using the fdt blob at 0x48000000
   Using Device Tree in place at 0000000048000000, end 0000000048013e0d

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.0-yocto-standard (oe-user@oe-host) (gcc version 7.3.0 (GCC)) #1 SMP PREEMPT Fri Oct 19 01:57:21 UTC 2018
[    0.000000] Boot CPU: AArch64 Processor [411fd073]
[    0.000000] Machine model: Renesas H3ULCB board based on r8a7795 ES1.x
[    0.000000] debug: ignoring loglevel setting.
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x0000000057000000, size 400 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x0000000070000000, size 256 MiB
[    0.000000] OF: reserved mem: initialized node linux,multimedia, compatible id shared-dma-pool
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000000000000-0x000000073fffffff]
[    0.000000] NUMA: NODE_DATA [mem 0x73ff99a00-0x73ff9b4ff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000048000000-0x00000000ffffffff]
[    0.000000]   Normal   [mem 0x0000000100000000-0x000000073fffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000048000000-0x0000000053ffffff]
[    0.000000]   node   0: [mem 0x0000000057000000-0x000000007fffffff]
[    0.000000]   node   0: [mem 0x0000000500000000-0x000000053fffffff]
[    0.000000]   node   0: [mem 0x0000000600000000-0x000000063fffffff]
[    0.000000]   node   0: [mem 0x0000000700000000-0x000000073fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000048000000-0x000000073fffffff]
[    0.000000] On node 0 totalpages: 1003520
[    0.000000]   DMA zone: 3392 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 217088 pages, LIFO batch:31
[    0.000000]   Normal zone: 12288 pages used for memmap
[    0.000000]   Normal zone: 786432 pages, LIFO batch:31
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.0 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS resident on physical CPU 0x0
[    0.000000] random: fast init done
[    0.000000] percpu: Embedded 23 pages/cpu @ffff8006ffede000 s55576 r8192 d30440 u94208
[    0.000000] pcpu-alloc: s55576 r8192 d30440 u94208 alloc=23*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7
[    0.000000] Detected PIPT I-cache on CPU0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 987840
[    0.000000] Policy zone: Normal
[    0.000000] Kernel command line: console=ttySC0,115200 ignore_loglevel vmalloc=384M video=HDMI-A-1:1920x1080-32@60 root=/dev/mmcblk1p1 rw rootfstype=ext4 rootwait rootdelay=2
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] software IO TLB [mem 0x4ffff000-0x53fff000] (64MB) mapped at [ffff80000ffff000-ffff800013ffefff]
[    0.000000] Memory: 3190236K/4014080K available (11196K kernel code, 1230K rwdata, 5276K rodata, 1152K init, 426K bss, 152100K reserved, 671744K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     modules : 0xffff000000000000 - 0xffff000008000000   (   128 MB)
[    0.000000]     vmalloc : 0xffff000008000000 - 0xffff7dffbfff0000   (129022 GB)
[    0.000000]       .text : 0xffff000008080000 - 0xffff000008b70000   ( 11200 KB)
[    0.000000]     .rodata : 0xffff000008b70000 - 0xffff0000090a0000   (  5312 KB)
[    0.000000]       .init : 0xffff0000090a0000 - 0xffff0000091c0000   (  1152 KB)
[    0.000000]       .data : 0xffff0000091c0000 - 0xffff0000092f3a00   (  1231 KB)
[    0.000000]        .bss : 0xffff0000092f3a00 - 0xffff00000935e550   (   427 KB)
[    0.000000]     fixed   : 0xffff7dfffe7fd000 - 0xffff7dfffec00000   (  4108 KB)
[    0.000000]     PCI I/O : 0xffff7dfffee00000 - 0xffff7dffffe00000   (    16 MB)
[    0.000000]     vmemmap : 0xffff7e0000000000 - 0xffff800000000000   (  2048 GB maximum)
[    0.000000]               0xffff7e0000200000 - 0xffff7e001c000000   (   446 MB actual)
[    0.000000]     memory  : 0xffff800008000000 - 0xffff800700000000   ( 28544 MB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=8.
[    0.000000]  Tasks RCU enabled.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GIC: Adjusting CPU interface base to 0x00000000f102f000
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] arch_timer: cp15 timer(s) running at 8.33MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1ec02923e, max_idle_ns: 440795202125 ns
[    0.000003] sched_clock: 56 bits at 8MHz, resolution 120ns, wraps every 2199023255496ns
[    0.000357] Console: colour dummy device 80x25
[    0.000399] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.66 BogoMIPS (lpj=33333)
[    0.000407] pid_max: default: 32768 minimum: 301
[    0.000449] Security Framework initialized
[    0.000458] Smack:  Initializing.
[    0.000461] Smack:  IPv6 port labeling enabled.
[    0.002078] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    0.002886] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[    0.002929] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
[    0.002961] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes)
[    0.015963] ASID allocator initialised with 65536 entries
[    0.023952] Hierarchical SRCU implementation.
[    0.032444] Detected Renesas R-Car Gen3 r8a7795 ES1.1
[    0.033480] EFI services will not be available.
[    0.039974] smp: Bringing up secondary CPUs ...
[    0.068129] Detected PIPT I-cache on CPU1
[    0.068172] CPU1: Booted secondary processor [411fd073]
[    0.096136] Detected PIPT I-cache on CPU2
[    0.096154] CPU2: Booted secondary processor [411fd073]
[    0.124164] Detected PIPT I-cache on CPU3
[    0.124182] CPU3: Booted secondary processor [411fd073]
[    0.152106] psci: failed to boot CPU4 (-22)
[    0.152119] CPU4: failed to boot: -22
[    0.152123] CPU4: failed in unknown state : 0x0
[    0.180134] psci: failed to boot CPU5 (-22)
[    0.180138] CPU5: failed to boot: -22
[    0.180141] CPU5: failed in unknown state : 0x0
[    0.208166] psci: failed to boot CPU6 (-22)
[    0.208170] CPU6: failed to boot: -22
[    0.208174] CPU6: failed in unknown state : 0x0
[    0.236196] psci: failed to boot CPU7 (-22)
[    0.236200] CPU7: failed to boot: -22
[    0.236204] CPU7: failed in unknown state : 0x0
[    0.236233] smp: Brought up 1 node, 4 CPUs
[    0.236237] SMP: Total of 4 processors activated.
[    0.236242] CPU features: detected feature: 32-bit EL0 Support
[    0.236354] CPU: All CPU(s) started at EL2
[    0.236890] devtmpfs: initialized
[    0.241742] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.241802] futex hash table entries: 2048 (order: 6, 262144 bytes)
[    0.249675] pinctrl core: initialized pinctrl subsystem
[    0.251047] DMI not present or invalid.
[    0.251298] NET: Registered protocol family 16
[    0.252559] cpuidle: using governor menu
[    0.253416] vdso: 2 pages (1 code @ ffff000008b76000, 1 data @ ffff0000091c5000)
[    0.253429] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.253964] DMA: preallocated 256 KiB pool for atomic allocations
[    0.254199] Serial: AMBA PL011 UART driver
[    0.257329] sh-pfc e6060000.pin-controller: r8a77950_pfc support registered
[    0.277022] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.277982] ACPI: Interpreter disabled.
[    0.279989] rcar-cpufreq: use avs value: 0
[    0.280002] rcar-cpufreq: /cpus/cpu@0 is running with: /opp_table0
[    0.280010] rcar-cpufreq: /cpus/cpu@1 is running with: /opp_table0
[    0.280017] rcar-cpufreq: /cpus/cpu@2 is running with: /opp_table0
[    0.280023] rcar-cpufreq: /cpus/cpu@3 is running with: /opp_table0
[    0.281259] vgaarb: loaded
[    0.281426] SCSI subsystem initialized
[    0.281548] libata version 3.00 loaded.
[    0.281708] usbcore: registered new interface driver usbfs
[    0.281732] usbcore: registered new interface driver hub
[    0.281789] usbcore: registered new device driver usb
[    0.282679] i2c-sh_mobile e60b0000.i2c: I2C adapter 7, bus speed 400000 Hz
[    0.283007] media: Linux media interface: v0.10
[    0.283028] Linux video capture interface: v2.00
[    0.283094] pps_core: LinuxPPS API ver. 1 registered
[    0.283098] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.283109] PTP clock support registered
[    0.283336] EDAC MC: Ver: 3.0.0
[    0.283481] dmi: Firmware registration failed.
[    0.284052] Advanced Linux Sound Architecture Driver Initialized.
[    0.284296] NetLabel: Initializing
[    0.284301] NetLabel:  domain hash size = 128
[    0.284304] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.284340] NetLabel:  unlabeled traffic allowed by default
[    0.284628] clocksource: Switched to clocksource arch_sys_counter
[    0.284741] VFS: Disk quotas dquot_6.6.0
[    0.284779] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.284880] pnp: PnP ACPI: disabled
[    0.290375] NET: Registered protocol family 2
[    0.290883] TCP established hash table entries: 32768 (order: 6, 262144 bytes)
[    0.291028] TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
[    0.291290] TCP: Hash tables configured (established 32768 bind 32768)
[    0.291416] UDP hash table entries: 2048 (order: 4, 65536 bytes)
[    0.291447] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[    0.291569] NET: Registered protocol family 1
[    0.291814] RPC: Registered named UNIX socket transport module.
[    0.291818] RPC: Registered udp transport module.
[    0.291822] RPC: Registered tcp transport module.
[    0.291825] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.291833] PCI: CLS 0 bytes, default 128
[    0.292536] hw perfevents: enabled with armv8_cortex_a57 PMU driver, 7 counters available
[    0.292683] hw perfevents: /soc/pmu_a53: failed to probe PMU!
[    0.292689] hw perfevents: /soc/pmu_a53: failed to register PMU devices!
[    0.293028] kvm [1]: 8-bit VMID
[    0.293032] kvm [1]: IDMAP page: 48b57000
[    0.293036] kvm [1]: HYP VA range: 800000000000:ffffffffffff
[    0.293770] kvm [1]: vgic-v2@f1040000
[    0.293828] kvm [1]: vgic interrupt IRQ1
[    0.293838] kvm [1]: virtual timer IRQ4
[    0.293892] kvm [1]: Hyp mode initialized successfully
[    0.295643] audit: initializing netlink subsys (disabled)
[    0.295726] audit: type=2000 audit(0.291:1): state=initialized audit_enabled=0 res=1
[    0.295950] workingset: timestamp_bits=44 max_order=20 bucket_order=0
[    0.299072] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.299470] NFS: Registering the id_resolver key type
[    0.299491] Key type id_resolver registered
[    0.299495] Key type id_legacy registered
[    0.299503] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.299631] 9p: Installing v9fs 9p2000 file system support
[    0.301093] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    0.301101] io scheduler noop registered
[    0.301199] io scheduler cfq registered (default)
[    0.301204] io scheduler mq-deadline registered
[    0.301208] io scheduler kyber registered
[    0.306365] gpio_rcar e6050000.gpio: driving 16 GPIOs
[    0.306594] gpio_rcar e6051000.gpio: driving 28 GPIOs
[    0.306797] gpio_rcar e6052000.gpio: driving 15 GPIOs
[    0.306996] gpio_rcar e6053000.gpio: driving 16 GPIOs
[    0.307180] gpio_rcar e6054000.gpio: driving 18 GPIOs
[    0.307378] gpio_rcar e6055000.gpio: driving 26 GPIOs
[    0.307569] gpio_rcar e6055400.gpio: driving 32 GPIOs
[    0.307765] gpio_rcar e6055800.gpio: driving 4 GPIOs
[    0.326177] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.327725] SuperH (H)SCI(F) driver initialized
[    0.328146] e6e88000.serial: ttySC0 at MMIO 0xe6e88000 (irq = 139, base_baud = 0) is a scif
[    1.424882] console [ttySC0] enabled
[    1.429315] msm_serial: driver initialized
[    1.434422] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.441043] [drm] No driver support for vblank timestamp query.
[    1.447499] rcar-dw-hdmi fead0000.hdmi: Detected HDMI TX controller v2.01a with HDCP (DWC HDMI 2.0 TX PHY)
[    1.457336] rcar-dw-hdmi fead0000.hdmi: registered DesignWare HDMI I2C bus driver
[    1.470891] brd: module loaded
[    1.478402] loop: module loaded
[    1.494743] libphy: Fixed MDIO Bus: probed
[    1.499093] tun: Universal TUN/TAP device driver, 1.6
[    1.505151] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    1.511170] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.517131] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[    1.524107] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.529704] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k
[    1.537536] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.543801] sky2: driver version 1.30
[    1.548255] ravb e6800000.ethernet: no valid MAC address supplied, using a random one
[    1.556152] libphy: ravb_mii: probed
[    1.560769] ravb e6800000.ethernet eth0: Base address at 0xe6800000, 62:ee:99:bb:a7:a4, IRQ 136.
[    1.570101] VFIO - User Level meta-driver version: 0.3
[    1.576303] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.582834] ehci-pci: EHCI PCI platform driver
[    1.587299] ehci-platform: EHCI generic platform driver
[    1.592799] ehci-platform ee0a0100.usb: EHCI Host Controller
[    1.598473] ehci-platform ee0a0100.usb: new USB bus registered, assigned bus number 1
[    1.606445] ehci-platform ee0a0100.usb: irq 146, io mem 0xee0a0100
[    1.628637] ehci-platform ee0a0100.usb: USB 2.0 started, EHCI 1.10
[    1.635158] hub 1-0:1.0: USB hub found
[    1.638920] hub 1-0:1.0: 1 port detected
[    1.643102] ehci-orion: EHCI orion driver
[    1.647241] ehci-exynos: EHCI EXYNOS driver
[    1.651508] ehci-msm: Qualcomm On-Chip EHCI Host Controller
[    1.657151] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.663361] ohci-pci: OHCI PCI platform driver
[    1.667839] ohci-platform: OHCI generic platform driver
[    1.673225] ohci-platform ee0a0000.usb: Generic Platform OHCI controller
[    1.679936] ohci-platform ee0a0000.usb: new USB bus registered, assigned bus number 2
[    1.687847] ohci-platform ee0a0000.usb: irq 146, io mem 0xee0a0000
[    1.782910] hub 2-0:1.0: USB hub found
[    1.786671] hub 2-0:1.0: 1 port detected
[    1.790813] ohci-exynos: OHCI EXYNOS driver
[    1.795547] usbcore: registered new interface driver usb-storage
[    1.801603] usbcore: registered new interface driver usbserial
[    1.807453] usbcore: registered new interface driver usbserial_generic
[    1.813992] usbserial: USB Serial support registered for generic
[    1.822387] i2c /dev entries driver
[    1.833146] cs2000-cp 2-004f: revision - C1
[    1.837376] i2c-rcar e6510000.i2c: probed
[    1.846003] i2c-rcar e66d8000.i2c: probed
[    1.850492] usbcore: registered new interface driver i2c-tiny-usb
[    1.858064] imr fe860000.imr-lx4: IMR device (pdev: -1) registered as /dev/video0
[    1.865757] imr fe870000.imr-lx4: IMR device (pdev: -1) registered as /dev/video1
[    1.873387] imr fe880000.imr-lx4: IMR device (pdev: -1) registered as /dev/video2
[    1.881003] imr fe890000.imr-lx4: IMR device (pdev: -1) registered as /dev/video3
[    1.892080] rcar_gen3_thermal e6198000.thermal: is using pseudo fixed FUSE values
[    1.904493] rcar_gen3_thermal e6198000.thermal: TSC0: Loaded 1 trip points
[    1.915812] rcar_gen3_thermal e6198000.thermal: TSC1: Loaded 1 trip points
[    1.927080] rcar_gen3_thermal e6198000.thermal: TSC2: Loaded 3 trip points
[    1.936207] sdhci: Secure Digital Host Controller Interface driver
[    1.942394] sdhci: Copyright(c) Pierre Ossman
[    1.947274] renesas_sdhi_internal_dmac ee100000.sd: Got CD GPIO
[    1.953425] Synopsys Designware Multimedia Card Interface Driver
[    1.960174] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.967100] ledtrig-cpu: registered to indicate activity on CPUs
[    1.974050] usbcore: registered new interface driver usbhid
[    1.979626] usbhid: USB HID core driver
[    1.984346] optee: probing for conduit method from DT.
[    1.984651] usb 1-1: new high-speed USB device number 2 using ehci-platform
[    1.996781] R-Car Rev.1.0.8
[    1.999890] optee: initialized driver
[    2.004952] usbcore: registered new interface driver snd-usb-audio
[    2.019227] rcar_sound ec500000.sound: probed
[    2.023915] NET: Registered protocol family 17
[    2.028422] 9pnet: Installing 9P2000 support
[    2.032739] Key type dns_resolver registered
[    2.037915] registered taskstats version 1
[    2.047017] thermal emergency: set temperature to 110 celsius
[    2.052832] thermal emergency: shutdown target cpus 1-3
[    2.058056] thermal emergency: freq scaled target cpus 0
[    2.063668] renesas_irqc e61c0000.interrupt-controller: driving 6 irqs
[    2.071503] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.078129] [drm] No driver support for vblank timestamp query.
[    2.147727] hub 1-1:1.0: USB hub found
[    2.151652] hub 1-1:1.0: 4 ports detected
[    2.251577] Console: switching to colour frame buffer device 240x67
[    2.274840] rcar-du feb00000.display: fb0:  frame buffer device
[    2.280995] [drm] Initialized rcar-du 1.0.0 20130110 for feb00000.display on minor 0
[    2.288740] [drm] Device feb00000.display probed
[    2.294385] bd9571mwv 7-0030: Device: BD9571MWV rev. 1
[    2.304694] renesas_sdhi_internal_dmac ee100000.sd: Got CD GPIO
[    2.372989] renesas_sdhi_internal_dmac ee100000.sd: mmc0 base at 0xee100000 max clock rate 200 MHz
[    2.383200] asoc-simple-card sound: ak4613-hifi <-> ec500000.sound mapping ok
[    2.390356] asoc-simple-card sound: ASoC: no DMI vendor name!
[    2.398750] input: keyboard as /devices/platform/keyboard/input/input0
[    2.405480] hctosys: unable to open rtc device (rtc0)
[    2.411026] ALSA device list:
[    2.413997]   #0: Loopback 1
[    2.416875]   #1: ak4613
[    2.419744] Waiting 2 sec before mounting root device...
[    2.460636] usb 1-1.1: new full-speed USB device number 3 using ehci-platform
[    2.596971] input: ILITEK Multi-Touch-V5100 as /devices/platform/soc/ee0a0100.usb/usb1/1-1/1-1.1/1-1.1:1.0/0003:222A:011E.0001/input/input1
[    2.609611] hid-multitouch 0003:222A:011E.0001: input: USB HID v1.10 Device [ILITEK Multi-Touch-V5100] on usb-ee0a0100.usb-1.1/input0
[    2.622380] hid-generic 0003:222A:011E.0002: device has no listeners, quitting
[    2.686881] mmc0: new ultra high speed SDR104 SDHC card at address aaaa
[    2.693689] mmcblk0: mmc0:aaaa SL16G 14.8 GiB
[    2.701819]  mmcblk0: p1
[    2.720635] usb 1-1.4: new full-speed USB device number 4 using ehci-platform
[    4.448658] md: Skipping autodetection of RAID arrays. (raid=autodetect will force)
[    4.456436] Waiting for root device /dev/mmcblk1p1...
00:35, 22 October 2018

Hi, I report because this issue progress has changed.

I seemed that the U-boot parameters(discribed at http://docs.automotivelinux.org/docs/getting_started/en/dev/reference/machines/R-Car-Starter-Kit-gen3.html) were wrong from the previous Booting log.

[ 2.693689] mmcblk0: mmc0:aaaa SL16G 14.8 GiB
[ 2.701819] mmcblk0: p1
[ 2.720635] usb 1-1.4: new full-speed USB device number 4 using ehci-platform
[ 4.448658] md: Skipping autodetection of RAID arrays. (raid=autodetect will force)
[ 4.456436] Waiting for root device /dev/mmcblk1p1...

So, I tried changing the device name from "/dev/mmcblk1p1" to "/dev/mmcblk0p1".
And reboot, the shell is launched completely but home-screen is not shown at hdmi-display yet.
The kernel outputs trace log of WARNING below.

[ 16.128912] -----------[ cut here ]-----------
[ 16.133663] WARNING: CPU: 1 PID: 54 at /mnt/AGL/workspace_agl_ff_6.0.0_rcar/build-h3/tmp/work/h3ulcb-agl-linux/kernel-module-gles/1.0-r0/rogue_km/binary_r8a7795_linux_release/target_aarch64/kbuild/services/server/devices/rgx/rgxfwutils.c:4115 RGXCheckFirmwareCCB+0x210/0x330 [pvrsrvkm]
[ 16.160150] Modules linked in: can_bcm can bnep nfc btwilink st_drv bluetooth ecdh_generic rfkill crc32_ce crct10dif_ce pvrsrvkm(O) vspm_if(O) vsp2(O) vspm(O) uvcs_drv(O) mmngrbuf(O) mmngr(O) hdm_usb(O) hdm_i2c(O) hdm_dim2(O) aim_v4l2(O) aim_sound(O) aim_network(O) aim_cdev(O) mostcore(O) ipv6
[ 16.186172] CPU: 1 PID: 54 Comm: kworker/u16:2 Tainted: G O 4.14.0-yocto-standard #1
[ 16.195037] Hardware name: Renesas H3ULCB board based on r8a7795 ES1.x (DT)
[ 16.202108] Workqueue: pvr_workqueue MISRWrapper [pvrsrvkm]
[ 16.207676] task: ffff8006fae20000 task.stack: ffff000009b40000
[ 16.213698] PC is at RGXCheckFirmwareCCB+0x210/0x330 [pvrsrvkm]
[ 16.219761] LR is at RGXCheckFirmwareCCB+0x210/0x330 [pvrsrvkm]
[ 16.225676] pc : [<ffff000000ce6e28>] lr : [<ffff000000ce6e28>] pstate: 60000145
[ 16.233063] sp : ffff000009b43d60
[ 16.236371] x29: ffff000009b43d60 x28: 0000000000000000
[ 16.241680] x27: 0000000000000000 x26: ffff0000210790a0
[ 16.246988] x25: 0000000070014008 x24: ffff8006f4a705e8
[ 16.252296] x23: ffff000000d45618 x22: ffff8006f4a70000
[ 16.257603] x21: ffff000021079080 x20: 0000000000000020
[ 16.262911] x19: ffff000021079040 x18: 0000000000000010
[ 16.268219] x17: 00000000000012c8 x16: 00000000000012cc
[ 16.273526] x15: 0000000000000001 x14: 0000000000000400
[ 16.278833] x13: 0000000000000400 x12: 0000000000000000
[ 16.284141] x11: 0000000000000005 x10: 0000000000000000
[ 16.289448] x9 : 00000000006cd4b7 x8 : ffff8006ffeea6c0
[ 16.294756] x7 : ffff8006ffeea668 x6 : 00000000000000a7
[ 16.300063] x5 : 0000000000000001 x4 : ffff0000091d2c00
[ 16.305370] x3 : 00000000000f4240 x2 : ffff8006fa5e7088
[ 16.310678] x1 : 0000000000000000 x0 : 0000000000000002
[ 16.315986] Call trace:
[ 16.318427] Exception stack(0xffff000009b43c20 to 0xffff000009b43d60)
[ 16.324862] 3c20: 0000000000000002 0000000000000000 ffff8006fa5e7088 00000000000f4240
[ 16.332684] 3c40: ffff0000091d2c00 0000000000000001 00000000000000a7 ffff8006ffeea668
[ 16.340507] 3c60: ffff8006ffeea6c0 00000000006cd4b7 0000000000000000 0000000000000005
[ 16.348329] 3c80: 0000000000000000 0000000000000400 0000000000000400 0000000000000001
[ 16.356152] 3ca0: 00000000000012cc 00000000000012c8 0000000000000010 ffff000021079040
[ 16.363974] 3cc0: 0000000000000020 ffff000021079080 ffff8006f4a70000 ffff000000d45618
[ 16.371796] 3ce0: ffff8006f4a705e8 0000000070014008 ffff0000210790a0 0000000000000000
[ 16.379619] 3d00: 0000000000000000 ffff000009b43d60 ffff000000ce6e28 ffff000009b43d60
[ 16.387441] 3d20: ffff000000ce6e28 0000000060000145 ffff000009b43d60 ffff000000ce6e28
[ 16.395263] 3d40: ffffffffffffffff 0000000000000020 ffff000009b43d60 ffff000000ce6e28
[ 16.403248] [<ffff000000ce6e28>] RGXCheckFirmwareCCB+0x210/0x330 [pvrsrvkm]
[ 16.410302] [<ffff000000ce893c>] RGX_MISRHandler+0x24/0x38 [pvrsrvkm]
[ 16.416840] [<ffff000000cb5058>] MISRWrapper+0x18/0x20 [pvrsrvkm]
[ 16.422935] [<ffff0000080e06bc>] process_one_work+0x1d4/0x348
[ 16.428675] [<ffff0000080e0878>] worker_thread+0x48/0x470
[ 16.434070] [<ffff0000080e6b64>] kthread+0x12c/0x130
[ 16.439033] [<ffff000008084c10>] ret_from_fork+0x10/0x18
[ 16.444339] --[ end trace da55878e442ea43e ]--

I should do something else?
Perhaps, my knowledge may be missing, but I appreciate if someone let me know advice to solve it.

18:55, 23 October 2018

> [ 0.005858] NOTICE: BL2: PRR is R-Car H3 Ver1.1 According to this log you are using H3 v1.1.

AGL 6.0.0 is based on Yocto v3.7.0.
And Yocto v3.7.0 doesn't support H3 v1.1 SK. Please refer to the following.
https://elinux.org/R-Car/Boards/H3SK#Limitation

Currently, H3 v2.0 and M3 SK are out of stock. I hope that you already have H3 v2.0 SK or M3 SK.

02:23, 24 October 2018

Thank you for letting me know it.

I found that I'm not happy, but I will find someone who already has H3 v2.0 SK or M3 SK.

15:57, 24 October 2018
 
 
 

PCM3168A driver for Kingfisher

PCM3168A driver opened in eLinux seems to have some tentative implementations to support LINEout x8ch (CN12) for Kingfisher. e.g. no support 16_LE. If my understanding is correct, can I ask if there is any plan to replace the tentative implementation with permanent one?

https://github.com/CogentEmbedded/meta-rcar/blob/v3.9.0/meta-rcar-gen3-adas/recipes-kernel/linux/linux-renesas/0063-ASoC-PCM3168A-add-TDM-modes-merge-ADC-and-DAC.patch

Thanks, WN

20:33, 19 August 2018

Renesas will post patches to the upstream. However schedule is undecided.

17:17, 3 October 2018
 

8bit parallel video driver for Kingfisher

8bit parallel video driver opened in eLinux seems to have some tentative implementationsp. If my understanding is correct, can I ask if there is any plan to replace the tentative implementation with permanent one?

"LEGACY" was observed in Kernel configuration like below:

VIDEO_RCAR_VIN_LEGACY VIDEO_RCAR_CSI2_LEGACY

Patch title also contains the same:

media: soc_camera: add legacy VIN/CSI2

https://github.com/CogentEmbedded/meta-rcar/tree/v3.9.0/meta-rcar-gen3-adas/recipes-kernel/linux/linux-renesas 0013-IMR-driver-interim-patch.patch 0017-media-soc_camera-add-legacy-VIN-CSI2.patch 0030-Gen3-LVDS-cameras.patch 0032-media-i2c-Add-ov5642-sensor.patch 0033-media-soc-camera-fix-parallel-i-f-in-VIN.patch 0034-media-soc_camera-Fix-VIDIOC_S_SELECTION-ioctl-miscal.patch 0105-media-rcar-imr-IMR-driver-updates-for-raw-DL.patch 0106-media-rcar-imr-Add-RSE-support.patch

Thanks, WN

20:37, 19 August 2018

It seems that it is currently active in the public place.
Ex) https://patchwork.kernel.org/patch/10558575/

23:13, 19 August 2018
 

Enabling Reset button/Power button functionality on Kingfisher + M3 Starter Kit

Reset button (SW8) and Power button (SW9) do not work when M3 starter Kit connected to Kingfisher board.

We need this in order to evaluate fastboot feature with Camera connected to Kingfisher.

Any workaround?

Note: SW8 and SW9 work fine without connecting Kingfisher board to M3 starter Kit.

[Use Case]

1. Connect M3 starter Kit to Kingfisher Advanced Model board.

2. Boot up the board.

3. Press SW9 for resetting the board, without physical power disconnection. (Volatile memory should be maintained.)

OR

1. Connect M3 starter Kit to Kingfisher Advanced Model board.

2. Boot up the board.

3. Software suspend the board. Press SW8 in order to power on the board, without physical power disconnection. (Volatile memory should be maintained.)

[Board and other env.]

Renesas RCAR M3 Starter Kit

Sample Loader V3.02 2017.07.04 (M3 Starter Kit)

MiniMonitor V3.02 2017.07.04 (M3 Starter Kit)

Kingfisher Board Version (SBEV-RCAR-KF-M05)


Thanks,

WN

18:32, 11 July 2018

According to the schematic the power supply seems to be controlled from Kingfisher(M05). I think you can not control power from SW8.

21:52, 12 July 2018

Is there any switch/workaround to reset the kingfisher board ? Or would this be considered as a hardware limitation and no work around possible ? Although we would hope this is not the case.

18:06, 23 July 2018

SW9 on Starter Kit can reset to CPU( and devices on Starter Kit). However it cannot reset to devices on Kingfisher.

Why do you need reset rather than SW6 on Kingfisher?

21:42, 26 July 2018

>>Why do you need reset rather than SW6 on Kingfisher?

We want to evaluate suspend to RAM mode of hibernation. For this, we are expecting to keep the power ON for the board so that during hibernation the contents of RAM are not lost. Software control for reset is not present so we need a RESET functionality equivalent like provided by SW8.

Also we need kingfisher board for getting CAMERA interface CN29 access to M3 target.

SW6 erases the RAM contents so we are not able to use it.

Would you please let us know any workarounds, if possible, for this use case ?

Thanks in advance.

17:11, 31 July 2018

KF doesn't support Suspend to RAM(S2R).

In order to support S2R on SK+KF, it is necessary to redesign the power control schematics on KF.
(I have never heard of such a plan.)

18:32, 31 July 2018
 
 
 
 
 

Camera Low lever test issue on H3 Adas

Hi

i build a yocto 2.23.1 with ADAS setup for H3 v2 board and an adas view card (boot with Image-r8a7795-h3ulcb-view.dtb)
but i have a crash when i start the surround test:

[30.855979] 894ac000:[DISPLAY_WL.INIT] Wayland display interface initialized
[30.856564] 894ac000:[DISPLAY_WL.INIT] spacenav input added
[30.856603] 894ac000:[DISPLAY_WL.INIT] no joystick connected
sv-utest: /opt/storage/projects/renesas/public_releases/SV_closed/libsv/src/utils/CV4L2UserControl.cpp:68: virtual void CV4L2UserControl::internalSet(int): Assertion `-1 != ret' failed.
Aborted (core dumped)

same problem with low level test (under /usr/share/tests)

[ 401.533829] imr fe890000.imr-lx4: unsupported format request: 'XR24'
[ 401.545811] imr fe860000.imr-lx4: unsupported format request: 'XR24'
[ 401.557503] imr fe870000.imr-lx4: unsupported format request: 'XR24'
[ 401.570159] imr fe880000.imr-lx4: unsupported format request: 'XR24'
[ 401.580563] imr fe890000.imr-lx4: unsupported format request: 'XR24'

Could you help me?
charles

10:39, 20 February 2018

How to use usb webcam in H3??

How to use usb webcam in H3??

Because I use python opencv

>> cap = cv2.VideoCapture(0)

It doesn't capture webcam

How to solve this problem??

10:52, 17 October 2017

Hi

I write information when I checked the usb webcam using Yocto v2.23.0.
I don't understand your detailed environment, but I am glad if this is helpful for you.

Environment:
- H3 Starter Kit
- Yocto v2.23.0
- USB Webcam Logicool C920t

1. Enable the following kernel config.
        Device Drivers --> Multimedia support  ---> [*] Media USB Adapters
                [*] USB Video Class (UVC)
                [*] UVC input events device support (NEW)

2. Modify the gstreamer1.0-plugin-vspfilter
 # vi gst/vspfilter/vspfilterutils.c
   {GST_VIDEO_FORMAT_UYVY, V4L2_PIX_FMT_UYVY, V4L2_MBUS_FMT_AYUV8_1X32, 1},
+  {GST_VIDEO_FORMAT_YUY2, V4L2_PIX_FMT_YUYV, V4L2_MBUS_FMT_AYUV8_1X32, 1},

3. bitbake

4. How to run
 Ex)
 # gst-launch-1.0 v4l2src device=/dev/video16 ! video/x-raw,width=1920,height=1080 ! vspfilter ! video/x-raw,format=BGRA ! waylandsink

 * videoN: Please set according to your environment.
   Ex) In case of M3 SK it was video8.
03:38, 23 October 2017

My environment : - Yocto v2.19.0 - USB Webcam logitech HD WEBCAM C525

I refer https://elinux.org/R-Car/Boards/Yocto-Gen3/OpenCL & https://elinux.org/index.php?title=R-Car/Boards/Yocto-Gen3&oldid=449821

sorry I don't know where can I revise the code you say in the first 1. Enable the following kernel config.

       Device Drivers --> Multimedia support  ---> [*] Media USB Adapters
               [*] USB Video Class (UVC)
               [*] UVC input events device support (NEW)
06:33, 23 October 2017
21:54, 23 October 2017

for enter in the configuration of the kernel ( you must have a X server configured because you have a popup with the menuconfig) : bitbake linux-renesas -c do_menuconfig

03:33, 11 January 2018
 
 
 
 

How to execute OP-TEE cryptographic algorithms directly from ARM Trusted Firmware

I want to evaluate cryptographic algorithms on the boot loader before Linux starts up.

We plan to include evaluation software in ARM Trusted Firmware (bl31-h3ulcb).

ARM Trusted Firmware has no encryption algorithm, so we are considering using a library in OP-TEE (tee-h3ulcb).

For example, in evaluating signature verification using RSA, the following processing is considered necessary.

・ Register the public key and secret key.

・ And generates a hash value of the evaluation target data. (For example SHA 256)

・ Generate a signature by encrypting the hash value with the secret key.

・ Generate a hash value by decrypting the signature with the public key.

Among these processes, I do not know how to register the public key and secret key to OP-TEE.

Please tell me what kind of processing can be realized from ARM Trusted Firmware.

17:23, 7 December 2017

(If you have product planning, )I think that you should officially contact Renesas.

02:31, 12 December 2017

I am not a product planning representative.
I'm considering running cryptographic algorithms implemented on R-Car H3 on a boot loader on which Linux is not running.

I will concretely describe what I can not realize.

First, when ARM Trusted Firmware jumps to the address where the OP-TEE function exists, an exception will be raised.
After that, "plat_panic_handler" will be in infinite loop state.
I guess that it is probably guarded by MMU, but I do not know how to deal with it.

Second, About signature verification using key of RSA.
In order to register the key of RSA, I guess using functions like "alloc_rsa_public_key" and "alloc_rsa_keypair" in OP - TEE.
However, I do not know how to use functions such as arguments and procedures.

17:52, 14 December 2017
 
 

How to Flash kernel and device tree using flash writer instead using nfs

I am trying to flash the linux kernel and device tree using flash writer I created the srec files, but also an over size error appeared, is it possible to flash those file with flash writer?

08:26, 15 November 2017

Can the following information help you?(Note:The "Program Top Address" is different according to Yocto version)
H3 Starter Kit case: https://elinux.org/R-Car/Boards/H3SK#Flashing_firmware
M3 Starter Kit case: https://elinux.org/R-Car/Boards/M3SK#Flashing_firmware

17:09, 16 November 2017
 

Installing PyCaffe

Hello,

I have managed to successfully build OpenCL/ViennaCL, OpenCV, Caffe, etc. following the instructions here http://elinux.org/R-Car/Boards/Yocto-Gen3/OpenCL Unfortunately I am having trouble installing the python bindings for caffe (which allows one to simply import caffe in python and run caffe commands natively in python). I tried to do this by changing the CMake parameter -DBUILD_python in caffe_git.bb to ON. My error is as follows. I've tried setting the various python (and git and boost) paths manually but none seem to work correctly. Has anybody else had experience with this?

 DEBUG: Executing python function sysroot_cleansstate
 DEBUG: Python function sysroot_cleansstate finished
 DEBUG: Executing shell function do_configure
 -- The C compiler identification is GNU 5.2.1
 -- The CXX compiler identification is GNU 5.2.1
 -- Check for working C compiler: /home/eli/build/build/tmp/sysroots/x86_64-linux/usr/bin/aarch64-poky-linux/aarch64-poky-linux-gcc
 -- Check for working C compiler: /home/eli/build/build/tmp/sysroots/x86_64-linux/usr/bin/aarch64-poky-linux/aarch64-poky-linux-gcc -- works
 -- Detecting C compiler ABI info
 -- Detecting C compiler ABI info - done
 -- Detecting C compile features
 -- Detecting C compile features - done
 -- Check for working CXX compiler: /home/eli/build/build/tmp/sysroots/x86_64-linux/usr/bin/aarch64-poky-linux/aarch64-poky-linux-g++
 -- Check for working CXX compiler: /home/eli/build/build/tmp/sysroots/x86_64-linux/usr/bin/aarch64-poky-linux/aarch64-poky-linux-g++ -- works
 -- Detecting CXX compiler ABI info
 -- Detecting CXX compiler ABI info - done
 -- Detecting CXX compile features
 -- Detecting CXX compile features - done
 -- Boost version: 1.60.0
 -- Found the following Boost libraries:
 --   system
 --   thread
 --   filesystem
 -- Looking for pthread.h
 -- Looking for pthread.h - found
 -- Looking for pthread_create
 -- Looking for pthread_create - not found
 -- Looking for pthread_create in pthreads
 -- Looking for pthread_create in pthreads - not found
 -- Looking for pthread_create in pthread
 -- Looking for pthread_create in pthread - found
 -- Found Threads: TRUE
 -- Found GFlags: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/include
 -- Found gflags  (include: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/include, library: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/lib/libgflags.so)
 -- Found Glog: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/include
 -- Found glog    (include: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/include, library: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/lib/libglog.so)
 -- Found PROTOBUF: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/lib/libprotobuf.so
 -- Found PROTOBUF Compiler: /home/eli/build/build/tmp/sysroots/x86_64-linux/usr/bin/protoc
 -- -- CUDA is disabled. Building without it...
 -- Found ViennaCL include: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/include
 -- Found OpenCL: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/lib/libOpenCL.so
 -- Found OpenCL include: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/include
 -- OpenCV found (/home/eli/build/build/tmp/sysroots/h3ulcb/usr/share/OpenCV)
 -- Found OpenBLAS libraries: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/lib/libopenblas.so
 -- Found OpenBLAS include: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/include
 -- Could NOT find PythonInterp (missing:  PYTHON_EXECUTABLE) (Required is at least version "2.7")
 -- Found PythonLibs: /home/eli/build/build/tmp/sysroots/h3ulcb/usr/lib/libpython2.7.so (found suitable version "2.7.11", minimum required is "2.7")
 -- To find NumPy Python interpretator is required to be found.
 -- Could NOT find NumPy (missing:  NUMPY_INCLUDE_DIR NUMPY_VERSION) (Required is at least version "1.7.1")
 -- Could NOT find Boost
 -- Could NOT find Doxygen (missing:  DOXYGEN_EXECUTABLE)
 -- Python interface is disabled or not all required dependencies found. Building without it...
 -- Could NOT find Git (missing:  GIT_EXECUTABLE)
 -- ******************* Caffe Configuration Summary *******************
 -- General:
 --   Version           :   1.0.0
 --   Git               :   unknown
 --   System            :   Linux
 --   C++ compiler      :   /home/eli/build/build/tmp/sysroots/x86_64-linux/usr/bin/aarch64-poky-linux/aarch64-poky-linux-g++
 --   Release CXX flags :   -DNDEBUG -march=armv8-a -mtune=cortex-a57.cortex-a53  --sysroot=/home/eli/build/build/tmp/sysroots/h3ulcb  -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-
 map=/home/eli/build/build/tmp/work/aarch64-poky-linux/caffe/git-r0=/usr/src/debug/caffe/git-r0 -fdebug-prefix-map=/home/eli/build/build/tmp/sysroots/x86_64-linux= -fdebug-prefix-
 map=/home/eli/build/build/tmp/sysroots/h3ulcb=  -fvisibility-inlines-hidden -fPIC -Wall -std=c++11 -DCMAKE_BUILD -Wno-sign-compare -Wno-uninitialized
 --   Debug CXX flags   :   -g -march=armv8-a -mtune=cortex-a57.cortex-a53  --sysroot=/home/eli/build/build/tmp/sysroots/h3ulcb  -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-
 map=/home/eli/build/build/tmp/work/aarch64-poky-linux/caffe/git-r0=/usr/src/debug/caffe/git-r0 -fdebug-prefix-map=/home/eli/build/build/tmp/sysroots/x86_64-linux= -fdebug-prefix-
 map=/home/eli/build/build/tmp/sysroots/h3ulcb=  -fvisibility-inlines-hidden -fPIC -Wall -std=c++11 -DCMAKE_BUILD -Wno-sign-compare -Wno-uninitialized
 --   Build type        :   Release
 --   BUILD_SHARED_LIBS :   ON
 --   BUILD_python      :   ON
 --   BUILD_matlab      :   OFF
 --   BUILD_docs        :   ON
 --   CPU_ONLY          :   OFF
 --   USE_OPENCV        :   ON
 --   USE_FFT           :   OFF
 --   USE_LEVELDB       :   OFF
 --   USE_LMDB          :   OFF
 --   USE_NCCL          :   OFF
 --   ALLOW_LMDB_NOLOCK :   OFF
 --   USE_HDF5          :   OFF
 -- Dependencies:
 --   BLAS              :   Yes (open)
 --   Boost             :   Yes (ver. 1.60)
 --   glog              :   Yes
 --   gflags            :   Yes
 --   protobuf          :   Yes (ver. 2.6.1)
 --   OpenCV            :   Yes (ver. 3.1.0)
 --   CUDA              :   No
 -- 
 -- Documentaion:
 --   Doxygen           :   No
 --   config_file       :   
 -- 
 -- Install:
 --   Install path      :   /usr
 --  
 -- Configuring done
 CMake Error at CMakeLists.txt:211 (add_dependencies):
 The dependency target "pycaffe" of target "pytest" does not exist.
 -- Generating done
 -- Build files have been written to: /home/eli/build/build/tmp/work/aarch64-poky-linux/caffe/git-r0/build
 WARNING: exit code 1 from a shell command.
 ERROR: Function failed: do_configure (log file is located at /home/eli/build/build/tmp/work/aarch64-poky-linux/caffe/git-r0/temp/log.do_configure.27252)
00:13, 3 August 2017

I have finished building with caffe and pycaffe on h3
I refer https://elinux.org/R-Car/Boards/Yocto-Gen3/OpenCL
and add "IMAGE_FEATURES_append = " tools-sdk dev-pkgs " to your local.conf
this line can add g++ compiler to your yocto system
When you finish building kernel ,you can turn on h3 with sd card.
you can git clone opencl-caffe on your home in h3
you need to build hdf5 boost first
and then you can enter into your opencl caffe with compile command
$ make
$ make pycaffe

10:42, 30 October 2017
 

Format eMMC in EXT3

hello.
I want to write in Linux Image at eMMC.
Therefore I was going to format eMMC in EXT3 form,
but the following messages were displayed and did not get along well.
Please tell me how I should format it.

root@h3ulcb:/mnt# fdisk /dev/mmcblk0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT dl
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.
The number of cylinders for this disk is set to 238592.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): d
No partition is defined yet!
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-238592, default 1): Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-238592, default 238592): Using de2
Command (m for help): p
Disk /dev/mmcblk0: 7818 MB, 7818182656 bytes
4 heads, 16 sectors/track, 238592 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 238592 7634936 83 Linux
Command (m for help): t
Selected partition 1
Hex code (type L to list codes): 83
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
[ 1039.079522] mmcblk0: p1
root@h3ulcb:/mnt# mkfs.ext3 /dev/mmcblk0
-sh: mkfs.ext3: command not found
root@h3ulcb:/mnt# ls /sbin/mkfs.ext*
ls: cannot access '/sbin/mkfs.ext*': No such file or directory
15:20, 5 October 2017

I think that you need to add a package.

Ex) Add the following to build/conf/local.conf IMAGE_INSTALL_append = " e2fsprogs"

For details, please refer to Yocto manual.

22:55, 5 October 2017

Thank you very much for having you teach it.
I try it. I report the result some other time.

15:22, 9 October 2017
 

Thanks to you, I was able to format eMMC.
And I was able to write in Linux image at eMMC.

22:43, 9 October 2017
 
 

Can't Modify U-Boot Environment Variables on Updated Firmware

I am trying to get up and running with the R-Car H3 Starter Kit Premier Board (h3ulcb). I first followed the instructions here http://elinux.org/R-Car/Boards/Yocto-Gen3 to build Yocto 2.19 for the board. When I attempted to run the built Yocto image on the board (both via tftp and via microSD), I received a kernel panic message. The limited resources on the internet (i.e., the other posts on this wiki) indicated this could likely be resolved by updating the firmware. I then followed the instructions here http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware to update the firmware on the board. Now when I turn the board on, I cannot get to the stage where the option of cancelling autoboot (as shown in examples in the links given). I am therefore not able to change U-Boot's environment variables to specify the Image file to boot. It seems that U-Boot is perhaps not loading at all. Any help would be greatly appreciated!

Output of boot sequence is below:

user@user-linux:~$ sudo picocom -b 115200 --send-cmd "ascii-xfr -vvs" /dev/ttyUSB0

[sudo] password for user:

picocom v1.7

port is : /dev/ttyUSB0

flowcontrol : none

baudrate is : 115200

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 : ascii-xfr -vvs

receive_cmd is : rz -vv

imap is :

omap is :

emap is : crcrlf,delbs,

Terminal ready

[ 0.000194] NOTICE: BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.14

[ 0.005761] NOTICE: BL2: PRR is R-Car H3 Ver2.0

[ 0.010335] NOTICE: BL2: Board is unknown Rev0.0

[ 0.015006] NOTICE: BL2: Boot device is HyperFlash(80MHz)

[ 0.020445] NOTICE: BL2: LCM state is CM

[ 0.024423] NOTICE: BL2: AVS setting succeeded. DVFS_SetVID=0x52

[ 0.030611] NOTICE: BL2: DDR3200(rev.0.22)NOTICE: [COLD_BOOT]NOTICE: ..0

[ 0.091270] NOTICE: BL2: DRAM Split is 4ch

[ 0.095155] NOTICE: BL2: QoS is default setting(rev.0.14)

[ 0.100655] NOTICE: BL2: Lossy Decomp areas

[ 0.104832] NOTICE: Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570

[ 0.111917] NOTICE: Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0

[ 0.118829] NOTICE: Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0

[ 0.125743] NOTICE: BL2: v1.3(release):4eef9a2

[ 0.130233] NOTICE: BL2: Built : 17:35:56, Jul 13 2017

[ 0.135420] NOTICE: BL2: Normal boot

[ 0.139062] NOTICE: BL2: dst=0xe6320190 src=0x8180000 len=512(0x200)

[ 0.145608] NOTICE: BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)

[ 0.152070] NOTICE: BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)

[ 0.159295] NOTICE: BL2: dst=0x44100000 src=0x8200000 len=524288(0x80000)

[ 0.169775] NOTICE: BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)

05:25, 17 July 2017

I'm not sure if the Renesas engineers are watching these pages to handle support requests. I think you would be better served by asking the question on their board mailing list. See http://elinux.org/R-Car#R-Car_Community.

15:13, 17 July 2017

I have done so. It looks like my problem is similar to the "Firmware update hangs" thread below except that I can actually get the firmware update to happen. The update obviously doesn't work though since U-Boot doesn't load when it should.

00:57, 18 July 2017

I have the same h3ulcb board(RTP0RC77951SKBX010SA00) as you. I updated the loader but it started normally.

[    0.000194] NOTICE:  BL2: R-Car Gen3 Initial Program Loader(CA57) Rev.1.0.14
[    0.005761] NOTICE:  BL2: PRR is R-Car H3 Ver2.0
[    0.010335] NOTICE:  BL2: Board is unknown Rev0.0
[    0.015006] NOTICE:  BL2: Boot device is HyperFlash(80MHz)
[    0.020445] NOTICE:  BL2: LCM state is CM
[    0.024423] NOTICE:  BL2: AVS setting succeeded. DVFS_SetVID=0x52
[    0.030611] NOTICE:  BL2: DDR3200(rev.0.22)NOTICE:  [COLD_BOOT]NOTICE:  ..0
[    0.091235] NOTICE:  BL2: DRAM Split is 4ch
[    0.095121] NOTICE:  BL2: QoS is default setting(rev.0.14)
[    0.100621] NOTICE:  BL2: Lossy Decomp areas
[    0.104798] NOTICE:       Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
[    0.111883] NOTICE:       Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0
[    0.118795] NOTICE:       Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0
[    0.125709] NOTICE:  BL2: v1.3(release):4eef9a2
[    0.130199] NOTICE:  BL2: Built : 10:20:37, Jul 19 2017
[    0.135386] NOTICE:  BL2: Normal boot
[    0.139028] NOTICE:  BL2: dst=0xe6320190 src=0x8180000 len=512(0x200)
[    0.145574] NOTICE:  BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)
[    0.152037] NOTICE:  BL2: dst=0x44000000 src=0x81c0000 len=65536(0x10000)
[    0.159261] NOTICE:  BL2: dst=0x44100000 src=0x8200000 len=524288(0x80000)
[    0.169741] NOTICE:  BL2: dst=0x50000000 src=0x8640000 len=1048576(0x100000)


U-Boot 2015.04 (Jul 19 2017 - 10:20:39)

CPU: Renesas Electronics R8A7795 rev 2.0
Board: H3ULCB
I2C:   ready
DRAM:  3.9 GiB
MMC:   sh-sdhi: 0, sh-sdhi: 1
In:    serial
Out:   serial
Err:   serial
Net:   ravb
Hit any key to stop autoboot:  0
=>

However, the following are different.

[    0.100623] NOTICE:  BL2: Lossy Decomp areas
[    0.104798] NOTICE:       Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570
(snip)

It seems that you changed something. At first, could you build according to procedure of elinux?

17:31, 18 July 2017

I'm sorry. The log was completely the same halfway. Have you updated all the files?

- bootparam_sa0.srec
- bl2-h3ulcb.srec
- cert_header_sa6.srec
- bl31-h3ulcb.srec
- tee-h3ulcb.srec
- u-boot-elf.srec
17:50, 18 July 2017

Yes. One thing that wasn't clear to me was where to actually get those files. I've been using the ones that are found in ~/tmp/deploy/images/h3ulcb/ after building yocto. Assuming that's the correct path, I'm going to try rebuilding yocto in case I messed something up in that process.

One possible indication of what the issue is: I looked through the Renesas Device Manual https://www.renesas.com/en-us/doc/products/rcar/R-Car_StarterKit_Gen3_H3_M3_DEV_Rev.053.pdf to find a solution and found that in the section on booting the addresses the board boots from are slightly different from those on the e-linux wiki (looking at page 238 in particular). I'm a machine learning guy by trade and my architecture knowledge is rather scant comparatively so maybe this is nothing/not what I thought it means.

23:10, 18 July 2017
 
 
 
 
 

Build for Yocto Gen3 not completing.

I started developing the Yocto Gen3 for the Renesas M3SK. I followed the guide at the link: http://elinux.org/R-Car/Boards/Yocto-Gen3

I was able to complete till step 11 in the 'Building the BSP for Renesas H3ULCB, M3ULCB section'. During the bitbake process I got an error as follows.

NOTE: Sending SIGTERM to runqemu WARNING: Qemu ended unexpectedly, dump data from host is in /tmp/oe-saved-tests/201706200953_qemu DEBUG: Python function do_testimage_auto finished ERROR: Function failed: do_testimage_auto ERROR: Task 10 (/home/pisquare-dev/Yocto/build/build/../poky/meta/recipes-graphics/images/core-image-weston.bb, do_testimage_auto) failed with exit code '1' NOTE: Tasks Summary: Attempted 5155 tasks of which 5154 didn't need to be rerun and 1 failed. No currently running tasks (5154 of 5156)

Summary: 1 task failed:

 /home/pisquare-dev/Yocto/build/build/../poky/meta/recipes-graphics/images/core-image-weston.bb, do_testimage_auto


Please help me with this issue.

08:16, 20 June 2017

Seems that you enabled TEST_IMAGE option in your local.conf:

Please comment it back:

  1. TEST_IMAGE = "1"

In case you need to use it then you need properly setup QEMU on your host machine.

02:45, 21 June 2017

That worked out

Thanks for the assist !

14:00, 27 June 2017
 
 

Firmware update hangs

I got a new WS1.1 Premier starter kit, tried to build 2.19.0 but the kernel was crashing.

Tried to upgrade the firmware, but it failed to download bl2 srec. Now, it is not even booting into u-boot.

I tried downloading the firmware from windows PC (Teraterm) and Linux (minicom), boot params is getting programmed. I can't program none of the other firmware as given in the instructions.

Either it hangs after sending the file (bl2, bl32, cert), or over size error (uboot)

Any inputs to recover the board is welcome.

09:41, 31 May 2017

Address of bl2 has been chenged from Yocto v2.17.0. Please check the following page. http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware

18:39, 4 June 2017

yeah, following the exact instruction in your link. After downloading the bl2 the mini monitor is stuck.

I see that the board can boot into SCIF download, is it possible recover the board by this route?

02:30, 5 June 2017

I've attached the my log.

H3 SAMPLE LOADER V1.16 2016.10.24                                                          
 CPU   : AArch64 CA57                                                                      
 DRAM  : LPDDR4 DDR3200 DEVICE: QSPI Flash(S25FS128) at 40MHz DMA                          
 BOOT  : Normal Boot                                                                       
 Backup: DDR Cold Boot                                                                     
                                                                                           
 jump to 0xE6330000                                                                        
                                                                                           
H3 MiniMonitor V0.23 2016.10.24                                                            
 Work Memory SystemRAM (H'E6328000-H'E632FFFF)                                             
>                                                                                          
>                                                                                          
>xls2                                                                                      
===== Qspi/HyperFlash writing of Gen3 Board Command =============                          
Load Program to Spiflash                                                                   
Writes to any of SPI address.                                                              
Please select,FlashMemory.                                                                 
   1 : QspiFlash       (U5 : S25FS128S)                                                    
   2 : QspiFlash Board (CN2: S25FL512S)                                                    
   3 : HyperFlash      (SiP internal)                                                      
  Select (1-3)>3                                                                           
 READ ID OK.                                                                               
Program Top Address & Qspi/HyperFlash Save Address                                         
===== Please Input Program Top Address ============                                        
  Please Input : H'e6304000                                                                
                                                                                           
===== Please Input Qspi/HyperFlash Save Address ===                                        
  Please Input : H'40000                                                                   
Work RAM(H'50000000-H'53FFFFFF) Clear....
please send ! ('.' & CR stop load)                                                         
H'00040000-0007FFFF Erasing..Erase Completed 
SAVE SPI-FLASH....... complete!

======= Qspi/HyperFlash Save Information  =================
 SpiFlashMemory Stat Address : H'00040000
 SpiFlashMemory End Address  : H'0005B03B
===========================================================

>

If you don't solve it please attach your log.

00:38, 6 June 2017

Issue is not yet resolved, please see log below.


H3 SAMPLE LOADER V1.17 2016.11.08

CPU   : AArch64 CA57
DRAM  : LPDDR4 DDR3200
DEVICE: QSPI Flash(S25FS128) at 40MHz DMA
BOOT  : Normal Boot
Backup: DDR Cold Boot
jump to 0xE6330000

H3 MiniMonitor V0.24 2016.11.08

Work Memory SystemRAM (H'E6328000-H'E632FFFF)

>xls2

Qspi/HyperFlash writing of Gen3 Board Command ========[edit]

Load Program to Spiflash Writes to any of SPI address. Please select,FlashMemory.

  1 : QspiFlash       (U5 : S25FS128S)
  2 : QspiFlash Board (CN2: S25FL512S)
  3 : HyperFlash      (SiP internal)
 Select (1-3)>3
READ ID OK.

Program Top Address & Qspi/HyperFlash Save Address

Please Input Program Top Address =======[edit]
 Please Input : H'e6320000

== Please Input Qspi/HyperFlash Save Address[edit]

 Please Input : H'0

Work RAM(H'50000000-H'53FFFFFF) Clear.... please send ! ('.' & CR stop load) SPI Data Clear(H'FF) Check :H'00000000-0003FFFF Erasing..Erase Completed SAVE SPI-FLASH....... complete!

= Qspi/HyperFlash Save Information ===========[edit]
SpiFlashMemory Stat Address : H'00000000
SpiFlashMemory End Address  : H'00000E67
===============================================[edit]

>xls2

Qspi/HyperFlash writing of Gen3 Board Command ========[edit]

Load Program to Spiflash Writes to any of SPI address. Please select,FlashMemory.

  1 : QspiFlash       (U5 : S25FS128S)
  2 : QspiFlash Board (CN2: S25FL512S)
  3 : HyperFlash      (SiP internal)
 Select (1-3)>3
READ ID OK.

Program Top Address & Qspi/HyperFlash Save Address

Please Input Program Top Address =======[edit]
 Please Input : H'44000000

== Please Input Qspi/HyperFlash Save Address[edit]

 Please Input : H'1C0000

Work RAM(H'50000000-H'53FFFFFF) Clear.... please send ! ('.' & CR stop load) Program over size Error

SpiFlashMemory Stat Address : H'001C0000
SpiFlashMemory End Address  : H'105C05D3

>xls2

Qspi/HyperFlash writing of Gen3 Board Command ========[edit]

Load Program to Spiflash Writes to any of SPI address. Please select,FlashMemory.

  1 : QspiFlash       (U5 : S25FS128S)
  2 : QspiFlash Board (CN2: S25FL512S)
  3 : HyperFlash      (SiP internal)
 Select (1-3)>3
READ ID OK.

Program Top Address & Qspi/HyperFlash Save Address

Please Input Program Top Address =======[edit]
 Please Input : H'e6302000

== Please Input Qspi/HyperFlash Save Address[edit]

 Please Input : H'40000

Work RAM(H'50000000-H'53FFFFFF) Clear.... please send ! ('.' & CR stop load)

01:25, 8 June 2017

> Please Input : H'e6302000 This is wrong address. e6304000 is correct.

I added a table to the wiki. please check again.

http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware

17:57, 18 June 2017
 
 
 
 
 

CA57CA53BOOT

Currently, two CA57s are running in StarterKitPro. Could you tell me how to boot with six cores total of two CA57s and four CA53s?

To try it here, CA57CA53BOOT = "1" was added to local.conf.

root@m3ulcb:~# cat /proc/cpuinfo
processor       : 0
BogoMIPS        : 16.66
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x1
CPU part        : 0xd07
CPU revision    : 3

processor       : 1
BogoMIPS        : 16.66
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x1
CPU part        : 0xd07
CPU revision    : 3
23:55, 15 May 2017

Hi

This is quoted from the AGL mailing list.

[agl-discussions] A53 CPU on renesas board? 2017/05/10 (水) 18:01

> Out of curiosity, A53 cores on R-Car board (in additoin to A57 cores) could also be enabled for AGL system easily (for accelaration), or rather to be used to host different OSs?
>
Hello,
In order to enable the A53 CPU's on the r-car boards, you need to add this line in
meta-rcar/meta-rcar-gen3/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb:
export PSCI_DISABLE_BIGLITTLE_IN_CA57BOOT="0"
and rebuild and reflash the firmware as explained in http://elinux.org/R-Car/Boards/M3SK.

Is this useful for you?

22:25, 17 May 2017

Thank you very much.
I solved it.

16:56, 21 May 2017
 
 

I can not build Linux (2.16.0) for HAD Solution Kit.

I am trying to build Linux (2.16.0) for HAD Solution Kit.
However, the following error message appears and can not be built.
Is there anything you can understand?

ERROR: gstreamer1.0-plugins-bad-1.6.3-r0 do_init_submodule: Function failed: do_init_submodule (log file is located at /mnt/work/build/tmp/work/aarch64-poky-linux/gstreamer1.0-plugins-bad/1.6.3-r0/temp/log.do_init_submodule.18637)
ERROR: Logfile of failure stored in: /mnt/work/build/tmp/work/aarch64-poky-linux/gstreamer1.0-plugins-bad/1.6.3-r0/temp/log.do_init_submodule.18637
ERROR: Task 1796 (/mnt/work/build/../poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.6.3.bb, do_init_submodule) failed with exit code '1'
ERROR: gstreamer1.0-plugins-good-1.6.3-r0 do_init_submodule: Function failed: do_init_submodule (log file is located at /mnt/work/build/tmp/work/aarch64-poky-linux/gstreamer1.0-plugins-good/1.6.3-r0/temp/log.do_init_submodule.23409)
ERROR: Logfile of failure stored in: /mnt/work/build/tmp/work/aarch64-poky-linux/gstreamer1.0-plugins-good/1.6.3-r0/temp/log.do_init_submodule.23409
ERROR: Task 1782 (/mnt/work/build/../poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-good_1.6.3.bb, do_init_submodule) failed with exit code '1'
ERROR: kernel-module-vspm-1.0-r0 do_populate_lic: The recipe kernel-module-vspm is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/mnt/work/build/tmp/deploy/licenses/kernel-module-vspm/generic_MIT
Matched in manifest-salvator_x-kernel-module-vspm.populate_lic
/mnt/work/build/tmp/deploy/licenses/kernel-module-vspm/GPL-COPYING
Matched in manifest-salvator_x-kernel-module-vspm.populate_lic
/mnt/work/build/tmp/deploy/licenses/kernel-module-vspm/generic_GPLv2
Matched in manifest-salvator_x-kernel-module-vspm.populate_lic
/mnt/work/build/tmp/deploy/licenses/kernel-module-vspm/recipeinfo
Matched in manifest-salvator_x-kernel-module-vspm.populate_lic
/mnt/work/build/tmp/deploy/licenses/kernel-module-vspm/MIT-COPYING
Matched in manifest-salvator_x-kernel-module-vspm.populate_lic
Please verify which recipe should provide the above files.
The build has stopped as continuing in this scenario WILL break things, if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error however switching DISTRO_FEATURES on an existing build directory is not supported, you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above.
ERROR: kernel-module-vspm-1.0-r0 do_populate_lic: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases.
ERROR: kernel-module-vspm-1.0-r0 do_populate_lic: Function failed: sstate_task_postfunc
ERROR: Logfile of failure stored in: /mnt/work/build/tmp/work/h3ulcb-poky-linux/kernel-module-vspm/1.0-r0/temp/log.do_populate_lic.16804
ERROR: Task 1578 (/mnt/work/build/../meta-renesas/meta-rcar-gen3/recipes-kernel/kernel-module-vspm/kernel-module-vspm.bb, do_populate_lic) failed with exit code '1'
02:45, 1 March 2017
$ sudo apt-get update
$ sudo apt-get upgrade

I am doing these, but it is not going well.

03:05, 1 March 2017
 

Please hold on until the end of this week

The BSP2.16 supports only basic/reference boards

HAD and .View boards will be added this week.

Please use temporary bsp2.12 http://elinux.org/R-Car/Boards/Yocto-Gen3-legacy

04:24, 1 March 2017

Regarding Yocto 2.16.0 for HAD solution kit, we tried 5155 tasks which were all successful, without having to retry.
Thank you.

21:52, 5 March 2017
 
 

Error in Bitbake

Hi

I followed all the steps to make yocto image.
I get the following error during bitbake.
Please tell me How can i solve this error.

Regard.



Build Configuration:
BB_VERSION = "1.28.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-14.04"
TARGET_SYS = "aarch64-poky-linux"
MACHINE = "m3ulcb"
DISTRO = "poky"
DISTRO_VERSION = "2.0.2"
TUNE_FEATURES = "aarch64 cortexa57-cortexa53"
TARGET_FPU = ""
SOC_FAMILY = "rcar-gen3:r8a7796"
meta
meta-yocto
meta-yocto-bsp = "tmp:40376446904ae3529be41737fed9a0b650ed167d"
meta-rcar-gen3 = "v2.12.0:2b0598e0a252a8cf1dc4edacf4ef3a7071dbfd87"
meta-linaro-toolchain = "tmp:9b1fd178309544dff1f7453e796a9437125bc0d9"
meta-oe = "tmp:8ab04afbffb4bc5184cfe0655049de6f44269990"






In file included from .../work/build/tmp/work/aarch64-poky-linux/gstreamer1.0-plugins-bad/1.4.5-r0/git/ext/wayland/gstwaylandsink.h:30:0,
from .../work/build/tmp/work/aarch64-poky-linux/gstreamer1.0-plugins-bad/1.4.5-r0/git/ext/wayland/gstwaylandsink.c:44:
.../work/build/tmp/work/aarch64-poky-linux/gstreamer1.0-plugins-bad/1.4.5-r0/git/ext/wayland/wldisplay.h:27:42: fatal error: linux-dmabuf-client-protocol.h: No such file or directory
compilation terminated.
make[3]: *** [libgstwaylandsink_la-gstwaylandsink.lo] Error 1
make[3]: Leaving directory `.../work/build/tmp/work/aarch64-poky-linux/gstreamer1.0-plugins-bad/1.4.5-r0/build/ext/wayland'
make[2]: *** [wayland] Error 2
make[2]: Leaving directory `.../work/build/tmp/work/aarch64-poky-linux/gstreamer1.0-plugins-bad/1.4.5-r0/build/ext'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `.../work/build/tmp/work/aarch64-poky-linux/gstreamer1.0-plugins-bad/1.4.5-r0/build'
make: *** [all] Error 2
WARNING: exit code 1 from a shell command.
ERROR: oe_runmake failed
ERROR: Function failed: do_compile (log file is located at .../work/build/tmp/work/aarch64-poky-linux/gstreamer1.0-plugins-bad/1.4.5-r0/temp/log.do_compile.2811)
ERROR: Task 2138 (.../work/build/../poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.4.5.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2510 tasks of which 2509 didn't need to be rerun and 1 failed.
No currently running tasks (2509 of 4905)

19:40, 12 January 2017

Hi

I have the same problem. Did anyone find any solution in the meantime?

Regard.

06:43, 23 February 2017

I am using ubuntu 14.04 LTE. I solved it by executing the following command.

 $ sudo apt-get update
 $ sudo apt-get upgrade

After that,

 $ sudo apt-get install ***

Was executed.

02:58, 1 March 2017

And *** stands for what?

06:44, 2 March 2017

The

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

It is.

That is,

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

execute.

16:56, 5 March 2017
 
 
 
 

I can't build Linux for the R-Car-M3 Starter Kit Pro.

I tried building Linux for the R-Car-M3 Starter Kit Pro according to the guide, It can not be built due to an error in bitbake.
Please tell me how to solve it.

The operation is as follows.

First, I downloaded and unpacked zip files.
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20160906.zip
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20160906.zip

Then I unzipped these.
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20160906.tar.gz
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20160906.tar.gz

Next, I installed the package.
$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-dev xterm python-crypto

I built a BSP.

1.
$ mkdir build
$ cd build
$ export WORK=`pwd`

2.
cd $WORK
$ git clone git://git.yoctoproject.org/poky
$ git clone git://git.openembedded.org/meta-openembedded
$ git clone git://git.linaro.org/openembedded/meta-linaro.git

3.
$ cd $WORK/poky
$ git checkout -b tmp 40376446904ae3529be41737fed9a0b650ed167d
$ cd $WORK/meta-openembedded
$ git checkout -b tmp 8ab04afbffb4bc5184cfe0655049de6f44269990
$ cd $WORK/meta-linaro
$ git checkout -b tmp 9b1fd178309544dff1f7453e796a9437125bc0d9

4.
$ cd $WORK
$ git clone git://github.com/CogentEmbedded/meta-rcar.git meta-renesas -b v2.12.0

5.
$ cd $WORK/meta-renesas
$ export PATCH_DIR=meta-rcar-gen3/docs/sample/patch/patch-for-linaro-gcc
$ patch -p1 < ${PATCH_DIR}/0001-rcar-gen3-add-readme-for-building-with-Linaro-Gcc.patch
$ unset PATCH_DIR

6.
$ ls -1 $WORK/proprietary
R-Car_Gen3_Series_Evaluation_Software_Package_for_Linux-20160906.tar.gz
R-Car_Gen3_Series_Evaluation_Software_Package_of_Linux_Drivers-20160906.tar.gz

7.
$ export PKGS_DIR=$WORK/proprietary
$ cd $WORK/meta-renesas
$ sh meta-rcar-gen3/docs/sample/copyscript/copy_evaproprietary_softwares.sh -f $PKGS_DIR
$ unset PKGS_DIR

8.
$ cd $WORK
$ source poky/oe-init-build-env

9.
$ cp $WORK/meta-renesas/meta-rcar-gen3/docs/sample/conf/m3ulcb/linaro-gcc/mmp/*.conf ./conf/
$ cd $WORK/build
$ cp conf/local-wayland.conf conf/local.conf

10.
I am not care.

11.
enabled
MACHINE_FEATURES_append = " m3ulcb-view"

12.
enabled
DISTRO_FEATURES_append = " use_eva_pkg"

13.
$ bitbake core-image-weston


At this time, the following error message was output.

 ERROR: Nothing PROVIDES 'python-pycrypto-native' (but /media/rcar/Test_M3_Starterkitpro_yocto2.12.0/work/build/build/../meta-renesas/meta-rcar-gen3/recipes-bsp/optee/optee-os_git.bb DEPENDS on or otherwise requires it). Close matches:
   python-pycairo-native
   python-pycurl-native
   python-pyrex-native
 ERROR: Required build target 'core-image-weston' has no buildable providers.
 Missing or unbuildable dependency chain was: ['core-image-weston', 'optee-os', 'python-pycrypto-native']


03:31, 14 December 2016

I have corrected the link for the BSP download on that page, and have now overcome this build issue. Please have a look at updated step 4 in the build instructions.

Pat Shelly

11:04, 15 December 2016
 
13:00, 15 December 2016

Thank you for your support.
If there is something again, thank you.

16:52, 21 December 2016