Dear All,
I am currently using the MCUX Secure Provisioning Tool v25.06 to generate a manufacturing package for an i.MX RT1052 device.
The package is successfully created and works correctly on the same PC where it was generated. However, when I try to use the same manufacturing package on a different computer, the provisioning process fails because several directory paths are not found.
It seems that the exported package contains absolute file paths instead of relative ones, and the required files are not automatically included inside the .zip package.
As a result, the package is not portable between different environments or PCs.
Could you please confirm if this is the expected behavior in version 25.06, or if there is an option to export a fully self-contained (portable) manufacturing package that includes all dependencies and uses relative paths?
If not, is there a recommended procedure or update to make the generated package portable?
Thank you in advance for your help and clarification.
Best regards,
Fabio Rossi
Hi @fabiorossi ,
the manufacturing package should be portable. The script uses environment variable to access tool path, if the tool is installed in different directory, see SPT_INSTALL_BIN.
Info the tool documentation: Generic workflows — MCUXpresso Secure Provisioning Tool 25.06
Note: manufacturing package can be installed only to the same tool version, that was used to create the package.