> From: Jamin Lin
> Sent: Wednesday, December 11, 2024 10:35 AM
> To: openembedded-core@lists.openembedded.org
> Cc: Troy Lee ; Jamin Lin
>
> Subject: [PATCH v5 0/3] uboot-sign: support ATF and TFE ITS generation
>
> v0:
> 1. add variable to set load address and entrypoint.
> 2. Fix to insta
Hi Adrian, Ross
I resend v5 patch series here,
https://patchwork.yoctoproject.org/project/oe-core/cover/20241211023515.2108415-1-jamin_...@aspeedtech.com/
Thanks-Jamin
> Subject: RE: [OE-core] [PATCH v4 0/3] uboot-sign: support ATF and TFE ITS
> generation
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: Yo
Currently, uboot-sign.bbclass only supports to create Image Tree Source(ITS)
for "u-boot" and "flat_dt". However, users may want to add their private
images into u-boot FIT image for specific application and purpose.
To make this bbclass more flexible and support to add users specific snippet
ITS,
Currently, uboot-sign.bbclass only supports to create Image Tree Source(ITS)
for "u-boot" and "flat_dt". However, users may want to support multiple images
such as ARM Trusted Firmware(ATF), Trusted Execution Environment(TEE) and
users private images for specific application and purpose.
To make
Add "test_uboot_atf_tee_fit_image" test caste to check u-boot FIT image and
Image Tree Source(ITS) are built and the ITS has the correct fields.
Add "test_sign_standalone_uboot_atf_tee_fit_image" test case to check if u-boot
FIT image and Image Tree Source (ITS) are created and signed correctly fo
v0:
1. add variable to set load address and entrypoint.
2. Fix to install nonexistent dtb file.
3. support to verify signed FIT
4. support to load optee-os and TFA images
v1:
Fix patch for code review
v2:
created a series patch
v3:
add cover letter
v4:
Add oe-self testcases for revi
n Environment";
> data = /incbin/("tee-raw.bin");
> type = "tee";
> arch = "";
> os = "tee";
> load = <0xb008>;
> entry = <0xb008>;
> compression =
ule.
> > https://github.com/russhousley/pyhsslms
> > https://github.com/russhousley/pyhsslms/blob/master/README.md
> >
> > Thanks-Jamin
> >
> > > Subject: Re: [OE-core] [PATCH v1] python3-pyhsslms: Add 2.0.0 recipe
> > >
> > > Hello,
> > >
tests
> that ensure it works?
>
> Alex
>
> On Mon, 9 Dec 2024 at 09:41, Jamin Lin via lists.openembedded.org
> wrote:
> >
> > This recipe was placed in meta-arm meta layer,
> > https://git.yoctoproject.org/meta-arm/tree/meta-arm/recipes-devtools/p
> > y
This recipe was placed in meta-arm meta layer,
https://git.yoctoproject.org/meta-arm/tree/meta-arm/recipes-devtools/python/python3-pyhsslms_2.0.0.bb
However, users may want to build this python module but do not want to add
"meta-arm" layer. To make this recipe more flexible, move this recipe from
arch = "arm";
os = "zephyr";
load = <0xb200>;
entry = <0xb200>;
compression = "none";
};
tspfw {
description = "TSP Firmware";
data = /incbin/("ast2
Then, users set “USER_XXX” variables to create their own ITS file for
u-boot/kernel FIT image generation.
Or can you give me any suggestion about your goal and ITS improvement?
Thanks-Jamin
> Cheers,
> Ross
>
>
> > On 18 Nov 2024, at 06:32, Jamin Lin via lists.openembedded.o
Linux kernel supports to compress its output binary with lzma algorithm and
U-Boot support to decompress lzma compressed image.
Both xz and lzma algorithms are identical and users can use xz utility with
format parameter to compress Image which supports lzma algorithm.
Add the following command t
Currently, uboot-sign.bbclass only supports to create Image Tree Source(ITS)
for "u-boot" and "flat_dt". However, users may want to support multiple images
such as ARM Trusted Firmware(ATF), Trusted Execution Environment(TEE) and
users private images for specific application and purpose.
To make
v0:
1. add variable to set load address and entrypoint.
2. Fix to install nonexistent dtb file.
3. support to verify signed FIT
4. support to load optee-os and TFA images
v1:
Fix patch for code review
v2:
created a series patch
v3:
add cover letter
v4:
Add oe-self testcases for revi
Currently, uboot-sign.bbclass only supports to create Image Tree Source(ITS)
for "u-boot" and "flat_dt". However, users may want to support their private
images for specific application and purpose.
To make this bbclass more flexible and support users specific ITS, creates new
"uboot_fitimage_user
Add "test_uboot_atf_tee_fit_image" test caste to check u-boot FIT image and
Image Tree Source(ITS) are built and the ITS has the correct fields.
Add "test_sign_standalone_uboot_atf_tee_fit_image" test case to check if u-boot
FIT image and Image Tree Source (ITS) are created and signed correctly fo
1444
Thanks-Jamin
> On 17/01/2024 10:10:51+0800, Jamin Lin via lists.openembedded.org wrote:
> > Currently, u-boot FIT image only support to load u-boot image.
> > To support optee-os and trusted-firmware-a, update ITS file generation
> > scripts, so users are able to use
Currently, u-boot FIT image only support to load u-boot image.
To support optee-os and trusted-firmware-a, update ITS file generation
scripts, so users are able to use u-boot FIT image to load
u-boot, optee-os and treustred-firmware-a images
Add a variable "UBOOT_FIT_ARM_TRUSTED_FIRMWARE_A" to
ena
Add to check dtb file exist, then install it.
Signed-off-by: Jamin Lin
---
meta/classes-recipe/uboot-sign.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/uboot-sign.bbclass
b/meta/classes-recipe/uboot-sign.bbclass
index abde0bc61c..4b462698f9 1
It does not verify the signed FIT image of kernel and uboot.
To catch the unexpected errors as far as possible at the build time,
add uboot-fit-check-sign tool which is provided by u-boot to
verify the signed FIT image.
Signed-off-by: Jamin Lin
---
meta/classes-recipe/uboot-config.bbclass | 3 +
According to the design of uboot-sign.bbclass and kernel-fitimage.bbclass,
both of them use an UBOOT_LOADADDRESS variable to set the load address of
kernel and u-boot image and use an UBOOT_ENTRYPOINT variable to set the entry
address of
kernel and u-boot image.
However, users may want to set the
> -Original Message-
> From: Tom Rini
> Sent: Wednesday, January 17, 2024 10:37 PM
> To: Jamin Lin
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [PATCH] uboot-sign: support to load optee-os and TFA images
>
> On Tue, Jan 16, 2024 at 07:37:04PM -0800, Jamin Lin wrote:
>
>
Hi Alexander,
One more thing, So far, bitman only support hash 256.
Thanks
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193885):
https://lists.openembedded.org/g/openembedded-core/message/193885
Mute This Topic: https://lists.openembedded.org/m
Currently, u-boot FIT image only support to load u-boot image.
To support optee-os and trusted-firmware-a, update ITS file generation
scripts, so users are able to use u-boot FIT image to load
u-boot, optee-os and treustred-firmware-a images
Add a variable "UBOOT_FIT_ARM_TRUSTED_FIRMWARE_A" to
ena
Yes, it is a typo and will fix it.
Thanks-Jamin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193882):
https://lists.openembedded.org/g/openembedded-core/message/193882
Mute This Topic: https://lists.openembedded.org/mt/103734859/21656
Group Owner
Hi Alexander,
Thanks for review.
I tested it in ASPEED AST2600 and AST2700 SOCs. Yoc can see our Github
repository here.
https://github.com/AspeedTech-BMC
You are right the latest version of u-boot(2024.01) support binman python tool
to create FIT image and support optee-os and trusted-firmwa
Currently, u-boot FIT image only support to load u-boot image.
To support optee-os and trusted-firmware-a, update ITS file generation
scripts, so users are able to use u-boot FIT image to load
u-boot, optee-os and treustred-firmware-a images
Add a variable "UBOOT_FIT_ARM_TRUSTED_FIRMWARE_A" to
ena
It does not verify the signed FIT image of kernel and uboot.
To catch the unexpected errors as far as possible at the build time,
add uboot-fit-check-sign tool which is provided by u-boot tools to
verify the signed FIT image.
Signed-off-by: Jamin Lin
---
meta/classes-recipe/uboot-config.bbclass
Add to check dtb file is exist, then install it.
Signed-off-by: Jamin Lin
---
meta/classes-recipe/uboot-sign.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/uboot-sign.bbclass
b/meta/classes-recipe/uboot-sign.bbclass
index ad04c82378..26d75995a
According to the design of uboot-sign.bbclass and kernel-fitimage.bbclass,
both of them use an UBOOT_LOADADDRESS variable to set the load address of
kernel and u-boot image and use an UBOOT_ENTRYPOINT to set the entry address of
kernel and u-boot image.
However, users may set the different load ad
Hi all,
I encountered the issue about do_create_spdx task and my descriptions as
following.
1. I have two target machines whcih are ast2700-default and ast2700-emmc,
respectively.
2. I have an appliction package call phosphor-logging.
I succesfully to build ast2700-emmc target machine and crea
Root Cause:
initial_revs is an empty dictionary and do not have "." key.
Traceback (most recent call last):
File "scripts/devtool", line 349, in
ret = main()
File "scripts/devtool", line 336, in main
ret = args.func(args, config, basepath, workspace)
File "scripts/lib/devtool/standa
33 matches
Mail list logo
