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.
