Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 63810C46467 for ; Tue, 10 Jan 2023 18:41:13 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id DE30E855C5; Tue, 10 Jan 2023 19:41:10 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=konsulko.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=pass (1024-bit key; unprotected) header.d=konsulko.com header.i=@konsulko.com header.b="VhheUBrk"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 1302D855ED; Tue, 10 Jan 2023 19:41:09 +0100 (CET) Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id E645C851E6 for ; Tue, 10 Jan 2023 19:41:04 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=konsulko.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=trini@konsulko.com Received: by mail-qt1-x82e.google.com with SMTP id v14so11695722qtq.3 for ; Tue, 10 Jan 2023 10:41:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=konsulko.com; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=brgz9FfrqgqrJOGSHckkWjDLcN/Ki6H8tG1sQw9o+mo=; b=VhheUBrkjmAfyDlUUvexKJcIQmjlnGGnCTUY07RTwpsQ1O5erHdjxQfBPNWIKckTXs 3elBsRoEbt2Xx3LOJIPpAJ2Fygf0739p2LU/r62ZJXKB7Y3oIP9rRUjNUwVd7IU8kkxL /ZASX6e8z3Id0ftdeturjjb9JgzBNVhH5Vz/o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=brgz9FfrqgqrJOGSHckkWjDLcN/Ki6H8tG1sQw9o+mo=; b=nwAwFy1fJ5at3Ydq9HmoSEeoEqVIyTey30K2g0FSRiiZK3XoX7Oxq2Lmr74l/sdtvP JaGXojZhB+4Rp8xNjXUEpszqKWx/jk9m9g+2anWFTg3KlZYiWpNLFhH4dmWcS2lRMDmQ USuzwAJj/03RDnTlayGCiqDlB/09erdg3uHlq/WwrpP2Rm4OhlzBIvINNY68BJSbdq5L yVIWCA8qAwpAafKxLMkwvuYf6nkdet0RB17IIeqrmCRgpFHWys2w9ettP2Oaz7Fz4O8Q brD4ymYXyLwO9S4eiVB5a/vFHJAiy8zLRRDiZ+TKjVzAj5/SggAtLgkI65mz47pUBPAp xuUw== X-Gm-Message-State: AFqh2ko6Gqr8aUhLmg5WqJEowfXBE6+DnFi/bV871TWUX4Q+kmT5kjS2 ql3UwVc+oZ7fV3HFH68d+BP3Ow== X-Google-Smtp-Source: AMrXdXv27EIbEvEhSf4uEOeIrYIXXply1XDNUSjrS1fGax7ReXVYrSw7qFCIRDVBOepf/AiGOjgL1g== X-Received: by 2002:a05:622a:1927:b0:3a7:ec54:cfa2 with SMTP id w39-20020a05622a192700b003a7ec54cfa2mr94168542qtc.56.1673376063424; Tue, 10 Jan 2023 10:41:03 -0800 (PST) Received: from bill-the-cat (2603-6081-7b00-6400-2c2f-ce0f-8dee-7136.res6.spectrum.com. [2603:6081:7b00:6400:2c2f:ce0f:8dee:7136]) by smtp.gmail.com with ESMTPSA id dt9-20020a05620a478900b006fbf88667bcsm2901556qkb.77.2023.01.10.10.41.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 10 Jan 2023 10:41:02 -0800 (PST) Date: Tue, 10 Jan 2023 13:41:01 -0500 From: Tom Rini To: Joost van Zwieten Cc: u-boot@lists.denx.de Subject: Re: kernel doesn't start on Odroid U2 unless setting initrd_high Message-ID: <20230110184101.GO3787616@bill-the-cat> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="CuNFONos5VfSEk1S" Content-Disposition: inline In-Reply-To: X-Clacks-Overhead: GNU Terry Pratchett X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.39 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.6 at phobos.denx.de X-Virus-Status: Clean --CuNFONos5VfSEk1S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 10, 2023 at 09:13:32AM +0100, Joost van Zwieten wrote: > Dear maintainers, >=20 > As of commit 4963f63fe61f15329d77472a762b1d8bf754d24b U-Boot fails to sta= rt > a kernel (with `bootz`) on my Odroid U2 unless I force `initrd_high`, e.g. > to `0x50000000`. With commit 4963f63f and `initrd_high` *unset* I get the > following output: >=20 > U-Boot 2020.10-rc2-00314-g4963f63fe6 (Jan 09 2023 - 23:59:31 +0100) >=20 > 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: 2, EXYNOS DWMMC: 0 > Loading Environment from MMC... *** Warning - bad CRC, using default > environment >=20 > In: serial > Out: serial > Err: serial > Boot device: MMC(2) > Net: No ethernet found. > Hit any key to stop autoboot: 0 > Odroid # env set fk_kvers 5.10.0-20-armmp > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} ${fdt_addr_r} > /boot/dtbs/${fk_kvers}/exynos4412-odroidu3.dtb > 53440 bytes read in 50 ms (1 MiB/s) > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} ${kernel_addr_r} > /boot/vmlinuz-${fk_kvers} > 4973056 bytes read in 182 ms (26.1 MiB/s) > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} ${ramdisk_addr_r} > /boot/initrd.img-${fk_kvers} > 22231585 bytes read in 777 ms (27.3 MiB/s) > Odroid # env set bootargs console=3DttySAC1,115200n8 > Odroid # bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} > ${fdt_addr_r} > Kernel image @ 0x41000000 [ 0x000000 - 0x4be200 ] > ## Flattened Device Tree blob at 40800000 > Booting using the fdt blob at 0x40800000 > Loading Ramdisk to b9947000, end bae7aa21 ... OK > Loading Device Tree to b9936000, end b99460bf ... OK >=20 > Starting kernel ... >=20 > And that's all I ever see. Normally the initrd loads a module that causes= an > LED on the Odroid to blink, and this is not happening either, so I'm pret= ty > confident the kernel doesn't start or at least crashes before producing > output. If I set `initrd_high` to `0x50000000` (or something in the > neighborhood) the kernel starts just fine: >=20 > U-Boot 2020.10-rc2-00314-g4963f63fe6 (Jan 09 2023 - 23:59:31 +0100) >=20 > 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: 2, EXYNOS DWMMC: 0 > Loading Environment from MMC... *** Warning - bad CRC, using default > environment >=20 > In: serial > Out: serial > Err: serial > Boot device: MMC(2) > Net: No ethernet found. > Hit any key to stop autoboot: 0 > Odroid # env set fk_kvers 5.10.0-20-armmp > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} ${fdt_addr_r} > /boot/dtbs/${fk_kvers}/exynos4412-odroidu3.dtb > 53440 bytes read in 49 ms (1 MiB/s) > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} ${kernel_addr_r} > /boot/vmlinuz-${fk_kvers} > 4973056 bytes read in 181 ms (26.2 MiB/s) > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} ${ramdisk_addr_r} > /boot/initrd.img-${fk_kvers} > 22231585 bytes read in 777 ms (27.3 MiB/s) > Odroid # env set bootargs console=3DttySAC1,115200n8 > Odroid # env set initrd_high 0x50000000 > Odroid # bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} > ${fdt_addr_r} > Kernel image @ 0x41000000 [ 0x000000 - 0x4be200 ] > ## Flattened Device Tree blob at 40800000 > Booting using the fdt blob at 0x40800000 > Loading Ramdisk to 4eacc000, end 4ffffa21 ... OK > Loading Device Tree to bae6a000, end bae7a0bf ... OK >=20 > Starting kernel ... >=20 > [ 0.000000] Booting Linux on physical CPU 0xa00 > >=20 > The difference between those two runs is the location where U-Boot loads = the > initrd. The parent commit of 4963f63f boots fine without setting > `initrd_high`: >=20 > U-Boot 2020.10-rc2-00313-gdfaf6a5797 (Jan 10 2023 - 00:13:19 +0100) >=20 > 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: 2, EXYNOS DWMMC: 0 > Loading Environment from MMC... *** Warning - bad CRC, using default > environment >=20 > In: serial > Out: serial > Err: serial > Boot device: MMC(2) > Net: No ethernet found. > Hit any key to stop autoboot: 0 > Odroid # env set fk_kvers 5.10.0-20-armmp > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} ${fdt_addr_r} > /boot/dtbs/${fk_kvers}/exynos4412-odroidu3.dtb > 53440 bytes read in 49 ms (1 MiB/s) > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} ${kernel_addr_r} > /boot/vmlinuz-${fk_kvers} > 4973056 bytes read in 181 ms (26.2 MiB/s) > Odroid # load mmc ${mmcbootdev}:${mmcbootpart} ${ramdisk_addr_r} > /boot/initrd.img-${fk_kvers} > 22231585 bytes read in 776 ms (27.3 MiB/s) > Odroid # env set bootargs console=3DttySAC1,115200n8 > Odroid # bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} > ${fdt_addr_r} > Kernel image @ 0x41000000 [ 0x000000 - 0x4be200 ] > ## Flattened Device Tree blob at 40800000 > Booting using the fdt blob at 0x40800000 > Loading Ramdisk to 4eacc000, end 4ffffa21 ... OK > Loading Device Tree to 4eabb000, end 4eacb0bf ... OK >=20 > Starting kernel ... >=20 > [ 0.000000] Booting Linux on physical CPU 0xa00 > >=20 > I've tested two different kernels from Debian (buster and bullseye) and b= oth > have the same problem. I'm building U-Boot using the default config for > board `odroid` and boot the Odroid from an SD card with firmware (`bl1`, > `bl2` and `tzsw`) from Hardkernel's clone of the u-boot repository [1]. > There are no peripherals connected apart from the SD card and the serial > console. Please let me know if you need more information. Interesting. So what does "bdi" show, both in the older good and then current tree? Specifically the information about where DRAM is, and how large it is? Thanks. --=20 Tom --CuNFONos5VfSEk1S Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGzBAABCgAdFiEEGjx/cOCPqxcHgJu/FHw5/5Y0tywFAmO9sToACgkQFHw5/5Y0 tyzANgv/dft4uO2I/cDzWlvZF3qrFI88kVRt+Mu1yk3OFJkVF7PwhVfxylNVkoM9 jR5JgfwE/lz5pN7OUdt7HY0LaQrjglxcOsIX61BiVOE9YHaxbRZWKO9ejiBgbLDc /EQReUWnvhJOTeZL/HhEhBkT1CkyLEaD3FpNfbcICktvNt4W2LxpC0paL/gjXADz UzVGuMrZXqMVy+wMawbF7km9UDrzB1u5eAzwREyzo71LA19a3LMeXsczsJMeQVr0 4X3M1coDP/zgnigzAkMmVN7O8FEFKv/qc8wCcK4xbErF5MWI4183XWBdFRZxgkhB Q/L9mtyt0TxZWu+FQY0eBImyMsrq9HBSKrzTXwj9MKTOuTWIpY6hbnpLenphLGqJ 6yNUwt9qmEMlrBdDvqMQJahJSrQxTVDiJb/w5ADO1zJqZJOVHmnEErw+h7ucr3xt PR9eCQDU/0hDmxY8t+fDT7CU56fprl2zeKO5W44lZXXbkFL1xPezMYNoPbe3+FT+ bPw4fV9t =S/B9 -----END PGP SIGNATURE----- --CuNFONos5VfSEk1S--