View source for Special:NewMessages

Jump to: navigation, search
First page
First page
Next page
Next page
Last page
Last page

Full thread

From Talk:R-Car/Boards/Yocto-Gen3

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
 
 
 
 

Full thread

From Talk:R-Car/Boards/Yocto-Gen3

I would like to introduce NTL library to R-CarH3

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

 

Return to Thread:Talk:R-Car/Boards/Yocto-Gen3/I would like to introduce NTL library to R-CarH3.

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
 
 

Full thread

From Talk:R-Car/Boards/Yocto-Gen3

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...
Gumma (talk)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.

Gumma (talk)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.

Gumma (talk)15:57, 24 October 2018
 
 
 

Full thread

From Talk:R-Car/Boards/Yocto-Gen3

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
 

Full thread

From Talk:R-Car/Boards/Yocto-Gen3

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.

RenesasJa (talk)17:17, 3 October 2018
 

Full thread

From Talk:R-Car/Boards/Yocto-Gen3

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.

Chetan (talk)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.

Chetan (talk)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

We understood no support considered for S2R so far. Thanks, Gohda-san, Chetan-san.

WN

04:34, 9 August 2018
 
 
 
 
 
 

Full thread

From Talk:R-Car/Boards/Yocto-Gen3

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

Cdorbell (talk)10:39, 20 February 2018

Full thread

From Talk:R-Car/Boards/Yocto-Gen3

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.

TNoda (talk)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.

TNoda (talk)17:52, 14 December 2017
 
 

Full thread

From Talk:R-Car/Boards/Yocto-Gen3

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??

Ipodslessteven (talk)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)
Ipodslessteven (talk)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

Cdorbell (talk)03:33, 11 January 2018
 
 
 
 
First page
First page
Next page
Next page
Last page
Last page