New messages

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

Full thread

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

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?

Joanvaro (talk)08:26, 15 November 2017

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

Ygohda (talk)17:09, 16 November 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.
Ygohda (talk)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
 
 

Full thread

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

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)15:20, 5 October 2017

I think that you need to add a package.

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

For details, please refer to Yocto manual.

Ygohda (talk)22: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)15:22, 9 October 2017
 

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

Kazu (talk)22:43, 9 October 2017
 
 

Full thread

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

Installing PyCaffe

Hello,

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

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

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

Ipodslessteven (talk)10:42, 30 October 2017
 

Full thread

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

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)

Eli.sherman (talk)05:25, 17 July 2017

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

Tim Bird (talk)15:13, 17 July 2017

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

Eli.sherman (talk)00:57, 18 July 2017

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

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


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

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

However, the following are different.

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

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

Ygohda (talk)17:31, 18 July 2017

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

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

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

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

Eli.sherman (talk)23:10, 18 July 2017

Yes, /tmp/deploy/images/h3ulcb is correct path. Please refer to the No13 of http://elinux.org/R-Car/Boards/Yocto-Gen3#Building_the_BSP_for_Renesas_H3ULCB.2C_M3ULCB.

All updating methods are described below. http://elinux.org/R-Car/Boards/H3SK#Flashing_firmware Could you try again?

If "u-boot" still doesn't start up please attach the log when flashing the firmware.

Ygohda (talk)03:03, 21 July 2017

Rebuilding the whole thing from scratch worked. Something must have gone wrong in the initial build because the .dtb file sizes between the two builds were off by a few hundred bytes.

Eli.sherman (talk)22:38, 22 July 2017
 
 
 
 
 
 
 

Full thread

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

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)08:16, 20 June 2017

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

Please comment it back:

  1. TEST_IMAGE = "1"

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

Cogente (talk)02:45, 21 June 2017

That worked out

Thanks for the assist !

Smodak (talk)14:00, 27 June 2017
 
 

Full thread

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

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)09:41, 31 May 2017

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

Ygohda (talk)18:39, 4 June 2017

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

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

KarthikShanmugam (talk)02:30, 5 June 2017

I've attached the my log.

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

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

>

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

Ygohda (talk)00:38, 6 June 2017

Issue is not yet resolved, please see log below.


H3 SAMPLE LOADER V1.17 2016.11.08

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

H3 MiniMonitor V0.24 2016.11.08

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

>xls2

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

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

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

Program Top Address & Qspi/HyperFlash Save Address

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

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

 Please Input : H'0

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

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

>xls2

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

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

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

Program Top Address & Qspi/HyperFlash Save Address

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

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

 Please Input : H'1C0000

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

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

>xls2

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

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

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

Program Top Address & Qspi/HyperFlash Save Address

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

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

 Please Input : H'40000

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

KarthikShanmugam (talk)01:25, 8 June 2017

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

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

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

Ygohda (talk)17:57, 18 June 2017
 
 
 
 
 
First page
First page
Previous page
Previous page
Last page
Last page