Secure Provisioning Tool - Build image error

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

Secure Provisioning Tool - Build image error

Jump to solution
408 Views
Abhay2080
Contributor III

Hi i am trying to sign a package using SPT.

I have one binary that have FCFB + DCD + IVT + app.bin (a complete bootable image) and when i tried to sign it it is succesfull.

 

But when i am selecting a binary that only have IVT and app.bin why Build Image is disabled ?? I have attached the screen shot also.

0 Kudos
Reply
1 Solution
317 Views
Pablo_Ramos
NXP Employee
NXP Employee

Hi @Abhay2080,

I ran some tests with Secure Provisioning Tool v26.09 using the binary you shared and noticed the following:

According to Section 5.2.2, Source Image Formats of the Secure Provisioning Tool User Guide v26.09 the entry point can be specified explicitly for S19 files. For other image formats, the entry point is retrieved from the interrupt vector table (so the interrupt vector table must be at the beginning of the application image).

In the case of the image without an IVT and FCFB, the tool detects the entry point at 0x601006C9, which is outside the application code range. Additionally, the start address is expected to be within the range 0x600D2D01 to 0x601006C9.

Secure Provisioning Tool locates the entry point at offset 0x4 within the application image.

Could you please test whether changing the entry point to a valid address allows you to build the image successfully?

Best Regards,
Pablo

View solution in original post

4 Replies
330 Views
Abhay2080
Contributor III

I have attached the image now. Please check

0 Kudos
Reply
318 Views
Pablo_Ramos
NXP Employee
NXP Employee

Hi @Abhay2080,

I ran some tests with Secure Provisioning Tool v26.09 using the binary you shared and noticed the following:

According to Section 5.2.2, Source Image Formats of the Secure Provisioning Tool User Guide v26.09 the entry point can be specified explicitly for S19 files. For other image formats, the entry point is retrieved from the interrupt vector table (so the interrupt vector table must be at the beginning of the application image).

In the case of the image without an IVT and FCFB, the tool detects the entry point at 0x601006C9, which is outside the application code range. Additionally, the start address is expected to be within the range 0x600D2D01 to 0x601006C9.

Secure Provisioning Tool locates the entry point at offset 0x4 within the application image.

Could you please test whether changing the entry point to a valid address allows you to build the image successfully?

Best Regards,
Pablo

311 Views
Abhay2080
Contributor III
Yes it worked ..Thankyou
0 Kudos
Reply
369 Views
Pablo_Ramos
NXP Employee
NXP Employee

Hi @Abhay2080,

Could you share which version of the Secure Provisioning Tool you are using?

Additionally, I'm unable to see the image you mentioned in your attachment. Could you please try uploading it again?

Best Regards,
Pablo

0 Kudos
Reply