Hi @ajitsj3 ,
Thanks for the information! This is an expected result with SE051C2, as it has two OEF ids as shown in https://www.nxp.com/webapp/Download?colCode=AN12973 , so you have to manually confirm which default platform SCP03 keys should be used according to the OEF ID you get from the GetInfo demo. Please open the fsl_sss_ftr.h.in file which is located in: /simw-top/sss/inc. and enable the option for "A564" as below:
Then reconfigure the MW with cmake to generate a new "fsl_sss_ftr.h" in place and build it as well. You may have a result something like below:
Hope that makes sense,
Have a great day,
Kan
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
Hi @ajitsj3 ,
Thanks for the information! Actually I run this demo on Raspberry Pi platform just now, but no issue found.
App :INFO :PlugAndTrust_v04.02.00_20220524
App :INFO :Running bin/se05x_Minimal
App :INFO :If you want to over-ride the selection, use ENV=EX_SSS_BOOT_SSS_PORT or pass in command line arguments.
App :INFO :Using default PlatfSCP03 keys. You can use keys from file using ENV=EX_SSS_BOOT_SCP03_PATH
sss :INFO :atr (Len=35)
00 A0 00 00 03 96 04 03 E8 00 FE 02 0B 03 E8 08
01 00 00 00 00 64 00 00 0A 4A 43 4F 50 34 20 41
54 50 4F
App :INFO :mem=32767
App :WARN :If 32768 bytes or more bytes are available, 32767 bytes free is reported.
App :INFO :se05x_Minimal Example Success !!!...
App :INFO :ex_sss Finished
pi@raspberrypi:~/se05x_mw_v04.02.00_20220701_151557/
The only difference is I set PTMW_SE05X_Ver = 03_XX as I am using OM-SE050ARD, would you please tell me the OEF ID you got from the GetInfo demo? The value is something like below:
Most likely your issue is due to the platform SCP03 keys mismatch. so if we know the exact variant from the OEF ID, we may use EX_SSS_BOOT_SCP03_PATH to check if the PlatfSCP03 keys are the root cause. For example, create a similar text file as below:
echo ENC D2DB63E7A0A5AED72A6460C4DFDCAF64 > se050E_scp_keys.txt
echo MAC 738D5B798ED241B0B24768514BFBA95B >> se050E_scp_keys.txt
echo DEK 6702DAC30942B2C85E7F47B42CED4E7F >> se050E_scp_keys.txt
(The default platfscp03 keys as well as the OEF ID for each variant can be referred from https://www.nxp.com.cn/docs/en/application-note/AN12436.pdf .)
and define the environment variable EX_SSS_BOOT_SCP03_PATH something like below:
export EX_SSS_BOOT_SCP03_PATH=~/se_mw/simw-top_build/
raspbian_native_se050_t1oi2c/bin/se050E_scp_keys.txt
Hope that makes sense,
Have a great day,
Kan
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
From the document https://www.nxp.com/docs/en/application-note/AN13027.pdf I figured out that for OEFID value "A564" the se05x variant is "SE051C2" and we need to use the PTMW_SE05x_Ver=06_00 which is what even we have used. I have attached screenshot of the table for your reference. So please use the variant "SE051C2" at your and perform same tests.
I also could not find scp_keys for "SE051C2" variant. Please could you provide the same?
Thanks and regards
Ajit S J
Hi @ajitsj3 ,
Thanks for the information! This is an expected result with SE051C2, as it has two OEF ids as shown in https://www.nxp.com/webapp/Download?colCode=AN12973 , so you have to manually confirm which default platform SCP03 keys should be used according to the OEF ID you get from the GetInfo demo. Please open the fsl_sss_ftr.h.in file which is located in: /simw-top/sss/inc. and enable the option for "A564" as below:
Then reconfigure the MW with cmake to generate a new "fsl_sss_ftr.h" in place and build it as well. You may have a result something like below:
Hope that makes sense,
Have a great day,
Kan
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
