Can't Modify U-Boot Environment Variables on Updated Firmware
← Thread: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:
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,
[ 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)
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.
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.
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.
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
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.
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.