From mboxrd@z Thu Jan 1 00:00:00 1970 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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 32499C433F5 for ; Tue, 19 Oct 2021 09:59:32 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 26BC061212 for ; Tue, 19 Oct 2021 09:59:30 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 26BC061212 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=etri.re.kr Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.denx.de Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 9F5C3815B7; Tue, 19 Oct 2021 11:59:28 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=fail (p=none dis=none) header.from=etri.re.kr Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=dooray.com header.i=@dooray.com header.b="uqZuSAnq"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 9B5FE81725; Tue, 19 Oct 2021 11:59:26 +0200 (CEST) Received: from mscreen.etri.re.kr (mscreen.etri.re.kr [129.254.9.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 2EDB8805F9 for ; Tue, 19 Oct 2021 11:59:15 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=etri.re.kr Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=ckim@etri.re.kr Received: from unknown (HELO send001-relay.gov-dooray.com) (211.180.235.152) by 129.254.9.16 with ESMTP; 19 Oct 2021 18:59:12 +0900 X-Original-SENDERIP: 211.180.235.152 X-Original-MAILFROM: ckim@etri.re.kr X-Original-RCPTTO: u-boot@lists.denx.de Received: from [10.162.225.106] (HELO smtp001-imp.gov-dooray.com) ([10.162.225.106]) by send001-relay.gov-dooray.com with SMTP id 8969c818616e96f0; Tue, 19 Oct 2021 18:59:12 +0900 DKIM-Signature: a=rsa-sha256; b=uqZuSAnqzW9fDd5L9VQfFnyD4iG/YSra6zrXa3INFOq84VzGD294hU1ft+VanSwGC4Y65kOiS9 Zk7wiXIjTLg6Bjk7ugXZ8rho1RwcnBLt0QWXpK2R9ZXPLTqoOkI5hR10EZ9zBaGmmsRvN0wkJj4/ YV8hQSQwylOueQTiGHGhf/h4uBfiprEnbCmyTIkrPlzeHMDXgW1xBE1HBqpFi2hS0zZ3MeKFns1j XgAnSRTXHDj8GXwoXmajupOZZNvc1d2vXFKvEHPdUo4iwQkonZ96YbcY2G2Ct0nQZrOxqRQQYDmP Zkb+6DF/ut8cKd2ksC2eTr0a48gTaxJ/J0b44IlQ==; c=relaxed/relaxed; s=selector; d=dooray.com; v=1; bh=+IYg+1Z2MpFcnpSKDF7bRcYdByFMYnPflCscrdovAlQ=; h=From:To:Subject:Message-ID; Received: from [129.254.132.39] (HELO CHANKIMPC) ([129.254.132.39]) by smtp001-imp.gov-dooray.com with SMTP id b1e576bb616e96ef; Tue, 19 Oct 2021 18:59:12 +0900 From: "Chan Kim" To: =?utf-8?Q?'Fran=C3=A7ois_Ozog'?= Cc: References: <024601d7bff5$5fbd8e70$1f38ab50$@etri.re.kr> In-Reply-To: Subject: RE: please help, "Ram disk image is corrupt or invalid" (qemu virt machine, arm64) Date: Tue, 19 Oct 2021 18:59:10 +0900 Message-ID: <0a4001d7c4cf$f7123940$e536abc0$@etri.re.kr> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQImBIZPj1iX9syUoKHd7Uri6DO/EwKRT8xsqykKmaA= Content-Language: ko Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.34 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.2 at phobos.denx.de X-Virus-Status: Clean Hi, Fran=C3=A7ois =20 Thank you for the response. I=E2=80=99m now studying u-boot so it=E2=80=99ll take some time to learn = about SystemReady boot. BTW, inspired by your email, I tried this one. (after tftp of all three = files) =20 =3D> fdt addr 0x40000000 =3D> fdt chosen 0x42000000 0x4211e2a1 // the length of = initramfs.cpio.gz is 1172129 =3D 0x11e2a1) =3D> fdt print /chosen chosen { linux,initrd-end =3D <0x00000000 0x4211e2a1>; linux,initrd-start =3D <0x00000000 0x42000000>; stdout-path =3D "/pl011@9000000"; }; =3D> booti 0x40200000 0x42000000 0x40000000 Moving Image from 0x40200000 to 0x40280000, end=3D41c44000 Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid =20 I hoped now I set the device tree to have the initrd location, the = kernel could find it, but not. Isn=E2=80=99t there a correct method using this approach? Thank you! Best regards, =20 Chan Kim =20 From: Fran=C3=A7ois Ozog =20 Sent: Tuesday, October 19, 2021 4:32 PM To: Chan Kim Cc: u-boot@lists.denx.de Subject: Re: please help, "Ram disk image is corrupt or invalid" (qemu = virt machine, arm64) =20 Hi =20 If you use the second argument to indicate the location of the initrd = then Linux will use device tree information to get the size of the = initrd. That information is probably absent or incorrect. =20 The initrd=3D in your command line is thus useless as you task U-boot to = load it. =20 You may want to consider the Arm defined SystemReady boot flow to avoid = issues and benefit from secure boot flow and future extensions. In the = SystemReady boot flow , the Linux efi stub asks uboot to load the initrd = and do not need devicectree metadata to get any location or size (this = is to reinforce the use of device tree for hardware description as = opposed to hacking all information sharing between boot stages). =20 Cheers =20 FF =20 =20 =20 =20 Le mer. 13 oct. 2021 =C3=A0 07:44, Chan Kim > a =C3=A9crit : =20 Hello all, I can boot linux kernel using this command line. ${QEMU_DIR}/qemu-system-aarch64 -M ${QMACHINE} -cpu cortex-a72 -kernel ${LINUX_DIR}/arch/arm64/boot/Image -initrd = ${BUSYBOX_DIR}/initramfs.cpio.gz --append "root=3D/dev/ram init=3D/init nokaslr earlycon ip=3Ddhcp" -m = 2048M -nographic -netdev user,id=3Dn1 -device e1000,netdev=3Dn1 After reading some docs and getting helps, I tried u-boot.=20 After loading Image (for arm64) and dtb.dtb, I could see the kernel = booting to the final stage of deploying initramfs but it failed because I didn't give the initramfs.cpio.gz address. (I used "booti 0x40200000 - = 0x40000000) So I added initramfs.cpio.gz under /opt/tftp, and loaded kernel, = initramfs, and dbt on memory and gave "booti 0x40200000 0x42000000 0x40000000", addresses are kernel, initramfs and dtb). Below is the log. (please see the final error message below) ++ /home/ckim/QEMU/qemu/build/aarch64-softmmu/qemu-system-aarch64 -M = virt -bios u-boot.bin -cpu cortex-a57 -bios u-boot.bin -nographic -drive if=3Dpflash,format=3Draw,index=3D1,file=3Denvstore.img -netdev user,id=3Dnet0,tftp=3D/opt/tftp -device e1000,netdev=3Dnet0 U-Boot 2021.10-00455-g50c84208ad (Oct 13 2021 - 12:58:40 +0900) DRAM: 128 MiB Flash: 64 MiB MMC: =20 Loading Environment from Flash... *** Warning - bad CRC, using default environment In: pl011@9000000 Out: pl011@9000000 Err: pl011@9000000 Net: e1000: 52:54:00:12:34:56 eth0: e1000#0 Hit any key to stop autoboot: 0=20 starting USB... No working controllers found USB is stopped. Please issue 'usb start' first. scanning bus for devices... Device 0: unknown device Device 0: unknown device starting USB... No working controllers found BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 DHCP client bound to address 10.0.2.15 (1004 ms) Using e1000#0 device TFTP from server 10.0.2.2; our IP address is 10.0.2.15 Filename 'boot.scr.uimg'. Load address: 0x40200000 Loading: * TFTP error: 'File not found' (1) Not retrying... BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 DHCP client bound to address 10.0.2.15 (1001 ms) Using e1000#0 device TFTP from server 10.0.2.2; our IP address is 10.0.2.15 Filename 'boot.scr.uimg'. Load address: 0x40400000 Loading: * TFTP error: 'File not found' (1) Not retrying... =3D> tftp 0x40000000 dtb.dtb Using e1000#0 device TFTP from server 10.0.2.2; our IP address is 10.0.2.15 Filename 'dtb.dtb'. Load address: 0x40000000 Loading: = ################################################################# ######### 963.9 KiB/s done Bytes transferred =3D 1048576 (100000 hex) =3D> tftp 0x40200000 Image Using e1000#0 device TFTP from server 10.0.2.2; our IP address is 10.0.2.15 Filename 'Image'. Load address: 0x40200000 Loading: = ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################### 10 MiB/s done Bytes transferred =3D 26489344 (1943200 hex) =3D> tftp 0x42000000 initramfs.cpio.gz Using e1000#0 device TFTP from server 10.0.2.2; our IP address is 10.0.2.15 Filename 'initramfs.cpio.gz'. Load address: 0x42000000 Loading: = ################################################################# ################# 1 MiB/s done Bytes transferred =3D 1169894 (11d9e6 hex) =3D> booti 0x40200000 0x42000000 0x40000000 Moving Image from 0x40200000 to 0x40280000, end=3D41c44000 Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid At the end, it says "Ram disk image is corrupt or invalid". What am I = doing wrong? I tried with un-gzipped file of initramfs, the same. Should I use real initrd format(dd image)? Any help will be very much appreciated. Thank you! Chan Kim --=20 =20 Fran=C3=A7ois-Fr=C3=A9d=C3=A9ric Ozog | Director Business Development T: +33.67221.6485 francois.ozog@linaro.org | Skype: = ffozog =20