Skip to content

Latest commit

 

History

History
92 lines (51 loc) · 3.66 KB

README.md

File metadata and controls

92 lines (51 loc) · 3.66 KB
Raw

About

Avnet IoTConnect AT Command Interface project example for the Renesas EK-RA8M1.

This code is based on the EK-RA8M1 Sample Code project and uses an IoTConnect AT Command-enabled PMOD module (e.g. DA16K based) as a gateway.

quickstart_ek_ra8m1_ep Copyright 2023 Renesas Electronics Corporation and/or its affiliates.

Dependencies

The project uses the following dependent projects:

A fully set up DA16600 PMOD Module is required to be set up and connected to IoTConnect.

Follow the DA16K AT Interface Quick Start guide.

Supported Boards

Renesas EK-RA8M1 with DA16600 Wi-Fi-BLE combo module.

Supported IoTC Device Commands

You can add these to your device template in the IoTConnect Dashboard.

  • set_red_led <state>

    Controls state of red LED on the board

    • on - Turns red LED on
    • off - Truns red LED off

  • set_led_frequency <freq>

    Controls the frequency of the blue LED flashing on the board

    • 0 - Slow blinking
    • 1 - Medium blinking
    • 2 - Fast blinking
    • 3 - Very fast blinking

Getting Started

Follow the Renesas EK-RA8M1 Quick Start Guide to set up your EK-RA8M1 board for use.

Make sure the DA16x00 device is connected to the PMOD1 connector.

Follow the Quickstart Guide to flash the included binary image and use it.

Building & Development

The project is tested and built with FSP version 5.0.0, but it may work with later 5.x.x versions.

You can now open / import, build and debug the project as per the Renesas Quick Start guide.

Enabling Automatic IoTConnect / Device Configuration

The underlying ATCMD library can configure the device automatically using certain APIs.

This allows you to skip manual configuration of the DA16xxx PMOD device (you are, however, still required to flash the firmware on it.)

The file iotc_demo_thread_entry.c contains definitions for these:

  • Define DA16K_IOTC_CONFIG_USED in the project to use custom IoTConnect configuration parameters
  • Define DA16K_WIFI_CONFIG_USED in the project to use custom WiFi configuration parameters

DA16K_IOTC_AWS may be replaced with DA16K_IOTC_AZURE to fit your environment.

Adding a Device Client Certificate / Private Key for Testing

NOTE: This requires a custom IOTC Configuration via DA16K_IOTC_CONFIG_USED to work (see above)!

You may place device client certificate and private key files in the PEM format into the e2studio/cert/ directory.

The file names must be:

  • device_cert.pem (client cert)
  • device_key.pem (private key)

There is an automatic pre-build step in the form of a python script, /util/pre_build.py. which generates a header file from these.

WARNING:

CLIENT CERTIFICATE TRANSMISSION IS INSECURE AND THE FUNCTIONALITY IS ONLY PROVIDED FOR TESTING PURPOSES.