Wrong mfg package version exported?

[DBS_LC]

I am using Secure Provisioning Tool v8. 

When I export an unsigned, open/HAB disabled manufacturing package (zip) for MIMXRT1020 and then try to import that into the same SEC v8, the tool complains the zip is for v7 and will not load it.

I am able to load it into SEC v7 and it works fine there. It is only SEC 8 that fails to ingest the file that it created. 

[DBS_LC]

It appears that the first export really thinks it was v7...

I am sure I was using v8 to generate the mfg package but since I have both installed, it is conceivable I was using the wrong one. I will try this again right now...

Steps as best as I could remember from before seemed to work ok for re-import case. Possibly user error...

• Open SEC v8.
• New workspace (imxrt1020) [unsigned, flexspi nor simplified, open/hab disabled]
• select hex; do not replace FCB
• build image
• write image tab / create mfg pkg
  • ok insecure
  • update write script
  • save zip
• Leaving SEC v8 open, try to import - SUCCESS

At this point, I think I must have been using V7 without realizing it. My manufacturing group has v7, so I have both installed on my development station.

[marek-trmac]

Hi Daniel,

the manufacturing package can be imported only in the same version, where it was exported. So if you have manufacturing package for SEC v7, it can be used only in SEC v7. And if you create package in SEC v8, it can be used only in SEC v8.

The reason is, there might be some new features supported and we cannot guarantee compatibility of new features. We think it is good practice to use same version, where the manufacturing package was designed and tested at OEM site.

The saving workspace should not affect the content of the manufacturing package. Can you compare the ZIP file and let us know the difference? Or provide step-by-step procedure how to reproduce the problem, so we can investigate and fix it?

Thank you

[DBS_LC]

I think I figured it out... evidently I exported the mfg package BEFORE saving the workspace, which while legal, seems to have omitted something important. After saving the workspace in V8 and re-exporting the mfg package, I was able to import it back into v8.