Add functional tests for AST2500 and AST2600 machines using the
OpenBMC SDK v11.00 with Linux kernel 5.15. These tests complement the
existing SDK tests and verify that QEMU correctly boots older kernel
versions on these platforms.
Link: https://lore.kernel.org/qemu-devel/20260209065044.239378-3-clg@redhat.com
Reviewed-by: Kane Chen <kane_chen@aspeedtech.com>
Signed-off-by: Cédric Le Goater <clg@redhat.com>
---
tests/functional/arm/meson.build | 4 +++
.../arm/test_aspeed_ast2500_sdk_515.py | 29 +++++++++++++++++++
.../arm/test_aspeed_ast2600_sdk_515.py | 29 +++++++++++++++++++
3 files changed, 62 insertions(+)
create mode 100755 tests/functional/arm/test_aspeed_ast2500_sdk_515.py
create mode 100755 tests/functional/arm/test_aspeed_ast2600_sdk_515.py
diff --git a/tests/functional/arm/meson.build b/tests/functional/arm/meson.build
index 175a83a2acd7..2f538f29a2de 100644
--- a/tests/functional/arm/meson.build
+++ b/tests/functional/arm/meson.build
@@ -5,10 +5,12 @@ test_arm_timeouts = {
'aspeed_romulus' : 120,
'aspeed_witherspoon' : 120,
'aspeed_ast2500_sdk' : 720,
+ 'aspeed_ast2500_sdk_515' : 720,
'aspeed_ast2500_buildroot' : 480,
'aspeed_ast2600_buildroot' : 480,
'aspeed_ast2600_buildroot_tpm' : 720,
'aspeed_ast2600_sdk' : 720,
+ 'aspeed_ast2600_sdk_515' : 720,
'aspeed_ast2600_sdk_otp' : 720,
'aspeed_bletchley' : 480,
'aspeed_catalina' : 480,
@@ -36,10 +38,12 @@ tests_arm_system_thorough = [
'aspeed_romulus',
'aspeed_witherspoon',
'aspeed_ast2500_sdk',
+ 'aspeed_ast2500_sdk_515',
'aspeed_ast2500_buildroot',
'aspeed_ast2600_buildroot',
'aspeed_ast2600_buildroot_tpm',
'aspeed_ast2600_sdk',
+ 'aspeed_ast2600_sdk_515',
'aspeed_ast2600_sdk_otp',
'aspeed_bletchley',
'aspeed_catalina',
diff --git a/tests/functional/arm/test_aspeed_ast2500_sdk_515.py b/tests/functional/arm/test_aspeed_ast2500_sdk_515.py
new file mode 100755
index 000000000000..464a4e43961d
--- /dev/null
+++ b/tests/functional/arm/test_aspeed_ast2500_sdk_515.py
@@ -0,0 +1,29 @@
+#!/usr/bin/env python3
+#
+# Functional test that boots the ASPEED machines
+#
+# SPDX-License-Identifier: GPL-2.0-or-later
+
+from qemu_test import Asset
+from aspeed import AspeedTest
+
+
+class AST2500Machine(AspeedTest):
+
+ ASSET_SDK_V1100_AST2500_515 = Asset(
+ 'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11.00/ast2500-default-515-obmc.tar.gz',
+ '5732255d4617d98b76bbbc116d331d6ac89906fa212969eb8213fdc4aea86451')
+
+ def test_arm_ast2500_evb_sdk_515(self):
+ self.set_machine('ast2500-evb')
+
+ self.archive_extract(self.ASSET_SDK_V1100_AST2500_515)
+
+ self.do_test_arm_aspeed_sdk_start(
+ self.scratch_file("ast2500-default-515", "image-bmc"))
+
+ self.wait_for_console_pattern('ast2500-default-515 login:')
+
+
+if __name__ == '__main__':
+ AspeedTest.main()
diff --git a/tests/functional/arm/test_aspeed_ast2600_sdk_515.py b/tests/functional/arm/test_aspeed_ast2600_sdk_515.py
new file mode 100755
index 000000000000..f48da301d567
--- /dev/null
+++ b/tests/functional/arm/test_aspeed_ast2600_sdk_515.py
@@ -0,0 +1,29 @@
+#!/usr/bin/env python3
+#
+# Functional test that boots the ASPEED machines
+#
+# SPDX-License-Identifier: GPL-2.0-or-later
+
+from qemu_test import Asset
+from aspeed import AspeedTest
+
+
+class AST2600Machine(AspeedTest):
+
+ ASSET_SDK_V1100_AST2600_515 = Asset(
+ 'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11.00/ast2600-default-515-obmc.tar.gz',
+ 'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6')
+
+ def test_arm_ast2600_evb_sdk_515(self):
+ self.set_machine('ast2600-evb')
+
+ self.archive_extract(self.ASSET_SDK_V1100_AST2600_515)
+
+ self.do_test_arm_aspeed_sdk_start(
+ self.scratch_file("ast2600-default-515", "image-bmc"))
+
+ self.wait_for_console_pattern('ast2600-default-515 login:')
+
+
+if __name__ == '__main__':
+ AspeedTest.main()
--
2.53.0
On Thu, 12 Feb 2026 at 21:42, Cédric Le Goater <clg@redhat.com> wrote: > > Add functional tests for AST2500 and AST2600 machines using the > OpenBMC SDK v11.00 with Linux kernel 5.15. These tests complement the > existing SDK tests and verify that QEMU correctly boots older kernel > versions on these platforms. > + ASSET_SDK_V1100_AST2600_515 = Asset( > + 'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11.00/ast2600-default-515-obmc.tar.gz', > + 'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6') This asset file is over a gigabyte in size, it takes forever to download, and our functional test asset download framework has no mechanism for giving any kind of progress indication for downloads (or even for telling you the URL it is downloading until after the download is complete). Can we have a size limit for test assets please, at least until the framework can support large assets a bit better ? thanks -- PMm
On Mon, 16 Feb 2026 at 11:13, Peter Maydell <peter.maydell@linaro.org> wrote: > > On Thu, 12 Feb 2026 at 21:42, Cédric Le Goater <clg@redhat.com> wrote: > > > > Add functional tests for AST2500 and AST2600 machines using the > > OpenBMC SDK v11.00 with Linux kernel 5.15. These tests complement the > > existing SDK tests and verify that QEMU correctly boots older kernel > > versions on these platforms. > > > > + ASSET_SDK_V1100_AST2600_515 = Asset( > > + 'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11.00/ast2600-default-515-obmc.tar.gz', > > + 'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6') > > This asset file is over a gigabyte in size, it takes forever to > download, and our functional test asset download framework has > no mechanism for giving any kind of progress indication for > downloads (or even for telling you the URL it is downloading > until after the download is complete). > > Can we have a size limit for test assets please, at least until > the framework can support large assets a bit better ? Followup: we have six test assets that are over 500MB in size, and they are all aspeed tests. Please can you have a look at slimming these down? thanks -- PMM
On Mon, Feb 16, 2026 at 11:17:38AM +0000, Peter Maydell wrote: > On Mon, 16 Feb 2026 at 11:13, Peter Maydell <peter.maydell@linaro.org> wrote: > > > > On Thu, 12 Feb 2026 at 21:42, Cédric Le Goater <clg@redhat.com> wrote: > > > > > > Add functional tests for AST2500 and AST2600 machines using the > > > OpenBMC SDK v11.00 with Linux kernel 5.15. These tests complement the > > > existing SDK tests and verify that QEMU correctly boots older kernel > > > versions on these platforms. > > > > > > > + ASSET_SDK_V1100_AST2600_515 = Asset( > > > + 'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11.00/ast2600-default-515-obmc.tar.gz', > > > + 'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6') > > > > This asset file is over a gigabyte in size, it takes forever to > > download, and our functional test asset download framework has > > no mechanism for giving any kind of progress indication for > > downloads (or even for telling you the URL it is downloading > > until after the download is complete). > > > > Can we have a size limit for test assets please, at least until > > the framework can support large assets a bit better ? > > Followup: we have six test assets that are over 500MB in size, > and they are all aspeed tests. Please can you have a look at > slimming these down? I see 2 big assets from aspeed only 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 what are the names of the other files in $HOME/.cache/qemu/download you have that are over 500 MB ? With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
On 2/16/26 15:59, Daniel P. Berrangé wrote: > On Mon, Feb 16, 2026 at 11:17:38AM +0000, Peter Maydell wrote: >> On Mon, 16 Feb 2026 at 11:13, Peter Maydell <peter.maydell@linaro.org> wrote: >>> >>> On Thu, 12 Feb 2026 at 21:42, Cédric Le Goater <clg@redhat.com> wrote: >>>> >>>> Add functional tests for AST2500 and AST2600 machines using the >>>> OpenBMC SDK v11.00 with Linux kernel 5.15. These tests complement the >>>> existing SDK tests and verify that QEMU correctly boots older kernel >>>> versions on these platforms. >>> >>> >>>> + ASSET_SDK_V1100_AST2600_515 = Asset( >>>> + 'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11.00/ast2600-default-515-obmc.tar.gz', >>>> + 'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6') >>> >>> This asset file is over a gigabyte in size, it takes forever to >>> download, and our functional test asset download framework has >>> no mechanism for giving any kind of progress indication for >>> downloads (or even for telling you the URL it is downloading >>> until after the download is complete). >>> >>> Can we have a size limit for test assets please, at least until >>> the framework can support large assets a bit better ? >> >> Followup: we have six test assets that are over 500MB in size, >> and they are all aspeed tests. Please can you have a look at >> slimming these down? > > I see 2 big assets from aspeed only > > 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 > ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 > > > what are the names of the other files in $HOME/.cache/qemu/download > you have that are over 500 MB ? > > With regards, > Daniel These are the files : 5732255d4617d98b76bbbc116d331d6ac89906fa212969eb8213fdc4aea86451 166M ast2500-default-515-obmc.tar.gz 2768e2526bdd3f928df31341801cb6de3b9a40ca942b538a3d0800cd26fbdbfe 166M ast2500-default-obmc.tar.gz ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 1.1G ast2600-default-515-obmc.tar.gz 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 1.2G ast2600-default-obmc.tar.gz 4f8778be176ece1b57d33c4aee13bb989be114c3e4703150eaeb6f996bd5587f 582M ast2700-a1-dcscm-obmc.tar.gz d5ceed511cd0dfefbb102fff2d731159e0472948a28066dc0d90bcd54be76525 520M ast2700-a1-obmc.tar.gz 0e93f7976139da71fab9df7952a58bdd80650e23e7abf5853b0eb6695deb02d0 581M ast2700-dcscm-obmc.tar.gz e2b8f043fe8063dd3b6ded93422e38bd41914dc9c3202199507652df024de4dc 519M ast2700-default-obmc.tar.gz Thanks, C.
Hello, + Jamin, On 2/16/26 16:08, Cédric Le Goater wrote: > On 2/16/26 15:59, Daniel P. Berrangé wrote: >> On Mon, Feb 16, 2026 at 11:17:38AM +0000, Peter Maydell wrote: >>> On Mon, 16 Feb 2026 at 11:13, Peter Maydell <peter.maydell@linaro.org> wrote: >>>> >>>> On Thu, 12 Feb 2026 at 21:42, Cédric Le Goater <clg@redhat.com> wrote: >>>>> >>>>> Add functional tests for AST2500 and AST2600 machines using the >>>>> OpenBMC SDK v11.00 with Linux kernel 5.15. These tests complement the >>>>> existing SDK tests and verify that QEMU correctly boots older kernel >>>>> versions on these platforms. >>>> >>>> >>>>> + ASSET_SDK_V1100_AST2600_515 = Asset( >>>>> + 'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11.00/ast2600-default-515-obmc.tar.gz', >>>>> + 'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6') >>>> >>>> This asset file is over a gigabyte in size, it takes forever to >>>> download, and our functional test asset download framework has >>>> no mechanism for giving any kind of progress indication for >>>> downloads (or even for telling you the URL it is downloading >>>> until after the download is complete). >>>> >>>> Can we have a size limit for test assets please, at least until >>>> the framework can support large assets a bit better ? >>> >>> Followup: we have six test assets that are over 500MB in size, >>> and they are all aspeed tests. Please can you have a look at >>> slimming these down? >> >> I see 2 big assets from aspeed only >> >> 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 >> ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 >> >> >> what are the names of the other files in $HOME/.cache/qemu/download >> you have that are over 500 MB ? >> >> With regards, >> Daniel > > These are the files : > > 5732255d4617d98b76bbbc116d331d6ac89906fa212969eb8213fdc4aea86451 166M ast2500-default-515-obmc.tar.gz > 2768e2526bdd3f928df31341801cb6de3b9a40ca942b538a3d0800cd26fbdbfe 166M ast2500-default-obmc.tar.gz > ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 1.1G ast2600-default-515-obmc.tar.gz > 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 1.2G ast2600-default-obmc.tar.gz > 4f8778be176ece1b57d33c4aee13bb989be114c3e4703150eaeb6f996bd5587f 582M ast2700-a1-dcscm-obmc.tar.gz > d5ceed511cd0dfefbb102fff2d731159e0472948a28066dc0d90bcd54be76525 520M ast2700-a1-obmc.tar.gz > 0e93f7976139da71fab9df7952a58bdd80650e23e7abf5853b0eb6695deb02d0 581M ast2700-dcscm-obmc.tar.gz > e2b8f043fe8063dd3b6ded93422e38bd41914dc9c3202199507652df024de4dc 519M ast2700-default-obmc.tar.gz The image size for v09.08 was around 250 MB for the ast2500, ast2600 and ast2700 SoCs. It would be best to keep it like this for testing. Would it be possible in v12.00 ? Thanks, C.
+ Troy Hi Cédric, > Subject: Re: [PULL 02/16] tests/functional: Add SDK tests with Linux 5.15 > > Hello, > > + Jamin, > > On 2/16/26 16:08, Cédric Le Goater wrote: > > On 2/16/26 15:59, Daniel P. Berrangé wrote: > >> On Mon, Feb 16, 2026 at 11:17:38AM +0000, Peter Maydell wrote: > >>> On Mon, 16 Feb 2026 at 11:13, Peter Maydell <peter.maydell@linaro.org> > wrote: > >>>> > >>>> On Thu, 12 Feb 2026 at 21:42, Cédric Le Goater <clg@redhat.com> > wrote: > >>>>> > >>>>> Add functional tests for AST2500 and AST2600 machines using the > >>>>> OpenBMC SDK v11.00 with Linux kernel 5.15. These tests complement > >>>>> the existing SDK tests and verify that QEMU correctly boots older > >>>>> kernel versions on these platforms. > >>>> > >>>> > >>>>> + ASSET_SDK_V1100_AST2600_515 = Asset( > >>>>> + > >>>>> > +'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11. > >>>>> +00/ast2600-default-515-obmc.tar.gz', > >>>>> + > >>>>> > +'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 > >>>>> +') > >>>> > >>>> This asset file is over a gigabyte in size, it takes forever to > >>>> download, and our functional test asset download framework has no > >>>> mechanism for giving any kind of progress indication for downloads > >>>> (or even for telling you the URL it is downloading until after the > >>>> download is complete). > >>>> > >>>> Can we have a size limit for test assets please, at least until the > >>>> framework can support large assets a bit better ? > >>> > >>> Followup: we have six test assets that are over 500MB in size, and > >>> they are all aspeed tests. Please can you have a look at slimming > >>> these down? > >> > >> I see 2 big assets from aspeed only > >> > >> 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7 > 039e93 > >> ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a857 > 44c0f6 > >> > >> > >> what are the names of the other files in $HOME/.cache/qemu/download > >> you have that are over 500 MB ? > >> > >> With regards, > >> Daniel > > > > These are the files : > > > > > 5732255d4617d98b76bbbc116d331d6ac89906fa212969eb8213fdc4aea86451 > 166M > > ast2500-default-515-obmc.tar.gz > > > 2768e2526bdd3f928df31341801cb6de3b9a40ca942b538a3d0800cd26fbdbfe > 166M > > ast2500-default-obmc.tar.gz > > > ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 > 1.1G > > ast2600-default-515-obmc.tar.gz > > > 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 > 1.2G > > ast2600-default-obmc.tar.gz > > > 4f8778be176ece1b57d33c4aee13bb989be114c3e4703150eaeb6f996bd5587f > 582M > > ast2700-a1-dcscm-obmc.tar.gz > > > d5ceed511cd0dfefbb102fff2d731159e0472948a28066dc0d90bcd54be76525 > 520M > > ast2700-a1-obmc.tar.gz > > > 0e93f7976139da71fab9df7952a58bdd80650e23e7abf5853b0eb6695deb02d0 > 581M > > ast2700-dcscm-obmc.tar.gz > > > e2b8f043fe8063dd3b6ded93422e38bd41914dc9c3202199507652df024de4dc > 519M > > ast2700-default-obmc.tar.gz > > The image size for v09.08 was around 250 MB for the ast2500, > ast2600 and ast2700 SoCs. It would be best to keep it like this for testing. > > Would it be possible in v12.00 ? > Thank you for your suggestion and for reporting this issue. To allow QEMU to accept the image tarball size, I will create new tarballs specifically for QEMU functional testing. The "ast2600-default-image.tar.gz" tarball will be based on "ast2600-default-obmc.tar.gz". It will contain only the necessary images from ast2600-default-obmc.tar.gz for QEMU functional testing, such as image-bmc. Including only image-bmc in the tarball will significantly reduce its size. In SDK v11.01, the size should be around 64MB. I plan to create the following new tarballs for QEMU functional testing: 1. ast2600-default-image.tar.gz 2. ast2600-default-66-image.tar.gz 3. ast2700-default-image.tar.gz 4, ast2700-a1-image.tar.gz 5. ast2700-dcscm-image.tar.gz 6. ast2700-a1-dcscm-image.tar.gz ASPEED will release v11.01 this week. After the v11.01 release, I will update these tarballs and the QEMU functional tests accordingly. Sorry for the late reply and for any inconvenience caused. Jamin > Thanks, > > C. > > > >
On 2/24/26 03:53, Jamin Lin wrote: > + Troy > > Hi Cédric, > >> Subject: Re: [PULL 02/16] tests/functional: Add SDK tests with Linux 5.15 >> >> Hello, >> >> + Jamin, >> >> On 2/16/26 16:08, Cédric Le Goater wrote: >>> On 2/16/26 15:59, Daniel P. Berrangé wrote: >>>> On Mon, Feb 16, 2026 at 11:17:38AM +0000, Peter Maydell wrote: >>>>> On Mon, 16 Feb 2026 at 11:13, Peter Maydell <peter.maydell@linaro.org> >> wrote: >>>>>> >>>>>> On Thu, 12 Feb 2026 at 21:42, Cédric Le Goater <clg@redhat.com> >> wrote: >>>>>>> >>>>>>> Add functional tests for AST2500 and AST2600 machines using the >>>>>>> OpenBMC SDK v11.00 with Linux kernel 5.15. These tests complement >>>>>>> the existing SDK tests and verify that QEMU correctly boots older >>>>>>> kernel versions on these platforms. >>>>>> >>>>>> >>>>>>> + ASSET_SDK_V1100_AST2600_515 = Asset( >>>>>>> + >>>>>>> >> +'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11. >>>>>>> +00/ast2600-default-515-obmc.tar.gz', >>>>>>> + >>>>>>> >> +'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 >>>>>>> +') >>>>>> >>>>>> This asset file is over a gigabyte in size, it takes forever to >>>>>> download, and our functional test asset download framework has no >>>>>> mechanism for giving any kind of progress indication for downloads >>>>>> (or even for telling you the URL it is downloading until after the >>>>>> download is complete). >>>>>> >>>>>> Can we have a size limit for test assets please, at least until the >>>>>> framework can support large assets a bit better ? >>>>> >>>>> Followup: we have six test assets that are over 500MB in size, and >>>>> they are all aspeed tests. Please can you have a look at slimming >>>>> these down? >>>> >>>> I see 2 big assets from aspeed only >>>> >>>> 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7 >> 039e93 >>>> ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a857 >> 44c0f6 >>>> >>>> >>>> what are the names of the other files in $HOME/.cache/qemu/download >>>> you have that are over 500 MB ? >>>> >>>> With regards, >>>> Daniel >>> >>> These are the files : >>> >>> >> 5732255d4617d98b76bbbc116d331d6ac89906fa212969eb8213fdc4aea86451 >> 166M >>> ast2500-default-515-obmc.tar.gz >>> >> 2768e2526bdd3f928df31341801cb6de3b9a40ca942b538a3d0800cd26fbdbfe >> 166M >>> ast2500-default-obmc.tar.gz >>> >> ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 >> 1.1G >>> ast2600-default-515-obmc.tar.gz >>> >> 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 >> 1.2G >>> ast2600-default-obmc.tar.gz >>> >> 4f8778be176ece1b57d33c4aee13bb989be114c3e4703150eaeb6f996bd5587f >> 582M >>> ast2700-a1-dcscm-obmc.tar.gz >>> >> d5ceed511cd0dfefbb102fff2d731159e0472948a28066dc0d90bcd54be76525 >> 520M >>> ast2700-a1-obmc.tar.gz >>> >> 0e93f7976139da71fab9df7952a58bdd80650e23e7abf5853b0eb6695deb02d0 >> 581M >>> ast2700-dcscm-obmc.tar.gz >>> >> e2b8f043fe8063dd3b6ded93422e38bd41914dc9c3202199507652df024de4dc >> 519M >>> ast2700-default-obmc.tar.gz >> >> The image size for v09.08 was around 250 MB for the ast2500, >> ast2600 and ast2700 SoCs. It would be best to keep it like this for testing. >> >> Would it be possible in v12.00 ? >> > > > Thank you for your suggestion and for reporting this issue. > > To allow QEMU to accept the image tarball size, I will create new tarballs specifically for QEMU functional testing. > > The "ast2600-default-image.tar.gz" tarball will be based on "ast2600-default-obmc.tar.gz". > It will contain only the necessary images from ast2600-default-obmc.tar.gz for QEMU functional testing, such as image-bmc. > Including only image-bmc in the tarball will significantly reduce its size. In SDK v11.01, the size should be around 64MB. I think the increase in size comes mainly from the rsa* directories. Removing these would save 1G. Can you keep the same v09.08 contents : u-boot.bin, kernel, dtb, rootfs etc ? It is good to have the different OpenBMC files for tests too. > I plan to create the following new tarballs for QEMU functional testing: > 1. ast2600-default-image.tar.gz > 2. ast2600-default-66-image.tar.gz > 3. ast2700-default-image.tar.gz > 4, ast2700-a1-image.tar.gz > 5. ast2700-dcscm-image.tar.gz > 6. ast2700-a1-dcscm-image.tar.gz ok. No need to change the AST2500 tarballs. > ASPEED will release v11.01 this week. After the v11.01 release, I will update these tarballs and the QEMU functional tests accordingly. Great ! Thanks, C.
Hi Cédric, > Subject: Re: [PULL 02/16] tests/functional: Add SDK tests with Linux 5.15 > > On 2/24/26 03:53, Jamin Lin wrote: > > + Troy > > > > Hi Cédric, > > > >> Subject: Re: [PULL 02/16] tests/functional: Add SDK tests with Linux > >> 5.15 > >> > >> Hello, > >> > >> + Jamin, > >> > >> On 2/16/26 16:08, Cédric Le Goater wrote: > >>> On 2/16/26 15:59, Daniel P. Berrangé wrote: > >>>> On Mon, Feb 16, 2026 at 11:17:38AM +0000, Peter Maydell wrote: > >>>>> On Mon, 16 Feb 2026 at 11:13, Peter Maydell > >>>>> <peter.maydell@linaro.org> > >> wrote: > >>>>>> > >>>>>> On Thu, 12 Feb 2026 at 21:42, Cédric Le Goater <clg@redhat.com> > >> wrote: > >>>>>>> > >>>>>>> Add functional tests for AST2500 and AST2600 machines using the > >>>>>>> OpenBMC SDK v11.00 with Linux kernel 5.15. These tests > >>>>>>> complement the existing SDK tests and verify that QEMU correctly > >>>>>>> boots older kernel versions on these platforms. > >>>>>> > >>>>>> > >>>>>>> + ASSET_SDK_V1100_AST2600_515 = Asset( > >>>>>>> + > >>>>>>> > >> +'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11. > >>>>>>> +00/ast2600-default-515-obmc.tar.gz', > >>>>>>> + > >>>>>>> > >> > +'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 > >>>>>>> +') > >>>>>> > >>>>>> This asset file is over a gigabyte in size, it takes forever to > >>>>>> download, and our functional test asset download framework has no > >>>>>> mechanism for giving any kind of progress indication for > >>>>>> downloads (or even for telling you the URL it is downloading > >>>>>> until after the download is complete). > >>>>>> > >>>>>> Can we have a size limit for test assets please, at least until > >>>>>> the framework can support large assets a bit better ? > >>>>> > >>>>> Followup: we have six test assets that are over 500MB in size, and > >>>>> they are all aspeed tests. Please can you have a look at slimming > >>>>> these down? > >>>> > >>>> I see 2 big assets from aspeed only > >>>> > >>>> 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c > 8c7 > >> 039e93 > >>>> ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a > 857 > >> 44c0f6 > >>>> > >>>> > >>>> what are the names of the other files in $HOME/.cache/qemu/download > >>>> you have that are over 500 MB ? > >>>> > >>>> With regards, > >>>> Daniel > >>> > >>> These are the files : > >>> > >>> > >> > 5732255d4617d98b76bbbc116d331d6ac89906fa212969eb8213fdc4aea86451 > >> 166M > >>> ast2500-default-515-obmc.tar.gz > >>> > >> > 2768e2526bdd3f928df31341801cb6de3b9a40ca942b538a3d0800cd26fbdbfe > >> 166M > >>> ast2500-default-obmc.tar.gz > >>> > >> > ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 > >> 1.1G > >>> ast2600-default-515-obmc.tar.gz > >>> > >> > 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 > >> 1.2G > >>> ast2600-default-obmc.tar.gz > >>> > >> > 4f8778be176ece1b57d33c4aee13bb989be114c3e4703150eaeb6f996bd5587f > >> 582M > >>> ast2700-a1-dcscm-obmc.tar.gz > >>> > >> d5ceed511cd0dfefbb102fff2d731159e0472948a28066dc0d90bcd54be76525 > >> 520M > >>> ast2700-a1-obmc.tar.gz > >>> > >> > 0e93f7976139da71fab9df7952a58bdd80650e23e7abf5853b0eb6695deb02d0 > >> 581M > >>> ast2700-dcscm-obmc.tar.gz > >>> > >> > e2b8f043fe8063dd3b6ded93422e38bd41914dc9c3202199507652df024de4dc > >> 519M > >>> ast2700-default-obmc.tar.gz > >> > >> The image size for v09.08 was around 250 MB for the ast2500, > >> ast2600 and ast2700 SoCs. It would be best to keep it like this for testing. > >> > >> Would it be possible in v12.00 ? > >> > > > > > > Thank you for your suggestion and for reporting this issue. > > > > To allow QEMU to accept the image tarball size, I will create new tarballs > specifically for QEMU functional testing. > > > > The "ast2600-default-image.tar.gz" tarball will be based on > "ast2600-default-obmc.tar.gz". > > It will contain only the necessary images from ast2600-default-obmc.tar.gz > for QEMU functional testing, such as image-bmc. > > Including only image-bmc in the tarball will significantly reduce its size. In > SDK v11.01, the size should be around 64MB. > > I think the increase in size comes mainly from the rsa* directories. > Removing these would save 1G. > > Can you keep the same v09.08 contents : u-boot.bin, kernel, dtb, rootfs etc ? It > is good to have the different OpenBMC files for tests too. > Okay. > > > I plan to create the following new tarballs for QEMU functional testing: > > 1. ast2600-default-image.tar.gz > > 2. ast2600-default-66-image.tar.gz > > 3. ast2700-default-image.tar.gz > > 4, ast2700-a1-image.tar.gz > > 5. ast2700-dcscm-image.tar.gz > > 6. ast2700-a1-dcscm-image.tar.gz > ok. No need to change the AST2500 tarballs. > Do we need to generate ast2700-dcscm-image.tar.gz and ast2700-a1-dcscm-image.tar.gz? These packages do not include signed images in v11.00 (e.g., the ecdsa384 and ecdsa384-lms directories). Furthermore, the contents of ast2700-dcscm-obmc.tar.gz are identical between versions v09.08 and v11.00. Thanks, Jamin > > ASPEED will release v11.01 this week. After the v11.01 release, I will update > these tarballs and the QEMU functional tests accordingly. > > Great ! > > Thanks, > > C.
On 2/24/26 10:33, Jamin Lin wrote:
> Hi Cédric,
>
>> Subject: Re: [PULL 02/16] tests/functional: Add SDK tests with Linux 5.15
>>
>> On 2/24/26 03:53, Jamin Lin wrote:
>>> + Troy
>>>
>>> Hi Cédric,
>>>
>>>> Subject: Re: [PULL 02/16] tests/functional: Add SDK tests with Linux
>>>> 5.15
>>>>
>>>> Hello,
>>>>
>>>> + Jamin,
>>>>
>>>> On 2/16/26 16:08, Cédric Le Goater wrote:
>>>>> On 2/16/26 15:59, Daniel P. Berrangé wrote:
>>>>>> On Mon, Feb 16, 2026 at 11:17:38AM +0000, Peter Maydell wrote:
>>>>>>> On Mon, 16 Feb 2026 at 11:13, Peter Maydell
>>>>>>> <peter.maydell@linaro.org>
>>>> wrote:
>>>>>>>>
>>>>>>>> On Thu, 12 Feb 2026 at 21:42, Cédric Le Goater <clg@redhat.com>
>>>> wrote:
>>>>>>>>>
>>>>>>>>> Add functional tests for AST2500 and AST2600 machines using the
>>>>>>>>> OpenBMC SDK v11.00 with Linux kernel 5.15. These tests
>>>>>>>>> complement the existing SDK tests and verify that QEMU correctly
>>>>>>>>> boots older kernel versions on these platforms.
>>>>>>>>
>>>>>>>>
>>>>>>>>> + ASSET_SDK_V1100_AST2600_515 = Asset(
>>>>>>>>> +
>>>>>>>>>
>>>> +'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11.
>>>>>>>>> +00/ast2600-default-515-obmc.tar.gz',
>>>>>>>>> +
>>>>>>>>>
>>>>
>> +'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6
>>>>>>>>> +')
>>>>>>>>
>>>>>>>> This asset file is over a gigabyte in size, it takes forever to
>>>>>>>> download, and our functional test asset download framework has no
>>>>>>>> mechanism for giving any kind of progress indication for
>>>>>>>> downloads (or even for telling you the URL it is downloading
>>>>>>>> until after the download is complete).
>>>>>>>>
>>>>>>>> Can we have a size limit for test assets please, at least until
>>>>>>>> the framework can support large assets a bit better ?
>>>>>>>
>>>>>>> Followup: we have six test assets that are over 500MB in size, and
>>>>>>> they are all aspeed tests. Please can you have a look at slimming
>>>>>>> these down?
>>>>>>
>>>>>> I see 2 big assets from aspeed only
>>>>>>
>>>>>> 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c
>> 8c7
>>>> 039e93
>>>>>> ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a
>> 857
>>>> 44c0f6
>>>>>>
>>>>>>
>>>>>> what are the names of the other files in $HOME/.cache/qemu/download
>>>>>> you have that are over 500 MB ?
>>>>>>
>>>>>> With regards,
>>>>>> Daniel
>>>>>
>>>>> These are the files :
>>>>>
>>>>>
>>>>
>> 5732255d4617d98b76bbbc116d331d6ac89906fa212969eb8213fdc4aea86451
>>>> 166M
>>>>> ast2500-default-515-obmc.tar.gz
>>>>>
>>>>
>> 2768e2526bdd3f928df31341801cb6de3b9a40ca942b538a3d0800cd26fbdbfe
>>>> 166M
>>>>> ast2500-default-obmc.tar.gz
>>>>>
>>>>
>> ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6
>>>> 1.1G
>>>>> ast2600-default-515-obmc.tar.gz
>>>>>
>>>>
>> 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93
>>>> 1.2G
>>>>> ast2600-default-obmc.tar.gz
>>>>>
>>>>
>> 4f8778be176ece1b57d33c4aee13bb989be114c3e4703150eaeb6f996bd5587f
>>>> 582M
>>>>> ast2700-a1-dcscm-obmc.tar.gz
>>>>>
>>>> d5ceed511cd0dfefbb102fff2d731159e0472948a28066dc0d90bcd54be76525
>>>> 520M
>>>>> ast2700-a1-obmc.tar.gz
>>>>>
>>>>
>> 0e93f7976139da71fab9df7952a58bdd80650e23e7abf5853b0eb6695deb02d0
>>>> 581M
>>>>> ast2700-dcscm-obmc.tar.gz
>>>>>
>>>>
>> e2b8f043fe8063dd3b6ded93422e38bd41914dc9c3202199507652df024de4dc
>>>> 519M
>>>>> ast2700-default-obmc.tar.gz
>>>>
>>>> The image size for v09.08 was around 250 MB for the ast2500,
>>>> ast2600 and ast2700 SoCs. It would be best to keep it like this for testing.
>>>>
>>>> Would it be possible in v12.00 ?
>>>>
>>>
>>>
>>> Thank you for your suggestion and for reporting this issue.
>>>
>>> To allow QEMU to accept the image tarball size, I will create new tarballs
>> specifically for QEMU functional testing.
>>>
>>> The "ast2600-default-image.tar.gz" tarball will be based on
>> "ast2600-default-obmc.tar.gz".
>>> It will contain only the necessary images from ast2600-default-obmc.tar.gz
>> for QEMU functional testing, such as image-bmc.
>>> Including only image-bmc in the tarball will significantly reduce its size. In
>> SDK v11.01, the size should be around 64MB.
>>
>> I think the increase in size comes mainly from the rsa* directories.
>> Removing these would save 1G.
>>
>> Can you keep the same v09.08 contents : u-boot.bin, kernel, dtb, rootfs etc ? It
>> is good to have the different OpenBMC files for tests too.
>>
> Okay.
>>
>>> I plan to create the following new tarballs for QEMU functional testing:
>>> 1. ast2600-default-image.tar.gz
>>> 2. ast2600-default-66-image.tar.gz
>>> 3. ast2700-default-image.tar.gz
>>> 4, ast2700-a1-image.tar.gz
>>> 5. ast2700-dcscm-image.tar.gz
>>> 6. ast2700-a1-dcscm-image.tar.gz
>> ok. No need to change the AST2500 tarballs.
>>
> Do we need to generate ast2700-dcscm-image.tar.gz and ast2700-a1-dcscm-image.tar.gz?
They slightly exceed the 512 MB limit that QEMU was planning
to enforce.
581.6 MiB [####### ] ast2700-a1-dcscm-obmc.tar.gz
580.3 MiB [####### ] ast2700-dcscm-obmc.tar.gz
519.3 MiB [###### ] ast2700-a1-obmc.tar.gz
518.4 MiB [###### ] ast2700-default-obmc.tar.gz
I suppose this is sufficient for the time being. If you find ways
to reduce their size, that would be welcome.
Coming back to your proposal, a longer-term solution would be
indeed to provide a new set of artifacts, one for each QEMU
machine, containing only what is required to run the functional
tests :
<version>/<QEMU machine name>-qemu.tar.gz
What would be easier for you : change the existing tarballs or
add new ones for QEMU ?
Thanks,
C.
> These packages do not include signed images in v11.00 (e.g., the ecdsa384 and ecdsa384-lms directories).
> Furthermore, the contents of ast2700-dcscm-obmc.tar.gz are identical between versions v09.08 and v11.00.
>
> Thanks,
> Jamin
>
>>> ASPEED will release v11.01 this week. After the v11.01 release, I will update
>> these tarballs and the QEMU functional tests accordingly.
>>
>> Great !
>>
>> Thanks,
>>
>> C.
>
Hi Cédric > Subject: Re: [PULL 02/16] tests/functional: Add SDK tests with Linux 5.15 > > On 2/24/26 10:33, Jamin Lin wrote: > > Hi Cédric, > > > >> Subject: Re: [PULL 02/16] tests/functional: Add SDK tests with Linux > >> 5.15 > >> > >> On 2/24/26 03:53, Jamin Lin wrote: > >>> + Troy > >>> > >>> Hi Cédric, > >>> > >>>> Subject: Re: [PULL 02/16] tests/functional: Add SDK tests with > >>>> Linux > >>>> 5.15 > >>>> > >>>> Hello, > >>>> > >>>> + Jamin, > >>>> > >>>> On 2/16/26 16:08, Cédric Le Goater wrote: > >>>>> On 2/16/26 15:59, Daniel P. Berrangé wrote: > >>>>>> On Mon, Feb 16, 2026 at 11:17:38AM +0000, Peter Maydell wrote: > >>>>>>> On Mon, 16 Feb 2026 at 11:13, Peter Maydell > >>>>>>> <peter.maydell@linaro.org> > >>>> wrote: > >>>>>>>> > >>>>>>>> On Thu, 12 Feb 2026 at 21:42, Cédric Le Goater <clg@redhat.com> > >>>> wrote: > >>>>>>>>> > >>>>>>>>> Add functional tests for AST2500 and AST2600 machines using > >>>>>>>>> the OpenBMC SDK v11.00 with Linux kernel 5.15. These tests > >>>>>>>>> complement the existing SDK tests and verify that QEMU > >>>>>>>>> correctly boots older kernel versions on these platforms. > >>>>>>>> > >>>>>>>> > >>>>>>>>> + ASSET_SDK_V1100_AST2600_515 = Asset( > >>>>>>>>> + > >>>>>>>>> > >>>> > +'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11. > >>>>>>>>> +00/ast2600-default-515-obmc.tar.gz', > >>>>>>>>> + > >>>>>>>>> > >>>> > >> > +'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 > >>>>>>>>> +') > >>>>>>>> > >>>>>>>> This asset file is over a gigabyte in size, it takes forever to > >>>>>>>> download, and our functional test asset download framework has > >>>>>>>> no mechanism for giving any kind of progress indication for > >>>>>>>> downloads (or even for telling you the URL it is downloading > >>>>>>>> until after the download is complete). > >>>>>>>> > >>>>>>>> Can we have a size limit for test assets please, at least until > >>>>>>>> the framework can support large assets a bit better ? > >>>>>>> > >>>>>>> Followup: we have six test assets that are over 500MB in size, > >>>>>>> and they are all aspeed tests. Please can you have a look at > >>>>>>> slimming these down? > >>>>>> > >>>>>> I see 2 big assets from aspeed only > >>>>>> > >>>>>> 64d8926a7d01b649168be96c986603b5690f06391286c438a3a7 > 72c > >> 8c7 > >>>> 039e93 > >>>>>> ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d > 12a > >> 857 > >>>> 44c0f6 > >>>>>> > >>>>>> > >>>>>> what are the names of the other files in > >>>>>> $HOME/.cache/qemu/download you have that are over 500 MB ? > >>>>>> > >>>>>> With regards, > >>>>>> Daniel > >>>>> > >>>>> These are the files : > >>>>> > >>>>> > >>>> > >> > 5732255d4617d98b76bbbc116d331d6ac89906fa212969eb8213fdc4aea86451 > >>>> 166M > >>>>> ast2500-default-515-obmc.tar.gz > >>>>> > >>>> > >> > 2768e2526bdd3f928df31341801cb6de3b9a40ca942b538a3d0800cd26fbdbfe > >>>> 166M > >>>>> ast2500-default-obmc.tar.gz > >>>>> > >>>> > >> > ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 > >>>> 1.1G > >>>>> ast2600-default-515-obmc.tar.gz > >>>>> > >>>> > >> > 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 > >>>> 1.2G > >>>>> ast2600-default-obmc.tar.gz > >>>>> > >>>> > >> > 4f8778be176ece1b57d33c4aee13bb989be114c3e4703150eaeb6f996bd5587f > >>>> 582M > >>>>> ast2700-a1-dcscm-obmc.tar.gz > >>>>> > >>>> > d5ceed511cd0dfefbb102fff2d731159e0472948a28066dc0d90bcd54be76525 > >>>> 520M > >>>>> ast2700-a1-obmc.tar.gz > >>>>> > >>>> > >> > 0e93f7976139da71fab9df7952a58bdd80650e23e7abf5853b0eb6695deb02d0 > >>>> 581M > >>>>> ast2700-dcscm-obmc.tar.gz > >>>>> > >>>> > >> > e2b8f043fe8063dd3b6ded93422e38bd41914dc9c3202199507652df024de4dc > >>>> 519M > >>>>> ast2700-default-obmc.tar.gz > >>>> > >>>> The image size for v09.08 was around 250 MB for the ast2500, > >>>> ast2600 and ast2700 SoCs. It would be best to keep it like this for testing. > >>>> > >>>> Would it be possible in v12.00 ? > >>>> > >>> > >>> > >>> Thank you for your suggestion and for reporting this issue. > >>> > >>> To allow QEMU to accept the image tarball size, I will create new > >>> tarballs > >> specifically for QEMU functional testing. > >>> > >>> The "ast2600-default-image.tar.gz" tarball will be based on > >> "ast2600-default-obmc.tar.gz". > >>> It will contain only the necessary images from > >>> ast2600-default-obmc.tar.gz > >> for QEMU functional testing, such as image-bmc. > >>> Including only image-bmc in the tarball will significantly reduce > >>> its size. In > >> SDK v11.01, the size should be around 64MB. > >> > >> I think the increase in size comes mainly from the rsa* directories. > >> Removing these would save 1G. > >> > >> Can you keep the same v09.08 contents : u-boot.bin, kernel, dtb, > >> rootfs etc ? It is good to have the different OpenBMC files for tests too. > >> > > Okay. > >> > >>> I plan to create the following new tarballs for QEMU functional testing: > >>> 1. ast2600-default-image.tar.gz > >>> 2. ast2600-default-66-image.tar.gz > >>> 3. ast2700-default-image.tar.gz > >>> 4, ast2700-a1-image.tar.gz > >>> 5. ast2700-dcscm-image.tar.gz > >>> 6. ast2700-a1-dcscm-image.tar.gz > >> ok. No need to change the AST2500 tarballs. > >> > > Do we need to generate ast2700-dcscm-image.tar.gz and > ast2700-a1-dcscm-image.tar.gz? > > They slightly exceed the 512 MB limit that QEMU was planning to enforce. > > 581.6 MiB [####### ] ast2700-a1-dcscm-obmc.tar.gz > 580.3 MiB [####### ] ast2700-dcscm-obmc.tar.gz > 519.3 MiB [###### ] ast2700-a1-obmc.tar.gz > 518.4 MiB [###### ] ast2700-default-obmc.tar.gz > > I suppose this is sufficient for the time being. If you find ways to reduce their > size, that would be welcome. > > > Coming back to your proposal, a longer-term solution would be indeed to > provide a new set of artifacts, one for each QEMU machine, containing only > what is required to run the functional tests : > > <version>/<QEMU machine name>-qemu.tar.gz > > What would be easier for you : change the existing tarballs or add new ones > for QEMU ? > I plan to create a new set of artifacts for each QEMU machine. The original packages will remain available on the ASPEED SDK release page, as they should not be modified. These packages are used by customers as well as for ASPEED internal testing. If users need to test specific images such as ROFS, U-Boot, the kernel, or perform full OpenBMC firmware updates, they can download the default package (for example, ast2600-default-obmc.tar.gz) for complete testing. The ast2600-default-image.tar.gz package will include only image-bmc for QEMU functional testing and will support programming the entire FMC flash. The contents of the new tarballs will be as follows: 1. ast2600-default-image.tar.gz image-bmc 2. ast2600-default-66-image.tar.gz image-bmc 3. ast2700-default-image.tar.gz image-bmc u-boot.bin zephyr-aspeed-ssp.elf zephyr-aspeed-tsp.elf bl31.bin optee/tee-raw.bin 4, ast2700-a1-image.tar.gz image-bmc u-boot.bin zephyr-aspeed-ssp.elf zephyr-aspeed-tsp.elf bl31.bin optee/tee-raw.bin 5. ast2700-dcscm-image.tar.gz image-bmc u-boot.bin zephyr-aspeed-ssp.elf zephyr-aspeed-tsp.elf bl31.bin optee/tee-raw.bin 6. ast2700-a1-dcscm-image.tar.gz image-bmc u-boot.bin zephyr-aspeed-ssp.elf zephyr-aspeed-tsp.elf bl31.bin optee/tee-raw.bin Please let me know if this approach works for you. Thanks, Jamin > Thanks, > > C. > > > > > These packages do not include signed images in v11.00 (e.g., the ecdsa384 > and ecdsa384-lms directories). > > Furthermore, the contents of ast2700-dcscm-obmc.tar.gz are identical > between versions v09.08 and v11.00. > > > > Thanks, > > Jamin > > > >>> ASPEED will release v11.01 this week. After the v11.01 release, I > >>> will update > >> these tarballs and the QEMU functional tests accordingly. > >> > >> Great ! > >> > >> Thanks, > >> > >> C. > >
Hello Jamin, > I plan to create a new set of artifacts for each QEMU machine. > The original packages will remain available on the ASPEED SDK release page, as they should not be modified. > These packages are used by customers as well as for ASPEED internal testing. yes. This is what I expected. > > If users need to test specific images such as ROFS, U-Boot, the kernel, or perform full OpenBMC firmware updates, > they can download the default package (for example, ast2600-default-obmc.tar.gz) for complete testing. Good. > The ast2600-default-image.tar.gz package will include only image-bmc for QEMU functional testing and will support programming the entire FMC flash. > > The contents of the new tarballs will be as follows: > > 1. ast2600-default-image.tar.gz > image-bmc > > 2. ast2600-default-66-image.tar.gz > image-bmc > > 3. ast2700-default-image.tar.gz > image-bmc > u-boot.bin > zephyr-aspeed-ssp.elf > zephyr-aspeed-tsp.elf > bl31.bin > optee/tee-raw.bin > > 4, ast2700-a1-image.tar.gz > image-bmc > u-boot.bin > zephyr-aspeed-ssp.elf > zephyr-aspeed-tsp.elf > bl31.bin > optee/tee-raw.bin > > 5. ast2700-dcscm-image.tar.gz > image-bmc > u-boot.bin > zephyr-aspeed-ssp.elf > zephyr-aspeed-tsp.elf > bl31.bin > optee/tee-raw.bin > > 6. ast2700-a1-dcscm-image.tar.gz > image-bmc > u-boot.bin > zephyr-aspeed-ssp.elf > zephyr-aspeed-tsp.elf > bl31.bin > optee/tee-raw.bin > > Please let me know if this approach works for you. That seems perfect to me. Thank you very much. C.
Hi Cedric, Due to my vacation, I will be back in the office next week. I will update you then. Thanks, Jamin 取得 Android 版 Outlook<https://aka.ms/AAb9ysg> ________________________________ From: Cédric Le Goater <clg@redhat.com> Sent: Tuesday, February 17, 2026 6:19:04 PM To: Daniel P. Berrangé <berrange@redhat.com>; Peter Maydell <peter.maydell@linaro.org> Cc: Thomas Huth <thuth@redhat.com>; qemu-arm@nongnu.org <qemu-arm@nongnu.org>; qemu-devel@nongnu.org <qemu-devel@nongnu.org>; Kane Chen <kane_chen@aspeedtech.com>; Jamin Lin <jamin_lin@aspeedtech.com> Subject: Re: [PULL 02/16] tests/functional: Add SDK tests with Linux 5.15 Hello, + Jamin, On 2/16/26 16:08, Cédric Le Goater wrote: > On 2/16/26 15:59, Daniel P. Berrangé wrote: >> On Mon, Feb 16, 2026 at 11:17:38AM +0000, Peter Maydell wrote: >>> On Mon, 16 Feb 2026 at 11:13, Peter Maydell <peter.maydell@linaro.org> wrote: >>>> >>>> On Thu, 12 Feb 2026 at 21:42, Cédric Le Goater <clg@redhat.com> wrote: >>>>> >>>>> Add functional tests for AST2500 and AST2600 machines using the >>>>> OpenBMC SDK v11.00 with Linux kernel 5.15. These tests complement the >>>>> existing SDK tests and verify that QEMU correctly boots older kernel >>>>> versions on these platforms. >>>> >>>> >>>>> + ASSET_SDK_V1100_AST2600_515 = Asset( >>>>> + 'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11.00/ast2600-default-515-obmc.tar.gz', >>>>> + 'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6') >>>> >>>> This asset file is over a gigabyte in size, it takes forever to >>>> download, and our functional test asset download framework has >>>> no mechanism for giving any kind of progress indication for >>>> downloads (or even for telling you the URL it is downloading >>>> until after the download is complete). >>>> >>>> Can we have a size limit for test assets please, at least until >>>> the framework can support large assets a bit better ? >>> >>> Followup: we have six test assets that are over 500MB in size, >>> and they are all aspeed tests. Please can you have a look at >>> slimming these down? >> >> I see 2 big assets from aspeed only >> >> 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 >> ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 >> >> >> what are the names of the other files in $HOME/.cache/qemu/download >> you have that are over 500 MB ? >> >> With regards, >> Daniel > > These are the files : > > 5732255d4617d98b76bbbc116d331d6ac89906fa212969eb8213fdc4aea86451 166M ast2500-default-515-obmc.tar.gz > 2768e2526bdd3f928df31341801cb6de3b9a40ca942b538a3d0800cd26fbdbfe 166M ast2500-default-obmc.tar.gz > ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 1.1G ast2600-default-515-obmc.tar.gz > 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 1.2G ast2600-default-obmc.tar.gz > 4f8778be176ece1b57d33c4aee13bb989be114c3e4703150eaeb6f996bd5587f 582M ast2700-a1-dcscm-obmc.tar.gz > d5ceed511cd0dfefbb102fff2d731159e0472948a28066dc0d90bcd54be76525 520M ast2700-a1-obmc.tar.gz > 0e93f7976139da71fab9df7952a58bdd80650e23e7abf5853b0eb6695deb02d0 581M ast2700-dcscm-obmc.tar.gz > e2b8f043fe8063dd3b6ded93422e38bd41914dc9c3202199507652df024de4dc 519M ast2700-default-obmc.tar.gz The image size for v09.08 was around 250 MB for the ast2500, ast2600 and ast2700 SoCs. It would be best to keep it like this for testing. Would it be possible in v12.00 ? Thanks, C.
On Mon, 16 Feb 2026 at 14:59, Daniel P. Berrangé <berrange@redhat.com> wrote: > > On Mon, Feb 16, 2026 at 11:17:38AM +0000, Peter Maydell wrote: > > Followup: we have six test assets that are over 500MB in size, > > and they are all aspeed tests. Please can you have a look at > > slimming these down? > > I see 2 big assets from aspeed only > > 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 > ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 > > > what are the names of the other files in $HOME/.cache/qemu/download > you have that are over 500 MB ? -r--r----- 1 pm215 pm215 519M Feb 16 11:07 e2b8f043fe8063dd3b6ded93422e38bd41914dc9c3202199507652df024de4dc -r--r----- 1 pm215 pm215 520M Feb 5 15:57 d5ceed511cd0dfefbb102fff2d731159e0472948a28066dc0d90bcd54be76525 -r--r----- 1 pm215 pm215 581M Feb 16 11:15 0e93f7976139da71fab9df7952a58bdd80650e23e7abf5853b0eb6695deb02d0 -r--r----- 1 pm215 pm215 582M Feb 5 15:59 4f8778be176ece1b57d33c4aee13bb989be114c3e4703150eaeb6f996bd5587f -r--r----- 1 pm215 pm215 1.1G Feb 16 11:11 ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6 -r--r----- 1 pm215 pm215 1.2G Feb 5 16:02 64d8926a7d01b649168be96c986603b5690f06391286c438a3a772c8c7039e93 All these hash values turn up in tests/functional/arm/test_aspeed_* so they're not stale leftovers. thanks -- PMM
+Jamin, On 2/16/26 12:17, Peter Maydell wrote: > On Mon, 16 Feb 2026 at 11:13, Peter Maydell <peter.maydell@linaro.org> wrote: >> >> On Thu, 12 Feb 2026 at 21:42, Cédric Le Goater <clg@redhat.com> wrote: >>> >>> Add functional tests for AST2500 and AST2600 machines using the >>> OpenBMC SDK v11.00 with Linux kernel 5.15. These tests complement the >>> existing SDK tests and verify that QEMU correctly boots older kernel >>> versions on these platforms. >> >> >>> + ASSET_SDK_V1100_AST2600_515 = Asset( >>> + 'https://github.com/AspeedTech-BMC/openbmc/releases/download/v11.00/ast2600-default-515-obmc.tar.gz', >>> + 'ece1a934095378929780f03e7d092e562f4b33b2841b80ad7c3d12a85744c0f6') >> >> This asset file is over a gigabyte in size, it takes forever to >> download, and our functional test asset download framework has >> no mechanism for giving any kind of progress indication for >> downloads (or even for telling you the URL it is downloading >> until after the download is complete). >> >> Can we have a size limit for test assets please, at least until >> the framework can support large assets a bit better ? > > Followup: we have six test assets that are over 500MB in size, > and they are all aspeed tests. Please can you have a look at > slimming these down? Yes. There has been a considerable increase in size over the last 6m. Thanks, C.
© 2016 - 2026 Red Hat, Inc.