summaryrefslogtreecommitdiff
path: root/meta-phosphor/classes/image_types_phosphor_nuvoton_npcm8xx.bbclass
AgeCommit message (Collapse)AuthorFilesLines
2023-06-16meta-phosphor: npcm8xx.bbclass: sign images for TIP mode onlyTim Lee1-2/+2
For NO TIP mode there is no need for signatures at all. Expected result: | TIP_IMAGE = True | TIP_IMAGE = False | | SECURED_IMAGE = True | Need sign | No need sign | | SECURED_IMAGE = False | No need sign | No need sign Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: Ia48960732f9090f46f1944ee6bd51c1f0b121abe
2023-06-09meta-phosphor: npcm8xx.bbclass: support sign images featureTim Lee1-20/+124
Add sign images feature according customer's requirement. Set "SECURED_IMAGE" to "True" and enable sign images feature. When sign images feature be enabled. Use default keys to sign images if customer didn't point their own local keys path. Note: "SECURED_IMAGE" default is "True". Tested: Use default keys sign: That will use default path and keys from igps to sign. Use local keys sign: That will use local path and keys to sign. When KEY_FOLDER and KEY definition both are valid. However, when KEY_FOLDER and KEY definition are invalid either, that will output sign images failed then stop build full images. Tested: build pass and boot up successfully with signed Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: If2b793906ab338aec391062d9bfeae2b1e790078
2022-12-03meta-phosphor: npcm8xx.bbclass: change binary depends for do_pad_binaryTim Lee1-1/+1
Before do_pad_binary be exectued, those binaries need to be ready for padding. Otherwise there are errors about "No such file or directory" for those binaries. Tested: build pass and boot up successfully Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: I602ad0fdd95f207978b7dd2ed492ff7ef40573fb
2022-11-30meta-phosphor: npcm8xx.bbclass: pad binary in place for alignmentTim Lee1-0/+34
Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: I9bfe4ed6065c7f031bfd2bedc2c6eaedc7a5ee62
2022-11-01meta-phosphor: npcm8xx.bbclass: adjust each image alignment by its definitionTim Lee1-7/+7
Tested: buid pass and boot up successful when loading BB at 0x80000 for example Verified by bootblock log as below: ========== Load bootblock ========== tip_firmware_image_init fiu0 cs0 BOOTBLOCK tag U. scan from 0x80000000 to 0x88000000 tip_firmware_image_scan_flash BOOTBLOCK found addr 0x80080000 dst 0xfffd0000 Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: I62eced6d80b48d488348d43468f8f01edf83d79a
2022-09-27meta-phosphor: classes: npcm8xx: fix image-u-boot didn't include merged filesTim Lee1-1/+2
Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: I2d1ed130d2db71ba0ae4446a9380d7c9e8ad95fd
2022-09-27meta-nuvoton: add support to generate full flash image for npcm8xxTim Lee1-0/+128
Nuvoton's npcm8xx full flash image includes TIP FW, Bootblock, ATF, OPTEE and UBOOT with headers. Generating headers and merging images are being done by Nuvoton's binary generator tool (Bingo) which uses external parameters from XML files for that. Thus, we need to add related fitimage and image type for npcm8xx. However, before merge this commit, we must wait for below commits were merged. meta-nuvoton: arm-trusted-firmware: add arm trusted firmware recipe https://gerrit.openbmc.org/c/openbmc/openbmc/+/55234 meta-nuvoton: add npcm8xx-bootblock recipe https://gerrit.openbmc.org/c/openbmc/openbmc/+/55117 meta-nuvoton: add npcm8xx-igps recipe https://gerrit.openbmc.org/c/openbmc/openbmc/+/55099 meta-nuvoton: npcm7xx-bingo: upgrade latest version 0.0.5 support Arbel https://gerrit.openbmc.org/c/openbmc/openbmc/+/55128 Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: I4599e39d3873f07cde6904d0f10161964fc45c7a