evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
VINOTHKUMAR RK
vkrk.user at gmail.com
Fri Feb 5 15:19:16 AEDT 2021
Hi Troy,
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?
Error log:
------------
fdt_root: FDT_ERR_BADMAGIC
ERROR: root node setup failed
- must RESET the board to recover.
FDT creation failed! hanging...### ERROR ### Please RESET the board ###
Qemu command:
-----------------------
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
Qemu log:
--------------
U-Boot 2019.04 (Feb 04 2021 - 10:27:21 +0000)
SOC: AST2600-A0
eSPI Mode: SIO:Enable : SuperIO-2e
Eth: MAC0: RGMII, MAC1: RGMII, MAC2: RGMII, MAC3: RGMII
Model: AST2600 EVB
DRAM: already initialized, 240 MiB (capacity:256 MiB, VGA:64 MiB), ECC off
PCIE-0: Link down
MMC:
sdhci_slot0 at 100: 1, sdhci_slot1 at 200: 2, emmc_slot0 at 100: 0
Loading Environment from SPI Flash... *** Warning -
spi_flash_probe_bus_cs() failed, using default environment
In: serial at 1e784000
Out: serial at 1e784000
Err: serial at 1e784000
Model: AST2600 EVB
Net:
Warning: ftgmac at 1e660000 (eth0) using random MAC address - 5e:23:16:3b:07:db
eth0: ftgmac at 1e660000
Warning: ftgmac at 1e680000 (eth1) using random MAC address - 92:2d:b9:4b:a5:93
, eth1: ftgmac at 1e680000
Warning: ftgmac at 1e670000 (eth2) using random MAC address - f6:16:60:c6:0a:2d
, eth2: ftgmac at 1e670000
Warning: ftgmac at 1e690000 (eth3) using random MAC address - 02:43:32:16:41:6d
, eth3: ftgmac at 1e690000
Hit any key to stop autoboot: 0
## Loading kernel from FIT Image at 20100000 ...
Using 'conf at aspeed-ast2600-evb.dtb' configuration
Trying 'kernel at 1' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: uncompressed
Data Start: 0x2010012c
Data Size: 3527112 Bytes = 3.4 MiB
Architecture: ARM
OS: Linux
Load Address: 0x80001000
Entry Point: 0x80001000
Hash algo: sha256
Hash value:
d3bfde4459bab8272cda12f0747d47735521c9ee4f5786283cfea439398c976d
Verifying Hash Integrity ... sha256+ OK
## Loading ramdisk from FIT Image at 20100000 ...
Using 'conf at aspeed-ast2600-evb.dtb' configuration
Trying 'ramdisk at 1' ramdisk subimage
Description: obmc-phosphor-initramfs
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x20465cf8
Data Size: 1087608 Bytes = 1 MiB
Architecture: ARM
OS: Linux
Load Address: unavailable
Entry Point: unavailable
Hash algo: sha256
Hash value:
488f44eb0c954ef85ede0c1dde3803696b3637d41996fc2be9610bbdb756b1a9
Verifying Hash Integrity ... sha256+ OK
## Loading fdt from FIT Image at 20100000 ...
Using 'conf at aspeed-ast2600-evb.dtb' configuration
Trying 'fdt at aspeed-ast2600-evb.dtb' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x2045d408
Data Size: 34852 Bytes = 34 KiB
Architecture: ARM
Hash algo: sha256
Hash value:
a9bcf2a34ea7477d2c5f86ec793b659ecce07554dee5897460198f513ede4d0b
Verifying Hash Integrity ... sha256+ OK
Booting using the fdt blob at 0x2045d408
Loading Kernel Image ... OK
Loading Ramdisk to 8ce57000, end 8cf60878 ... OK
Loading Device Tree to 8ce4b000, end 8ce56823 ... OK
fdt_root: FDT_ERR_BADMAGIC
ERROR: root node setup failed
- must RESET the board to recover.
FDT creation failed! hanging...### ERROR ### Please RESET the board ###
Regards,
Vinoth Kumar RK
On Fri, 5 Feb 2021 at 07:57, Troy Lee <troy_lee at aspeedtech.com> wrote:
> Hi Vinothkumar,
>
>
>
> Please refer to the following two changes in Gerrit:
>
> - https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/39343
> - https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/39344
>
>
>
> Thanks,
>
> Troy Lee
>
>
>
> *From:* openbmc <openbmc-bounces+troy_lee=aspeedtech.com at lists.ozlabs.org>
> *On Behalf Of *VINOTHKUMAR RK
> *Sent:* Thursday, February 4, 2021 8:28 PM
> *To:* openbmc at lists.ozlabs.org
> *Subject:* evb-ast2600: Getting some build errors - 'u-boot.bin' is too
> large!'
>
>
>
> Hi,
>
>
>
> I'm trying to build for evb-ast2600 platform, but it doesn't succeed.
> Please help.
>
>
>
> Build command: (fresh checkout and build)
>
> TEMPLATECONF=meta-evb/meta-evb-aspeed/meta-evb-ast2600/conf . openbmc-env
> bitbake obmc-phosphor-image
>
>
>
> Branch details:
>
> commit 7dc2f7a38dccb3d87a9b79d0a66b25da1027a72f
>
>
>
>
>
> Error Log:
>
> Loading cache: 100% |
>
> | ETA: --:--:--
> Loaded 0 entries from dependency cache.
> Parsing recipes: 100%
> |########################################################################################################################################################################|
> Time: 0:00:44
> Parsing of 2424 .bb files complete (0 cached, 2424 parsed). 3683 targets,
> 362 skipped, 0 masked, 0 errors.
> WARNING: No bb files in default matched BBFILE_PATTERN_meta-evb-ast2600
> '^/home/vinoth/project/openbmc/meta-evb/meta-evb-aspeed/meta-evb-ast2600/'
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION = "1.49.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "ubuntu-20.04"
> TARGET_SYS = "arm-openbmc-linux-gnueabi"
> MACHINE = "evb-ast2600"
> DISTRO = "openbmc-phosphor"
> DISTRO_VERSION = "0.1.0"
> TUNE_FEATURES = "arm armv7a vfp vfpv4d16 callconvention-hard"
> TARGET_FPU = "hard"
> meta
> meta-poky
> meta-oe
> meta-networking
> meta-python
> meta-phosphor
> meta-aspeed
> meta-evb-ast2600 = "master:7dc2f7a38dccb3d87a9b79d0a66b25da1027a72f"
>
> Initialising tasks: 100%
> |#####################################################################################################################################################################|
> Time: 0:00:03
> Sstate summary: Wanted 1378 Found 939 Missed 439 Current 0 (68% match, 0%
> complete)
> NOTE: Executing Tasks
> 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
> WARNING: linux-aspeed-5.8.17+gitAUTOINC+3cc95ae407-r0 do_kernel_metadata:
> This may cause runtime issues, dropping feature and allowing configuration
> to continue
> 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
> WARNING: linux-aspeed-5.8.17+gitAUTOINC+3cc95ae407-r0 do_kernel_metadata:
> This may cause runtime issues, dropping feature and allowing configuration
> to continue
> 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
> WARNING: linux-aspeed-5.8.17+gitAUTOINC+3cc95ae407-r0 do_kernel_configme:
> This may cause runtime issues, dropping feature and allowing configuration
> to continue
> 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
> WARNING: linux-aspeed-5.8.17+gitAUTOINC+3cc95ae407-r0 do_kernel_configme:
> This may cause runtime issues, dropping feature and allowing configuration
> to continue
> WARNING: obmc-phosphor-sysd-1.0-r1 do_package_qa: QA Issue:
> obmc-phosphor-sysd: SRC_URI uses PN not BPN [src-uri-bad]
> 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!
> 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
> ERROR: Task
> (/home/vinoth/project/openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:do_generate_static)
> failed with exit code '1'
> NOTE: Tasks Summary: Attempted 4041 tasks of which 2680 didn't need to be
> rerun and 1 failed.
>
> Summary: 1 task failed:
>
> /home/vinoth/project/openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:
> do_generate_static
> Summary: There were 10 WARNING messages shown.
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
>
>
>
>
>
>
> Regards,
>
> VINOTHKUMAR RK
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20210205/78db19b0/attachment.htm>
More information about the openbmc
mailing list