Secure AuthenticationのトピックRe: I2C Communication between STM32 and SE050 - R-APDU body missing

I2C Communication between STM32 and SE050 - R-APDU body missing

genygbo — Wed, 26 Feb 2020 11:10:46 GMT

Hello team,

I'm performing an i2c communication between OM-SE050ARD (SE) and STM32F030R8 Nucleo (Master). I'm able to get the response. But whenever I perform an operation (say "Get_Version" or "Digest_OneShot"), I only get the Header part and the CRC as response. The actual response body is not displayed. My output is always seen as "A5, 90, 00, FB, E9". Is there any particular command I need to send for the actual response? Any leads would be much appreciated.

Thanks!

Elshadai

Re: Communication between STM32 and SE050 - Response data incomplete

Kan_Li — Thu, 27 Feb 2020 05:10:43 GMT

Do you have the trace data for a review?

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: Communication between STM32 and SE050 - Response data incomplete

genygbo — Thu, 27 Feb 2020 07:42:08 GMT

Hello Kan,

Thanks for the reply. Kindly find the attached response seen when I try to call 'Get Version'.

This is the response I get when I also call other functions like digest one shot etc. I'm able to see the R-APDU trailer in the response but I couldn't see the R-APDU body part. Please let me know if you require more information.

Many Thanks,

Elshadai

Re: Communication between STM32 and SE050 - Response data incomplete

genygbo — Thu, 27 Feb 2020 08:18:31 GMT

Hello Kan,

Please also find the T=1 block frame values for "Get version" below:

5A 20 08 8004002002410709 7306

Should I send any other values additional to this ?

Many Thanks,

Elshadai

Re: I2C Communication between STM32 and SE050 - R-APDU body missing

stephaniesmi606 — Fri, 28 Feb 2020 06:32:30 GMT

I am a bit concerned with the level shift observed at high level at the moment the I2C starts. Are you sure that you correctly configured GPIO as open drain in the PIO controller of the STM32 ? walgreenslistens

Re: I2C Communication between STM32 and SE050 - R-APDU body missing

Kan_Li — Fri, 28 Feb 2020 08:50:31 GMT

Hi Elshadai,

Thanks for the information! I can recognize Get Version command from the “80040020"， but what is the following "024107" for? From my understanding, this command should be "8004002009" according to the spec.

Have a great day,
Kan

Re: I2C Communication between STM32 and SE050 - R-APDU body missing

genygbo — Mon, 02 Nov 2020 14:34:35 GMT

Thanks for the clarification. I corrected my C-APDU commands as follows:

// for Version Info
uint8_t versionPacket[10] = {0x5A, // NAD
                             0x20, // PCB
                             0x05, // LEN
                             0x80, // CLA
                             0x04, // INS
                             0x00, // P1
                             0x20, // P2
                                   // Lc-?
                             0x09, // Le
                             0x66, // CRC1
                             0xAA  // CRC2 };‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I have 2 questions:

1. As per my understanding, Lc field is used for the length of the payload. In this case we do not have a payload. So shouldn't we write Lc = 0x00 ?

2. With the above values this is my trace and i only get 9000 but not the body. Before sending these commands I do a soft reset and read out the ATR bytes which works fine.

Really appreciate your help. Thanks!

Re: I2C Communication between STM32 and SE050 - R-APDU body missing

genygbo — Tue, 03 Mar 2020 07:37:18 GMT

Hi bukiw nci,

Thanks for the comment. The GPIO is configured as open drain in STM32. The i2c trasmission is acknowledged well. Although, my concern is that I couldn't see the R-APDU body in my output. Trying to figure out the missing data.

Re: I2C Communication between STM32 and SE050 - R-APDU body missing

Kan_Li — Tue, 03 Mar 2020 07:43:55 GMT

Hi Elshadai,

1. As per my understanding, Lc field is used for the length of the payload. In this case we do not have a payload. So shouldn't we write Lc = 0x00 ?

- Since no payload but Le is required, so you just need to specify Le here.

2. With the above values this is my trace and i only get 9000 but not the body. Before sending these commands I do a soft reset and read out the ATR bytes which works fine.

- Did you select the applet after ATR? Please kindly refer to 4.4 from https://www.nxp.com/docs/en/application-note/AN12413-SE050_APDU_specification.pdf for details.

Hope that helps,

Have a great day,
Kan

Re: I2C Communication between STM32 and SE050 - R-APDU body missing

genygbo — Tue, 03 Mar 2020 14:53:57 GMT

Hi Kan,

Thanks a lot for the clarification. I was missing the part of applet selection. I've included it and now, I'm able to get the R-APDU body.

Have a nice day !

Elshadai

Re: I2C Communication between STM32 and SE050 - R-APDU body missing

ronan_prezioso — Fri, 10 Jul 2020 15:43:18 GMT

Hello!

I am currently evaluating the SE050 and I am newbie on T=1 and APDU protocols.

I almost get the same problem of R-APDU body missing...

Like Elshadai, I try to get an answer to "Get_Version" command.

First, I send a T=1 interface soft reset request and get a correct ATR anwser.

Then, I send the applet selection command as indicate in 4.4:

- If I set the M bit of the PCB field of the I-Block to 0 (not chained), I get an Nack to my read address byte (0x91).

- If I set the M bit of the PCB field of the I-Block to 1 (chained), I get the R-APDU trailer (9000), but not the R-APDU body (Applet version) as expected.

I don't anderstand why I have to set this M bit to 1 to get answer, and why I can't get the R-APDU body?

Any leads would be much appreciated too!

Thanks in advance!

Ronan

Re: I2C Communication between STM32 and SE050 - R-APDU body missing

badhri_radhakri — Tue, 14 Jul 2020 10:49:37 GMT

Hi ronan.prezioso@swing.e-i.com,

For applet selection, try setting the sequence bit N(S) and the chaining bit M both to 0 of PCB. Please refer section 2.1.1.2.1 of UM11225.

Alternatively, you can use the functions in the Plug & Trust middleware library. You just need to set up the I2C functions according to your Master board.

Hope it helps!

Badhri

Re: I2C Communication between STM32 and SE050 - R-APDU body missing

ronan_prezioso — Wed, 15 Jul 2020 07:10:07 GMT

Hi Badhri,

Thank you!

I will try this as soon as possible.

Ronan

Re: I2C Communication between STM32 and SE050 - R-APDU body missing

ronan_prezioso — Wed, 15 Jul 2020 08:51:41 GMT

Hello,

I tried with N(s) and M both to 0.

First I got a NACK.

Then I added more delay between command and answer, and now, it works fine.

Thank for the help!

Ronan

Re: I2C Communication between STM32 and SE050 - R-APDU body missing

saireddy_saredd — Sun, 04 Jul 2021 18:29:30 GMT

Hallo Elshadai,

Kindly help on these two topics,

1. How acn you calculate the CRC1 and CRC2??

2. Can you share a piece of code how to send the applet selection ??

Regards,

Sai