On Mon, 18 Mar 2019 at 13:32, Anand Moon <linux.amoon@xxxxxxxxx> wrote:
>
> Hi Krzysztof / Marek,
>
> After I update the latest u-boot on my Odroud U3+ it fails to load the
> kernel it hangs.
> I am using Archlinux on Odroid U3.
>
> U-Boot 2019.04-rc3-00131-g8303467e80d-dirty (Mar 18 2019 - 12:12:23 +0000)
>
> CPU: Exynos4412 @ 1 GHz
> Model: Odroid based on Exynos4412
> Type: u3
> DRAM: 2 GiB
> LDO20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling
> LDO22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling
> LDO21@TFLASH_2.8V: set 2800000 uV; enabling
> MMC: SAMSUNG SDHCI: 1, EXYNOS DWMMC: 0
> Loading Environment from MMC... Card did not respond to voltage select!
> *** Warning - No block device, using default environment
>
> Net: No ethernet found.
> Hit any key to stop autoboot: 0
> switch to partitions #0, OK
> mmc1 is current device
> Scanning mmc 1:1...
> Found U-Boot script /boot/boot.scr
> 769 bytes read in 6 ms (125 KiB/s)
> ## Executing script at 42000000
> 6901856 bytes read in 253 ms (26 MiB/s)
> 53078 bytes read in 19 ms (2.7 MiB/s)
> 6590950 bytes read in 240 ms (26.2 MiB/s)
> Kernel image @ 0x41000000 [ 0x000000 - 0x695060 ]
> ## Flattened Device Tree blob at 40800000
> Booting using the fdt blob at 0x40800000
> Loading Ramdisk to 4f9b6000, end 4ffff1e6 ... OK
> Loading Device Tree to 4f9a6000, end 4f9b5f55 ... OK
>
> Starting kernel ...
Can you attach your boot.init file (the source of boot.scr)?
By the size of DTB you can see that different DTB is loaded. I assume
you tried to boot the same kernel, then it could mean that boardname
was used instead of board_name to choose DTB. Suspicious is that
kernel size also differs... so maybe you booted something else? As
usual debugging practice, reduce number of unknown factors. Do not
change kernel and U-Boot at the same time.
Also, you can try reverting commit e6b1467081d3 ("arm: exynos: Remove
duplicated "boardname" env setting") and see if it helps. Or just try
to bisect around changes coming from u-boot samsung tree. Try booting
v2019.01 and paste the results as well.
Best regards,
Krzysztof
>
> Old u-boot boots fine see the logs below.
> --------------------------------------------------------------------------------------------------
> U-Boot 2018.01-1 (Feb 13 2018 - 02:19:55 +0000) Arch Linux ARM
>
> CPU: Exynos4412 @ 1 GHz
> Model: Odroid based on Exynos4412
> Board: Odroid based on Exynos4412
> Type: u3
> DRAM: 2 GiB
> LDO20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling
> LDO22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling
> LDO21@TFLASH_2.8V: set 2800000 uV; enabling
> MMC: sdhci@12530000 - probe failed: -19
>
> *** Warning - bad CRC, using default environment
>
> Net: No ethernet found.
> Hit any key to stop autoboot: 0
> no mmc device at slot 1
> switch to partitions #0, OK
> mmc0(part 0) is current device
> Scanning mmc 0:1...
> Found U-Boot script /boot/boot.scr
> 770 bytes read in 31 ms (23.4 KiB/s)
> ## Executing script at 50000000
> 6625416 bytes read in 267 ms (23.7 MiB/s)
> 72531 bytes read in 483 ms (146.5 KiB/s)
> 6590888 bytes read in 256 ms (24.6 MiB/s)
> Kernel image @ 0x42000000 [ 0x000000 - 0x651888 ]
> ## Flattened Device Tree blob at 43000000
> Booting using the fdt blob at 0x43000000
> Loading Ramdisk to 4f9b6000, end 4ffff1a8 ... OK
> Loading Device Tree to 4f9a1000, end 4f9b5b52 ... OK
>
> Starting kernel ...
>
> [ 0.000000] Booting Linux on physical CPU 0xa00
> [ 0.000000] Linux version 5.0.1-1-ARCH (builduser@leming) (gcc
> version 8.2.1 20181127 (GCC)) #1 SMP PREEMPT Tue Mar 12 04:09:35 UTC
> 2019
> [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c5387d
> [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
> instruction cache
> [ 0.000000] OF: fdt: Machine model: Hardkernel ODROID-U3 board
> based on Exynos4412
> [ 0.000000] Memory policy: Data cache writealloc
> [ 0.000000] Reserved memory: created DMA memory pool at 0xbf700000,
> size 8 MiB
> [ 0.000000] OF: reserved mem: initialized node region_mfc_right,
> compatible id shared-dma-pool
> [ 0.000000] Reserved memory: created DMA memory pool at 0xbd300000,
> size 36 MiB
>
> Please could you share the details on how to debug this issue or how to resolve.
>
> Best Regards
> -Anand
