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

AGL 6.0.0 booting on R-Car H3 not completed

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/AGL 6.0.0 booting on R-Car H3 not completed.

Hi, I report because this issue progress has changed.

I seemed that the U-boot parameters(discribed at 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.

19: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.

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

Ygohda (talk)03: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.

16: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:


Patch title also contains the same:

media: soc_camera: add legacy VIN/CSI2 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

Wnatsume (talk)21:37, 19 August 2018

It seems that it is currently active in the public place.

Ygohda (talk)00:13, 20 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?

Thanks, WN

Wnatsume (talk)21:33, 19 August 2018

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

RenesasJa (talk)18: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.)


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)



Wnatsume (talk)19: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.

Ygohda (talk)22: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)19: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?

Ygohda (talk)22: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)18: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.)

Ygohda (talk)19:32, 31 July 2018

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


Wnatsume (talk)05:34, 9 August 2018

Full thread

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

Camera Low lever test issue on H3 Adas


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?

Cdorbell (talk)11: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)18:23, 7 December 2017

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

Ygohda (talk)03: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)18: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)11:52, 17 October 2017


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.

- 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

3. bitbake

4. How to run
 # 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.
Ygohda (talk)04:38, 23 October 2017

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

I refer &

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)07:33, 23 October 2017
Ygohda (talk)22: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)04:33, 11 January 2018
First page
First page
Next page
Next page
Last page
Last page