* evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
@ 2021-02-04 12:27 VINOTHKUMAR RK
2021-02-05 2:27 ` Troy Lee
0 siblings, 1 reply; 12+ messages in thread
From: VINOTHKUMAR RK @ 2021-02-04 12:27 UTC (permalink / raw)
To: openbmc
[-- Attachment #1: Type: text/plain, Size: 4045 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 4969 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
2021-02-04 12:27 evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!' VINOTHKUMAR RK
@ 2021-02-05 2:27 ` Troy Lee
2021-02-05 4:19 ` VINOTHKUMAR RK
2021-03-08 5:52 ` Thang Nguyen
0 siblings, 2 replies; 12+ messages in thread
From: Troy Lee @ 2021-02-05 2:27 UTC (permalink / raw)
To: VINOTHKUMAR RK, openbmc
[-- Attachment #1: Type: text/plain, Size: 4738 bytes --]
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@lists.ozlabs.org> On Behalf Of VINOTHKUMAR RK
Sent: Thursday, February 4, 2021 8:28 PM
To: openbmc@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
[-- Attachment #2: Type: text/html, Size: 11745 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
2021-02-05 2:27 ` Troy Lee
@ 2021-02-05 4:19 ` VINOTHKUMAR RK
2021-02-05 7:29 ` Troy Lee
2021-03-08 5:52 ` Thang Nguyen
1 sibling, 1 reply; 12+ messages in thread
From: VINOTHKUMAR RK @ 2021-02-05 4:19 UTC (permalink / raw)
To: Troy Lee; +Cc: openbmc
[-- Attachment #1: Type: text/plain, Size: 8569 bytes --]
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@100: 1, sdhci_slot1@200: 2, emmc_slot0@100: 0
Loading Environment from SPI Flash... *** Warning -
spi_flash_probe_bus_cs() failed, using default environment
In: serial@1e784000
Out: serial@1e784000
Err: serial@1e784000
Model: AST2600 EVB
Net:
Warning: ftgmac@1e660000 (eth0) using random MAC address - 5e:23:16:3b:07:db
eth0: ftgmac@1e660000
Warning: ftgmac@1e680000 (eth1) using random MAC address - 92:2d:b9:4b:a5:93
, eth1: ftgmac@1e680000
Warning: ftgmac@1e670000 (eth2) using random MAC address - f6:16:60:c6:0a:2d
, eth2: ftgmac@1e670000
Warning: ftgmac@1e690000 (eth3) using random MAC address - 02:43:32:16:41:6d
, eth3: ftgmac@1e690000
Hit any key to stop autoboot: 0
## Loading kernel from FIT Image at 20100000 ...
Using 'conf@aspeed-ast2600-evb.dtb' configuration
Trying 'kernel@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@aspeed-ast2600-evb.dtb' configuration
Trying 'ramdisk@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@aspeed-ast2600-evb.dtb' configuration
Trying 'fdt@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@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@lists.ozlabs.org>
> *On Behalf Of *VINOTHKUMAR RK
> *Sent:* Thursday, February 4, 2021 8:28 PM
> *To:* openbmc@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
>
[-- Attachment #2: Type: text/html, Size: 13092 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
2021-02-05 4:19 ` VINOTHKUMAR RK
@ 2021-02-05 7:29 ` Troy Lee
2021-02-05 8:15 ` VINOTHKUMAR RK
0 siblings, 1 reply; 12+ messages in thread
From: Troy Lee @ 2021-02-05 7:29 UTC (permalink / raw)
To: VINOTHKUMAR RK; +Cc: openbmc
Hi Vinothkumar,
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.
I could boot into OS with the following qemu command:
qemu-system-arm -M ast2600-evb -drive file=image-bmc,format=raw,if=mtd -nographic -nic user
My QEMU version:
qemu-system-arm --version
QEMU emulator version 5.2.50 (v5.2.0-991-g45240eed4f)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
Thanks,
Troy Lee
From: VINOTHKUMAR RK <vkrk.user@gmail.com>
Sent: Friday, February 5, 2021 12:19 PM
To: Troy Lee <troy_lee@aspeedtech.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
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@100: 1, sdhci_slot1@200: 2, emmc_slot0@100: 0
Loading Environment from SPI Flash... *** Warning - spi_flash_probe_bus_cs() failed, using default environment
In: serial@1e784000
Out: serial@1e784000
Err: serial@1e784000
Model: AST2600 EVB
Net:
Warning: ftgmac@1e660000 (eth0) using random MAC address - 5e:23:16:3b:07:db
eth0: ftgmac@1e660000
Warning: ftgmac@1e680000 (eth1) using random MAC address - 92:2d:b9:4b:a5:93
, eth1: ftgmac@1e680000
Warning: ftgmac@1e670000 (eth2) using random MAC address - f6:16:60:c6:0a:2d
, eth2: ftgmac@1e670000
Warning: ftgmac@1e690000 (eth3) using random MAC address - 02:43:32:16:41:6d
, eth3: ftgmac@1e690000
Hit any key to stop autoboot: 0
## Loading kernel from FIT Image at 20100000 ...
Using 'conf@aspeed-ast2600-evb.dtb' configuration
Trying 'kernel@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@aspeed-ast2600-evb.dtb' configuration
Trying 'ramdisk@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@aspeed-ast2600-evb.dtb' configuration
Trying 'fdt@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 <mailto:troy_lee@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=mailto:aspeedtech.com@lists.ozlabs.org> On Behalf Of VINOTHKUMAR RK
Sent: Thursday, February 4, 2021 8:28 PM
To: mailto:openbmc@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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
2021-02-05 7:29 ` Troy Lee
@ 2021-02-05 8:15 ` VINOTHKUMAR RK
2021-02-05 9:28 ` Troy Lee
0 siblings, 1 reply; 12+ messages in thread
From: VINOTHKUMAR RK @ 2021-02-05 8:15 UTC (permalink / raw)
To: Troy Lee; +Cc: openbmc
[-- Attachment #1: Type: text/plain, Size: 10610 bytes --]
Hi Troy,
Thanks a lot for your input!
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)".
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.
Output:
---------
Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 0.1.0
evb-ast2600 ttyS4
evb-ast2600 login: root
Password:
root@evb-ast2600:~#
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.
Regards,
Vinoth Kumar RK
On Fri, 5 Feb 2021 at 12:59, Troy Lee <troy_lee@aspeedtech.com> wrote:
> Hi Vinothkumar,
>
> 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.
>
> I could boot into OS with the following qemu command:
> qemu-system-arm -M ast2600-evb -drive file=image-bmc,format=raw,if=mtd
> -nographic -nic user
>
> My QEMU version:
> qemu-system-arm --version
> QEMU emulator version 5.2.50 (v5.2.0-991-g45240eed4f)
> Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
>
> Thanks,
> Troy Lee
>
> From: VINOTHKUMAR RK <vkrk.user@gmail.com>
> Sent: Friday, February 5, 2021 12:19 PM
> To: Troy Lee <troy_lee@aspeedtech.com>
> Cc: openbmc@lists.ozlabs.org
> Subject: Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too
> large!'
>
> 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@100: 1, sdhci_slot1@200: 2, emmc_slot0@100: 0
> Loading Environment from SPI Flash... *** Warning -
> spi_flash_probe_bus_cs() failed, using default environment
>
> In: serial@1e784000
> Out: serial@1e784000
> Err: serial@1e784000
> Model: AST2600 EVB
> Net:
> Warning: ftgmac@1e660000 (eth0) using random MAC address -
> 5e:23:16:3b:07:db
> eth0: ftgmac@1e660000
> Warning: ftgmac@1e680000 (eth1) using random MAC address -
> 92:2d:b9:4b:a5:93
> , eth1: ftgmac@1e680000
> Warning: ftgmac@1e670000 (eth2) using random MAC address -
> f6:16:60:c6:0a:2d
> , eth2: ftgmac@1e670000
> Warning: ftgmac@1e690000 (eth3) using random MAC address -
> 02:43:32:16:41:6d
> , eth3: ftgmac@1e690000
> Hit any key to stop autoboot: 0
> ## Loading kernel from FIT Image at 20100000 ...
> Using 'conf@aspeed-ast2600-evb.dtb' configuration
> Trying 'kernel@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@aspeed-ast2600-evb.dtb' configuration
> Trying 'ramdisk@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@aspeed-ast2600-evb.dtb' configuration
> Trying 'fdt@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 <mailto:troy_lee@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=mailto:
> aspeedtech.com@lists.ozlabs.org> On Behalf Of VINOTHKUMAR RK
> Sent: Thursday, February 4, 2021 8:28 PM
> To: mailto:openbmc@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
>
[-- Attachment #2: Type: text/html, Size: 12960 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
2021-02-05 8:15 ` VINOTHKUMAR RK
@ 2021-02-05 9:28 ` Troy Lee
2021-02-15 11:45 ` VINOTHKUMAR RK
0 siblings, 1 reply; 12+ messages in thread
From: Troy Lee @ 2021-02-05 9:28 UTC (permalink / raw)
To: VINOTHKUMAR RK; +Cc: openbmc
[-- Attachment #1: Type: text/plain, Size: 11031 bytes --]
Hi Vinothkumar,
If you want to boot different Kernel from TFTP, I think you can use tftp command in u-boot.
ast# dhcp
ast# tftp 0x83000000 serverip:/path/image-kernel
ast# bootm 0x83000000
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.
Thanks,
Troy Lee
From: VINOTHKUMAR RK <vkrk.user@gmail.com>
Sent: Friday, February 5, 2021 4:16 PM
To: Troy Lee <troy_lee@aspeedtech.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
Hi Troy,
Thanks a lot for your input!
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)".
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.
Output:
---------
Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 0.1.0 evb-ast2600 ttyS4
evb-ast2600 login: root
Password:
root@evb-ast2600:~#
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.
Regards,
Vinoth Kumar RK
On Fri, 5 Feb 2021 at 12:59, Troy Lee <troy_lee@aspeedtech.com<mailto:troy_lee@aspeedtech.com>> wrote:
Hi Vinothkumar,
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.
I could boot into OS with the following qemu command:
qemu-system-arm -M ast2600-evb -drive file=image-bmc,format=raw,if=mtd -nographic -nic user
My QEMU version:
qemu-system-arm --version
QEMU emulator version 5.2.50 (v5.2.0-991-g45240eed4f)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
Thanks,
Troy Lee
From: VINOTHKUMAR RK <vkrk.user@gmail.com<mailto:vkrk.user@gmail.com>>
Sent: Friday, February 5, 2021 12:19 PM
To: Troy Lee <troy_lee@aspeedtech.com<mailto:troy_lee@aspeedtech.com>>
Cc: openbmc@lists.ozlabs.org<mailto:openbmc@lists.ozlabs.org>
Subject: Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
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@100: 1, sdhci_slot1@200: 2, emmc_slot0@100: 0
Loading Environment from SPI Flash... *** Warning - spi_flash_probe_bus_cs() failed, using default environment
In: serial@1e784000
Out: serial@1e784000
Err: serial@1e784000
Model: AST2600 EVB
Net:
Warning: ftgmac@1e660000 (eth0) using random MAC address - 5e:23:16:3b:07:db
eth0: ftgmac@1e660000
Warning: ftgmac@1e680000 (eth1) using random MAC address - 92:2d:b9:4b:a5:93
, eth1: ftgmac@1e680000
Warning: ftgmac@1e670000 (eth2) using random MAC address - f6:16:60:c6:0a:2d
, eth2: ftgmac@1e670000
Warning: ftgmac@1e690000 (eth3) using random MAC address - 02:43:32:16:41:6d
, eth3: ftgmac@1e690000
Hit any key to stop autoboot: 0
## Loading kernel from FIT Image at 20100000 ...
Using 'conf@aspeed-ast2600-evb.dtb' configuration
Trying 'kernel@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@aspeed-ast2600-evb.dtb' configuration
Trying 'ramdisk@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@aspeed-ast2600-evb.dtb' configuration
Trying 'fdt@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 <mailto:troy_lee@aspeedtech.com<mailto:troy_lee@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=mailto:aspeedtech.com@lists.ozlabs.org<mailto:aspeedtech.com@lists.ozlabs.org>> On Behalf Of VINOTHKUMAR RK
Sent: Thursday, February 4, 2021 8:28 PM
To: mailto:openbmc@lists.ozlabs.org<mailto:openbmc@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
[-- Attachment #2: Type: text/html, Size: 18200 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
2021-02-05 9:28 ` Troy Lee
@ 2021-02-15 11:45 ` VINOTHKUMAR RK
2021-02-17 2:40 ` Troy Lee
0 siblings, 1 reply; 12+ messages in thread
From: VINOTHKUMAR RK @ 2021-02-15 11:45 UTC (permalink / raw)
To: Troy Lee; +Cc: openbmc
[-- Attachment #1: Type: text/plain, Size: 14172 bytes --]
Hi Troy,
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?
Please check the below link for complete log:
- https://gist.github.com/vkrk-user/909b554aa4cddd10663ad706d4c182a7
Crash log:
-------------
mount: mounting /dev/mtdblock4 on run/initramfs/ro failed: Invalid argument
[ 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.
[ 2.768965] overlayfs: upper fs does not support tmpfile.
[ 3.040864] overlayfs: upper fs does not support RENAME_WHITEOUT.
chroot: can't execute '/bin/sh': No such file or directory
Unable to confirm /sbin/init is an executable non-empty file
in[ 3.333044] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00000100
[ 3.342421] CPU: 0 PID: 1 Comm: init Not tainted 5.8.17-3cc95ae #1
[ 3.349316] Hardware name: Generic DT based system
[ 3.354661] Backtrace:
[ 3.357411] [<8010d92c>] (dump_backtrace) from [<8010db80>]
(show_stack+0x20/0x24)
[ 3.365860] r7:80a049bc r6:60000093 r5:00000000 r4:80c66358
[ 3.372184] [<8010db60>] (show_stack) from [<808b7000>]
(dump_stack+0x9c/0xb0)
[ 3.380248] [<808b6f64>] (dump_stack) from [<801211a0>]
(panic+0x114/0x340)
[ 3.388016] r7:80a049bc r6:80c0df08 r5:00000000 r4:80c88380
[ 3.394336] [<8012108c>] (panic) from [<80127178>]
(complete_and_exit+0x0/0x2c)
[ 3.402492] r3:00000001 r2:00000000 r1:00000100 r0:80a049bc
[ 3.408803] r7:ffffe000
[ 3.411630] [<8012678c>] (do_exit) from [<80127214>]
(do_group_exit+0x50/0xc8)
[ 3.419677] r7:000000f8
[ 3.422503] [<801271c4>] (do_group_exit) from [<801272ac>]
(__wake_up_parent+0x0/0x30)
[ 3.431338] r7:000000f8 r6:00000004 r5:00000004 r4:006ec190
[ 3.437656] [<8012728c>] (sys_exit_group) from [<80100060>]
(ret_fast_syscall+0x0/0x54)
[ 3.446587] Exception stack(0xbd0dffa8 to 0xbd0dfff0)
[ 3.452225] ffa0: 006ec190 00000004 00000001 00000000
00000001 006ec190
[ 3.461351] ffc0: 006ec190 00000004 00000004 000000f8 00000000 00000000
00507a7c 00000000
[ 3.470476] ffe0: 00507b34 7ed76a14 00497934 76dcc574
[ 3.476121] CPU1: stopping
[ 3.479141] CPU: 1 PID: 99 Comm: jffs2_gcd_mtd5 Not tainted
5.8.17-3cc95ae #1
[ 3.487099] Hardware name: Generic DT based system
Regards,
Vinoth Kumar RK
On Fri, 5 Feb 2021 at 14:58, Troy Lee <troy_lee@aspeedtech.com> wrote:
> Hi Vinothkumar,
>
>
>
> If you want to boot different Kernel from TFTP, I think you can use tftp
> command in u-boot.
>
> ast# dhcp
>
> ast# tftp 0x83000000 serverip:/path/image-kernel
>
> ast# bootm 0x83000000
>
>
>
> 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.
>
>
>
> Thanks,
>
> Troy Lee
>
>
>
> *From:* VINOTHKUMAR RK <vkrk.user@gmail.com>
> *Sent:* Friday, February 5, 2021 4:16 PM
> *To:* Troy Lee <troy_lee@aspeedtech.com>
> *Cc:* openbmc@lists.ozlabs.org
> *Subject:* Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is
> too large!'
>
>
>
> Hi Troy,
>
>
>
> Thanks a lot for your input!
>
>
>
> 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)".
>
> 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.
>
>
>
> Output:
>
> ---------
>
> Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 0.1.0
> evb-ast2600 ttyS4
>
>
>
> evb-ast2600 login: root
>
> Password:
>
> root@evb-ast2600:~#
>
>
>
> 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.
>
>
>
>
>
> Regards,
>
> Vinoth Kumar RK
>
>
>
>
>
> On Fri, 5 Feb 2021 at 12:59, Troy Lee <troy_lee@aspeedtech.com> wrote:
>
> Hi Vinothkumar,
>
> 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.
>
> I could boot into OS with the following qemu command:
> qemu-system-arm -M ast2600-evb -drive file=image-bmc,format=raw,if=mtd
> -nographic -nic user
>
> My QEMU version:
> qemu-system-arm --version
> QEMU emulator version 5.2.50 (v5.2.0-991-g45240eed4f)
> Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
>
> Thanks,
> Troy Lee
>
> From: VINOTHKUMAR RK <vkrk.user@gmail.com>
> Sent: Friday, February 5, 2021 12:19 PM
> To: Troy Lee <troy_lee@aspeedtech.com>
> Cc: openbmc@lists.ozlabs.org
> Subject: Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too
> large!'
>
> 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@100: 1, sdhci_slot1@200: 2, emmc_slot0@100: 0
> Loading Environment from SPI Flash... *** Warning -
> spi_flash_probe_bus_cs() failed, using default environment
>
> In: serial@1e784000
> Out: serial@1e784000
> Err: serial@1e784000
> Model: AST2600 EVB
> Net:
> Warning: ftgmac@1e660000 (eth0) using random MAC address -
> 5e:23:16:3b:07:db
> eth0: ftgmac@1e660000
> Warning: ftgmac@1e680000 (eth1) using random MAC address -
> 92:2d:b9:4b:a5:93
> , eth1: ftgmac@1e680000
> Warning: ftgmac@1e670000 (eth2) using random MAC address -
> f6:16:60:c6:0a:2d
> , eth2: ftgmac@1e670000
> Warning: ftgmac@1e690000 (eth3) using random MAC address -
> 02:43:32:16:41:6d
> , eth3: ftgmac@1e690000
> Hit any key to stop autoboot: 0
> ## Loading kernel from FIT Image at 20100000 ...
> Using 'conf@aspeed-ast2600-evb.dtb' configuration
> Trying 'kernel@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@aspeed-ast2600-evb.dtb' configuration
> Trying 'ramdisk@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@aspeed-ast2600-evb.dtb' configuration
> Trying 'fdt@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 <mailto:troy_lee@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=mailto:
> aspeedtech.com@lists.ozlabs.org> On Behalf Of VINOTHKUMAR RK
> Sent: Thursday, February 4, 2021 8:28 PM
> To: mailto:openbmc@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
>
>
[-- Attachment #2: Type: text/html, Size: 19482 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
2021-02-15 11:45 ` VINOTHKUMAR RK
@ 2021-02-17 2:40 ` Troy Lee
0 siblings, 0 replies; 12+ messages in thread
From: Troy Lee @ 2021-02-17 2:40 UTC (permalink / raw)
To: VINOTHKUMAR RK; +Cc: openbmc
Hi Vinoth Kumar,
> mount: mounting /dev/mtdblock4 on run/initramfs/ro failed: Invalid argument
It seems that kernel is corrected loaded and runs, but the rofs isn’t.
You could check if the rofs in your flash image, or you could load it into ram through tftp, then modifying bootarg indicate Kernel to mount rofs from different place.
Thanks,
Troy Lee
From: VINOTHKUMAR RK <vkrk.user@gmail.com>
Sent: Monday, February 15, 2021 7:46 PM
To: Troy Lee <troy_lee@aspeedtech.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
Hi Troy,
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?
Please check the below link for complete log:
- https://gist.github.com/vkrk-user/909b554aa4cddd10663ad706d4c182a7
Crash log:
-------------
mount: mounting /dev/mtdblock4 on run/initramfs/ro failed: Invalid argument
[ 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.
[ 2.768965] overlayfs: upper fs does not support tmpfile.
[ 3.040864] overlayfs: upper fs does not support RENAME_WHITEOUT.
chroot: can't execute '/bin/sh': No such file or directory
Unable to confirm /sbin/init is an executable non-empty file
in[ 3.333044] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[ 3.342421] CPU: 0 PID: 1 Comm: init Not tainted 5.8.17-3cc95ae #1
[ 3.349316] Hardware name: Generic DT based system
[ 3.354661] Backtrace:
[ 3.357411] [<8010d92c>] (dump_backtrace) from [<8010db80>] (show_stack+0x20/0x24)
[ 3.365860] r7:80a049bc r6:60000093 r5:00000000 r4:80c66358
[ 3.372184] [<8010db60>] (show_stack) from [<808b7000>] (dump_stack+0x9c/0xb0)
[ 3.380248] [<808b6f64>] (dump_stack) from [<801211a0>] (panic+0x114/0x340)
[ 3.388016] r7:80a049bc r6:80c0df08 r5:00000000 r4:80c88380
[ 3.394336] [<8012108c>] (panic) from [<80127178>] (complete_and_exit+0x0/0x2c)
[ 3.402492] r3:00000001 r2:00000000 r1:00000100 r0:80a049bc
[ 3.408803] r7:ffffe000
[ 3.411630] [<8012678c>] (do_exit) from [<80127214>] (do_group_exit+0x50/0xc8)
[ 3.419677] r7:000000f8
[ 3.422503] [<801271c4>] (do_group_exit) from [<801272ac>] (__wake_up_parent+0x0/0x30)
[ 3.431338] r7:000000f8 r6:00000004 r5:00000004 r4:006ec190
[ 3.437656] [<8012728c>] (sys_exit_group) from [<80100060>] (ret_fast_syscall+0x0/0x54)
[ 3.446587] Exception stack(0xbd0dffa8 to 0xbd0dfff0)
[ 3.452225] ffa0: 006ec190 00000004 00000001 00000000 00000001 006ec190
[ 3.461351] ffc0: 006ec190 00000004 00000004 000000f8 00000000 00000000 00507a7c 00000000
[ 3.470476] ffe0: 00507b34 7ed76a14 00497934 76dcc574
[ 3.476121] CPU1: stopping
[ 3.479141] CPU: 1 PID: 99 Comm: jffs2_gcd_mtd5 Not tainted 5.8.17-3cc95ae #1
[ 3.487099] Hardware name: Generic DT based system
Regards,
Vinoth Kumar RK
On Fri, 5 Feb 2021 at 14:58, Troy Lee <mailto:troy_lee@aspeedtech.com> wrote:
Hi Vinothkumar,
If you want to boot different Kernel from TFTP, I think you can use tftp command in u-boot.
ast# dhcp
ast# tftp 0x83000000 serverip:/path/image-kernel
ast# bootm 0x83000000
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.
Thanks,
Troy Lee
From: VINOTHKUMAR RK <mailto:vkrk.user@gmail.com>
Sent: Friday, February 5, 2021 4:16 PM
To: Troy Lee <mailto:troy_lee@aspeedtech.com>
Cc: mailto:openbmc@lists.ozlabs.org
Subject: Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
Hi Troy,
Thanks a lot for your input!
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)".
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.
Output:
---------
Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 0.1.0 evb-ast2600 ttyS4
evb-ast2600 login: root
Password:
root@evb-ast2600:~#
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.
Regards,
Vinoth Kumar RK
On Fri, 5 Feb 2021 at 12:59, Troy Lee <mailto:troy_lee@aspeedtech.com> wrote:
Hi Vinothkumar,
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.
I could boot into OS with the following qemu command:
qemu-system-arm -M ast2600-evb -drive file=image-bmc,format=raw,if=mtd -nographic -nic user
My QEMU version:
qemu-system-arm --version
QEMU emulator version 5.2.50 (v5.2.0-991-g45240eed4f)
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
Thanks,
Troy Lee
From: VINOTHKUMAR RK <mailto:vkrk.user@gmail.com>
Sent: Friday, February 5, 2021 12:19 PM
To: Troy Lee <mailto:troy_lee@aspeedtech.com>
Cc: mailto:openbmc@lists.ozlabs.org
Subject: Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
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@100: 1, sdhci_slot1@200: 2, emmc_slot0@100: 0
Loading Environment from SPI Flash... *** Warning - spi_flash_probe_bus_cs() failed, using default environment
In: serial@1e784000
Out: serial@1e784000
Err: serial@1e784000
Model: AST2600 EVB
Net:
Warning: ftgmac@1e660000 (eth0) using random MAC address - 5e:23:16:3b:07:db
eth0: ftgmac@1e660000
Warning: ftgmac@1e680000 (eth1) using random MAC address - 92:2d:b9:4b:a5:93
, eth1: ftgmac@1e680000
Warning: ftgmac@1e670000 (eth2) using random MAC address - f6:16:60:c6:0a:2d
, eth2: ftgmac@1e670000
Warning: ftgmac@1e690000 (eth3) using random MAC address - 02:43:32:16:41:6d
, eth3: ftgmac@1e690000
Hit any key to stop autoboot: 0
## Loading kernel from FIT Image at 20100000 ...
Using 'conf@aspeed-ast2600-evb.dtb' configuration
Trying 'kernel@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@aspeed-ast2600-evb.dtb' configuration
Trying 'ramdisk@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@aspeed-ast2600-evb.dtb' configuration
Trying 'fdt@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 <mailto:mailto:troy_lee@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=mailto:mailto:aspeedtech.com@lists.ozlabs.org> On Behalf Of VINOTHKUMAR RK
Sent: Thursday, February 4, 2021 8:28 PM
To: mailto:mailto:openbmc@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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
2021-02-05 2:27 ` Troy Lee
2021-02-05 4:19 ` VINOTHKUMAR RK
@ 2021-03-08 5:52 ` Thang Nguyen
2021-03-09 22:10 ` Brad Bishop
1 sibling, 1 reply; 12+ messages in thread
From: Thang Nguyen @ 2021-03-08 5:52 UTC (permalink / raw)
To: openbmc
[-- Attachment #1: Type: text/plain, Size: 5103 bytes --]
Hi,
On 05/02/2021 09:27, Troy Lee 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-phosphor/+/39343>
> * https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/39344
> <https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/39344>
>
Are these changes merged? I can't access these links.
>
> *
>
> Thanks,
>
> Troy Lee
>
> *From:* openbmc
> <openbmc-bounces+troy_lee=aspeedtech.com@lists.ozlabs.org> *On Behalf
> Of *VINOTHKUMAR RK
> *Sent:* Thursday, February 4, 2021 8:28 PM
> *To:* openbmc@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
>
[-- Attachment #2: Type: text/html, Size: 12060 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
2021-03-08 5:52 ` Thang Nguyen
@ 2021-03-09 22:10 ` Brad Bishop
2021-03-11 3:11 ` Troy Lee
0 siblings, 1 reply; 12+ messages in thread
From: Brad Bishop @ 2021-03-09 22:10 UTC (permalink / raw)
To: Thang Nguyen; +Cc: openbmc
On Mon, Mar 08, 2021 at 12:52:41PM +0700, Thang Nguyen wrote:
>Hi,
>
>On 05/02/2021 09:27, Troy Lee 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-phosphor/+/39343>
>> * https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/39344
>> <https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/39344>
>>
>Are these changes merged? I can't access these links.
Hi - We changed our process a bit and now patches are to be submitted to
openbmc/openbmc instead of openbmc/meta-aspeed.
To help with that transition I thought it would make sense to mark these
as hidden in Gerrit, but that seems to have gotten in the way a couple
times now.
I've changed the project flag again on all these meta-repos to read only
- you should be able to view them again now.
If we want any of these merged - they'll need to be re-submitted to
openbmc/openbmc.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
2021-03-09 22:10 ` Brad Bishop
@ 2021-03-11 3:11 ` Troy Lee
2021-03-11 12:00 ` Brad Bishop
0 siblings, 1 reply; 12+ messages in thread
From: Troy Lee @ 2021-03-11 3:11 UTC (permalink / raw)
To: Brad Bishop; +Cc: openbmc, Thang Nguyen
Hi Brad,
The 03/10/2021 06:10, Brad Bishop wrote:
> On Mon, Mar 08, 2021 at 12:52:41PM +0700, Thang Nguyen wrote:
> >Hi,
> >
> >On 05/02/2021 09:27, Troy Lee 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-phosphor/+/39343>
> >> * https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/39344
> >> <https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/39344>
> >>
> >Are these changes merged? I can't access these links.
>
> Hi - We changed our process a bit and now patches are to be submitted to
> openbmc/openbmc instead of openbmc/meta-aspeed.
>
> To help with that transition I thought it would make sense to mark these
> as hidden in Gerrit, but that seems to have gotten in the way a couple
> times now.
>
> I've changed the project flag again on all these meta-repos to read only
> - you should be able to view them again now.
>
> If we want any of these merged - they'll need to be re-submitted to
> openbmc/openbmc.
That explains why I can't find these patches a week ago, and it appears
again yesterday. Thanks for pointing it out, I'll re-submit the change
against to openbmc/openbmc.
Thanks,
Troy Lee
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!'
2021-03-11 3:11 ` Troy Lee
@ 2021-03-11 12:00 ` Brad Bishop
0 siblings, 0 replies; 12+ messages in thread
From: Brad Bishop @ 2021-03-11 12:00 UTC (permalink / raw)
To: Troy Lee; +Cc: openbmc, Thang Nguyen
On Thu, Mar 11, 2021 at 03:11:07AM +0000, Troy Lee wrote:
>Hi Brad,
>
>The 03/10/2021 06:10, Brad Bishop wrote:
>> Hi - We changed our process a bit and now patches are to be submitted to
>> openbmc/openbmc instead of openbmc/meta-aspeed.
>>
>> To help with that transition I thought it would make sense to mark these
>> as hidden in Gerrit, but that seems to have gotten in the way a couple
>> times now.
>>
>> I've changed the project flag again on all these meta-repos to read only
>> - you should be able to view them again now.
>>
>> If we want any of these merged - they'll need to be re-submitted to
>> openbmc/openbmc.
>
>That explains why I can't find these patches a week ago, and it appears
>again yesterday. Thanks for pointing it out, I'll re-submit the change
>against to openbmc/openbmc.
>
>Thanks,
>Troy Lee
Thanks Troy! Sorry about the hassle :-(
-brad
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2021-03-11 12:01 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-04 12:27 evb-ast2600: Getting some build errors - 'u-boot.bin' is too large!' VINOTHKUMAR RK
2021-02-05 2:27 ` Troy Lee
2021-02-05 4:19 ` VINOTHKUMAR RK
2021-02-05 7:29 ` Troy Lee
2021-02-05 8:15 ` VINOTHKUMAR RK
2021-02-05 9:28 ` Troy Lee
2021-02-15 11:45 ` VINOTHKUMAR RK
2021-02-17 2:40 ` Troy Lee
2021-03-08 5:52 ` Thang Nguyen
2021-03-09 22:10 ` Brad Bishop
2021-03-11 3:11 ` Troy Lee
2021-03-11 12:00 ` Brad Bishop
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.