Receive firmware update for S32K3 via MQTT by using AWS OTA agent using any type of sensor

[kolyanimohanto]

I want to use S32K3X4EVB T-172 Evaluation Board as a medium for firmware OTA updates via MQTT using AWS IOT Core. How should I proceed with this can you please suggest.

I have gone through other different posts related to Ethernet communication using S32K344 board, now I want to implement the "Receive firmware update for S32K3 via MQTT by using AWS OTA agent" maybe connecting any sensor compatible with automotive vehicle (especially cars) and upload the data to AWS cloud through the NXP board.

Please help me out with the software and hardware setup and how should I start coding for the same and also implement connection of S32DS v3.5 with AWS. 

The following posts and documents i have referred are mentioned as follows:

1) AWS Libraries for S32K3 | NXP Semiconductors

2) Getting Started with AWS Libraries for S32K3 | NXP Semiconductors

3) Automotive Ethernet Connector on TJA110x Adapter and S32k3x T172 Dev Board - NXP Community

4) Ethernet (board: S32K3X4EVB-T172) _transceiver TJA1103 - NXP Community

[Julián_AragónM]

Hi @kolyanimohanto,

We provide a Getting Started with S32K3 AWS IoT Core guide.

It shows how to run the aws_mqtt_s32k344 application. If execution is successful, you can verify that the MQTT messages are received by AWS IoT Core as described in the Verify messages in AWS IoT Core section.

Best regards,
Julián

[kolyanimohanto]

Hi Julian, Thank you for replying.

I wanted to ask will that example project help with sending the sensor data updates from NXP board to the AWS cloud?

Thanks and Regards,

Kolyani

[Julián_AragónM]

Hi @kolyanimohanto,

This example is used to create an MQTT connection to your AWS IoT account. The device will publish MQTT topic messages to the AWS endpoint and is able to receive publish messages from the server to which will reply with acknowledgement messages.

You can publish the sensor's data output, but that would be custom implementation on your side.

Best regards,
Julián

[kolyanimohanto]

Hi @Julián_AragónM 

1) Understood your point that to get sensor data output, the implementation has to be written additionally but how to map that implementation with the cloud? 

2) Also, if I only connect a sensor with the NXP board and the board with my laptop will the code work normally or is the ethernet cable and 100BASE T1 Media converter compulsory? 

Thanks and Regards

Kolyani

[Julián_AragónM]

Hi @kolyanimohanto,

1) Could you explain further what do you mean with "mapping the implementation"? The example includes the necessary steps for setting up AWS account and permissions and IOT:

### Setup your AWS account and Permissions

To create an AWS account, see Create and Activate an AWS Account (https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/). To add an IAM user to your AWS account, see IAM User Guide (https://docs.aws.amazon.com/IAM/latest/UserGuide/). To grant your IAM user account access to AWS IoT and FreeRTOS, attach the following IAM policies to your IAM user account:
- AmazonFreeRTOSFullAccess
- AWSIoTFullAccess
NOTE “The policy examples in this document are intended only for dev environments. All devices in your fleet must have credentials with privileges that authorize only intended actions on specific resources. The specific permission policies can vary for your use case. Identify the permission policies that best meet your business and security requirements. For more information, refer to Example policies (https://docs.aws.amazon.com/iot/latest/developerguide/example-iot-policies.html) and Security best practices (https://docs.aws.amazon.com/iot/latest/developerguide/security-best-practices.html)."

### Provision the device with AWS IoT

Refer to Registering your MCU board
(https://docs.aws.amazon.com/freertos/latest/userguide/freertos-prereqs.html#get-started-freertos-thi...).
Follow steps 1-6 under the heading To create an AWS IoT policy. In step 1, note that the AWS region for your account can also be found in the drop-down between the account name and Support drop-downs in the top menu bar. Follow steps 1-10 under the heading To create an IoT thing, private key, and certificate for your device.

There are two types of certificates which you can use depending on the cipher suite you chose in the S32CT AWS IoT Core configuration. By default, an RSA signed certificate is created for your device if using the steps above. For ECDHE signed certificates follow the instructions provided at https://aws.amazon.com/it/blogs/iot/elliptic-curve-cryptography-and-forward-secrecy-support-in-aws-i... .

2) Yes, the 100BASE T1 Media converter is needed since the EVB uses automotive ethernet.

Best regards,
Julián

[kolyanimohanto]

Hi @Julián_AragónM 

By "Mapping the implementation" I meant to ask that after writing the code for the sensor, how should I connect it with the AWS so that it is passed on to the cloud.

[Julián_AragónM]

Hi @kolyanimohanto,

I recommend firstly running the examples and seeing how the aws_mqtt_s32k344 example works. Please go over the AWS Libraries for S32K3 User Manual, it describes the different libraries integration, such as coreMQTT to connect to the broker and Mbed to create a TLS connection.

You can see the process for connecting to the AWS account through TLS in the prvMQTTDemoTask() function from the previously mentioned example.

Best regards,
Julián