Hi Support Team,
We were using hihope board for development in which we used Yocto Rocko version and kernel version 4.19, VLP package 1.0.12 based on hihope having chip ID "R8A774A1".
We received RZG2M processor physical chip from Renesas as R8A774A2 but it shows chip ID "R8A774A3" i.e. Rev3.0 in attached logs. When we boot this processor, it stucks in uboot. Please find the logs.
Query: Do we need to use dtb and other dependencies files in uboot for R8A774A1 or R8A774A3? However, in uboot source, there are no dtb and source files for R8A774A1 or R8A774A3 chip ID in VLP package 1.0.12.
Please find the logs of board bootup and the processor silicon.
NOTICE: BL2: RZ/G2 Initial Program Loader(CA57) Rev.3.0.3NOTICE: BL2: PRR is RZ/G2M Ver.3.0NOTICE: BL2: Board is Custom Board RZ/G2M Rev.6.0NOTICE: BL2: Boot device is QSPI Flash(40MHz)NOTICE: BL2: DDR3200(rev.0.41)NOTICE: BL2: [COLD_BOOT]NOTICE: BL2: DRAM Split is 2chNOTICE: BL2: QoS is default setting(rev.0.04)NOTICE: BL2: DRAM refresh interval 1.95 usecNOTICE: BL2: Periodic Write DQ TrainingNOTICE: BL2: DRAM don't have ECC configurationNOTICE: BL2: CH0: 400000000 - 47fffffff, 2 GiBNOTICE: BL2: CH2: 600000000 - 67fffffff, 2 GiBNOTICE: BL2: Lossy Decomp areasNOTICE: Entry 0: DCMPAREACRAx:0x80000540 DCMPAREACRBx:0x570NOTICE: Entry 1: DCMPAREACRAx:0x40000000 DCMPAREACRBx:0x0NOTICE: Entry 2: DCMPAREACRAx:0x20000000 DCMPAREACRBx:0x0NOTICE: BL2: FDT at 0xe6321a70NOTICE: BL2: v2.6(release):7faef7375-dirtyNOTICE: BL2: Built : 06:36:41, Mar 1 2023NOTICE: BL2: Normal bootINFO: BL2: Doing platform setupINFO: BL2: Loading image id 3NOTICE: BL2: dst=0xe6321300 src=0x8180000 len=512(0x200)NOTICE: BL2: dst=0x43f00000 src=0x8180400 len=6144(0x1800)WARNING: r-car ignoring the BL31 size from certificate,using RCAR_TRUSTED_SRAM_SIZE insteadINFO: Loading image id=3 at address 0x44000000NOTICE: rcar_file_len: len: 0x0003e000NOTICE: BL2: dst=0x44000000 src=0x81c0000 len=253952(0x3e000)INFO: Image id=3 loaded: 0x44000000 - 0x4403e000INFO: BL2: Loading image id 5INFO: Loading image id=5 at address 0x50000000NOTICE: rcar_file_len: len: 0x00100000NOTICE: BL2: dst=0x50000000 src=0x8300000 len=1048576(0x100000)INFO: Image id=5 loaded: 0x50000000 - 0x50100000NOTICE: BL2: Booting BL31INFO: Entry point address = 0x44000000INFO: SPSR = 0x3cd U-Boot 2021.10 (Mar 01 2023 - 10:40:27 +0000) CPU: Renesas Electronics R8A774A3Model: HopeRun HiHope RZ/G2M with sub boardDRAM: 3.9 GiBWDT: watchdog@00000000e6020000WDT: Started with servicing (60s timeout)MMC: mmc@ee100000: 0, mmc@ee160000: 1Loading Environment from MMC... OKIn: serial@e6e88000Out: serial@e6e88000Err: serial@e6e88000U-boot WDT started!Net: Error: ethernet@e6800000 address not set.No ethernet found. Hit any key to stop autoboot: 2 1 0 Card did not respond to voltage select! : -110Couldn't find partition mmc 0:1Can't set block deviceCard did not respond to voltage select! : -110Couldn't find partition mmc 0:1Can't set block deviceBad Linux ARM64 Image magic!
MicBis Can you help here?
I do not think it is stuck, apparently it just can't find what it is looking for on the mmc 0 dev part 1.
Where do you want to boot from?
What about printenv?
MicBis Please find below logs.
Hit any key to stop autoboot: 2 0 => printenvbaudrate=115200board_rev=6bootargs=root=/dev/mmcblk0p2 rootwaitbootcmd=fatload mmc 0:1 0x48080000 Image-custom-rzg2m.bin; fatload mmc 0:1 0x48000000 Image-r8a774a1-custom-rzg2m-ex.dtb; booti 0x48080000 - 0x48000000bootdelay=2bootm_size=0x10000000fdtcontroladdr=b9ee79d0loadaddr=0x58000000mem=1933312kplatform=r8a774a3stderr=serial@e6e88000stdin=serial@e6e88000stdout=serial@e6e88000usb_pgood_delay=2000ver=U-Boot 2021.10 (Mar 01 2023 - 10:40:27 +0000)wdt_status=1wdt_timeout=60000
Environment size: 506/131068 bytes=> mmc infoCard did not respond to voltage select! : -110=> mmc dev 1switch to partitions #0, OKmmc1(part 0) is current device=> mmc dev 1 mmc infoDevice: mmc@ee160000Manufacturer ID: 13OEM: 14eName: R1J57 Bus Speed: 199999992Mode: HS200 (200MHz)Rd Block Len: 512MMC version 5.0High Capacity: YesCapacity: 29.1 GiBBus Width: 8-bitErase Group Size: 512 KiBHC WP Group Size: 8 MiBUser Capacity: 29.1 GiB WRRELBoot Capacity: 8 MiB ENHRPMB Capacity: 4 MiB ENHBoot area 0 is not write protectedBoot area 1 is not write protected
Thanks MicBis for quick response.
As Hitixa shared, env variables are stored in eMMC which is connected to sdhi3.
SD card is connected to sdhi0, which is not accessible.
We just resolve this issue after adding "no-1-8-v" in sdhi0 in DTS. We also got clarification from Renesas FAE about R8A774A2 chip.