Secure Authentication中的主题 Re: Failure in Se05x_API_SessionOpen on SE052F (Raspberry Pi I2C Communication Issue)

Failure in Se05x_API_SessionOpen on SE052F (Raspberry Pi I2C Communication Issue)

krsuresh — Wed, 03 Dec 2025 03:25:46 GMT

Hi Team,

I am facing an issue while trying to communicate with the SE052F over I2C using the Plug & Trust Nano Package.
According to the AN14277 application note, I configured the SCP03 keys as follows:

ENC Key: 3ae441c747e32ebc16b3bb2d843c6dd8
MAC Key: 6c18f3d08fee1cb96a3c8de5d3538aaa

However, Se05x_API_SessionOpen consistently fails.

System Information
Platform: Raspberry Pi
Package: Plug and Trust Nano Package v1.5.4
Example used: ex_se05x_GetInfo

Log Details:

./ex_se05x_GetInfo
Se05x Getinfo Example !
Plug and Trust nano package - version: 1.5.4
I2C driver supports plain i2c-level commands.
APDU Tx> :00 a4 04 00 0b d2 76 00 00 85 30 4a 43 4f 90 03 00
Failed writing data (nrWritten=-1).
Se05x_API_SessionOpen failedError in Se05x_API_SessionOpen
SE05x Getinfo Example Failed !

I2C Detect details in Raspberry Pi:
flexxon@raspberrypi:~/SE050/NEW-NANO/se052f/nano-package/examples/se05x_GetInfo/linux/build $ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Thanks,

Sureshkumar R

Re: Failure in Se05x_API_SessionOpen on SE052F (Raspberry Pi I2C Communication Issue)

Kan_Li — Wed, 03 Dec 2025 07:52:33 GMT

Hi @krsuresh ,

Since you are testing this on Raspberry Pi , did you also test with the full version of MW? Did it work anyway? Please kindly clarify.

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

Re: Failure in Se05x_API_SessionOpen on SE052F (Raspberry Pi I2C Communication Issue)

krsuresh — Wed, 03 Dec 2025 08:44:29 GMT

Hi @Kan_Li,

Thanks for the quick response.

I used the following configuration during the simw_top build, and while se05x_GetInfo runs successfully, se05x_Minimal fails; the log is provided below.

PTMW_ Applet = SE05X_C
PTMW_ FIPS = None
PTMW_ SE05X_ Ver = 03_XX
PTMW_SE05X_Auth = PlatfSCP03
PTMW_ SCP = SCP03_SSS
SSSFTR_ SE05X_ RSA = disable/enable

./se05x_GetInfo
Failed to export Enable pin : Invalid argument
Failed to open GPIO value file : No such file or directory
Failed to unexport GPIO : Invalid argument
App :INFO :Running ./se05x_GetInfo
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 :PlugAndTrust_v04.07.01_20250519
sss :INFO :atr (Len=35)
01 A0 00 00 03 96 04 03 E8 00 FE 02 0B 03 E8 00
01 00 00 00 00 64 13 88 0A 00 65 53 45 30 35 31
00 00 00
App :WARN :#####################################################
App :INFO :uid (Len=18)
04 00 50 01 39 97 7A C3 BF 57 52 04 26 1F 32 0A
1D 90
App :INFO :Running ./se05x_GetInfo
App :INFO :If you want to over-ride the selection, use ENV=EX_SSS_BOOT_SSS_PORT or pass in command line arguments.
sss :INFO :atr (Len=35)
01 A0 00 00 03 96 04 03 E8 00 FE 02 0B 03 E8 00
01 00 00 00 00 64 13 88 0A 00 65 53 45 30 35 31
00 00 00
sss :INFO :Newer version of Applet Found
sss :INFO :Compiled for 0x70200. Got newer 0x70216
sss :WARN :Communication channel is Plain.
sss :WARN :!!!Not recommended for production use.!!!
App :WARN :#####################################################
App :INFO :Applet Major = 7
App :INFO :Applet Minor = 2
App :INFO :Applet patch = 22
App :INFO :AppletConfig = 26F2
App :INFO :With ECDSA_ECDH_ECDHE
App :INFO :WithOut EDDSA
App :INFO :WithOut DH_MONT
App :INFO :With HMAC
App :INFO :With RSA_PLAIN
App :INFO :With RSA_CRT
App :INFO :With AES
App :INFO :WithOut DES
App :INFO :With PBKDF
App :INFO :With TLS
App :INFO :WithOut MIFARE
App :INFO :With I2CM
App :INFO :Internal = FFFF
App :WARN :#####################################################
App :INFO :Tag value - proprietary data 0xFE = 0xFE
App :INFO :Length of following data 0x45 = 0x4F
App :INFO :Tag card identification data (Len=2)
DF 28
App :INFO :Length of card identification data = 0x4C
App :INFO :Tag configuration ID (Must be 0x01) = 0x01
App :INFO :Configuration ID (Len=12)
00 05 B5 01 1B 7D B8 1B 89 99 D0 5D
App :INFO :OEF ID (Len=2)
B5 01
App :INFO :Tag patch ID (Must be 0x02) = 0x02
App :INFO :Patch ID (Len=8)
00 00 00 00 00 00 00 00
App :INFO :Tag platform build ID1 (Must be 0x03) = 0x03
App :INFO :Platform build ID (Len=24)
4A 33 52 36 30 30 30 33 37 33 31 38 31 32 30 30
6D 20 B6 19 7D 63 5E 7C
App :INFO :JCOP Platform ID = J3R6000373181200
App :INFO :Tag FIPS mode (Must be 0x05) = 0x05
App :INFO :FIPS mode var = 0x01
App :INFO :Tag pre-perso state (Must be 0x07) = 0x07
App :INFO :Bit mask of pre-perso state var = 0x00
App :INFO :Tag ROM ID (Must be 0x08) = 0x08
App :INFO :ROM ID (Len=8)
B3 37 5F E9 B5 50 8B C4
App :INFO :Tag JCOP OS Core ID (Must be 0x0A) = 0x0A
App :INFO :JCOP OS Core (Len=8)
55 60 6F D4 BE EC F3 CD
App :INFO :Status Word (SW) (Len=2)
90 00
App :INFO :se05x_GetInfoPlainApplet Example Success !!!...
App :WARN :#####################################################
App :INFO :cplc_data.IC_fabricator (Len=2)
47 90
App :INFO :cplc_data.IC_type1 (Len=2)
D6 00
App :INFO :cplc_data.Operating_system_identifier (Len=2)
47 00
App :INFO :cplc_data.Operating_system_release_date (Len=2)
00 00
App :INFO :cplc_data.Operating_system_release_level (Len=2)
00 00
App :INFO :cplc_data.IC_fabrication_date (Len=2)
41 02
App :INFO :cplc_data.IC_Serial_number (Len=4)
38 51 87 21
App :INFO :cplc_data.IC_Batch_identifier (Len=2)
02 67
App :INFO :cplc_data.IC_module_fabricator (Len=2)
00 00
App :INFO :cplc_data.IC_module_packaging_date (Len=2)
00 00
App :INFO :cplc_data.ICC_manufacturer (Len=2)
00 00
App :INFO :cplc_data.IC_embedding_date (Len=2)
00 00
App :INFO :cplc_data.IC_OS_initializer (Len=2)
19 26
App :INFO :cplc_data.IC_OS_initialization_date (Len=2)
1F 38
App :INFO :cplc_data.IC_OS_initialization_equipment (Len=4)
35 31 38 37
App :INFO :cplc_data.IC_personalizer (Len=2)
00 00
App :INFO :cplc_data.IC_personalization_date (Len=2)
00 00
App :INFO :cplc_data.IC_personalization_equipment_ID (Len=4)
00 00 00 00
App :INFO :cplc_data.SW (Len=2)
90 00
App :INFO :ex_sss Finished
Failed to open GPIO value file : No such file or directory
Failed to unexport GPIO : Invalid argument
Failed to unexport GPIO : Invalid argument

flexxon@raspberrypi:~/SD/simw-top_build/raspbian_native_se050_t1oi2c/bin $ ./se05x_Minimal
Failed to export Enable pin : Invalid argument
Failed to open GPIO value file : No such file or directory
Failed to unexport GPIO : Invalid argument
App :INFO :Running ./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 :PlugAndTrust_v04.07.01_20250519
sss :INFO :atr (Len=35)
01 A0 00 00 03 96 04 03 E8 00 FE 02 0B 03 E8 00
01 00 00 00 00 64 13 88 0A 00 65 53 45 30 35 31
00 00 00
sss :INFO :Newer version of Applet Found
sss :INFO :Compiled for 0x70200. Got newer 0x70216
sss :WARN :Communication channel is Plain.
sss :WARN :!!!Not recommended for production use.!!!
sss :WARN :nxEnsure:'ret == SM_OK' failed. At Line:7839 Function:sss_se05x_TXn
sss :WARN :APDU Transaction Error: Conditions not satisfied (0x6985)

App :ERROR:Se05x_API_GetFreeMemory Failed
App :INFO :mem=0
App :ERROR:se05x_Minimal Example Failed !!!...
App :INFO :ex_sss Finished
App :ERROR:ex_sss_entry Failed
App :ERROR:!ERROR! ret != 0.

Thanks,

Sureshkumar R

Re: Failure in Se05x_API_SessionOpen on SE052F (Raspberry Pi I2C Communication Issue)

Kan_Li — Thu, 04 Dec 2025 03:13:27 GMT

Hi @krsuresh ,

Did you really rebuild the MW with the following options?

PTMW_ SE05X_ Ver = 03_XX
PTMW_SE05X_Auth = PlatfSCP03

From the log, there are some conflicts:

sss :INFO :Compiled for 0x70200. Got newer 0x70216
sss :WARN :Communication channel is Plain.

Please kindly clarify.

Have a great day,
Kan

Re: Failure in Se05x_API_SessionOpen on SE052F (Raspberry Pi I2C Communication Issue)

krsuresh — Thu, 04 Dec 2025 03:37:30 GMT

Kan_Li — Thu, 22 Jan 2026 06:47:14 GMT

Hi @krsuresh ,

Have you tried a larger value instead? The MW has put this in plan, but the fix I would expect to be the next release.

Have a great day,
Kan

Re: Failure in Se05x_API_SessionOpen on SE052F (Raspberry Pi I2C Communication Issue)

Ben-FLX — Wed, 28 Jan 2026 04:17:46 GMT

@Kan_Li Do you know of any scheduled release that happens on regular interval in which we can expect this to be made available?

For e.g, within every quarter, or every Q1 & Q3?

If it is not something that is happening soon, then we need to know whether there is any possibility for a off-cycle release such that it does not affect our development activity.

Otherwise, we may have to consider other options such as going back to using SE050 (for our upcoming prototype build) and understand what it takes to migrate to SE052.

Re: Failure in Se05x_API_SessionOpen on SE052F (Raspberry Pi I2C Communication Issue)

Kan_Li — Fri, 30 Jan 2026 03:25:18 GMT

Hi @Ben-FLX ,

We could plan for a release on the end of Feb 2026 along with our Main Package Release. Does it align with your timeline?

Best Regards,

Kan

Re: Failure in Se05x_API_SessionOpen on SE052F (Raspberry Pi I2C Communication Issue)

Ben-FLX — Fri, 30 Jan 2026 07:48:56 GMT

Hi @Kan_Li

Yes, end feb works as long as we are able to execute all supported code/functions supplied by the package using SE052 eval board. Of course, the earlier this package can be made available, the better it is for us.

Lastly, what is a good way for us to be notified when the new package becomes available? I am not sure why I am not receiving email notifications here and I don't see myself refreshing NXP website on a daily basis to check for updates.

Re: Failure in Se05x_API_SessionOpen on SE052F (Raspberry Pi I2C Communication Issue)

Kan_Li — Fri, 30 Jan 2026 07:59:10 GMT

Hi @Ben-FLX ,

Thanks for the clarification! I will let the MW team know about this. and for notification, I think you may use the notify function from the github, as shown below:

and anyway, you may reach out to me here at anytime.

Have a great day,
Kan

Re: Failure in Se05x_API_SessionOpen on SE052F (Raspberry Pi I2C Communication Issue)

Ben-FLX — Tue, 24 Feb 2026 04:17:15 GMT

@Kan_Li Just wondering, any update/news about the planned code release? Is it progressing smoothly?