View source for Talk:R-Car/Boards/Yocto-Gen3

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/

First page
First page
Next page
Next page
Last page
Last page

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

21:37, 19 August 2018

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

00:13, 20 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

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.

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.

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?

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.

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.)

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

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

11: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.
04: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)
07:33, 23 October 2017
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

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

18:23, 7 December 2017

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

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.

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

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

18:09, 16 November 2017
 

Installing PyCaffe

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/Installing PyCaffe.

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

11: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
Kazu (talk)16: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.

23:55, 5 October 2017

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

Kazu (talk)16:22, 9 October 2017
 

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

Kazu (talk)23: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)

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

Tim Bird (talk)16: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.

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

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

00:10, 19 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.

Smodak (talk)09: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.

Cogente (talk)03:45, 21 June 2017

That worked out

Thanks for the assist !

Smodak (talk)15: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.

KarthikShanmugam (talk)10: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

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

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

01: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)

KarthikShanmugam (talk)02: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

18: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
ryuohno (talk)00:55, 16 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?

23:25, 17 May 2017

Thank you very much.
I solved it.

ryuohno (talk)17: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'
ryuohno (talk)03:45, 1 March 2017
$ sudo apt-get update
$ sudo apt-get upgrade

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

ryuohno (talk)04: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

Cogente (talk)05: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.

ryuohno (talk)22: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)

Ksawa (talk)20:40, 12 January 2017

Hi

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

Regard.

VikiC (talk)07: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.

ryuohno (talk)03:58, 1 March 2017

And *** stands for what?

VikiC (talk)07: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.

ryuohno (talk)17: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']


Ryuohno (talk)04: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

PatShelly (talk)12:04, 15 December 2016
 
Cogente (talk)14:00, 15 December 2016

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

ryuohno (talk)17:52, 21 December 2016
 
 
First page
First page
Next page
Next page
Last page
Last page