Renesas DA16200 PMOD User manual

User Manual
DA16200 Getting Started with AT-
Command for Azure-IoT
UM-WI-060
Abstract
This document introduces the AT-Command interface for Azure IoT through a demonstration of the
Azure IoT reference design and the Azure IoT Android/iOS mobile applications.

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
2 of 39
© 2022 Renesas Electronics
Contents
Abstract................................................................................................................................................ 1
Contents............................................................................................................................................... 2
Figures.................................................................................................................................................. 3
Tables ................................................................................................................................................... 3
1Abstract.......................................................................................................................................... 4
2Terms and Definitions................................................................................................................... 4
3References..................................................................................................................................... 4
4What is AT-Command for Azure-IoT ........................................................................................... 5
5Release Package ........................................................................................................................... 5
6Demonstration Hardware Description......................................................................................... 6
6.1 Configuring the Hardware..................................................................................................... 7
6.1.1 UART Connection.................................................................................................. 7
6.1.2 DA16200 Wake Up Connection............................................................................. 9
6.1.3 External Host Wake Up Connection...................................................................... 9
7Software Setting Guide............................................................................................................... 11
7.1 The DA16200......................................................................................................................11
7.1.1 How to Connect with Tera Term..........................................................................11
7.1.2 How to Download a Firmware Image to the DA16200 ........................................12
7.1.3 Configuration items for Testing............................................................................14
7.1.4 Stand-Alone Mode...............................................................................................15
7.2 MCU Setting........................................................................................................................16
8Mobile App................................................................................................................................... 22
8.1 Overview ............................................................................................................................. 22
8.2 Open Door...........................................................................................................................23
8.3 Close Door .......................................................................................................................... 25
8.4 OTA Update of the MCU Firmware..................................................................................... 27
8.5 Mobile App UI......................................................................................................................27
Appendix A Azure IoT AT-Command List....................................................................................... 29
A.1 Operating Modes................................................................................................................. 29
A.1.1 Setting Mode........................................................................................................29
A.1.2 Provisioning Mode ............................................................................................... 29
A.1.3 Communication Mode.......................................................................................... 30
A.2 How to report Topic and update device twin....................................................................... 31
A.2.1 Configure device twin topic.................................................................................. 31
A.3 AT-CMD List........................................................................................................................31
A.3.1 Basic Set..............................................................................................................31
A.3.2 TLS certificate......................................................................................................32
A.3.3 PIN MUX.............................................................................................................. 33
A.3.4 Configuration Data as Topics .............................................................................. 34
A.3.5 Command –MCU to DA16200............................................................................34
A.3.6 Command –DA16200 to MCU............................................................................35

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
3 of 39
© 2022 Renesas Electronics
A.3.7 DA16200 Status –DA16200 to MCU .................................................................. 35
Revision History ................................................................................................................................ 37
Figures
Figure 1: Overview of AT-CMD with Azure-IoT..................................................................................... 5
Figure 2: Hardware Configuration ......................................................................................................... 6
Figure 3: Default UART HW Connection............................................................................................... 8
Figure 4: User Example of Custom UART1 HW Connection................................................................ 8
Figure 5: DA16200 Wake Up HW Connection...................................................................................... 9
Figure 6: Default Wake Up Pin HW Connection.................................................................................... 9
Figure 7: User Example for External Host Wake Up Pin HW Connection .......................................... 10
Figure 8: Tera Term............................................................................................................................. 11
Figure 9: Serial Port Setup..................................................................................................................11
Figure 10: DA16200 Image Download ................................................................................................ 12
Figure 11: Reset Button....................................................................................................................... 13
Figure 12: CubeIDE Project File.......................................................................................................... 16
Figure 13: Device ID(THINGNAME), Primary Key, Hostname and Primary connection string in MCU
Source Code........................................................................................................................................17
Figure 14: Build Project....................................................................................................................... 17
Figure 15: Debug Configurations Menu ..............................................................................................18
Figure 16: Set Debug Configurations..................................................................................................18
Figure 17: Set Perspective Switch ...................................................................................................... 19
Figure 18: Block Diagram for Opening a Door.................................................................................... 23
Figure 19: Open Door in the App ........................................................................................................ 23
Figure 20: Device Twin when door is opened..................................................................................... 24
Figure 21: Block Diagram for Closing a Door...................................................................................... 25
Figure 22: Close Door in the App........................................................................................................25
Figure 23: Device Twin when door is closed....................................................................................... 26
Figure 24: Android Application Screenshots ....................................................................................... 28
Figure 25: Setting Mode ...................................................................................................................... 29
Figure 26: Provisioning Mode.............................................................................................................. 30
Figure 27: Communication Mode ........................................................................................................ 30
Figure 28: Communication from MCU to Phone ................................................................................. 31
Tables
Table 1: Pin Connection........................................................................................................................ 7
Table 2: UART1 Pin Configuration........................................................................................................ 8
Table 3: GPIO Pin Configuration......................................................................................................... 10
Table 4: Configuration of the Topics ................................................................................................... 31
Table 5: The Basic set of MCU to DA16200 .......................................................................................31
Table 6: TLS certificate from MCU to DA16200.................................................................................. 32
Table 7: The PIN MUX from MCU to DA16200................................................................................... 33
Table 8: Configuration Data from MCU to DA16200...........................................................................34
Table 9: Command of MCU to DA16200............................................................................................. 34
Table 10: Command of DA16200 to MCU........................................................................................... 35
Table 11: Status from DA16200 to MCU............................................................................................. 35

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
4 of 39
© 2022 Renesas Electronics
1 Abstract
The DA16200 AT-Command for Azure-IoT helps IoT designers and engineers accelerate the
development of IoT applications and solutions. This guide introduces the DA16200 AT-Command for
Azure-IoT and describes how to use the DA16200 EVB and STM32 Nucleo-64 board to set up a
hardware development environment, install the necessary software, and download and run an
example application.
2 Terms and Definitions
AP Access Point
Azure Microsoft Web Services
CFG CONFIGURE
CMD COMMAND
DPM Dynamic Power Management
IoT Internet of Things
MCU Micro-Controller Unit
OTA Over-The-Air
RTC Real Time Clock
SDK Software Development Kit
TIM Traffic Indication MAP
TLS Transport Layer Security
3 References
[1] UM-WI-058, DA16200 Getting Started with Azure-IoT, Renesas Electronics
[2] UM-WI-056, DA16200 DA16600 FreeRTOS Getting Started Guide, Renesas Electronics
[3] UM-WI-042, DA16200 Provisioning the Mobile App, Renesas Electronics

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
5 of 39
© 2022 Renesas Electronics
4 What is AT-Command for Azure-IoT
The AT-Command interface for Azure-IoT is a solution developed for the DA16200 Wi-Fi device and
modules that provides connectivity between an MCU and a Mobile phone through an Azure-IoT
server using the AT-Command interface. This reference design can be used to easily develop a
Azure-IoT solution and quickly go to mass production. (see Figure 1).
Figure 1: Overview of AT-CMD with Azure-IoT
5 Release Package
The contents of the AT-Command for Azure IoT package are as follows:
○\DA16200
–Firmware images for the DA16200 Wi-Fi devices
–Tera Term script for downloading the firmware images to a DA16200 Wi-Fi device
–An example of a Tera Term script to demonstrate AT-Command for Azure IoT using a PC
and the DA16200 EVK
○\doc
–Getting Stared with AT-Command for Azure IoT
•Introduces the DA16200 AT-Command for Azure IoT and describes
how to set up the development environment and test the examples.
•Describes how to connect an external host to the DA16200 EVK for
using the AT-Command for Azure IoT.
•Describes the AT-Command for Azure IoT command list.
○\MCU
–Sample project based on the STM32 development environment which demonstrates how
to use AT-Command for Azure IoT

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
6 of 39
© 2022 Renesas Electronics
6 Demonstration Hardware Description
As shown in Figure 2, the demonstration hardware for the DA16200 AT-Command for Azure IoT
consists of:
- DA16200 EVK
- STM32 Nucleo-64 board
- Windows laptop or PC
The DA16200 AT-Command for Azure IoT requires two UART ports:
- UART0 is used to download firmware and to log output.
- UART1 or UART2 is used to communicate AT commands and responses between the MCU
and the DA16200.
Additionally, two other connections are required between the MCU and the DA16200:
- GPIO from the MCU to the DA16200 to wake up the DA16200 from DPM mode.
- GPIO from the DA16200 to the MCU which wakes up the MCU if it is in sleep mode.
Figure 2: Hardware Configuration
The pin connections between the DA16200 EVK and the STM32 Nucleo-64 board are shown in
Table 1.

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
7 of 39
© 2022 Renesas Electronics
Table 1: Pin Connection
Function
DA16200 EVK
STM32 Nucleo64 Board
Pin Number
Pin Name
Pin Number
Pin Name
Ground
J3.18
GND
CN10.20
GND
UART_TX
J4.11
TX1/GPIOA_4
CN10.33
PA10
UART_RX
J4.12
RX1/GPIOA_5
CN10.21
PA9
DA16200_WAKE_UP
J3.2
RTC_WAKE_UP
CN10.3
PB8
MCU_WAKE_UP
J4.18
GPIOA_11
CN10.19
PC7
6.1 Configuring the Hardware
This section describes how to connect an external processor system, called the ‘External Host’, to
the DA16200 EVK via hard wires, and use the UART interface for the AT+CMD protocol.
There are three connections required:
●UART connection
●DA16200 wake up connection from DPM
●External Host wake up connection when using power saving mode
This section also describes the “AT Command” used to configure the GPIO connections to the
External Host.
6.1.1 UART Connection
The default UART1 (DA16200 EVK) configuration is shown in Table 2.
Table 2: Serial Port Configuration Values
Settings
Value
Baud Rate
115200
Data Bits
8
Parity
None
Stop Bits
1
Flow Control
(HW/SW)
None
6.1.1.1 Default UART Pin Connection
The DA16200 EVK uses GPIOA_4 for UART1 TX and GPIOA_5 for UART1 RX by default.
The RX, TX and GND signals of the External Host and the DA16200 must be connected as shown in
Figure 3.

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
8 of 39
© 2022 Renesas Electronics
Figure 3: Default UART HW Connection
6.1.1.2 User UART Pin Connection Sample for the DA16200 EVK
If required, an AT+CMD can be used to change the pin connection for UART1 in accordance with the
Pin Mux Configuration as shown in Error! Reference source not found.
For example, the following AT+CMD can be used to change the Pin Mux configuration to use
GPIOA_2 for UART1 TX and GPIOA_3 for UART1 RX:
AT+AZU=SET NV_PIN_BMUX BMUX_UART1d // GPIOA_2 and GPIOA_3 for UART1
Figure 4: User Example of Custom UART1 HW Connection
Table 2: UART1 Pin Configuration
PIN Mux
GPIO
Signal Name
PIN_AMUX
GPIOA_0
TX
GPIOA_1
RX
PIN_BMUX
GPIOA_2
TX
GPIOA_3
RX
PIN_CMUX
GPIOA_4
TX
GPIOA_5
RX
PIN_DMUX
GPIOA_6
TX
GPIOA_7
RX

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
9 of 39
© 2022 Renesas Electronics
6.1.2 DA16200 Wake Up Connection
The DA16200 has a maximum power saving mode called 'DPM'. When the DA16200 is configured in
DPM mode, the External Host must wake up the DA16200 before sending or receiving data. The
External Host can trigger a wakeup event by connecting a GPIO pin to the RTC_WAKE_UP pin of
DA16200 EVK. A wakeup event is triggered when the GPIO Pin transitions from Low to High and
then back to Low.
Figure 5: DA16200 Wake Up HW Connection
6.1.3 External Host Wake Up Connection
In a low power scenario, the External Host may be in sleep mode to save power. In this case, the
DA16200 requires a connection to the External Host to trigger a wake up from sleep mode. This
connection is not required if the External Host is not using sleep mode.
6.1.3.1 Default External Host Wake Up Pin Connection
By default, the DA16200 EVK uses pin GPIOA_11 to wake up an External Host (Figure 6). The
AT+CMDs to configure the External Host wake up pin are as follows:
AT+AZU SET APP_MCU_WKAEUP_PORT GPIO_UNIT_A // GPIO_A port
AT+AZU SET APP_MCU_WKAEUP_PIN GPIO_PIN11 // GPIO_11
Figure 6: Default Wake Up Pin HW Connection
6.1.3.2 External Host Wake Up Pin Configuration example for DA16200 EVK
On the DA16200 EVK, GPIOA_0~ GPIOA_11 and GPIOC_6 ~ GPIOC_8 can be used as an External
Host wake up pin.
To avoid duplication, assign the External Host wake up pin to a GPIO pin that is available. Table 3
shows the GPIO pin configuration information.

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
10 of 39
© 2022 Renesas Electronics
For example, to use GPIOC_6 of the DA16200 EVK for the External Host wake up pin, set the GPIO
port and the GPIO pin using the following AT+CMDs:
AT+AZU SET APP_MCU_WKAEUP_PORT GPIO_UNIT_C // GPIO_C port
AT+AZU SET APP_MCU_WKAEUP_PIN GPIO_PIN6 // GPIO_6
Figure 7: User Example for External Host Wake Up Pin HW Connection
Table 3: GPIO Pin Configuration
Port
PIN Mux
GPIO
GPIO_UNIT_A
PIN_AMUX
GPIOA_0
GPIOA_1
PIN_BMUX
GPIOA_2
GPIOA_3
PIN_CMUX
GPIOA_4
GPIOA_5
PIN_DMUX
GPIOA_6
GPIOA_7
PIN_EMUX
GPIOA_8
GPIOA_9
PIN_FMUX
GPIOA_10
GPIOA_11
GPIO_UNIT_C
PIN_UMUX
GPIOC_6
GPIOC_7
GPIOC_8

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
11 of 39
© 2022 Renesas Electronics
7 Software Setting Guide
7.1 The DA16200
A serial communication tool such as “Tera Term” is required to connect the laptop/PC to the
DA16200 to download the firmware images and monitor the debug logs.
Tera Term is available for download from: https://ttssh2.osdn.jp/
7.1.1 How to Connect with Tera Term
Procedure:
1. Locate and connect the serial port on the PC.
Figure 8: Tera Term
2. Select a baud-rate. The default value for DA16200 is 230400.
Figure 9: Serial Port Setup

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
12 of 39
© 2022 Renesas Electronics
3. After connecting to the DA16200 with "Tera Term", check for the command prompt as shown
below
******************************************************
* DA16200 SDK Information
* ---------------------------------------------------
*
* - CPU Type : Cortex-M4 (120MHz)
* - OS Type : FreeRTOS 10.4.3
* - Serial Flash : 4 MB
* - SDK Version : V3.2.3.1 GEN
* - F/W Version : FRTOS-GEN01-01-55b96089e-004098
* - F/W Build Time : Jun 14 2022 10:12:18
* - Boot Index : 0
*
******************************************************
Not define feature and set Default EVK
EVK Doorlock or Default EVK (current board=0)
System Mode : Station Only (0)
>>> Start DA16X Supplicant ...
>>> DA16x Supp Ver2.7 - 2022_03
>>> Wi-Fi mode : b/g/n -> b/g (for DPM)
>>> MAC address (sta0) : d4:3d:39:10:d5:06
>>> sta0 interface add OK
>>> Start STA mode...
>>> UART1 : Clock=80000000, BaudRate=115200
>>> UART1 : DMA Enabled ...
[reg_user_atcmd_help_cb] Start AZURE AT Command
[UART ready notification]
7.1.2 How to Download a Firmware Image to the DA16200
Procedure
Note 1 There are two types of DA16200 firmware images in the DA16200\img folder: DA16200_FBOOT and
DA16200_FRTOS.
1. The firmware images can be downloaded to the DA16200 by selecting Control > Marco >
Download_W25Q32JW_FreeRTOS.ttl script in the DA16200\img \folder.
Figure 10: DA16200 Image Download

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
13 of 39
© 2022 Renesas Electronics
2. A factory reset is required to enter the Azure-IoT Configuration Setting mode. This can be done
by pushing the “Factory_RST” button for 5 seconds as shown in Figure 11.
Figure 11: Reset Button
RTC switched to XTAL5 seconds
Factory reset ready.
Factory Reseting....
DA16200 concurrent factory reset AP mode = 1 ("AP_ONLY")....
....[app_set_customer_ap_configure] set AP config mode = 0
apps_reboot_ap_mode Customer configuration ...
.
default_ssid = "Dialog_DA16200" ..., ap_config_param->ssid_name
PW = 1234567890
PW = 1234567890 completed
.
apps_reboot_ap_mode IPADDR_CUSTOMER...
....
apps_reboot_ap_mode customer_dhcpd_flag == DHCPD_CUSTOMER..
......
OK
The DA16200 is now ready to enter the Azure-IoT Configuration Settings.

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
14 of 39
© 2022 Renesas Electronics
Soft-AP is Ready (d4:3d:39:11:5e:73)
>>> UART1 : Clock=80000000, BaudRate=115200
>>> UART1 : DMA Enabled ...
[reg_user_atcmd_help_cb] Start AZURE AT Command
[UART ready notification]
[http_server_task] HTTP-Server Start!!
===========================================
[ AZURE-IOT AT-COMMAND ]
[ azure_twin_dpm_auto_start]
AZURE_IOT on Station Mode for "DA16200"
============================================
[azure_twin_dpm_auto_start] mcu_wakeup_port=-1, mcu_wakeup_pin=0x0
default set to mcu_wakeup_port=0, mcu_wakeup_pin=0x800
Root CA: X
Not ready Cert for Azure service ...
invalid AZURE feature...can't start AZURE thread...check again
.. UART ready
7.1.3 Configuration items for Testing
The following information is required for testing on the provided Azure IoT reference server:
●unique device id
●primary key
●primary connection string
●hostname
Note 2 The required information can be requested from a Field Application Engineering (FAE). For more
information to create and set up an Azure IoT own server, please refer to the UM-WI-058-
DA16200_Getting_Started_with_Azure-IoT [1].
Set the information in the MCU source code or set it in the provided scripts.
The Tera Term scripts can be found in the SDK at the following location:
\DA16200\script\doorlock.ttl

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
15 of 39
© 2022 Renesas Electronics
;In order to use this script on DA16200, the console should be prompt
;after setting the DA16200 to STA mode, SNTP client enable, and no DPM mode in easy setup through the
console.
;set configurations with DA16200's console
;set features
sendln "user"
;set board type
sendln "SET APP_BOARD_FEATURE EVK"
mpause 400
;set your thingname
sendln "SET APP_THINGNAME da16200_atcmd_thing"
mpause 400
;set primary key of device
sendln "SET APP_DEV_PRIMARY_KEY dWKJjGHX9TiCOPheiKyRjjcmmUtBBZsuASBB+K6OoGs="
mpause 400
;set hostname of device
sendln "SET APP_HOSTNAME azure-atcmd-iothub.azure-devices.net"
mpause 400
;set connection string of device
sendln "SET APP_IOTHUB_CONN_STRING HostName=azure-atcmd-iothub.azure-
devices.net;SharedAccessKeyName=iothubowner;SharedAccessKey=Xq970WfOFvEmVU9Ixcm96zPGTKh1ztcoxF64QBmyvU
8="
mpause 400
The MCU source code can be found in the file:
\MCU\STM_32\Stm32Cube_atcmd\Core\Src\at_cmd.c.
const char* cmd_set_azure_cfg[MAX_CFG_NUM] =
{
"\r\nAT+"PLATFORM" SET APP_BOARD_FEATURE EVK\r\n",
"\r\nAT+"PLATFORM" SET APP_THINGNAME da16200_atcmd_thing\r\n",
"\r\nAT+"PLATFORM" SET APP_DEV_PRIMARY_KEY dWKJjGHX9TiCOPheiKyRjjcmmUtBBZsuASBB+K6OoGs=\r\n",
"\r\nAT+"PLATFORM" SET APP_HOSTNAME azure-atcmd-iothub.azure-devices.net\r\n",
"\r\nAT+"PLATFORM" SET APP_IOTHUB_CONN_STRING HostName=azure-atcmd-iothub.azure-
devices.net;SharedAccessKeyName=iothubowner;SharedAccessKey=Xq970WfOFvEmVU9Ixcm96zPGTKh1ztcoxF64QBmyvU
8=\r\n",
"\r\nAT+"PLATFORM" CFG 0 app_door 1 2\r\n", /* mcu sub. str */
"\r\nAT+"PLATFORM" CFG 1 mcu_door 1 0\r\n", /* mcu pub. str */
"\r\nAT+"PLATFORM" CFG 2 battery 0 1\r\n", /* shadow int */
"\r\nAT+"PLATFORM" CFG 3 temperature 2 1\r\n", /* shadow float */
"\r\nAT+"PLATFORM" CFG 4 doorState 1 1\r\n", /* shadow str */
"\r\nAT+"PLATFORM" CFG 5 app_shadow 1 2\r\n", /* mcu sub. str */
"\r\nAT+"PLATFORM" CFG 6 mcu_shadow 1 0\r\n", /* mcu pub. str */
"\r\nAT+"PLATFORM" CFG 7 openMethod 1 1\r\n", /* shadow str */
"\r\nAT+"PLATFORM" SET SLEEP_MODE 3\r\n",
"\r\nAT+"PLATFORM" SET USE_DPM 1\r\n",
"\r\nAT+"PLATFORM" SET RTC_TIME 1740\r\n", /* 1740 */
"\r\nAT+"PLATFORM" SET DPM_KEEP_ALIVE 30000\r\n",
"\r\nAT+"PLATFORM" SET USE_WAKE_UP 0\r\n",
"\r\nAT+"PLATFORM" SET TIM_WAKE_UP 10\r\n",
"\r\nAT+"PLATFORM" SET APP_MCU_WKAEUP_PORT GPIO_UNIT_A\r\n", /* GPIO_UNIT_A or GPIO_UNIT_C */
"\r\nAT+"PLATFORM" SET APP_MCU_WKAEUP_PIN GPIO_PIN11\r\n" /* GPIO_PIN0 ~ GPIO_PIN11 or
GPIO_PIN6~GPIO_PIN8 */
};
7.1.4 Stand-Alone Mode
If an external host MCU is not available, the Azure-IoT commands can be tested with the sample
script provided in the SDK.
Door-lock for two-way communication: \DA16200\script\doorlock.ttl.

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
16 of 39
© 2022 Renesas Electronics
Note that the example script only supports initial value setting, To fully verify the operation of the AT
Commands, an MCU should be used for interacting with the server and application.
7.2 MCU Setting
Requirements:
CubeIDE, Free IDE for referencing, and testing MCU source code.
CubeIDE link: https://www.st.com/en/development-tools/stm32cubeide.html
Procedure
1. After installing CubeIDE, double-click to open the .project file at
\MCU\STM_32\Stm32Cube_atcmd\ (see Figure 12).
Figure 12: CubeIDE Project File
2. Use the “device id" (thingname), “primary key”, “hostname”, and “primary connection string”
received from the FAE to test without setting up a server.
3. Change the configuration to the received configuration (see Figure 13).

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
17 of 39
© 2022 Renesas Electronics
Figure 13: Device ID(THINGNAME), Primary Key, Hostname and Primary connection string in
MCU Source Code
4. Select project > Build all to build (see Figure 14).
Figure 14: Build Project
Note 3 When connecting to the STM32 MCU for the first time, follow steps 5-7 to set upthe Debug
Configuration.
5. Select Debug Configurations to set the connection to the STM32 MCU (see Figure 15).

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
18 of 39
© 2022 Renesas Electronics
Figure 15: Debug Configurations Menu
6. Selecting the debug tab will open the window shown in Figure 16. Change the configuration as
shown and then select the “Apply” and “Debug”buttons.
Figure 16: Set Debug Configurations

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
19 of 39
© 2022 Renesas Electronics
7. Click "NO" when the “Confirm Perspective Switch” pop-up appears, as shown in Figure 17.
Figure 17: Set Perspective Switch
8. When clicking the “Debug”icon on the Tool bar, the MCU image will be downloaded to the
device.
9. The following shows the console output of the DA16200 after a factory mode reset.
System Mode : Soft-AP (1)
>>> DHCP Server Started
>>> Start DA16X Supplicant ...
>>> DA16x Supp Ver2.7 - 2022_03
>>> Add SoftAP Inteface (softap1) ...
>>> MAC address (softap1) : d4:3d:39:10:d5:07
>>> softap1 interface add OK
>>> AP Operating Channel: 1(2412)
>>> Network Interface (wlan1) : UP
BSS Isolate Disabled
Soft-AP is Ready (d4:3d:39:10:d5:07)
>>> UART1 : Clock=80000000, BaudRate=115200
>>> UART1 : DMA Enabled ...
[reg_user_atcmd_help_cb] Start AZURE AT Command
[UART ready notification]
[http_server_task] HTTP-Server Start!!
===========================================
[ AZURE-IOT AT-COMMAND ]
[ azure_twin_dpm_auto_start]
AZURE_IOT on Station Mode for "DA16200"
============================================
[azure_twin_dpm_auto_start] mcu_wakeup_port=-1, mcu_wakeup_pin=0x0
default set to mcu_wakeup_port=0, mcu_wakeup_pin=0x800
Root CA: X
Not ready Cert for Azure service ...
invalid AZURE feature...can't start AZURE thread...check again
.. UART ready

UM-WI-060
DA16200 Getting Started with AT-Command for Azure-IoT
User Manual
Revision 1.0
10-Aug-2022
CFR0012
20 of 39
© 2022 Renesas Electronics
10. The following shows the console output of the DA16200 when setting the Azure IoT configuration
via AT-Commands from an MCU.
=======================================================
argc num = 2
argv[0]: AT+AZU
argv[1]: SET APP_BOARD_FEATURE EVK
=======================================================
APP SET EVK
=======================================================
argc num = 2
argv[0]: AT+AZU
argv[1]: SET APP_THINGNAME da16200_atcmd_thing
=======================================================
APP SET da16200_atcmd_thing
=======================================================
argc num = 2
argv[0]: AT+AZU
argv[1]: SET APP_DEV_PRIMARY_KEY dWKJjGHX9TiCOPheiKyRjjcmmUtBBZsuASBB+K6OoGs=
=======================================================
APP SET dWKJjGHX9TiCOPheiKyRjjcmmUtBBZsuASBB+K6OoGs=
=======================================================
argc num = 2
argv[0]: AT+AZU
argv[1]: SET APP_HOSTNAME azure-atcmd-iothub.azure-devices.net
=======================================================
APP SET azure-atcmd-iothub.azure-devices.net
=======================================================
argc num = 2
argv[0]: AT+AZU
argv[1]: SET APP_IOTHUB_CONN_STRING HostName=azure-atcmd-iothub.azure-devices.net;SharedAccess
KeyName=iothubowner;SharedAccessKey=Xq970WfOFvEmVU9Ixcm96zPGTKh1ztcoxF64QBmyvU8=
=======================================================
APP SET HostName=azure-atcmd-iothub.azure-devices.net;SharedAccessKeyName=iothubowner;SharedAc
cessKey=Xq970WfOFvEmVU9Ixcm96zPGTKh1ztcoxF64QBmyvU8=
=======================================================
argc num = 2
argv[0]: AT+AZU
argv[1]: CFG 0 app_door 1 2
=======================================================
=======================================================
Att[0] number : 0
Att[0] name : app_door
Att[0] data type: 1
Att[0] MQTT type: 2
=======================================================