Quick Start Guide

Synergy Enterprise Cloud Toolbox

Demo for AE-CLOUD2
Quick Start Guide
Renesas Synergy™ Platform
Synergy Tools & Kits
Tools: Connectivity

All information contained in these materials, including products and product specifications, represents
information on the product at the time of publication and is subject to change by Renesas Electronics
Corp. without notice. Please review the latest information published by Renesas Electronics Corp.
through various means, including the Renesas Electronics Corp. website (http://www.renesas.com).

www.renesas.com Rev.2.1.0 April 2019

 Notice
1. Descriptions of circuits, software and other related information in this document are provided only to illustrate the operation of
semiconductor products and application examples. You are fully responsible for the incorporation or any other use of the
circuits, software, and information in the design of your product or system. Renesas Electronics disclaims any and all liability
for any losses and damages incurred by you or third parties arising from the use of these circuits, software, or information.
2. Renesas Electronics hereby expressly disclaims any warranties against and liability for infringement or any other claims
involving patents, copyrights, or other intellectual property rights of third parties, by or arising from the use of Renesas
Electronics products or technical information described in this document, including but not limited to, the product data,
drawings, charts, programs, algorithms, and application examples.
3. No license, express, implied or otherwise, is granted hereby under any patents, copyrights or other intellectual property rights of
Renesas Electronics or others.
4. You shall not alter, modify, copy, or reverse engineer any Renesas Electronics product, whether in whole or in part. Renesas
Electronics disclaims any and all liability for any losses or damages incurred by you or third parties arising from such alteration,
modification, copying or reverse engineering.
5. Renesas Electronics products are classified according to the following two quality grades: "Standard" and "High Quality". The
intended applications for each Renesas Electronics product depends on the product’s quality grade, as indicated below.
"Standard": Computers; office equipment; communications equipment; test and measurement equipment; audio and visual
equipment; home electronic appliances; machine tools; personal electronic equipment; industrial robots; etc.
"High Quality": Transportation equipment (automobiles, trains, ships, etc.); traffic control (traffic lights); large-scale
communication equipment; key financial terminal systems; safety control equipment; etc.
Unless expressly designated as a high reliability product or a product for harsh environments in a Renesas Electronics data sheet
or other Renesas Electronics document, Renesas Electronics products are not intended or authorized for use in products or
systems that may pose a direct threat to human life or bodily injury (artificial life support devices or systems; surgical
implantations; etc.), or may cause serious property damage (space system; undersea repeaters; nuclear power control systems;
aircraft control systems; key plant systems; military equipment; etc.). Renesas Electronics disclaims any and all liability for any
damages or losses incurred by you or any third parties arising from the use of any Renesas Electronics product that is
inconsistent with any Renesas Electronics data sheet, user’s manual or other Renesas Electronics document.
6. When using Renesas Electronics products, refer to the latest product information (data sheets, user’s manuals, application notes,
"General Notes for Handling and Using Semiconductor Devices" in the reliability handbook, etc.), and ensure that usage
conditions are within the ranges specified by Renesas Electronics with respect to maximum ratings, operating power supply
voltage range, heat dissipation characteristics, installation, etc. Renesas Electronics disclaims any and all liability for any
malfunctions, failure or accident arising out of the use of Renesas Electronics products outside of such specified ranges.
7. Although Renesas Electronics endeavors to improve the quality and reliability of Renesas Electronics products, semiconductor
products have specific characteristics, such as the occurrence of failure at a certain rate and malfunctions under certain use
conditions. Unless designated as a high reliability product or a product for harsh environments in a Renesas Electronics data
sheet or other Renesas Electronics document, Renesas Electronics products are not subject to radiation resistance design. You
are responsible for implementing safety measures to guard against the possibility of bodily injury, injury or damage caused by
fire, and/or danger to the public in the event of a failure or malfunction of Renesas Electronics products, such as safety design
for hardware and software, including but not limited to redundancy, fire control and malfunction prevention, appropriate
treatment for aging degradation or any other appropriate measures. Because the evaluation of microcomputer software alone is
very difficult and impractical, you are responsible for evaluating the safety of the final products or systems manufactured by
you.
8. Please contact a Renesas Electronics sales office for details as to environmental matters such as the environmental compatibility
of each Renesas Electronics product. You are responsible for carefully and sufficiently investigating applicable laws and
regulations that regulate the inclusion or use of controlled substances, including without limitation, the EU RoHS Directive, and
using Renesas Electronics products in compliance with all these applicable laws and regulations. Renesas Electronics disclaims
any and all liability for damages or losses occurring as a result of your noncompliance with applicable laws and regulations.
9. Renesas Electronics products and technologies shall not be used for or incorporated into any products or systems whose
manufacture, use, or sale is prohibited under any applicable domestic or foreign laws or regulations. You shall comply with any
applicable export control laws and regulations promulgated and administered by the governments of any countries asserting
jurisdiction over the parties or transactions.
10. It is the responsibility of the buyer or distributor of Renesas Electronics products, or any other party who distributes, disposes
of, or otherwise sells or transfers the product to a third party, to notify such third party in advance of the contents and conditions
set forth in this document.
11. This document shall not be reprinted, reproduced or duplicated in any form, in whole or in part, without prior written consent of
Renesas Electronics.
12. Please contact a Renesas Electronics sales office if you have any questions regarding the information contained in this document
or Renesas Electronics products.
(Note 1) "Renesas Electronics" as used in this document means Renesas Electronics Corporation and also includes its directly or
indirectly controlled subsidiaries.
(Note 2) "Renesas Electronics product(s)" means any product developed or manufactured by or for Renesas Electronics.
(Rev.4.0-1 November 2017)
 General Precautions
1. Precaution against Electrostatic Discharge (ESD)
A strong electrical field, when exposed to a CMOS device, can cause destruction of the gate oxide and ultimately degrade the
device operation. Steps must be taken to stop the generation of static electricity as much as possible, and quickly dissipate it
when it occurs. Environmental control must be adequate. When it is dry, a humidifier should be used. This is recommended to
avoid using insulators that can easily build up static electricity. Semiconductor devices must be stored and transported in an anti-
static container, static shielding bag or conductive material. All test and measurement tools including work benches and floors
must be grounded. The operator must also be grounded using a wrist strap. Semiconductor devices must not be touched with bare
hands. Similar precautions must be taken for printed circuit boards with mounted semiconductor devices.

2. Processing at power-on
The state of the product is undefined at the time when power is supplied. The states of internal circuits in the LSI are
indeterminate and the states of register settings and pins are undefined at the time when power is supplied. In a finished product
where the reset signal is applied to the external reset pin, the states of pins are not guaranteed from the time when power is
supplied until the reset process is completed. In a similar way, the states of pins in a product that is reset by an on-chip power-on
reset function are not guaranteed from the time when power is supplied until the power reaches the level at which resetting is
specified.

3. Input of signal during power-off state

Do not input signals or an I/O pull-up power supply while the device is powered off. The current injection that results from input
of such a signal or I/O pull-up power supply may cause malfunction and the abnormal current that passes in the device at this
time may cause degradation of internal elements. Follow the guideline for input signal during power-off state as described in
your product documentation.

4. Handling of unused pins

Handle unused pins in accordance with the directions given under handling of unused pins in the manual. The input pins of
CMOS products are generally in the high-impedance state. In operation with an unused pin in the open-circuit state, extra
electromagnetic noise is induced in the vicinity of the LSI, an associated shoot-through current flows internally, and
malfunctions occur due to the false recognition of the pin state as an input signal become possible.

5. Clock signals
After applying a reset, only release the reset line after the operating clock signal becomes stable. When switching the clock
signal during program execution, wait until the target clock signal is stabilized. When the clock signal is generated with an
external resonator or from an external oscillator during a reset, ensure that the reset line is only released after full stabilization of
the clock signal. Additionally, when switching to a clock signal produced with an external resonator or by an external oscillator
while program execution is in progress, wait until the target clock signal is stable.

6. Voltage application waveform at input pin

Waveform distortion due to input noise or a reflected wave may cause malfunction. If the input of the CMOS device stays in the
area between VIL (Max.) and VIH (Min.) due to noise, for example, the device may malfunction. Take care to prevent chattering
noise from entering the device when the input level is fixed, and also in the transition period when the input level passes through
the area between VIL (Max.) and VIH (Min.).

7. Prohibition of access to reserved addresses

Access to reserved addresses is prohibited. The reserved addresses are provided for possible future expansion of functions. Do
not access these addresses as the correct operation of the LSI is not guaranteed.

8. Differences between products

Before changing from one product to another, for example to a product with a different part number, confirm that the change will
not lead to problems. The characteristics of a microprocessing unit or microcontroller unit products in the same group but having
a different part number might differ in terms of internal memory capacity, layout pattern, and other factors, which can affect the
ranges of electrical characteristics, such as characteristic values, operating margins, immunity to noise, and amount of radiated
noise. When changing to a product with a different part number, implement a system-evaluation test for the given product.
 Quick Start Guide
Renesas Synergy™ Platform
R20QS0004EU0210
Synergy Enterprise Cloud Toolbox Demo Rev.2.1.0
April 18, 2019
for AE-CLOUD2
Contents

1. Introduction .............................................................................................................................. 2

2. Prerequisites............................................................................................................................ 2

3. Requirements .......................................................................................................................... 2

4. About the Demonstration ......................................................................................................... 3

5. Setting up the Hardware .......................................................................................................... 4

6. Setting up and executing the Demonstration ........................................................................... 5

6.1 Setting up the AE-CLOUD2 Project ........................................................................................................ 5
6.2 Setting up AE-CLOUD2 for Wi-Fi ............................................................................................................ 7
6.3 Setting up AE-CLOUD2 for Ethernet ....................................................................................................... 9
6.4 Setting up the Cellular network interface for AE-CLOUD2 ................................................................... 10
6.5 Signing up for the Synergy Enterprise Cloud Toolbox Demo Dashboard ............................................. 15
6.6 Adding a Device to the Synergy Enterprise Cloud Toolbox Demo Dashboard ..................................... 15
6.7 Configuring User Credentials for AE-CLOUD2 ..................................................................................... 17
6.8 Provisioning for AE-CLOUD2 ................................................................................................................ 18
6.9 Starting the Wind Turbine model on AE-CLOUD2 ................................................................................ 19
6.10 Remote Monitoring on the Synergy Enterprise Cloud Toolbox Demo Dashboard ............................... 20
6.11 Stimulating sensors on AE-CLOUD2 .................................................................................................... 20
6.12 Changing IoT cloud providers ............................................................................................................... 21
6.13 Development Kit view ............................................................................................................................ 22
6.14 Device Logs on Synergy Enterprise Cloud Toolbox Demo Dashboard ................................................ 23
6.15 Device firmware management on Synergy Enterprise Cloud Toolbox Demo Dashboard .................... 24
6.16 Resetting the system from the Synergy Enterprise Cloud Toolbox Demo Dashboard ......................... 25
6.17 Auto Start Feature ................................................................................................................................. 26
6.18 Non-Volatile Verbose Log mechanism .................................................................................................. 26
6.19 Notes and Limitations ............................................................................................................................ 29

7. Appendix — Downloading and running the Synergy Enterprise Cloud Toolbox Demo ........... 30

Revision History ............................................................................................................................ 32

R20QS0004EU0210 Rev.2.1.0 Page 1 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
1. Introduction
This Quick Start Guide for AE-CLOUD2 demonstrates the Synergy™ Enterprise Cloud Toolbox Demo. This
application project is downloadable from www.renesas.com/cloudtoolbox and includes the following items:
• Embedded binary
• Quick Start Guide

The demo can be used as a reference solution for users to quickly get started on the Synergy Software Package (SSP),
Wi-Fi Framework, and Cellular Framework as well as Ethernet connectivity, and cloud connectivity with different IoT
Cloud Providers using the Renesas Synergy™ Enterprise Cloud Toolbox Demo for AE-CLOUD2 Kit.
2. Prerequisites
The hardware and software requirements listed in the section 3 should be installed.
Note: The MCU board is not pre-programmed with firmware for the Synergy Enterprise Cloud Toolbox Demo
application project. To run the bat file and flash the MCU board, see the instructions in the Appendix —
Downloading and running the .

3. Requirements
• PC software requirements:
⎯ Microsoft® Windows® 7 or 10
• AE-Cloud2 kit (part# YSAECLOUD2) hardware requirements:
⎯ S5D9/S124 Pillar Synergy MCU Board (part # YIOTS5D9PILLAR v1.1 Rev F)
⎯ Wi-Fi Board (part# YSAEWIFI-1)
⎯ BG96 Arduino Shield (Ver 2.0 Rev F)
⎯ Two antennas
⎯ Global SIM with Data plan
⎯ SEGGER J-Link® Lite for Renesas Synergy (part# YSJLINKLITE)
⎯ Two micro USB connector cables
⎯ Ethernet Cable

R20QS0004EU0210 Rev.2.1.0 Page 2 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
4. About the Demonstration
The demonstration application provides a reference design and implementation to get your S5D9/S124 based platform
quickly onto the cloud. The application uses NetX™ Secure and NetX™ MQTT to communicate with Amazon Web
Solutions (AWS), Azure, and Google IoT Cloud Providers. The demo showcases how to integrate functionality of the
on-board sensors including accelerometer, barometric pressure sensor, temperature, and humidity sensor, and send this
sensor data to the cloud over Ethernet, Wi-Fi or Cellular network interfaces. How to send commands from the cloud to
devices to turn an LED ON or OFF is also shown.
The major components (see Figure 1) of the embedded application include:
• SSP components
⎯ Wi-Fi framework
⎯ Cellular framework
⎯ NetX IP stack
⎯ Cloud APIs (MQTT/TLS)
⎯ Console framework
• Sensor drivers

Figure 1 System overview

R20QS0004EU0210 Rev.2.1.0 Page 3 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
5. Setting up the Hardware
For connection details, see Figure 2.
1. Connect the Wi-Fi module to PMOD.
2. Connect micro USB cable to port J9 for serial console.
3. Connect BG96 Arduino shield to Arduino header.
4. Connect a micro USB cable to port J6 for on board J-Link or Connect the J-Link debugger to port J2.

Note: Do the next step only after all the other modules and connectors are plugged in! Port J9 connector supplies
power to the AE-CLOUD2 board, in addition to the debugger.

For Cellular Network connectivity, see Error! Reference source not found..
• Connect the antennas provided with your CATM1 module
• Connect cellular CATM1 module to MCU board with Arduino header.

Figure 2 Device Connections and Setup

Notes:

Please find driver files for latest Synergy USB CDC driver package at below location.
https://www.renesas.com/en-us/products/synergy/software/add-ons/usb-cdc-drivers.html
Please follow instructions in “Application Note – Installing Synergy signed USB CDC Drivers” to install Synergy USB
CDC driver on your computer.

R20QS0004EU0210 Rev.2.1.0 Page 4 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2

Figure 3 Device front view with cellular setup

6. Setting up and executing the Demonstration

The main components of the demonstration are the Renesas Synergy™ Enterprise Cloud Toolbox Demo Dashboard and
the S5D9 Synergy MCU built on AE-CLOUD2 kit.
The setup and execution of the demonstration is explained in the following sections.

6.1 Setting up the AE-CLOUD2 Project

The MCU board is not pre-programmed with the firmware for the Synergy Enterprise Cloud Toolbox Demo application
project. For quick flashing of the firmware to the MCU board, refer to the Appendix — Downloading and running the
to run the bat file that flashes the MCU board.
To access the command console from the computer, install TeraTerm Pro (or equivalent serial terminal emulator) and
open the terminal with the appropriate COM port configured. The default configuration for the terminal is 9600-8-N-1.
The application enters command line interface (CLI) mode if S1 switch is pressed within 5 secs after AE-CLOUD2 is
powered on. Once in command line interface mode, application waits for USB enumeration to complete and blinks
Green LED to indicate it. If USB enumeration is complete, Green LED is turned on and application waits for a key to
be pressed by the user on the terminal. Press any key to access the command prompt.
Note - Do not press and hold S1 switch before powering on the device as that will cause device to enter synergy
bootloader mode instead of command line interface mode (CLI).
The following screen shows what the console window looks like on a terminal emulator when the device is in CLI
mode, and you press any key to access the command prompt. Application prints the banner on the serial console.

R20QS0004EU0210 Rev.2.1.0 Page 5 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2

****************************************************************************
* Synergy Enterprise Cloud Toolbox *
* Version 2.1.0, Released-2019/04/18 *
* Build 2.0 *
****************************************************************************

Initializing sensors: done

Initializing data flash: done
Initializing GPS: done
>

Figure 4 Sensor Initialization and command prompt

Note: You can press Enter at any time to return to the Main Menu.

To see a list of available commands type: ?.

Figure 5 Help menu for commands

Obtain the Unique Kit ID using the command: ktid

Figure 6 ktid command output to get unique Kit ID

Note: This unique Kit ID is the Serial Number used to register/add the device on the Synergy Enterprise Cloud
Toolbox Demo Dashboard (see section 6.6).

R20QS0004EU0210 Rev.2.1.0 Page 6 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.2 Setting up AE-CLOUD2 for Wi-Fi
Configure the Wi-Fi interface as an active interface using command: cwiz

Figure 7 Setting Wi-Fi interface as active interface

This cwiz command displays supported network interfaces. To activate the Wi-Fi interface, enter command 2. Now
enter the SSID, passphrase, and security type associated with the network at each prompt.
If the Wi-Fi network is not secure, enter any value other than 1, 2 or 3. Wi-fi configuration details will be displayed on
console for final user confirmation. Please type ‘y’ if configuration details are correct. This Wi-Fi provisioning
information from you is stored in internal flash for subsequent use.

Figure 8 IP Configuration

R20QS0004EU0210 Rev.2.1.0 Page 7 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
To configure the IP address, you are given two options: Static and DHCP. In Figure 8 the user selected DHCP, and the
screen shows the IP address assigned to the device.
Figure 9 shows an alternate method to set up Wi-Fi as the network interface, where you provision the Wi-Fi module for
the first time on the network using the command wifi <SSID><KEY><SECURITY TYPE>.
>wifi TEST_AP no-Wifi4u wpa2
Wifi settings saved in flash
>

Figure 9 Setting Wi-Fi interface as the active interface

SSID is the SSID name, KEY is the password, and SECURITY TYPE is the security type of the Wi-Fi network that
can be set to wpa, wpa2, wep, or open. The Wi-Fi provisioning information is stored in internal flash for subsequent
use.
Set the Wi-Fi interface as active interface using the command: netif wifi
>netif wifi
Selected Network Interface : Wi-Fi

Wi-Fi setup may take a few moments and may require a few retries.

Connecting to SSID "TEST_AP": connected.

>

Figure 10 Setting Wi-Fi interface as the active interface

This command reads the provisioning information stored in the internal flash from the previous step and tries to
provision it automatically.
Configure the IP address using the command: ipcf.
Note – ipcf command must be preceded by netif command for successful network configuration.
>ipcf dhcp
Stopping DHCP client.done
Waiting for IP address.done

Wi-Fi Configuration
====================
SSID : Test_AP
Key : no-Wifi4u
Security : WPA2

IP Configuration
=======================
Interface : Wi-Fi
Mode : DHCP
IP Address : 192.168.1.251
Netmask : 255.255.255.0
Gateway : 192.168.1.1
DHCP Server : 192.168.1.7
DNS Server : 192.168.1.7

Waiting for SNTP Server . . .

SNTP Update Complete . . .
>
Figure 11 IP Configuration
The command must be used with either dhcp or static <IP> <MASK> <GW> <DNS>, depending on whether the IP
address is being obtained via DHCP or is statically assigned.
To continue with the demonstration setup, proceed to section 6.5.

R20QS0004EU0210 Rev.2.1.0 Page 8 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.3 Setting up AE-CLOUD2 for Ethernet
To use Ethernet as the network interface, enter the command: cwiz

Figure 12 Setting Ethernet interface as the active interface and IP configuration

This cwiz command displays supported network interfaces. To activate the Ethernet interface, enter command 1.
To configure the IP address, you are given two options: Static and DHCP. Select the desired option to configure the IP
address.
As an alternate method to configure Ethernet as the network interface, use the command: netif eth

>netif eth
Selected Network Interface : Ethernet
>
Figure 13 Setting Ethernet interface as the active interface

Configure the IP address using the command: ipcf

Note – ipcf command must be preceded by netif command for successful network configuration.

>ipcf dhcp
Stopping DHCP client.done
Waiting for IP address.done

IP Configuration
=======================
Interface : Ethernet
Mode : DHCP
IP Address : 192.168.1.241
Netmask : 255.255.255.0
Gateway : 192.168.1.1
DHCP Server : 192.168.1.7
DNS Server : 192.168.1.7

Cloud Toolbox Configuration

===========================
User : xyz@email.com
IoT Cloud : Azure

Waiting for SNTP Server . . .

SNTP Update Complete . . .
>
Figure 14 IP configuration

R20QS0004EU0210 Rev.2.1.0 Page 9 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
The command must be used with either DHCP or Static <IP> <MASK> <GW> <DNS>, depending on whether the IP
address is being obtained via DHCP or is statically assigned.

To continue with the demonstration setup, proceed to section 6.5.

6.4 Setting up the Cellular network interface for AE-CLOUD2
1) Cellular carriers with out of box operation -
User can connect to the carriers that are supported out of box with “cwiz” command. The “cwiz” command
displays supported network interfaces. To activate Cellular, enter command 3.
Whenever user selects “Cellular” as network interface, the menu option displayed on console is as shown in Figure
15. The menu option includes list of carriers that are supported to work out of box and a manual mode option. The
manual mode should be selected when the cellular carrier is not present in the list of carriers.
To select out of box mode of cellular carrier, enter the menu option corresponding to the cellular carrier in the list.
For e.g. To select Airtel (India), enter command 2.
Cellular configuration details will be displayed on console for final user confirmation. Please type ‘y’ if
configuration details are correct.
Carriers which are supported out of the box have their settings hardcoded in the embedded code. These settings
include APN, Context ID, PDP Type and associated set of sequential AT commands. Once user selects a cellular
carrier, these hardcoded settings and set of sequential AT commands are used to connect to the cellular carrier.

Figure 15 Setting Cellular interface as an active interface in out of box operation

R20QS0004EU0210 Rev.2.1.0 Page 10 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
2) Cellular carriers with manual mode of operation –
If cellular carrier is not supported with out of the box operation, user needs to identify the required configuration
and set of AT commands manually and provide it to the Synergy Enterprise Cloud Toolbox Demo application.
If new cellular carrier requires a set of AT commands to be applied to cellular module for SIM registration, the user
can use the atshell interface (CLI command atshell) to tryout AT commands with cellular modem. Once working
set of AT commands are available, user can save these commands to internal data flash (using CLI command
atsave) which will get reapplied for subsequent use.

CLI command – atshell:

Whenever user enters “atshell” command, user is provided with shell interface as shown in Figure 16.
This prompt is provided to tryout AT commands. This shell sends AT commands entered by user directly to the
cellular module and get the response back. This shell interface is only for tryout purpose of user. Any commands
that user enter using this shell interface is not saved to internal data flash.
Using this shell interface, user should try to get the SIM registered with the network. User can verify the network
SIM registration using command “at+cgreg?”. If the SIM registration is successful, then the expected output of this
command is either “+CGREG: 0,1” or “+CGREG: 0,5”

Figure 16 atshell interface

User can use the “exit” command to exit the shell interface as shown in Figure 16. This will exit the shell interface
and user can re-enter shell interface if required without restarting the device.

Note - “atshell” interface will only work when SIM card is inserted in BG96 Arduino shield’s SIM card slot and
cellular interface is not already configured or connected.

CLI command - atsave:

Whenever user enters “atsave” command, user will be provided with command prompt environment as shown in
Figure 17. This will allow user to save AT commands (identified using shell interface) to internal data flash. User
will be prompted to enter one AT command at a time and its associated parameters. Current supported parameters
are “retry count” and “retry delay”.
User need to enter these AT commands in sequential manner i.e. the order in which these need to be executed.
These saved AT commands will be applied to cellular modem during auto start or when user selects “Manual”
mode through “cwiz” command interface.
User can save maximum 16 AT commands to internal data flash with “atsave”. User can exit this “atsave”
command interface using “exit” command.
User can read the saved set of AT commands with “atread”.

R20QS0004EU0210 Rev.2.1.0 Page 11 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2

Figure 17 atsave command interface

CLI command - atread:

User is provided with a CLI command “atread” to read stored set of AT commands.

Figure 18 atread command interface

Once user has identified and saved set of AT commands with above interfaces, user can connect to the carriers with
“cwiz” command. The “cwiz” command displays supported network interfaces. To activate Cellular, enter
command 3.
Whenever user selects “Cellular” as network interface, the menu option displayed on console is as shown in Figure
19. The menu option includes list of carriers that are supported to work out of box and a manual mode option.
To select manual mode of cellular carrier, enter the menu option corresponding to the entry “Manual”.
For cellular carriers in manual mode, user is asked to enter APN, context ID and PDP type for the new carrier that
the user wants to establish connection with. Once entered, cellular configuration details will be displayed on
console for final user confirmation. Please type ‘y’ if configuration details are correct.

Once final confirmation from user is received as ‘y’, stored set of sequential AT commands will be applied to
cellular module for SIM registration and data connection.

R20QS0004EU0210 Rev.2.1.0 Page 12 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2

Figure 19 Setting Cellular interface as an active interface in manual mode

R20QS0004EU0210 Rev.2.1.0 Page 13 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2

Figure 20 Cellular interface link up in manual mode

Proceed to the following sections to sign up for the Synergy Enterprise Cloud Toolbox Demo Dashboard and add a
device to your dashboard.

R20QS0004EU0210 Rev.2.1.0 Page 14 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.5 Signing up for the Synergy Enterprise Cloud Toolbox Demo Dashboard
The Synergy Enterprise Cloud Toolbox Demo Dashboard is a hosted web application with the functionality to provision
devices on AWS, Microsoft Azure, or Google IoT Cloud Providers.
The Dashboard GUI provides:
• User Sign up
• Adding MQTT enabled devices to either AWS, Azure, or Google IoT
• A remote monitoring view to monitor the real-time sensor information of the connected devices
• Updating the device state

Note: The URL of the Synergy Enterprise Cloud Toolbox Demo Dashboard is: https://cloud.renesassynergy.com

Point your Internet browser to the Dashboard to display the Sign-in screen.

Figure 21 Sign up screen

Fill in the sign-up form and click on Accept and Continue. The hints given when you enter information in each field
specify any constraints. For example, Full Name and Company information may contain spaces in between text,
whereas space is not a valid input for Phone and Password fields. Characters allowed in passwords include uppercase
and lowercase letters, numbers, and the following special characters:
^$*.[]{}()?-"!@#%&/\,><':;|_~`
Note: Spaces are not supported in both the user name and password fields.

An activation email will be sent to the email address you used during registration. Clicking the link given in the email
will confirm and activate your account. You may then log in using the registered credentials.
6.6 Adding a Device to the Synergy Enterprise Cloud Toolbox Demo Dashboard
After logging in, click Add Device from the Device Management view to display an Add A Device view.

R20QS0004EU0210 Rev.2.1.0 Page 15 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2

Figure 22 Adding a device

The following steps show how to add a device:
1. Enter a user-friendly Name for the device (for example, South Wind Turbine).
2. Enter the device Serial Number.
The Serial Number is the Unique Kit ID obtained from the AE-CLOUD2 device in section 6.1.
3. Select the IoT Provider where the device is to be registered.

After a successful add operation, the device appears in the Device Management device-list. The device is added to the
IoT Cloud Provider and becomes available for monitoring after the device has been provisioned (bootstrapped) with the
Dashboard (see section 6.8).
In case the user has any devices bootstrapped to Azure IoT, a pop-up message will be displayed on the Device
management view as shown in the screens-capture below

R20QS0004EU0210 Rev.2.1.0 Page 16 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2

Figure 23 Notice for Azure Users

The next step is to configure the device with the registered username (email) and password.
6.7 Configuring User Credentials for AE-CLOUD2
Switch to the device for the CLI and configure your email address and password, using the command user <email_id>
<password>. Use the same email address and password you registered for your dashboard.

Figure 24 User registration

Notes:
1. This command should be triggered after adding the device to the Synergy Enterprise Cloud Toolbox Demo
Dashboard.
2. The user credentials should be the same as the ones used during Synergy Enterprise Cloud Toolbox Demo
Dashboard -User-signup.

R20QS0004EU0210 Rev.2.1.0 Page 17 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.8 Provisioning for AE-CLOUD2
To provision the device with the connection credentials and details of the IoT Cloud Provider platform, do the
following:
Execute the command: boot.

Figure 25 Device bootstrapping

The boot command triggers a request to the Dashboard REST API to pass the configured user credentials and device
unique ID. The Dashboard authenticates the user and verifies that a device has been added to the users account. Based
on the IoT platform the device was added, the Dashboard responds to the boot request by sending the connection’s
identifiers and authentication details.
Upon successful provisioning, the information received from the Dashboard is saved on the device’s internal flash.
Note: For the chks command, it is mandatory to run boot command first with the given \IoT service provider. Failing
to do so will cause the chks command to fail.

If the boot command fails, user may see following error logs. Please verify your settings as suggested.

HTTP Response code

Corresponding CLI log and user action
during bootstrap

Incorrect request.Please check Username and

401
Password
401 Bad header during authentication
Incorrect request.Please check Username and
400
Password

Device not found on Dashboard for

404
userid:xyz@email.com
500 Internal error

Figure 26 Bootstrap failure

R20QS0004EU0210 Rev.2.1.0 Page 18 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.9 Starting the Wind Turbine model on AE-CLOUD2

Figure 27 Start Wind Turbine model

To start the Wind Turbine model on the device, enter the command: turb start.
The demonstration application starts sending the sensor data to the Synergy Enterprise Cloud Toolbox Demo
Dashboard.
After the demonstration has started, you can press the Enter key to return to the prompt.
Note: Once the Wind Turbine model has been started, if you want to change the network interface or the IoT cloud
provider, the system MUST be power-cycled.

R20QS0004EU0210 Rev.2.1.0 Page 19 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.10 Remote Monitoring on the Synergy Enterprise Cloud Toolbox Demo
Dashboard
Switch to the Dashboard view in the browser. Navigate to the Remote Monitoring tab to view the real-time device
status and the sensor data.
The LEDs associated with the controls are shown in the LED LIGHTS section of the user interface.

Figure 28 Remote Monitoring

The Turbine switch controls the red LED on the device, while the Power switch controls green LED, and the
Ammeter controls the yellow LED.
Click the appropriate switches to update the state of the LEDs on the device.
6.11 Stimulating sensors on AE-CLOUD2
AE-CLOUD2 board comes equipped with various on-board sensors. These sensors can be stimulated, and the updated
readings observed on the Dashboard:
• Humidity sensor: Blow warm air on the device for 20 seconds. Observe the humidity value change on the
Dashboard.
• Temperature: Turn on the air conditioner and blow cold air towards the device for few minutes to observe the
temperature value change on the Dashboard.
• Pressure: Run the test at different altitudes. For example, run the test on the ground or top floor of a high-rise
building, to note the change in pressure on the Dashboard.
• Gas: Blow pullulated air or smoke on the device for few seconds and observe the Indoor Air Quality value change
on the Dashboard.
• Accelerometer: Without tilting the device, move it in any direction and observe the X, Y, and Z Axis value change
based on the direction that you move the device towards.
• Magnetometer: Rotate the board in clockwise or anticlockwise direction and observe the degree change on the
dashboard.
• Gyroscope: Tilt the device around X,Y and Z axis and observe the value change based on the tilt on the dashboard.
• Microphone: Clap in the room near to the device and observe the sound pressure level value changed on the
dashboard.
• GPS: Observe the GPS co-ordinates value and current device location in the map view on the dashboard.

R20QS0004EU0210 Rev.2.1.0 Page 20 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.12 Changing IoT cloud providers
Devices bootstrapped with the dashboard, can be switched between the supported IoT cloud providers.
In the following example, the device is provisioned for the Azure IoT platform. Use the following steps to change the
IoT cloud provider to AWS:
1. Login to the Synergy Enterprise Cloud Toolbox Demo Dashboard.
2. Navigate to Device Management view. Locate the device that must be switched to AWS and click the Delete icon.

Figure 29 Deleting a device

3. Click on OK when asked to confirm the operation.
4. Power cycle the device.
5. Follow the steps to add a device (see section 6.6) and choose AWS as the IoT cloud provider.
6. Run the demonstration as instructed in either of section 6.2 or 6.3 and then follow the instructions mentioned in
section, 6.8 and 6.9.

To switch a device provisioned for AWS to Azure, follow the same steps and choose Azure as the IoT cloud provider
when you add the device.
Notes:
1. At a given time only a single IoT cloud provider connection can be active on the system (dashboard and device).
2. Provisioning is a one-time operation for the Dashboard + Device-IoT Cloud Provider combination. Once the
device is provisioned for an IoT cloud provider, you do not need to re-provision unless the device is deleted and
added back again via the dashboard.
3. Every time you switch IoT providers, the device needs to be power cycled. This step is due to a limitation in the
MQTT client implementation.

R20QS0004EU0210 Rev.2.1.0 Page 21 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.13 Development Kit view
The Development Kit tab on the Dashboard provides links for the user to download the latest released firmware and
Quick Start Guide.

Figure 30 Development Kit – download firmware and Quick Start

In addition to downloading the firmware binary and the Quick Start Guide, this view has a link to buy the kit.

R20QS0004EU0210 Rev.2.1.0 Page 22 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.14 Device Logs on Synergy Enterprise Cloud Toolbox Demo Dashboard
The logs feature is available only to the admin user. Using the logs view, the admin user can see the CLI logs sent by
device.

Figure 31 Device Logs tab on the Dashboard

R20QS0004EU0210 Rev.2.1.0 Page 23 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.15 Device firmware management on Synergy Enterprise Cloud Toolbox Demo
Dashboard
The firmware-management feature is available only to the admin user. Using the firmware-management view, the
admin user can upload the latest released firmware for the device along with the Quick Start Guide.

Figure 32 Device Firmware Management tab on the Dashboard

R20QS0004EU0210 Rev.2.1.0 Page 24 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.16 Resetting the system from the Synergy Enterprise Cloud Toolbox Demo
Dashboard
The reset feature is available only to the admin user. Using the reset functionality, the admin user can delete all devices
and users from the system.
Note: This is an irreversible action. To access the reset view, click the Settings icon on the UI’s top-right corner.
Clicking Reset System, on the reset view, resets the system (see Figure 33 and Figure 34).

Figure 33 Device Management tab on the Dashboard

Figure 34 Reset System

R20QS0004EU0210 Rev.2.1.0 Page 25 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.17 Auto Start Feature
Device enters automatic startup mode if S1 switch is not pressed within 5 secs after AE-CLOUD2 is powered on.
Once device enters auto start mode, it performs below operations -
1. Turn on Yellow LED to indicate auto start.
2. Read and validate session header from internal data flash. Session header contains information about last used
network interface (Ethernet, Wi-Fi, Cellular), address mode (static, DHCP), cellular carrier selected and IoT
service provider information (AWS, Azure, Google). Validation of session header is achieved with CRC
checksum.
3. Device uses information read from internal flash to bring up network connection.
4. Device performs bootstrap operation automatically as described in section 6.8.
5. If any of the operation from above 2, 3 or 4 fails in auto start mode, then application transitions to command
line interface mode immediately.
6. If all the above operations are successful, device starts wind turbine application automatically as described in
section 6.9
7. If failure occurs while starting turbine application, red LED will start blinking.
Note - Do not press S1 switch before powering on the device as device will enter synergy bootloader mode instead of
auto start mode.
6.18 Non-Volatile Verbose Log mechanism
Device supports non-volatile verbose log mechanism which comprises a session header that stores session information
and a mechanism to store logs in internal data flash. Non-volatile log storage mechanism can be used for debugging
purpose.

A non-volatile memory block of 64 bytes is reserved for session header. For every cloud connectivity session, this
header is constructed according to user inputs. It captures information entered by user to start Turbine application.
The log mechanism has two levels of verbosity: Info and Trace
Info log:
Info log (Low verbosity) is ON by default. Info logs are stored in 16k block of memory in internal flash.
Info logs frame structure:

Figure 35 Info log structure

Timestamp: Timestamp is captured from SNTP server and maintained in first four bytes of log frame. (epoch time)
Function Name: Name of the function where Info log is located.
Line Number: Line number of the Info log in source file
Additional Log: Additional log info like error code, return value.
e.g. Info log are read from internal data flash and displayed on console.

Figure 36 Info logs printed on console with “LPOP” command

R20QS0004EU0210 Rev.2.1.0 Page 26 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
Info log will consist of two sections:

a) Non-circular Info logs

All info logs till “turb start” are stored here. Device receives current timestamp information from external SNTP
server after it gets connected to internet. Hence, some of these non-circular logs that gets stored in internal data
flash prior to this will have invalid timestamp information. During log retrieval, user will see “##########” on
console instead of actual UTC timestamp value for such logs. Non- circular Info logs are retained until a start of
new session – at which point they are overwritten. The start of a new session can be a device reset cycle. If the user
wants to get logs for the previous session, then user must enter the “LPOP” command immediately after a device
reset cycle prior to giving any command.

b) Circular Info logs

A Circular buffer mechanism is used for circular info logs and these logs will be overwritten when a wraparound of
circular buffer occurs.
Start address of these logs will be determined at runtime. These logs are stored in internal data flash immediate
after non-circular logs.

Info logs can be retrieved from the device using CLI command (LPOP).
Trace log:
Trace log is a High verbosity logging mechanism which captures in-depth information of most of the functions. These
logs are OFF by default. User needs to run the CLI command to turn trace logging ON in the device.
These logs are printed on console and not stored on the internal data flash. If user wants to capture all the trace logs,
then user needs to turn the logging on in the serial terminal emulator to save the logs. Trace Logs have same display
format as Info Logs.
Trace log frame structure

Figure 37 Trace log structure

e.g. Trace log as displayed on console

Figure 38 Trace logs printed on console after “LON” command

Debug log:
Debug logs are used to display cloud interaction information e.g. username/password used while connecting with cloud
provider. These logs are ON by default.

R20QS0004EU0210 Rev.2.1.0 Page 27 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2

Figure 39 Debug log printed on console after “DBUG ON” command

CLI commands for logging:
Below is the list of CLI commands for the user to access or control logs
Command Description Usage
LON This command starts the logging process for trace logs. By LON
default, logging process is OFF for trace log and ON for info log.

LOFF This command stops the logging process for trace log. LOFF

LPOP This command retrieves the session header and all the info logs LPOP
from internal data flash and displays them on console.
If the user has entered the LPOP command immediately after a
device reset cycle, the session header and info logs of the last
session are retrieved and displayed on the console. After retrieval,
this information is erased from flash.
In other cases, if user gives the LPOP command, then the session
header and info logs of the current session are retrieved and
displayed on console
LCLEAR This command erases all the info logs in internal data flash LCLEAR

LSEND This command sends info logs to the remote server. An active LSEND
network connection is needed to successfully run the thin
command.

DBUG This command controls debug messages printing on screen. DBUG ON

Start printing debug
messages on console
DBUG OFF
Stop printing debug
messages on console

R20QS0004EU0210 Rev.2.1.0 Page 28 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
6.19 Notes and Limitations
1. It is mandatory that user compiles the IAR project in a different folder from where the e2studio project has been
compiled.
2. After a network interface has been selected, if user wants to change it, then device MUST be power-cycled, and a
new network interface should be selected.
3. If the boot command fails for a device, user must delete the device from the dashboard and add it back. In the case
of a boot command failure, see Error! Reference source not found. for instructions. The command could fail with
the following errors:
A. Starting TLS session: Could not start TLS session (0x109).
B. Parsing Bootstrap Response: IoT Provider not found. Aborting.
C. The command gets stuck after starting the TLS session and the bootstrap does not begin.
4. After changing the LED status from Dashboard, it can take up to 10 seconds for the LED on the AE-CLOUD1
device to change.
5. Google-cloud IoT does not provide information regarding the connected state of the devices to its IoT platform. As a
result, on the Remote Monitoring tab view, the icon indicating the connectivity status may be shown as gray,
instead of green, for the device.
6. The Dashboard UI uses Server Sent Events (SSE).
SSE is part of the HTML5 standard. However, Microsoft (MSFT) does not support SSE in Internet Explorer
(IE) and Edge. As an alternative, polling is used to get events from the server. Depending on the polling
interval, the updates may appear to be delayed.
For details on SSE and the lack of support on MSFT browsers, visit https://en.wikipedia.org/wiki/Server-
sent_events and https://caniuse.com/#feat=eventsource.
7. In some corporate Ethernet and Wi-Fi connections, the browser refresh rate could be slow and may need manual
refreshing to receive updates. In certain cases, this error is indicated on the Dashboard with a warning on the status
of communication between the device and the Dashboard.
To mitigate this issue, ensure that the Corporate Network allows the following ports to successfully run the
Synergy Enterprise Cloud Toolbox Demo:
TCP Ports: 80 (HTTP), 443 (HTTPS) and 8883 (MQTT over TLS)
UDP Ports: 123 (SNTP), 53 (DNS).
In cases when these solutions do not update the browsers, the firewall settings should be checked.
8. If the command line returns an Unsupported Command error, check the format and retype the command using the
correct format.
9. If ‘turb start’ command on Google-cloud fails with an error “Unable to initialize IoT service Google,” power cycle
the device and retry the command.
10. When upgrading firmware, user will need to re-bootstrap a device using “boot" command after flashing new
version of firmware.
11. For Synergy Enterprise Cloud Toolbox Demo release build older than 1.1 ver 3.0, user will face issue during “turb
start” command to connect Azure IoT due to change in server certificate and will need to upgrade to SECT release
1.1 rev 3.0 or later.
12. Configuration updates are limited to 1 update per second, per device in Google IoT (Refer -
https://cloud.google.com/iot/docs/how-tos/config/configuring-devices).
13. CLI may hang if Wi-Fi access point gets inactive after “turb start” command.
14. Last known LED states may not get updated after device power cycle for Google-IoT provider. It gets updated after
any subsequent device configuration request.
15. “cell <APN><Context ID><PDP>” command followed with “netif cell” command are deprecated in 1.9.2 release.
These commands will not work in 1.9.2 release unless “cwiz” command was used previously on the device to setup
cellular network.
16. When user is using “atshell” interface to tryout different AT commands, if module receives unknown AT
command, module may stop responding. User will have power reset the device which will reset the cellular
module.
17. Currently microphone sensor detects clap and tap.
18. Sometimes the map widget does not occupy the entire widget area and a grey section is displayed in adjoining area
of the widget. This is observed intermittently in Safari browser.

R20QS0004EU0210 Rev.2.1.0 Page 29 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
19. When device is upgraded to Synergy Enterprise Cloud Toolbox Demo release build 2.0 and above, due to CRC
checksum mismatch, all user configuration data will be erased for the first power up. Hence, user will need to
update the user configuration after upgrading to 2.0 and above release.
7. Appendix — Downloading and running the Synergy Enterprise Cloud Toolbox
Demo
Use the following steps to download and run the Synergy Enterprise Cloud Toolbox Demo.
1. Install the driver to enable the J-Link Debugger connected to J2 to be recognized by Windows.
The driver can be downloaded at https://www.segger.com/downloads/jlink.
2. Extract AE_Cloud2_bat.zip.
3. Make sure all the hardware connections have been made as listed in section 5.
4. Run the s1.bat file in the unzipped folder.
5. Make sure the download is complete as shown in the following figures.

R20QS0004EU0210 Rev.2.1.0 Page 30 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2
Website and Support
Support: https://synergygallery.renesas.com/support
Technical Contact Details:
• America: https://www.renesas.com/en-us/support/contact.html
• Europe: https://www.renesas.com/en-eu/support/contact.html
• Japan: https://www.renesas.com/ja-jp/support/contact.html

All trademarks and registered trademarks are the property of their respective owners.

R20QS0004EU0210 Rev.2.1.0 Page 31 of 32

April 18, 2019
Renesas Synergy™ Platform Synergy Enterprise Cloud Toolbox for AE-CLOUD2

Revision History
Description
Rev. Date Page Summary
1.8.0 April 09, 2018 — Initial release
1.9.0 May 07, 2018 — Updated Dashboard screen captures to reflect release 1.9.0
Updated Synergy USB CDC driver link. Updates CLI screen
shots. Added details of Info, Trace and Debug logs in section
6.17.
1.9.2 May 24, 2018 — Updated section 6.4 for cellular changes
Added snap shots for new CLI commands to support cellular
changes.
Updated section 6.17 to add table of supported CLI commands
for logging
Updated SECT banner
1.9.3 June 28, 2018 — Updated section 6.11 for new sensors.
Updated figure 2 and figure 3 for new BG96 module.
Updated SECT banner.
Updated the Dashboard screen-captures to reflect the release
version. Update the remote-monitoring screen-capture to
reflect the additional sensor widgets.
1.9.4 July 12, 2018 — Updated banner information. Updated section 3 with latest
SSP and tool (e2studio and IAR) version.
Removed “connect” command support in atshell interface and
associated screen capture from section 6.4.. Updated section
6.15 for correct button label name “S1” for auto start.
Updated dashboard screen captures.
1.95 August 14, 2018 — Update section 3 to mention SSP 1.5.0 MP build1
Updated section 6.1 for CLI mode description changes and
banner information.
Updated section 6.15 for auto start description changes.
Aligned captured snap shots of console. Updated limitation
section.
Updated Dashboard screen captures
2.00 September 26, — Updated banner information. Removed comments from the
2018 doc. Changed reference of application “example” to application
“demo” in document. Added http response code and log map.
Updated CLI terminal snap shots.
Updated dashboard screen-captures.
2.1.0 April 18, 2019 — Updated banner information. Updated screen shots of cellular
carriers figure 15 and 19.

R20QS0004EU0210 Rev.2.1.0 Page 32 of 32

April 18, 2019
Synergy Enterprise Cloud Toolbox Demo for AE-CLOUD2
Quick Start Guide

Publication Date: Rev.2.1.0 April 18, 2019

Published by: Renesas Electronics Corporation

SALES OFFICES http://www.renesas.com
Refer to "http://www.renesas.com/" for the latest and detailed information.
Renesas Electronics America Inc.
1001 Murphy Ranch Road, Milpitas, CA 95035, U.S.A.
Tel: +1-408-432-8888, Fax: +1-408-434-5351
Renesas Electronics Canada Limited
9251 Yonge Street, Suite 8309 Richmond Hill, Ontario Canada L4C 9T3
Tel: +1-905-237-2004
Renesas Electronics Europe Limited
Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, U.K
Tel: +44-1628-651-700, Fax: +44-1628-651-804
Renesas Electronics Europe GmbH
Arcadiastrasse 10, 40472 Düsseldorf, Germany
Tel: +49-211-6503-0, Fax: +49-211-6503-1327
Renesas Electronics (China) Co., Ltd.
Room 1709 Quantum Plaza, No.27 ZhichunLu, Haidian District, Beijing, 100191 P. R. China
Tel: +86-10-8235-1155, Fax: +86-10-8235-7679
Renesas Electronics (Shanghai) Co., Ltd.
Unit 301, Tower A, Central Towers, 555 Langao Road, Putuo District, Shanghai, 200333 P. R. China
Tel: +86-21-2226-0888, Fax: +86-21-2226-0999
Renesas Electronics Hong Kong Limited
Unit 1601-1611, 16/F., Tower 2, Grand Century Place, 193 Prince Edward Road West, Mongkok, Kowloon, Hong Kong
Tel: +852-2265-6688, Fax: +852 2886-9022
Renesas Electronics Taiwan Co., Ltd.
13F, No. 363, Fu Shing North Road, Taipei 10543, Taiwan
Tel: +886-2-8175-9600, Fax: +886 2-8175-9670
Renesas Electronics Singapore Pte. Ltd.
80 Bendemeer Road, Unit #06-02 Hyflux Innovation Centre, Singapore 339949
Tel: +65-6213-0200, Fax: +65-6213-0300
Renesas Electronics Malaysia Sdn.Bhd.
Unit 1207, Block B, Menara Amcorp, Amcorp Trade Centre, No. 18, Jln Persiaran Barat, 46050 Petaling Jaya, Selangor Darul Ehsan, Malaysia
Tel: +60-3-7955-9390, Fax: +60-3-7955-9510
Renesas Electronics India Pvt. Ltd.
No.777C, 100 Feet Road, HAL 2nd Stage, Indiranagar, Bangalore 560 038, India
Tel: +91-80-67208700, Fax: +91-80-67208777
Renesas Electronics Korea Co., Ltd.
17F, KAMCO Yangjae Tower, 262, Gangnam-daero, Gangnam-gu, Seoul, 06265 Korea
Tel: +82-2-558-3737, Fax: +82-2-558-5338
© 2018 Renesas Electronics Corporation. All rights reserved.
Colophon 5.0
 Renesas Synergy™ Platform
Synergy Enterprise Cloud Toolbox
for AE-CLOUD2
Quick Start Guide

R20QS0004EU0110