Unable to read SE info: Se05x_GetInfo fails

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

Unable to read SE info: Se05x_GetInfo fails

1,706 Views
Riz
Contributor III

Hi @Kan_Li , Hi @michaelsalfer 
The Se05x_GetInfo fails with below error.

smCom :ERROR:Can not select Applet=SE050:C'
smCom :ERROR:Failed (SW_FILE_NOT_FOUND) selecting Applet.  (Len=16)
      A0 00 00 03    96 54 53 00    00 00 01 03    00 00 00 00
sss   :ERROR:SM_I2CConnect Failed. Status 6A82
App   :ERROR:sss_session_open failed
App   :ERROR:ex_sss_session_open Failed
smCom :ERROR: phNxpEse_Transceive ESE Not Initialized
smCom :ERROR: Transcive Failed
App   :ERROR:Could not select ISD.
App   :ERROR:se05x_GetInfoPlainApplet Example Failed !!!...
App   :ERROR:ex_sss_entry Failed

 

Briefly checking the code, I could see the error originated from here (sm_connect.c).
Not sure what the comment "// Applet can not be selected (most likely it is simply not installed)" really means here.

Any hints?

if (sw == SW_FILE_NOT_FOUND) {
// Applet can not be selected (most likely it is simply not installed)
LOG_E("Can not select Applet=%s'", SE_NAME);
LOG_MAU8_E("Failed (SW_FILE_NOT_FOUND) selecting Applet. ", appletName, APPLET_NAME_LEN);
return sw;
}
else if (sw != SW_OK) {
LOG_E("SM_CONNECT Failed.");
sw = ERR_CONNECT_SELECT_FAILED;
}

Labels (1)
10 Replies

1,668 Views
vishwanchandapu
Contributor III

Hi Kan,

This is on Linux platform and chip is SE050C.

Regards

Vishwa

1,632 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @vishwanchandapu ,

 

Thanks for the information! May I have the MW cmake configuration on the Linux platform? You may run "cmake . -L" in the building folder to have such info.

 

Thanks for your patience!

 

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.
-------------------------------------------------------------------------------

1,598 Views
vishwanchandapu
Contributor III

PAHO_BUILD_DEB_PACKAGE:BOOL=FALSE
PAHO_BUILD_DOCUMENTATION:BOOL=FALSE
PAHO_BUILD_SAMPLES:BOOL=FALSE
PAHO_BUILD_SHARED:BOOL=FALSE
PAHO_BUILD_STATIC:BOOL=TRUE
PAHO_ENABLE_CPACK:BOOL=TRUE
PAHO_ENABLE_TESTING:BOOL=FALSE
PAHO_WITH_SSL:BOOL=TRUE
PTMW_A71CH_AUTH:STRING=None
PTMW_Applet:STRING=SE05X_C
PTMW_FIPS:STRING=None
PTMW_Host:STRING=iMXLinux
PTMW_HostCrypto:STRING=OPENSSL
PTMW_Log:STRING=Silent
PTMW_OpenSSL:STRING=1_1_1
PTMW_RTOS:STRING=Default
PTMW_SBL:STRING=None
PTMW_SCP:STRING=SCP03_SSS
PTMW_SE05X_Auth:STRING=None
PTMW_SE05X_Ver:STRING=03_XX
PTMW_SMCOM:STRING=T1oI2C
PTMW_mbedTLS_ALT:STRING=None
PYTHON_EXECUTABLE:PATH=/usr/bin/python3
Python3_EXECUTABLE:PATH=/usr/bin/python3
Python_EXECUTABLE:PATH=/usr/bin/python3
SSSFTR_SE05X_AES:BOOL=ON
SSSFTR_SE05X_AuthECKey:BOOL=ON
SSSFTR_SE05X_AuthSession:BOOL=ON
SSSFTR_SE05X_CREATE_DELETE_CRYPTOOBJ:BOOL=ON
SSSFTR_SE05X_ECC:BOOL=ON
SSSFTR_SE05X_KEY_GET:BOOL=ON
SSSFTR_SE05X_KEY_SET:BOOL=ON
SSSFTR_SE05X_RSA:BOOL=ON
SSSFTR_SW_AES:BOOL=ON
SSSFTR_SW_ECC:BOOL=ON
SSSFTR_SW_KEY_GET:BOOL=ON
SSSFTR_SW_KEY_SET:BOOL=ON
SSSFTR_SW_RSA:BOOL=ON
SSSFTR_SW_TESTCOUNTERPART:BOOL=ON
WithAccessMgr_UnixSocket:BOOL=OFF
WithCodeCoverage:BOOL=OFF
WithExtCustomerTPMCode:BOOL=OFF
WithNXPNFCRdLib:BOOL=OFF
WithOPCUA_open62541:BOOL=OFF
WithSharedLIB:BOOL=OFF

 

Please find the cmake configuration and let me know if any thing required.

Regards

Vishwaa

Tags (1)

1,581 Views
vishwanchandapu
Contributor III

@Kan_Li 

Can this be an issue of Applet not being installed at production?

 

Regards

Vishwa

 

 

 

1,552 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @vishwanchandapu ,

 

Actually I could only imagine this on SE051P, which comes out without any IoT Applet preinstalled. But later on even the card manager select failed. That is also quite strange. I think I would like to see a debug log with more info on the communication. Is it possible to have the cmake option "-DPTMW_Log=Verbose" in your building?

 

And I would like to know if this happens just on one sample or if it happened suddenly, does the error stay when using another board or after unpowering the IC?

 

Please kindly clarify.

 

Thanks for your patience!

 

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.
-------------------------------------------------------------------------------

1,543 Views
Riz
Contributor III

Hi @Kan_Li 

Small correction, the Chip indeed is a SE051C and not SE050C. Sorry for confusion.

 

According to the documentation, The Se05x_GetInfo should work with or without the applet installed.

However, the Se05x_GetInfo still failed. Do you know why this is?

Riz_0-1688622941453.png

We are suspecting an error during "applet upgrade" might have resulted in a corrupted applet or something which eventually causes failure in card manager selection.

Could this be a culprit?

Below is the chronology of what happened until now:

  • We observed Se05x_GetInfo fails with "Can not select applet" error as reported earlier.
  • Upgrade status with : sems_lite_cli_app --checkUpgradeProgress returned "1".
  • A rerun of the applet-upgrade recovered the chip.

1,535 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @Riz ,

 

A failed applet upgrade might lead to such kind of issue, but in case of a torn applet update on SE051 simply the same script needs to be run again. It will again install the applet and recover the backed up data. Did you do this already? Please also make sure the applet update file matches the product you want to apply, depending on the OEF ID.

 

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.
-------------------------------------------------------------------------------

0 Kudos

1,528 Views
vishwaec08
Contributor I

Hi Kan,

We were able to recover by running same script. 

Ideally as you mentioned get info should work without applet.

we looked into code the API "GP_Select" is failing.
  

App :INFO :No IoT applet found
smCom :ERROR: phNxpEse_Transceive ESE Not Initialized
smCom :ERROR: Transcive Failed
App :ERROR:Could not select ISD.

With Regards
Vishwa

0 Kudos

1,515 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @vishwaec08 ,

 

Is it possible to have the cmake option "-DPTMW_Log=Verbose" in your building? so we may have the full log starting from the beginning.

 

And I would like to know if this happens just on one sample or if it happened suddenly, does the error stay when using another board or after unpowering the IC?

 

Would you please clarify?

 

Thanks for your patience!

 

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.
-------------------------------------------------------------------------------

1,675 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @Riz ,

 

May I have the info regarding the platform you run the demo on? Thanks for your patience!

 

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.
-------------------------------------------------------------------------------

0 Kudos