<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi Troy,<div><br></div><div>I tried to load the Kernel image (fitImage-obmc-phosphor-initramfs-evb-ast2600--5.8.17+git0+3cc95ae407-r0-evb-ast2600-20210205034901.bin) directly through TFTP in evb-ast2600. I could see a crash due to some file system mounting issue. Can you please let me know if you've any fix/workaround for this issue?</div><div><br></div><div><div>Please check the below link for complete log:</div><div>- <a href="https://gist.github.com/vkrk-user/909b554aa4cddd10663ad706d4c182a7">https://gist.github.com/vkrk-user/909b554aa4cddd10663ad706d4c182a7</a></div><div></div></div><div><br></div><div><br></div><div>Crash log:</div><div>-------------</div><div><div>mount: mounting /dev/mtdblock4 on run/initramfs/ro failed: Invalid argument</div><div>[ 2.475872] jffs2: notice: (98) jffs2_build_xattr_subsystem: complete building xattr subsystem, 2 of xdatum (0 unchecked, 2 orphan) and 2 of xref (2 dead, 0 orphan) found.</div><div>[ 2.768965] overlayfs: upper fs does not support tmpfile.</div><div>[ 3.040864] overlayfs: upper fs does not support RENAME_WHITEOUT.</div><div>chroot: can't execute '/bin/sh': No such file or directory</div><div><br></div><div>Unable to confirm /sbin/init is an executable non-empty file</div><div>in[ 3.333044] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100</div><div>[ 3.342421] CPU: 0 PID: 1 Comm: init Not tainted 5.8.17-3cc95ae #1</div><div>[ 3.349316] Hardware name: Generic DT based system</div><div>[ 3.354661] Backtrace:</div><div>[ 3.357411] [<8010d92c>] (dump_backtrace) from [<8010db80>] (show_stack+0x20/0x24)</div><div>[ 3.365860] r7:80a049bc r6:60000093 r5:00000000 r4:80c66358</div><div>[ 3.372184] [<8010db60>] (show_stack) from [<808b7000>] (dump_stack+0x9c/0xb0)</div><div>[ 3.380248] [<808b6f64>] (dump_stack) from [<801211a0>] (panic+0x114/0x340)</div><div>[ 3.388016] r7:80a049bc r6:80c0df08 r5:00000000 r4:80c88380</div><div>[ 3.394336] [<8012108c>] (panic) from [<80127178>] (complete_and_exit+0x0/0x2c)</div><div>[ 3.402492] r3:00000001 r2:00000000 r1:00000100 r0:80a049bc</div><div>[ 3.408803] r7:ffffe000</div><div>[ 3.411630] [<8012678c>] (do_exit) from [<80127214>] (do_group_exit+0x50/0xc8)</div><div>[ 3.419677] r7:000000f8</div><div>[ 3.422503] [<801271c4>] (do_group_exit) from [<801272ac>] (__wake_up_parent+0x0/0x30)</div><div>[ 3.431338] r7:000000f8 r6:00000004 r5:00000004 r4:006ec190</div><div>[ 3.437656] [<8012728c>] (sys_exit_group) from [<80100060>] (ret_fast_syscall+0x0/0x54)</div><div>[ 3.446587] Exception stack(0xbd0dffa8 to 0xbd0dfff0)</div><div>[ 3.452225] ffa0: 006ec190 00000004 00000001 00000000 00000001 006ec190</div><div>[ 3.461351] ffc0: 006ec190 00000004 00000004 000000f8 00000000 00000000 00507a7c 00000000</div><div>[ 3.470476] ffe0: 00507b34 7ed76a14 00497934 76dcc574</div><div>[ 3.476121] CPU1: stopping</div><div>[ 3.479141] CPU: 1 PID: 99 Comm: jffs2_gcd_mtd5 Not tainted 5.8.17-3cc95ae #1</div><div>[ 3.487099] Hardware name: Generic DT based system</div></div><div><br></div><div><br></div><div><br></div><div>Regards,</div><div>Vinoth Kumar RK</div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 5 Feb 2021 at 14:58, Troy Lee <<a href="mailto:troy_lee@aspeedtech.com">troy_lee@aspeedtech.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US" style="overflow-wrap: break-word;">
<div class="gmail-m_-3622655205325152665WordSection1">
<p class="MsoNormal">Hi Vinothkumar,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">If you want to boot different Kernel from TFTP, I think you can use tftp command in u-boot.<u></u><u></u></p>
<p class="MsoNormal">ast# dhcp<u></u><u></u></p>
<p class="MsoNormal">ast# tftp 0x83000000 serverip:/path/image-kernel<u></u><u></u></p>
<p class="MsoNormal">ast# bootm 0x83000000<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">If you want to use qemu options loading u-boot/kernel images to different memory offset, I’m not familiar with this. Need some expert’s help here.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
<p class="MsoNormal">Troy Lee<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b>From:</b> VINOTHKUMAR RK <<a href="mailto:vkrk.user@gmail.com" target="_blank">vkrk.user@gmail.com</a>> <br>
<b>Sent:</b> Friday, February 5, 2021 4:16 PM<br>
<b>To:</b> Troy Lee <<a href="mailto:troy_lee@aspeedtech.com" target="_blank">troy_lee@aspeedtech.com</a>><br>
<b>Cc:</b> <a href="mailto:openbmc@lists.ozlabs.org" target="_blank">openbmc@lists.ozlabs.org</a><br>
<b>Subject:</b> Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Hi Troy,<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks a lot for your input!<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Looks like there was some problem with my Qemu. I was using some older version "version 4.2.1 (Debian 1:4.2-3ubuntu6.11)".<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">The image came up fine when I tried with the latest Qemu "aspeed-6.0" branch, it gives the image version which you're using.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Output:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">---------<u></u><u></u></p>
</div>
<div>
<div>
<p class="MsoNormal">Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 0.1.0 evb-ast2600 ttyS4<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">evb-ast2600 login: root<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Password: <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">root@evb-ast2600:~# <u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">BTW, is there an option with Qemu to boot u-boot and linux image separately? Also something like TFTP from u-boot (Qemu) to my VM (Ubuntu) where I'm running my TFTP server. Please let me know if there are any steps for the same.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Regards,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Vinoth Kumar RK<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Fri, 5 Feb 2021 at 12:59, Troy Lee <<a href="mailto:troy_lee@aspeedtech.com" target="_blank">troy_lee@aspeedtech.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Hi Vinothkumar,<br>
<br>
I’m not sure what’s wrong. Beware that the QEMU will directly write into your image file, so you might want to running it on a copy or use -snapshot option.<br>
<br>
I could boot into OS with the following qemu command:<br>
qemu-system-arm -M ast2600-evb -drive file=image-bmc,format=raw,if=mtd -nographic -nic user<br>
<br>
My QEMU version:<br>
qemu-system-arm --version<br>
QEMU emulator version 5.2.50 (v5.2.0-991-g45240eed4f)<br>
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers<br>
<br>
Thanks,<br>
Troy Lee<br>
<br>
From: VINOTHKUMAR RK <<a href="mailto:vkrk.user@gmail.com" target="_blank">vkrk.user@gmail.com</a>>
<br>
Sent: Friday, February 5, 2021 12:19 PM<br>
To: Troy Lee <<a href="mailto:troy_lee@aspeedtech.com" target="_blank">troy_lee@aspeedtech.com</a>><br>
Cc: <a href="mailto:openbmc@lists.ozlabs.org" target="_blank">openbmc@lists.ozlabs.org</a><br>
Subject: Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'<br>
<br>
Hi Troy,<br>
<br>
Thanks for sharing the changes, with this I'm able to generate mtd image. But when I try to load them through Qemu, it's getting stuck with the below error. Is there any workaround?<br>
<br>
Error log:<br>
------------<br>
fdt_root: FDT_ERR_BADMAGIC<br>
ERROR: root node setup failed<br>
- must RESET the board to recover.<br>
<br>
FDT creation failed! hanging...### ERROR ### Please RESET the board ###<br>
<br>
<br>
Qemu command:<br>
-----------------------<br>
qemu-system-arm -m 1G -M ast2600-evb -nographic -drive file=obmc-phosphor-image-evb-ast2600-20210205034901.static.mtd,format=raw,if=mtd -net nic -net user,hostfwd=:127.0.0.1:2222-:22,hostfwd=:127.0.0.1:2443-:443,hostname=qemu<br>
<br>
Qemu log:<br>
--------------<br>
U-Boot 2019.04 (Feb 04 2021 - 10:27:21 +0000)<br>
<br>
SOC: AST2600-A0 <br>
eSPI Mode: SIO:Enable : SuperIO-2e<br>
Eth: MAC0: RGMII, MAC1: RGMII, MAC2: RGMII, MAC3: RGMII<br>
Model: AST2600 EVB<br>
DRAM: already initialized, 240 MiB (capacity:256 MiB, VGA:64 MiB), ECC off<br>
PCIE-0: Link down<br>
MMC: <br>
<br>
sdhci_slot0@100: 1, sdhci_slot1@200: 2, emmc_slot0@100: 0<br>
Loading Environment from SPI Flash... *** Warning - spi_flash_probe_bus_cs() failed, using default environment<br>
<br>
In: serial@1e784000<br>
Out: serial@1e784000<br>
Err: serial@1e784000<br>
Model: AST2600 EVB<br>
Net: <br>
Warning: ftgmac@1e660000 (eth0) using random MAC address - 5e:23:16:3b:07:db<br>
eth0: ftgmac@1e660000<br>
Warning: ftgmac@1e680000 (eth1) using random MAC address - 92:2d:b9:4b:a5:93<br>
, eth1: ftgmac@1e680000<br>
Warning: ftgmac@1e670000 (eth2) using random MAC address - f6:16:60:c6:0a:2d<br>
, eth2: ftgmac@1e670000<br>
Warning: ftgmac@1e690000 (eth3) using random MAC address - 02:43:32:16:41:6d<br>
, eth3: ftgmac@1e690000<br>
Hit any key to stop autoboot: 0 <br>
## Loading kernel from FIT Image at 20100000 ...<br>
Using 'conf@aspeed-ast2600-evb.dtb' configuration<br>
Trying 'kernel@1' kernel subimage<br>
Description: Linux kernel<br>
Type: Kernel Image<br>
Compression: uncompressed<br>
Data Start: 0x2010012c<br>
Data Size: 3527112 Bytes = 3.4 MiB<br>
Architecture: ARM<br>
OS: Linux<br>
Load Address: 0x80001000<br>
Entry Point: 0x80001000<br>
Hash algo: sha256<br>
Hash value: d3bfde4459bab8272cda12f0747d47735521c9ee4f5786283cfea439398c976d<br>
Verifying Hash Integrity ... sha256+ OK<br>
## Loading ramdisk from FIT Image at 20100000 ...<br>
Using 'conf@aspeed-ast2600-evb.dtb' configuration<br>
Trying 'ramdisk@1' ramdisk subimage<br>
Description: obmc-phosphor-initramfs<br>
Type: RAMDisk Image<br>
Compression: uncompressed<br>
Data Start: 0x20465cf8<br>
Data Size: 1087608 Bytes = 1 MiB<br>
Architecture: ARM<br>
OS: Linux<br>
Load Address: unavailable<br>
Entry Point: unavailable<br>
Hash algo: sha256<br>
Hash value: 488f44eb0c954ef85ede0c1dde3803696b3637d41996fc2be9610bbdb756b1a9<br>
Verifying Hash Integrity ... sha256+ OK<br>
## Loading fdt from FIT Image at 20100000 ...<br>
Using 'conf@aspeed-ast2600-evb.dtb' configuration<br>
Trying 'fdt@aspeed-ast2600-evb.dtb' fdt subimage<br>
Description: Flattened Device Tree blob<br>
Type: Flat Device Tree<br>
Compression: uncompressed<br>
Data Start: 0x2045d408<br>
Data Size: 34852 Bytes = 34 KiB<br>
Architecture: ARM<br>
Hash algo: sha256<br>
Hash value: a9bcf2a34ea7477d2c5f86ec793b659ecce07554dee5897460198f513ede4d0b<br>
Verifying Hash Integrity ... sha256+ OK<br>
Booting using the fdt blob at 0x2045d408<br>
Loading Kernel Image ... OK<br>
Loading Ramdisk to 8ce57000, end 8cf60878 ... OK<br>
Loading Device Tree to 8ce4b000, end 8ce56823 ... OK<br>
fdt_root: FDT_ERR_BADMAGIC<br>
ERROR: root node setup failed<br>
- must RESET the board to recover.<br>
<br>
FDT creation failed! hanging...### ERROR ### Please RESET the board ###<br>
<br>
<br>
<br>
<br>
<br>
Regards,<br>
Vinoth Kumar RK<br>
<br>
On Fri, 5 Feb 2021 at 07:57, Troy Lee <mailto:<a href="mailto:troy_lee@aspeedtech.com" target="_blank">troy_lee@aspeedtech.com</a>> wrote:<br>
Hi Vinothkumar,<br>
<br>
Please refer to the following two changes in Gerrit:<br>
• <a href="https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/39343" target="_blank">
https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/39343</a><br>
• <a href="https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/39344" target="_blank">
https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/39344</a><br>
<br>
Thanks,<br>
Troy Lee<br>
<br>
From: openbmc <openbmc-bounces+troy_lee=mailto:<a href="mailto:aspeedtech.com@lists.ozlabs.org" target="_blank">aspeedtech.com@lists.ozlabs.org</a>> On Behalf Of VINOTHKUMAR RK<br>
Sent: Thursday, February 4, 2021 8:28 PM<br>
To: mailto:<a href="mailto:openbmc@lists.ozlabs.org" target="_blank">openbmc@lists.ozlabs.org</a><br>
Subject: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'<br>
<br>
Hi,<br>
<br>
I'm trying to build for evb-ast2600 platform, but it doesn't succeed. Please help.<br>
<br>
Build command: (fresh checkout and build)<br>
TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2600/conf . openbmc-env<br>
bitbake obmc-phosphor-image<br>
<br>
Branch details:<br>
commit 7dc2f7a38dccb3d87a9b79d0a66b25da1027a72f <br>
<br>
<br>
Error Log:<br>
Loading cache: 100% | | ETA: --:--:--<br>
Loaded 0 entries from dependency cache.<br>
Parsing recipes: 100% |########################################################################################################################################################################| Time: 0:00:44<br>
Parsing of 2424 .bb files complete (0 cached, 2424 parsed). 3683 targets, 362 skipped, 0 masked, 0 errors.<br>
WARNING: No bb files in default matched BBFILE_PATTERN_meta-evb-ast2600 '^/home/vinoth/project/openbmc/meta-evb/meta-evb-aspeed/meta-evb-ast2600/'<br>
NOTE: Resolving any missing task queue dependencies<br>
<br>
Build Configuration:<br>
BB_VERSION = "1.49.0"<br>
BUILD_SYS = "x86_64-linux"<br>
NATIVELSBSTRING = "ubuntu-20.04"<br>
TARGET_SYS = "arm-openbmc-linux-gnueabi"<br>
MACHINE = "evb-ast2600"<br>
DISTRO = "openbmc-phosphor"<br>
DISTRO_VERSION = "0.1.0"<br>
TUNE_FEATURES = "arm armv7a vfp vfpv4d16 callconvention-hard"<br>
TARGET_FPU = "hard"<br>
meta <br>
meta-poky <br>
meta-oe <br>
meta-networking <br>
meta-python <br>
meta-phosphor <br>
meta-aspeed <br>
meta-evb-ast2600 = "master:7dc2f7a38dccb3d87a9b79d0a66b25da1027a72f"<br>
<br>
Initialising tasks: 100% |#####################################################################################################################################################################| Time: 0:00:03<br>
Sstate summary: Wanted 1378 Found 939 Missed 439 Current 0 (68% match, 0% complete)<br>
NOTE: Executing Tasks<br>
WARNING: linux-aspeed-5.8.17+gitAUTOINC+3cc95ae407-r0 do_kernel_metadata: Feature 'phosphor-gpio-keys' not found, but KERNEL_DANGLING_FEATURES_WARN_ONLY is set<br>
WARNING: linux-aspeed-5.8.17+gitAUTOINC+3cc95ae407-r0 do_kernel_metadata: This may cause runtime issues, dropping feature and allowing configuration to continue<br>
WARNING: linux-aspeed-5.8.17+gitAUTOINC+3cc95ae407-r0 do_kernel_metadata: Feature 'phosphor-vlan' not found, but KERNEL_DANGLING_FEATURES_WARN_ONLY is set<br>
WARNING: linux-aspeed-5.8.17+gitAUTOINC+3cc95ae407-r0 do_kernel_metadata: This may cause runtime issues, dropping feature and allowing configuration to continue<br>
WARNING: linux-aspeed-5.8.17+gitAUTOINC+3cc95ae407-r0 do_kernel_configme: Feature 'phosphor-gpio-keys' not found, but KERNEL_DANGLING_FEATURES_WARN_ONLY is set<br>
WARNING: linux-aspeed-5.8.17+gitAUTOINC+3cc95ae407-r0 do_kernel_configme: This may cause runtime issues, dropping feature and allowing configuration to continue<br>
WARNING: linux-aspeed-5.8.17+gitAUTOINC+3cc95ae407-r0 do_kernel_configme: Feature 'phosphor-vlan' not found, but KERNEL_DANGLING_FEATURES_WARN_ONLY is set<br>
WARNING: linux-aspeed-5.8.17+gitAUTOINC+3cc95ae407-r0 do_kernel_configme: This may cause runtime issues, dropping feature and allowing configuration to continue<br>
WARNING: obmc-phosphor-sysd-1.0-r1 do_package_qa: QA Issue: obmc-phosphor-sysd: SRC_URI uses PN not BPN [src-uri-bad]<br>
ERROR: obmc-phosphor-image-1.0-r0 do_generate_static: Image '/home/vinoth/project/openbmc/build/tmp/deploy/images/evb-ast2600/u-boot.bin' is too large!<br>
ERROR: Logfile of failure stored in: /home/vinoth/project/openbmc/build/tmp/work/evb_ast2600-openbmc-linux-gnueabi/obmc-phosphor-image/1.0-r0/temp/log.do_generate_static.2176796<br>
ERROR: Task (/home/vinoth/project/openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:do_generate_static) failed with exit code '1'<br>
NOTE: Tasks Summary: Attempted 4041 tasks of which 2680 didn't need to be rerun and 1 failed.<br>
<br>
Summary: 1 task failed:<br>
/home/vinoth/project/openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:do_generate_static<br>
Summary: There were 10 WARNING messages shown.<br>
Summary: There was 1 ERROR message shown, returning a non-zero exit code.<br>
<br>
<br>
<br>
Regards,<br>
VINOTHKUMAR RK<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
</blockquote></div>