Renesas DA16200 PMOD User manual

User Manual
DA16200 DA16600 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 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
2 of 40
© 2023RenesasElectronics
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 ................................................................................................................. 6
6Demonstration Hardware Description ................................................................................. 7
6.1 Configuring Hardware................................................................................................... 8
6.1.1 UART Connection.......................................................................................... 8
6.1.2 DA16200/DA16600 Wake Up Connection.......................................................10
6.1.3 External Host Wake Up Connection ...............................................................10
7Software Setting Guide.......................................................................................................13
7.1 The DA16200/DA16600...............................................................................................13
7.1.1 How to Connect with Tera Term.....................................................................13
7.1.2 How to Download Firmware Image to DA16200/DA16600 ...............................14
7.1.3 Configuration Items for Testing ......................................................................16
7.1.4 Stand-Alone Mode........................................................................................17
7.2 MCU Setting ...............................................................................................................18
8Mobile App .........................................................................................................................24
8.1 Overview ....................................................................................................................24
8.2 Open Door..................................................................................................................24
8.3 Close Door .................................................................................................................27
8.4 OTA Update of MCU Firmware.....................................................................................29
8.5 Mobile App UI.............................................................................................................29
Appendix A Azure IoT AT-Command List.................................................................................31
A.1 Operating Modes.........................................................................................................31
A.1.1 Setting Mode................................................................................................31
A.1.2 Provisioning Mode ........................................................................................31
A.1.3 Communication Mode ...................................................................................32
A.2 How to Report Topic and Update Device Twin ..............................................................33
A.2.1 Configure Device Twin Topic .........................................................................33
A.3 AT-CMD List...............................................................................................................33
A.3.1 Basic Set......................................................................................................33
A.3.2 TLS Certificate..............................................................................................34
A.3.3 PIN MUX......................................................................................................35
A.3.4 Configuration Data as Topics.........................................................................36
A.3.5 Command –MCU to DA16200/DA16600........................................................36
A.3.6 Command –DA16200/DA16600 to MCU........................................................37

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
3 of 40
© 2023RenesasElectronics
A.3.7 DA16200/DA16600 Status –DA16200/DA16600 to MCU ................................37
Revision History.......................................................................................................................38
Figures
Figure 1: Overview of AT-CMD with Azure-IoT...............................................................................5
Figure 2: Hardware Configuration..................................................................................................7
Figure 3: Default UART HW Connection........................................................................................9
Figure 4: User Example of Custom UART1 HW Connection............................................................9
Figure 5: DA16200/DA16600 Wake Up HW Connection ...............................................................10
Figure 6: Default Wake Up Pin HW Connection............................................................................11
Figure 7: User Example for External Host Wake Up Pin HW Connection........................................11
Figure 8: Tera Term ...................................................................................................................13
Figure 9: Serial Port Setup..........................................................................................................13
Figure 10: DA16200/DA16600 Image Download ..........................................................................14
Figure 11: Reset Button..............................................................................................................15
Figure 12: e2studio Project File...................................................................................................18
Figure 13: FSP configuration.......................................................................................................19
Figure 14: DeviceID (THINGNAME), Primary Key, Hostname and Primary connection string in MCU
Source Code..............................................................................................................................19
Figure 15: Build Project ..............................................................................................................20
Figure 16: Debug Configurations Menu........................................................................................20
Figure 17: Set Debug Configurations...........................................................................................21
Figure 18: Block Diagram for Opening a Door..............................................................................24
Figure 19: Open Door in the App.................................................................................................25
Figure 20: Device Twin When Door is Opened .............................................................................25
Figure 21: Block Diagram for Closing a Door................................................................................27
Figure 22: Close Door in the App.................................................................................................27
Figure 23: Device Twin When Door is Closed...............................................................................28
Figure 24: Block Diagram for MCU OTA ......................................................................................29
Figure 25: Android Application Screenshots.................................................................................30
Figure 26: Setting Mode..............................................................................................................31
Figure 27: Provisioning Mode......................................................................................................32
Figure 28: Communication Mode.................................................................................................32
Figure 29: Communication from MCU to Phone............................................................................33
Tables
Table 1: Pin Connection................................................................................................................8
Table 2: UART1 Pin Configuration.................................................................................................9
Table 3: GPIO Pin Configuration.................................................................................................11
Table 4: Configuration of Topics..................................................................................................33
Table 5: Basic Set of MCU to DA16200/DA16600 ........................................................................33
Table 6: TLS Certificate from MCU to DA16200/DA16600.............................................................34
Table 7: PIN MUX from MCU to DA16200/DA16600.....................................................................35
Table 8: Configuration Data from MCU to DA16200/DA16600.......................................................36
Table 9: Command from MCU to DA16200/DA16600 ...................................................................36
Table 10: Command from DA16200/DA16600 to MCU .................................................................37
Table 11: Status from DA16200/DA16600 to MCU .......................................................................37

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
4 of 40
© 2023RenesasElectronics
1 Abstract
The DA16200/DA16600 AT-Command for Azure-IoT helps IoT designers and engineers accelerate
the development of IoT applications and solutions. This guide introduces the DA16200/DA16600 AT-
Command for Azure-IoT and describes how to use the DA16200/DA16600 EVB and EK-RA6M4
board to set up a hardware development environment, install the necessary software, and download
and run an example application.
2 Termsand 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 DA16600, Getting Started with Azure-IoT, User Manual, Renesas
Electronics
[2] UM-WI-056, DA16200 DA16600, FreeRTOS Getting Started Guide, User Manual, Renesas
Electronics
[3] UM-WI-042, DA16200, Provisioning the Mobile App, User Manual, Renesas Electronics

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
5 of 40
© 2023RenesasElectronics
4 What is AT-Commandfor Azure-IoT
The AT-Command interface for Azure-IoT is a solution developed for the DA16200/DA16600 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 an Azure-IoT solution and quickly go to mass production (seeFigure 1).
Figure 1: Overview of AT-CMD with Azure-IoT

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
6 of 40
© 2023RenesasElectronics
5 ReleasePackage
The contents of theAT-Command forAzure IoT package are as follows:
○\DA16200 or \DA16600
–Firmware images for the DA16200/DA16600 Wi-Fi devices
–Tera Term script for downloading the firmware images to a DA16200/DA16600 Wi-Fi
device
○\DA16200\script (\DA16600\script)
–Tera Term script which demonstrates how to use AT-Command forAWS IoT using a
personal computer and the DA16200/DA16600 EVK\doc
–Getting Stared with AT-Command forAzure IoT
•Introduces the DA16200/DA16600 AT-Command forAzure IoT and
describes how to set up the development environment and test the
examples.
•Describes how to connect an external host to the
DA16200/DA16600 EVK forusing the AT-Command forAzure IoT.
•Describes the AT-Command for Azure IoT command list.
○\MCU
–Sample project based onthe RA6M4 development environment which demonstrates how
to use AT-Command forAzure IoT

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
7 of 40
© 2023RenesasElectronics
6 HardwareSetup
As shown in Figure 2, the demonstration hardware for the DA16200/DA16600 AT-Command for
Azure IoT consists of:
- DA16200/DA16600 EVK
- EK-RA6M4 board
- Windows laptop or PC
The DA16200/DA16600 AT-Command for Azure IoT requires two UART ports:
- UART0 is used to download firmware and log output.
- UART1 or UART2 is used to communicate AT commands and responses between the MCU
and the DA16200/DA16600.
Additionally, two otherconnections are required between the MCU and the DA16200/DA16600:
- GPIO from the MCU to the DA16200/DA16600 to wake up the DA16200/DA16600 from DPM
mode.
- GPIO from the DA16200/DA16600 to the MCU which wakes up the MCU if it is in sleep
mode.
Figure 2: Hardware Configuration
The pin connections between the DA16200/DA16600 EVK and the EK-RA6M4 board are shown in
Table 1.

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
8 of 40
© 2023RenesasElectronics
Table 1: Pin Connection
Function
DA16200EVK
DA16600EVK
EK-RA6M4 Board
Pin Number
Pin Name
Pin
Number
Pin Name
Pin
Number
Pin Name
Ground
J3.18
GND
J2.12
GND
J24-7
GND
UART_TX
J4.11
TX1/GPIOA_4
J2.2
TX2/GPIOC_6
J23-2
PA10
UART_RX
J4.12
RX1/GPIOA_5
J2.4
RX2/GPIOC_7
J23-1
PA9
DA16200_WA
KE_UP
J3.11
RTC_WAKE_UP2
SW1
RTC_WAKE_U
P2
J23-6
PB8
6.1 Configuring Hardware
This sectiondescribes how to connect an external processor system, called the “External Host,” to
the DA16200/DA16600 EVK via hard wires, and use the UART interface forthe AT+CMD protocol.
Three connections are required:
○UART connection
○DA16200/DA16600 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) orUART2 (DA16600 EVK) configuration is shown in Table 2.
Table 2: Serial Port Configuration Values
Settings
Value
BaudRate
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 forUART1 TX and GPIOA_5 forUART1 RX by default.
The DA16600 EVK uses GPIOC_6 forUART2 TX and GPIOC_7 forUART2 RX by default.
The RX, TX and GND signals of the External Host and the DA16200/DA16600 should be connected
as shown in Figure 3.

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
9 of 40
© 2023RenesasElectronics
Figure 3: Default UART HW Connection
6.1.1.2 User UART Pin Connection Sample for the DA16200 EVK
If needed, AT+CMD can be used to change the pinconnection forUART1 in accordance with the Pin
Mux Configuration as shown in Figure 4.
For example, the following AT+CMD can be used to change the Pin Mux configurationto use
GPIOA_2 forUART1 TX and GPIOA_3 forUART1 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

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
10of 40
© 2023RenesasElectronics
PIN Mux
GPIO
Signal Name
PIN_CMUX
GPIOA_4
TX
GPIOA_5
RX
PIN_DMUX
GPIOA_6
TX
GPIOA_7
RX
6.1.2 DA16200/DA16600 Wake UpConnection
The DA16200/DA16600 has a maximum power saving mode called “DPM.” When the
DA16200/DA16600 is configured in DPM mode, the External Host must wake up the
DA16200/DA16600 before sending orreceiving data. The External Host can trigger a wakeup event
by connecting a GPIO pin to the RTC_WAKE_UP pin of DA16200/DA16600 EVK. A wakeup event is
triggered when the GPIO pin transitions from Low to High and then back to Low.
Figure 5: DA16200/DA16600 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/DA16600 requires a connection to the External Host to triggera 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/DA16600 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

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
11of 40
© 2023RenesasElectronics
Figure 6: Default Wake Up Pin HW Connection
6.1.3.2 External Host Wake Up Pin Configuration for DA16200/DA16600 EVK
On the DA16200 EVK, GPIOA_0~ GPIOA_11 and GPIOC_6 ~ GPIOC_8 can beused as an External
Host wake up pin. To avoid duplication, assign theExternal Host wake up pin to a GPIO pin that is
available. Table 3 shows the GPIO pin configuration information.
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

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
12of 40
© 2023RenesasElectronics
Port
PIN Mux
GPIO
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 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
13of 40
© 2023RenesasElectronics
7 SoftwareSetup
7.1 DA16200/DA16600
A serial communication tool such as “Tera Term” is required forconnecting the desktop to the
DA16200/DA16600 to download the firmware images and monitor the debug logs. To download Tera
Term, visit https://ttssh2.osdn.jp/.
7.1.1 How to Connect withTeraTerm
Procedure:
1. Locate and connect the serial port on the personal computer.
Figure 8: Tera Term
2. Select a baud-rate. The default value forDA16200/DA16600 is 230400.
Figure 9: Serial Port Setup

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
14of 40
© 2023RenesasElectronics
3. After connecting to the DA16200 with Tera Term, check forthe 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 DownloadFirmwareImage to DA16200/DA16600
Procedure
NOTE
There are two types of DA16200/DA16600firmwareimagesinthe DA16200\imgorDA16600\img
folder:DA16200_FBOOTandDA16200_FRTOS or DA16600_FBOOTandDA16600_FRTOS.
1. The firmware images can be downloaded to the DA16200/DA16600 by selecting Control >
Marco > Download_W25Q32JW_FreeRTOS.ttl script in the DA16200\img \folder.
Figure 10: DA16200/DA16600 Image Download

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
15of 40
© 2023RenesasElectronics
2. A factory reset is required to enter the Azure-IoT Configuration Setting mode. This can be done
by pushing the “Factory_RST” button f or 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 = "Renesas_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/DA16600 is now ready to enter the Azure-IoT Configuration Settings.

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
16of 40
© 2023RenesasElectronics
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 fortesting on the provided Azure IoT reference server:
●unique device id
●primary key
●primary connection string
●hostname
NOTE
Contact a Field Application Engineering (FAE)for necessaryinformation.Formoreinformation how to
create andsetup an Azure IoT own server, seethe getting started guide,Ref. [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 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
17of 40
© 2023RenesasElectronics
;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 following file:
\MCU\RA6M4\Src\atcmd\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-AloneMode
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.
Note that the example script only supports initial value setting. To fully verify the operation of the AT
Commands, an MCU should be used forinteracting with the server and application.

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
18of 40
© 2023RenesasElectronics
7.2 MCU Setting
To set MCU, require E2studio, Free IDE for referencing, and MCU source code fortesting.
E2stduio link: e² studio |Renesas
Procedure
1. Afterinstalling e2studio, import the project file at \MCU\RA6M4\(see Figure 12).
Figure 12: E2studio Project File
NOTE
When connectingtothe RA6M4 MCU forthe first time or changingtheconfiguration,followthestep 2
to set upthe FSP Configuration.
2. Select Configurations.xml to set FSP configuration of the RA6M4 MCU (see Figure 13).

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
19of 40
© 2023RenesasElectronics
Figure 13: FSP Configuration
3. Use the “device id" (thingname), “primary key”, “hostname”, and “primary connection string”
received from the FAE to test without setting up a server.
4. Change the configuration to the received configuration (see Figure 14).
Figure 14: Thingname, Primarykey, Hostname and IotHub Connection String
5. Select project > Build all to build (see Figure 15).

UM-WI-060
DA16200 DA16600 Getting Started with AT-Command for Azure® IoT
User Manual
Revision 1.1
31-Jul-2023
CFR0012
20of 40
© 2023RenesasElectronics
Figure 15: Build Project
6. Select Debug Configurations to set the connection to the RA6M4 MCU (see Figure 16).
Figure 16: Debug Configurations