Build failed on BSP40 with enabling secboot feature.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Build failed on BSP40 with enabling secboot feature.

Jump to solution
614 Views
Jeff-CF-Huang
Contributor II

Hi Sir

I enable secboot feature like this.

DISTRO_FEATURES:append = " pfe hse secboot"

I encountered a build error.

Could you help me check it?

JeffCFHuang_0-1714989533384.png

 

0 Kudos
Reply
1 Solution
567 Views
chenyin_h
NXP Employee
NXP Employee

Hello, thanks for the reply.

If you do not want to remove corresponding 3 files mentioned from previous post, the following method may also be useful, add the following line to conf/local.conf, then rebuild:

PREFERRED_VERSION_arm-trusted-firmware-tools-native = "2.5"

 

Hope it helps.

 

Best Regards

Chenyin

View solution in original post

3 Replies
568 Views
chenyin_h
NXP Employee
NXP Employee

Hello, thanks for the reply.

If you do not want to remove corresponding 3 files mentioned from previous post, the following method may also be useful, add the following line to conf/local.conf, then rebuild:

PREFERRED_VERSION_arm-trusted-firmware-tools-native = "2.5"

 

Hope it helps.

 

Best Regards

Chenyin

593 Views
chenyin_h
NXP Employee
NXP Employee

Hello, Thanks for the question

  1. To enable SECBoot Support, update the conf/local.conf file in the Yocto build directory with these lines:

DISTRO_FEATURES:append = " secboot"

NXP_FIRMWARE_LOCAL_DIR = "/path/to/firmware/folder"

Enabling HSE Secure Boot in the conf/local.conf file will automatically enable PKCS11 Support & HSE Linux Driver as well. You may not need to add additional “hse” here.

  1. For the building error, since only TF-A 2.5 is used in BSP40, you may temporally remove the TF-A 2.10 related files under sources/meta-alb/recipes-bsp/arm-trusted-firmware/ as a workaround.

Hope it helps.

 

Best Regards

Chenyin

0 Kudos
Reply
591 Views
Jeff-CF-Huang
Contributor II

Hi Sir,
Can TF-A 2.10 be disregarded without being deleted?

0 Kudos
Reply