This guide is intended to help customers setup the hardware development environment, install
required software, download, and run an example application on the DA14585/586 Basic
development Kit development platform.
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
BLE Bluetooth Low Energy
COM Communication Port
CS Chip Select
DBG Debug
EEPROM Electrically Erasable Programmable Memory
FTDI Future Technology Devices International
GPIO General Purpose Input/Output
IDE Integrated Development Environment
IRQ Interrupt Request
LED Light Emitting Diode
OS Operating System
OTP One Time Programmable
PC Personal Computer
RF Radio frequency
SDK Software Development Kit
SoC System on Chip
SPI Serial Peripheral Interface
SRAM Static Random Access Memory
SW Software
SWD Serial Wire Debug
TCK JTAG Test Clock
TMS JTAG Test Mode Select
UART Universal Asynchronous Receiver/Transmitter
USB Universal Serial Bus
4 Prerequisites
• Minimum hardware requirements:
– Windows Operating System, 1 GHz, 32-bit or 64-bit processor
– 1 GB of system memory (RAM)
– 2 GB of available disk space
• Basic Development Kit DA14585/586 and accessories
• Serial-port terminal software (for example, Tera Term)
• A USB connection supporting USB-Serial (FTDI)
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
The DA14585/586 is a family of Bluetooth Smart SoC devices that operate at very low power levels
while providing world-class RF performance.
The devices are available in a small footprint while still offering a large flexibility in configuration of the
on-chip interfaces making them suitable for a wide range of applications. More information can be
found in the DA14585 Datasheet.
The development kit includes a set of hardware (for example, a development board with an on-board
debugger) and is supported by a Software Development Kit (SDK) (that is, a development toolchain,
source code examples, and so on), and documentation.
The purpose of this guide is to provide an overview of the DA14585/586 Basic Development Kit Board
and describe the setup of the hardware and installation of the software tools to fully use the board.
The following hardware and software elements are required to use the DA14585/586 Development Kit:
• The Basic Development kit
• SmartSnippets™ Studio which can be installed on Windows, see Section 8.
• Windows users should download and install terminal software such as RealTerm, Putty or Tera
Term. This document uses Tera Term for its examples.
The rest of guide is organized as follows:
• Section 6 describes the hardware components and their initial installation and setup.
• Sections 7 and 8 describe the installation of the SmartSnippets™ DA14585/586 SDK software,
along with all necessary tools.
•Section 9 contains all steps for downloading and executing your first DA14585/586 Applications.
5.1 Kit Content
The Basic Development Kit parts can be ordered via various distributors. The Basic Development Kit
contains the following:
• Bluetooth low energy Board
• Mini USB-cable
• Coin cell battery (CR2032)
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
The basic Development Kit consists of a single basic Board containing the DA14585/586 BLE SoC in
QFN40 package. For the schematics and layout of the board in full detail, please refer to the respective
documents on the portal.
6.1 The Basic Kit board
Figure 1 illustrates the physical layout of the Basic Kit board. The basic Kit board provides the
necessary hardware to enable:
• Full digital connectivity with external hardware using UART, SPI, GPIO, and I2C
• USB based debugging capabilities using the SEGGER J-Link on-board debugger
Figure 1: The DA14585/586 Basic Kit
6.2 Configuring the Basic Kit Board by Jumper Settings
The DA14585/586 supports booting from UART. The jumper settings are displayed below:
Figure 2: The DA14585/586 Basic Kit Jumper Setting
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
Figure 3 shows the layout of the header jumper, J4.
Figure 3: Jumper 4 Layout
Note: Please notice that the signals connected on the DA14585/586 SoC are located on the left
pins row of header J4 as shown in Figure 4.
Figure 4: Data direction of UART within J4
Note:
UART connectivity is enabled by shorting header as presented in Figure 2.
UART connection between DA14585/586 and the MCU that provides communication
over USB to a PC is realized through P0_4, P0_5 (for null mode), P0_6 and P0_7 (for full
UART).
For DA14585, data flash through SPI connectivity is enabled with the jumper configuration which is
presented in Figure 5.
Please notice that for DA14586, this configuration is meaningless and it must be avoided. DA14586
SoC incorporates the flash internally (2Mbits).
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
•U1: Dialog BLE SoC, DA14585 or DA14586 in QFN40 package. DCDC converter of SoC is
configured in Buck mode. Two crystals are used, 16MHz and 32.768 KHz.
•U5 or U7: SPI data flash, MX25R2035. Two packages are available, U5 –WSON
MX25R2035FM1IH0 and U7-SOIC8 - MX25R2035FZUIL0 – (default). For DA14586, flash
memory is not mounted.
•U4: MCU where Segger license is applied. UART and JTAG connectivity is provided to
DA14585/586 SoC
• SW1: Reset push button. By pressing the button, used can hardware reset the processor
• J4: 28 pins header. Signal and power pins of DA14585/586 are provided. Also the interconnection
between BLE processor and Segger license MCU for JTAG and UART is done through jumpers.
•J5: 3 pins connector. DA14585/586 can be supplied by either 3.3V generated from on the
development kit or by coin cell battery applied on the bottom side of the development kit.
• J9: two pins header. It enables user LED. LED is driven from P1_0.
• J10: 10 pins header. It is used for monitoring DA14585/586 port 2 pins.
• J11: 10 pins header. Only P3_0 is provided on pin 1. Please notice that for DA14586, P3_0 is
not used.
Note: The schematic diagrams, BOM, and Gerber files are illustrated in detail in the
Development Kit Documentation.
6.4 Connecting the Basic Kit to the host PC
The Basic Kit includes an embedded J-Link debugger which allow easy communication with the
development host over USB.
The DA14585/586 SoC is configured only in Buck mode on this development kit. A choice can be made
between 3.3 V (via USB: J5 1-2) or VDD (a coin cell: J5 2-3). No battery is needed when running via
the mini-USB cable.
Note: The basic Kit is connected to the host PC over the connector marked as USB (J3), as
shown in Figure 6 using a standard mini-USB cable.
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
This section describes the installation procedure for the drivers, the configuration of the serial port, and
all necessary steps to verify the connection with the PC. It also provides solutions to problems that
may occur.
7.1 Requirements of the Development PC
For proper evaluation and application development using the DA14585/586 SoC and the Basic
Development Kit, an external host is required. This external host must have a Windows already
installed and USB ports as described in Section 6.
7.2 Driver Installation
On first connection to a host PC running Microsoft Windows, the system will detect several devices
and will automatically install all necessary drivers. If the system is configured to use Windows Update,
this may take several minutes to complete.
When the driver installation is complete, the system displays a window similar to the one presented in
Figure 7.
Figure 7: Windows Driver Installation
There is one virtual COM port created by the Windows driver. This COM port (COM28 in this example)
provides a UART interface between the PC and the DA14585/586 device. For current measurement
please refer to the Figure 36 in Appendix C.
You can find also more information about the Power Profiler, see the SmartSnippets Toolbox User
Manual (UM-B-083).
Note: The COM port number assigned to the might be different to the one shown in Figure 7.
The COM port number can be found in the Windows Device Manager (Control Panel > Device Manager
> Ports (COM & LPT)) as shown in Figure 8.
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
Several development tools require UART to be routed to the FTDI serial port. Refer to Figure 32 in
Appendix B for the Basic Development Kit board connection verification and on how to properly
configure the specific port.
7.3.1 Using Serial Port
To make sure that the communication between the board and the Windows development host is
properly established, it is necessary to verify the UART connection between the two nodes.
On the Windows host, Tera Term can be used to validate the connection to the by Basic Development
Kit following these steps:
1. Connect the Basic Development Kit board to the PC via USB cable. The location of the board's
USB port is shown in Figure 6.
2. Use the Windows Device Manager to verify that the host discovered the COM28 serial port in this
case. See Figure 8.
3. Open Tera Term from the Windows Start menu as shown in Figure 9.
Figure 9: Start Tera Term
4. In the Tera Term: New connection dialog, select Serial, then select the COM Port to use, and
click OK.
5. Select Setup > Serial Port and configure your UART port using the parameters shown in Table 1
(you need to be an administrator on your local machine), see Figure 10.
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
Figure 10: Setting Up the Port and Testing Connectivity via Tera Term
7.4 Troubleshooting
If there are any problems with the connection to PC some possible solutions might be:
• Check for possible cabling issues by using a different USB cable.
• Connect the two elements using a different USB port on the host PC.
Note: If none of these actions resolve the issue, please contact Dialog Tools Forums.
8 Software Development Tools
Dialog SmartSnippets™ Studio is a royalty-free software development platform for Smartbond™
devices. It fully supports the DA14585/586 family of devices.
For the DA14585/586, KEIL must be used for compilation and debug instead of using the supplied
SmartSnippets GNU ARM GCC. KEIL needs to be installed separately (it is not included).
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
• SmartSnippets™ Toolbox which covers all software development requirements, including:
– programming and loading of firmware into SRAM, OTP, and Flash
– power profiling
• SmartSnippets™ documentation
The SmartSnippets™ IDE is enabled by an on-board J-Link debugger from SEGGER. This offers
standard debug capabilities such as single stepping, setting breakpoints, software download and many
more. For more details on the debugger capabilities, visit https://www.segger.com/.
8.1 SmartSnippets™ Installation
The installation procedure for SmartSnippets™ Studio is described in detail in UM-B-057
SmartSnippets Studio User Manual.
A summary of the steps is given here.
1. Download the latest version of SmartSnippets™ Studio from Software and tools, as shown
Figure 11.
Figure 11: SmartSnippets Studio Install Link
2. Run the SmartSnippets™ Studio installer (.msi). Several of the required tools are automatically
installed, others need to be manually downloaded and installed.
3. Select to install the latest version of SEGGER J-Link GDB server and click Next.
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
KEIL µVision IDE must be downloaded and installed separately, registration is required.
1. Download and install the Keil tools from https://www.keil.com/demo/eval/arm.htm.
Note: The Keil development tools can be run as a Lite/Evaluation version without a product
license, see Figure 14 (File > License Management). This Lite/Evaluation version has a 32 kB of
code (in ROM) limitation.
Figure 14: Keil Lite version
2. When the install is complete, a list of packs is shown, see Figure 15. If you do not see this list:
a. Click the Packs Installer button (or select Project > Manage > Pack Installer).
b. Click the Check for Updates button to show an updated list of packs.
3. Click on the Install or Updatebutton next to the “ARM::CMSIS” package if it is not up to date.
Figure 15: CMSIS Package Installation
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
If the installation was successful, the Pack Installer window will show the summary displayed in Figure
16.
Figure 16: CMSIS Package Installation Successful
9 Build a DA14585/586 Application
This section explains how the user can build, program, and run a simple software application on the
board.
It provides step-by-step instructions for loading the example as a project in the Keil environment, setting
it up and building it, and finally executing it via the debug environment on any of the DA14585/586
devices.
Make sure that you have all required tools installed as described in Section 7 and Section 8.
The DA14585/586 Software Development Kit (SDK) includes examples running on the Pro and the
Basic Development Kits. The examples are provided with preconfigured KEIL projects.
The SDK zip archive is downloaded from the customer support web page.
More details are provided in the DA14585 & DA14586 Software Developer's Guide (UM-B-080).
9.1 The Blinky Peripheral Example Application
Blinky is a simple application which demonstrates basic initialization of DA14585/586 and LED blinking.
After downloading the SDK, the blinky source code example can be found in the directory called
peripheral_examples.
1. Open the folder containing the SDK files. This is the folder where you extracted the SDK zip file.
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
When the blinky message is displayed on your UART terminal screen and the green LED is blinking
you have successfully programmed and started the blinky program on DA14585/586 Demo board.
Figure 27: Blinky Project: Blinky message on COM28 terminal
9.2 The Barebone BLE Example Application
The Barebone BLE example application demonstrates basic BLE procedures such as advertising,
connection, updating connection parameters, and implementation of the Device Information Service
Server (DISS). See the Bluetooth SIG for more details.
1. Open the folder containing the SDK files. This is the folder where you extracted the SDK zip file.
2. In <sdk_root_directory>\projects\target_apps\ble_examples\ble_app_barebone\Keil_5, double-
click ble_app_barebone.uvproj to open the project in Keil.
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
Figure 30: Barebone BLE: Interacting with BLE Application
Your BLE application is now running and advertising using the default advertiser string: "DIALOGBRBN".
Note: In this example, we used an Android application but you can also use the LightBlue iOS
application to connect an iPad/iPod/iPhone device to the application.
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
•If you can't see any blinky messages in your UART terminal and the LED is not blinking, check
the UART and LED jumper configuration, see Table 2. You can also make sure that the hardware
configuration is set for, see Figure 31 in Appendix A
Table 2: Blinky Example UART and LED Jumper Configuration
If you can't start a debug session, check the SWD debugger jumper configuration, see Table 3.
Table 3: Blinky Example SWD Debugger Jumper Configuration
If you have trouble with the J-link firmware or any issue with SDK operation, refer to the DA1458x/68x
Development Kit J-Link Interface Application Note AN-B-052.
Note: If none of these actions resolved the issue, please contact Dialog Software Forum.
9.4 What Next ?
This tutorial does not cover all the topics relevant to software development environments, it describes
the first steps necessary to get started with the Pro Development Kit. The following links provide more
information on DA14585/586:
• DA14585 Product Brief: To know more about the SmartBond™ DA14585 SoC.
• DA14586 Product Brief: To know more about the SmartBond™ DA14586 SoC.
• UM-B-079: DA14585/586 SDK 6 Software Platform Reference: To know more about software
architecture.
•UM-B-080: DA14585/586 SDK 6 Software Developer’s Guide: To build more BLE and peripheral
examples.
• Codeless Tutorial: To quick start your IoT application and learn more about AT commands.
• Sleep mode configurations and power measurement: To learn more DA14585/586 Power
management.
•Application Hardware Design Guideline : To learn how to prepare schematics and PCB layouts
for your application.
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
The user_periph_setup.h file contains hardware settings related to the used. The default is the
ProDev Kit.
Figure 31: Hardware Settings for Basic Development Kit
10.2 Appendix B: Latency Timer of the FTDI cable
If an external FTDI cable is used to burn the OTP (or to download the image into the external memory),
the latency timer of the FTDI cable has to be changed from 15 ms to <10 ms.
To change the latency timer:
1. In the Windows Device Manager, expand the list of COM ports.
2. Right click on the required COM port and select Properties.
3. In the Port Settings tab, click Advanced.
4. Set the Latency Timer to < 10 ms.
Figure 32: FTDI Latency Timer
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
10.3 Appendix C: Power Management: measuring current
The design of the DA14585 and DA14586 Basic Development Kit is made in such a way that the
microcontroller can be isolated completely from the rest of the board. This is illustrated in the block
diagram shown in Figure 33 and Figure 34 that showing the connections of the jumpers J4, J5 and
J6.
Figure 33: Setup of DA14585 Basic Development Kit during power measurement
Figure 34: Setup of DA14586 Basic Development Kit during power measurement
UM-B-048
DA14585/DA14586 Getting Started Guide with the Basic Development Kit
First HTML released version. Keep only DA14585/586.
Status
Definition
DRAFT
The content of this document is under review and subject to formal approval,
which may result in modifications or additions.
APPROVED or
unmarked
The content of this document has been approved for publication.
11 Revision history
Table 4: Revision history
12 Status definitions
Table 5: Status Definitions
13 Disclaimer
Information in this document is believed to be accurate and reliable. However, Dialog Semiconductor
does not give any representations or warranties, expressed or implied, as to the accuracy or
completeness of such information. Dialog Semiconductor furthermore takes no responsibility
whatsoever for the content in this document if provided by any information source outside of Dialog
Semiconductor.
Dialog Semiconductor reserves the right to change without notice the information published in this
document, including without limitation the specification and the design of the related semiconductor
products, software and applications.
Applications, software, and semiconductor products described in this document are for illustrative
purposes only. Dialog Semiconductor makes no representation or warranty that such applications,
software and semiconductor products will be suitable for the specified use without further testing or
modification. Unless otherwise agreed in writing, such testing or modification is the sole responsibility
of the customer and Dialog Semiconductor excludes all liability in this respect.
Customer notes that nothing in this document may be construed as a license for customer to use the
Dialog Semiconductor products, software and applications referred to in this document. Such license
must be separately sought by customer with Dialog Semiconductor.
All use of Dialog Semiconductor products, software and applications referred to in this document are
subject to Dialog Semiconductor’s Standard Terms and Conditions of Sale, unless otherwise stated.
Dialog and the Dialog logo are trademarks of Dialog Semiconductor plc or its subsidiaries. All other
product or service names are the property of their respective owners.
name
contacting-dialogsemiconductor
:class: ContactHeading
United Kingdom
(Headquarters)
Dialog Semiconductor
PLC
Phone: +44 1793 757700
Germany
Dialog Semiconductor
GmbH
Phone: +49 7021 805-0
The Netherlands
Dialog Semiconductor
B.V.
Phone: +31 73 640 8822
North America
Dialog Semiconductor
Inc.
Phone: +1 408 845
8500
Japan
Dialog Semiconductor
K. K.
Phone: +81 3 5769
5100
Taiwan
Dialog Semiconductor
Taiwan
Phone: +886 281 786
222
Hong Kong
Dialog
Semiconductor Hong
Kong
Phone: +852 2607
4271
Korea
Dialog
Semiconductor
Korea
Phone: +82 2 3469
8200
China (Shenzen)
Dialog
Semiconductor
China
Phone: +86 755
2981 3669
China (Shanghai)
Dialog
Semiconductor
China
Phone: +86 21
5424 9058
Email:
enquiry@diasemi.com
Web site:
https://www.dialogsemiconducto
r.com/
Table 6: Dialog Semiconductor
14 RoHS Compliance
Dialog Semiconductor complies to European Directive 2001/95/EC and from 2 January 2013 onwards
to European Directive 2011/65/EU concerning Restriction of Hazardous Substances (RoHS/RoHS2).
Dialog Semiconductor’s statement on RoHS can be found on the DA1458x RoHS 2 declaration. RoHS
certificates from our suppliers are available on request.
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.