Talk:R-Car/Boards/Kingfisher

From eLinux.org
Jump to: navigation, search

We have moved Q&A page to Renesas Rulz site.
Please submit a question to new site.
URL: http://renesasrulz.com/r-car-h3-m3-cockpit/

Contents

Thread titleRepliesLast modified
Yocto Image for H3ULCB+Kingfisher M041008:02, 9 April 2020
HDMI DU_DOTCLKOUT frequency on Kingfisher205:23, 28 November 2019
How to use Leopard Imaging LI-OV10635-GMSL323:44, 11 September 2019
About 60fps Camera for R-car103:32, 22 August 2019
USB3 ports not detected on King Fisher101:13, 10 May 2019
LVDS Camera driver source code218:52, 19 September 2018
HDMI output221:19, 23 April 2018
Debug serial I/F221:19, 23 April 2018
About 440p_ComExpress CN1B B055317:58, 15 April 2018
Kernel image for Kingfisher205:15, 9 March 2018
How to connect Starter Kit to Kingfisher and use Starter Kit's JTAG I/F402:55, 5 March 2018

Yocto Image for H3ULCB+Kingfisher M04

What is the best way to create a Linux Yocto (preferably 3.21) for the H3ULCB+Kingfisher M04 configuration?


I tried the build instructions from here, but the image doesn't boot: https://elinux.org/R-Car/Boards/Kingfisher#Build_image

During the Kernel startup I get a panic:

[ 1.531217] loop: module loaded

[ 1.537959] renesas-rpc ee200000.rpc0: using DMA read (dma0chan0)

[ 1.544521] Bad mode in Error handler detected on CPU1, code 0xbf000000 -- SError

[ 1.552007] Internal error: Oops - bad mode: 0 [#1] PREEMPT SMP


Full details here: http://renesasrulz.com/adas/f/adas---forum-1845141225/15725/boot-failure-on-renesas-h3ulcb-kingfisher-board-based-on-r8a7795-es2-0/51386#51386


How can I build a Image which supports the Kingfisher features (especially 8ch. audio and USB3.0): https://elinux.org/R-Car/Boards/Kingfisher#S.2FW_support_status

07:03, 26 March 2020

Hello,


I confirmed that Yocto v3.21.0 is booted on H3ULCB(ES2.0 8GB) + KF(M04).

I checked your boot log, and noticed IPL and U-boot is old.

So, please update IPL and U-boot, then try to boot again.


Best regards.

01:01, 27 March 2020

Thanks for your help!

I have to admit that the boot log from the link above is not mine (just the error was the same).

My u-boot and IPL is newer, here is my full log of the kernel Oops: https://pastebin.com/wiXmDzxz

It is a dual-boot system which can also boot Android (for development), so the bootloader is from the Android build. I hope that's not the problem?

Here is my u-boot environment: https://pastebin.com/qqw8cJJS

01:59, 27 March 2020

Sorry, I have never used android on H3ULCB + KF.

But, I tested Yocto v3.21.0 on H3ULCB(ES2.0 4GB) + KF(M04) again.

And I confirmed that it works.


How about using yocto bootloader ?

if yocto can be booted, android bootloder may not be good for yocto...


Best regards.

03:18, 27 March 2020

Thanks for your help Y.H. With the Yocto-Firmware it boots as expected.

How I need to get the Android part working again, but boota is not supported in the Yocto's u-boot. But that's a different story now.

07:44, 30 March 2020

Hello,


I prepared android 9 for H3ULCB(ES2.0 4GB) + KF(M4), and tested for booting yocto.

In my environment, yocto was booted with android's IPL and U-boot.


If you use old version of android, how about updating it ?

23:26, 1 April 2020
 
 
 
 
 

HDMI DU_DOTCLKOUT frequency on Kingfisher

Hi,

What is the maximum supported frequency for DU_DOTCLKOUT on Kingfisher (not ULCB)? Need to understand limitations of "SoC's DU (digital RGB out) -> ADV7513 (HDMI)" pipeline. According to chapter "4.13. HDMI" of http://www.shimafuji.co.jp/wp/wp-content/uploads/2018/04/SBEV-RCAR-KF-M05Board_HWSpecificationENRev120.pdf maximum supported resolution is 1920x1080i. But this manual does not tell maximum framerate and so maximum supported frequency is not clear.

Sincerely, Yaroslav

07:43, 21 November 2019

Hi

The maximum frequency of Kingfisher is 100MHz(DOTCLKOUT: Min 10ns).

01:48, 25 November 2019

Thank you.

05:23, 28 November 2019
 
 

How to use Leopard Imaging LI-OV10635-GMSL

Hi,

I am trying to use Leopard Imaging LI-OV10635-GMSL with Kingfisher.
Is there a difference in BSP build procedure for LI-OV10635-GMSL and RDACM21?
Is there any difference in handling on Linux?

Best Regards.

19:04, 1 September 2019

Please add the following to bootargs when linux starts up. ov106xx.dvp_order=0

23:02, 4 September 2019

I want to try it as soon as I get a camera.
Thank you very much.

19:58, 5 September 2019
 

I was able to solve this.
Thank you very much.

23:44, 11 September 2019
 
 

About 60fps Camera for R-car

Hi,
I'm looking for 60fps Camera for R-Car.
Because IMI camera RDACM21 is discontinued.
So, Can you please give me information about 60fps Camera that has been used successfully for R-car Kingfisher.
Best Regards.

00:56, 20 August 2019

The following cameras are currently supported: https://elinux.org/R-Car/Boards/Kingfisher#Connection-confirmed_Hardware_information

Development will continue, but the schedule is undecided. Please check the eLinux site regularly.

03:32, 22 August 2019
 

USB3 ports not detected on King Fisher

Hi,

Linux does not detect the RCAR M3 USB3 ports.

m3ulcb login: root Last login: Tue Apr 23 11:47:22 UTC 2019 on tty2 root@m3ulcb:~# lsusb Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Board SBEV-RCAR-KF-M06

U-Boot 2015.04 (Oct 17 2016 - 14:46:11)

The following is the Yocto Build Configuration

Build Configuration: BB_VERSION = "1.36.0" BUILD_SYS = "i686-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "aarch64-poky-linux" MACHINE = "m3ulcb" DISTRO = "poky" DISTRO_VERSION = "2.4.2" TUNE_FEATURES = "aarch64 cortexa57-cortexa53" TARGET_FPU = "" SOC_FAMILY = "rcar-gen3:r8a7796" meta meta-poky meta-yocto-bsp = "tmp:342fbd6a3e57021c8e28b124b3adb241936f3d9d" meta-rcar-gen3 = "tmp:fd078b6ece537d986852cb827bd21e022a797b2f" meta-optee = "tmp:75dfb67bbb14a70cd47afda9726e2e1c76731885" meta-oe = "tmp:dacfa2b1920e285531bec55cd2f08743390aaf57" meta-rcar-gen3-adas = "v3.9.0:c9fe17a631ea887fd682e3071e5cf62be8f021ef"

Kind Regards, Declan

06:13, 8 May 2019

USB3.0(CN2) cannot use with M3 SK. This is a limitation of M3 SK.

If you want to use USB3 ports, please use the H3 SK.

01:13, 10 May 2019
 

LVDS Camera driver source code

Is there LVDS camera driver source code available?
If any, please let me know the source code file path?
Thanks.

19:17, 12 September 2018

HDMI output

Is Kingfisher's HDMI output terminal CN49 ?
Can I use StarterKit's CN4 (HDMI mini) ?

01:29, 19 April 2018

You can use both (at the same time).

18:48, 19 April 2018

Thank you for your answer.

21:19, 23 April 2018
 
 

Debug serial I/F

Is Kingfisher's debug serial I/F CN4 ?
Can I use StarterKit's CN12 ?

01:29, 19 April 2018

Please use Starter Kit's CN12.

18:45, 19 April 2018

O.K.

But... What is Kingfisher's CN4 used for?

21:19, 23 April 2018
 
 

About 440p_ComExpress CN1B B055

I am investigating the connection relationship between Kingfisher (* 1) and StarterKit (* 2). (* 1), B055 of 440p_ComExpress is named IrqEXT0xE8 and it is connected with INT of U11 (TCA9539QPWRQ1).
(* 2), B055 of 440p_ComExpress is named AVB_AVTP_MATCH / SCL5 and is connected to B11 (AVB_AVTP_MATCH_A) of R-Car SiP.
How will it work (how do you communicate) with B055 when connecting (* 1) and (* 2) together?

(*1)Kingfisher(SBEV-RCAR-KF-M05)
http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/files/sbev-rcar-kf-m05_Rev3.2.pdf
440p_ComExpress CN1B B055

(*2)StarterKit(RTP0RC77951SKBX010SA01)
https://www.renesas.com/en-us/doc/products/rcar/R-Car_StarterKit_Gen3_SCH_Rev.110.pdf
440p_ComExpress CN1B B055

BACKGROUND:
When Kingfisher upgraded from M04 to M05, it seems that the connection has changed from A079 to B055, so I am investigating the reason.

22:36, 19 March 2018

440p_ComExpress B055 is an output terminal (INT output of IO Expander) for Kingfisher.
Even for StarterKit I think that it is an output terminal (AVB_AVTP_MATCH output of R - CarGen 3).
Therefore, I think that the outputs collide with each other.
Is my understanding wrong?

17:24, 22 March 2018

B055 of KF will be used as GP2_13(input) instead of AVB_AVTP_MATCH.

00:01, 23 March 2018

Thank you very much.
understood.

17:58, 15 April 2018
 
 
 

Kernel image for Kingfisher

Is the procedure shown in https://elinux.org/R-Car/Boards/Kingfisher#Build_image for SBEV-RCAR-KF-M04 or for the latest version of SBEV-RCAR-KF-M05?

05:26, 8 March 2018

I've never seen SBEV-RCAR-KF-M05 board. I'll check if I get the board.Do you have it?

04:48, 9 March 2018

I also do not have the SBEV-RCAR-KF-M05 board as well.
http://www.shimafuji.co.jp/DL/EN/InfotainmentCarrierBoard/#M05
I am worried about whether the Linux build procedure differs between SBEV-RCAR-KF-M04 and SBEV-RCAR-KF-M05.
If it is different, could you show it?

I have an SBEV-RCAR-KF-M04 board and I was planning to setup it from now.

05:09, 9 March 2018
 
 

How to connect Starter Kit to Kingfisher and use Starter Kit's JTAG I/F

I am using Kingfisher (SBEV-RCAR-KF-M04(Advanced Model)).
With Starter Kit connected to M04, Kingfisher manufacturer taught that Starter Kit's JTAG I/F can not be used.
However, by correcting the circuit on Starter Kit side, he taught him that Starter Kit's JTAG I/F can be used even when Starter Kit is connected to M04.

Please tell me about Starter Kit circuit correction contents necessary to use Starter Kit's JTAG I/F with Starter Kit connected to M04.

19:25, 19 February 2018

I think the problem is that the TMS_18 signal is connected to GND. As one method, cutting the signal of SK seems to be able to avoid the problem. However, I think that it is very difficult to cut short distances from other signals(for me at least).

Anyway, please give me time to cut and confirm.

20:14, 22 February 2018

Thank you for your response.
I will consider the correspondence.

22:27, 27 February 2018

I cut the signal of SK. Please refer to the picture on the back side of SK.

File:SK TMS18.zip

Then, I connected SK and M04 KF and confirmed that JTAG started up.

Note: Cutting the signal is very difficult. I can not recommend it.

22:02, 4 March 2018

Thank you for confirmation.

Wow! You are good with your hands!
I certainly think it is difficult to cut this.

02:55, 5 March 2018