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
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
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
> -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:
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
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
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
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
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
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
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
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
16 matches
Mail list logo
