how to use the EVSE setup without SE050

[Bay]

Hi currently I am doing the EVSE setup. 

The device status there: Provisioned. 

But in the serial terminal there display: Disconnected from IoTHub.

And also, I confuse the difference between EVSE setup without SE050 and with SE050. Can you explain more on this? Thanks

[Christine_Li]

Hi, @Bay 

Thanks for your interest of NXP EVSE solution.

Let me firstly explain the difference with and without SE050.
Credentials and critical information must be stored in a secure and protected place, to prevent malicious actor to steal or alter them. To solve this need, NXP provides the Edge Lock SE050 secure element IC, which performs cryptographic operations and provides a secure key and certificate store.  The SE050 does not only store credentials. It is also used to accelerate security operations as the security in the SE050 acts as an integral part of the overall security functionality.

After enrollment, you need to select authentication method:

#define EVSE_SAS_AUTH 1 //Means select Symmetric Key attestation 

#define EVSE_SAS_AUTH 0  //Means select X.509 certiticates

The advantages and disadvantages between SAS and X.509 certificate:

After select auth, then you need to select storage place:

#define EVSE_X509_SE050_AUTH 0

#define EVSE_X509 1 //Stored in I.MX RT106x NVM 

#define EVSE_X509_SE050_AUTH 1  //Securely stored in SE050.

#define EVSE_X509 0  

You can refer to  Section 5.1 Connection setup,  Figure 11, provides an overview of the connection setup of the EasyEVSE to your Azure IoT Central application in our NXP EasyEVSE EV Charging Station Development Platform User Manual.

For question 1, if you are not using SE050, you can refer to our User Manual section 5.1.2, X.509 from flash, which part give you a detailed reference about how to connect your device to IoT Central.

If still have question after referred our User Manual, please give me more detailed information about your setup, then we can discuss further.

Best regards,

Christine.

[Bay]

Here is my setting:

Why is the device status provisioned but my serial terminal is disconnected from IoT Hub?

[Bay]

I have copied the ID scope, device ID and primary key inside the IDE and build and debug.

Status is provisioned.

And in the serial terminal there 

Is it because of this?

[Christine_Li]

Hi，  @Bay 

Congratulations to your great job!

Yes, you are right.

As referred to 5.1.2 section in our User Manual, without the device ID, ID scope and authentication type information and updating source code, your actual device could not connect with the IOT Central.

Best regards,

Christine.

[Bay]

So, what is the reason of this: Disconnected from IoTHub! And how to solve it?

[Christine_Li]

Hi, @Bay 

Sorry for my misunderstanding. 

I thought you have connected successfully after modified device ID and scope information, and solved disconnected issue.

It seems that you still meet disconnection issue.

From the prompt window, we see that IOT hub and DPS are updating their TLS certificates with a new Microsoft Certificate Authority chained under a new CA root - DigiCert Global G2 Root.

Can you please click the "Here" link  to know the details or copy this link to me to have a check further?

I never met this issue before. 

Best regards,

Christine.

[Bay]

The prompt window is at the top of the page.

Here is the link: Azure IoT TLS: Critical changes are almost here! (…and why you should care) - Microsoft Community Hu...

[Christine_Li]

Hi, @Bay 

Thanks for your information.

I checked the link, and the latest modification was Updated June 21, 2023 - No longer accepting extension requests for IoT Hub. Only IoT Central apps can now request for extensions.

I remember I tested in Sep,2023, it worked well. So this prompt may have no relationship with disconnection issue.

May I ask which Board (RT1060 or RT1064) and which SDK version are you using? 

And how about: Metering Board, NFC Board,Display Panel, and Wi-Fi Module setup?

I prefer to have a test on my local side and check whether have same issue on my side.

Best regards,

Christine.

[Bay]

I am using RT1064, SDK 2.14.0

Everything is work just cannot connect to Iot Hub.

Can read the NFC card, can connect to wifi, when I press SW1 in metering board, LCD panel there will also change the State A, B,C and so on. 

[Christine_Li]

Hi, @Bay 

Thanks for your quick reply.

If everything is ok except connecting to IoT Hub, the issue may from Microsoft Azure cloud or network.

Anyway, let me have a try on my local side and will update to you once I have any progress.

Best regards,

Christine.

[Christine_Li]

Hi, @Bay 

Can you please have a try with X.509 stored in I.MX RT106x NVM?

EVSE_X509_AUTH 1
EVSE_X509_SE050_AUTH 0
EVSE_SAS_AUTH 0

And also need to change the source code and IoT cloud ID device, scope, and certification, authentication information.

Best regards,

Christine.

[Bay]

Error when build the project.

Can you teach step by step as I not sure where need to change in code or azure iot central

[Christine_Li]

Hi, @Bay 

About how to use X.509 from flash, we have step by step references including how to update source code in our User Manual, Section:5.1.2, page 22.

I will also follow this guide to setup my test environment. 

Today I will start to setup on my local side.

Best regards,

Christine.

[Bay]

Can you try for this setting first and update me whether you are getting same error as mine or can successfully connect to IoT Hub.

EVSE_X509_AUTH 0
EVSE_X509_SE050_AUTH 0
EVSE_SAS_AUTH 1

[Christine_Li]

Hi, @Bay 

Sure, that is what I will do today. It is my today's plan.

Just I have some other things to deal with and meetings, so I may need some time to share my results.

Once have any updates, I will keep you posted.

Best regards,

Christine.

[Christine_Li · Accepted solution]

Hi, @Bay 

I reproduced your issue and asked our expert AE team about the reason.

The answer is: 

This is caused by a certificate from the Azure IoT Hub.

We have a new version of the Software package that solves this issue.

May I ask where do you get the software package?  

If from our local FAE, you may ask him to get a new software package.

And I am also trying to figure out which detailed part of our source code to resolve this issue. But it may need some time.

Best regards,

Christine.

[Bay]

Hi Christine,

Thanks for your update.

I will contact NXP local FAE to get a new software package. Thanks for your time.

[Christine_Li]

Hi, @Bay 

Thanks for your reply.

Yes, please ask our local FAE for new source package. I tried with the new source package, it won't have this error.

Do you have any queries on this case? 

If no, would you mind help to close this thread by clicking on "Solved"?

Thanks for your corporation and have a nice day.

Best regards,

Christine.