Skip to main content

SmartBond DA14530 and DA14531

The world’s smallest and lowest power Bluetooth 5.1 System-on-Chip

DA14530 and DA15531 Diagram

The SmartBond TINY™ DA14530 and DA14531 are the Bluetooth® low energy solution to power the next 1 billion IoT devices

SmartBond TINY™, the world’s smallest and lowest power Bluetooth 5.1 System-on-Chip, brings down the cost of adding Bluetooth low energy in any system to $0.50 in high volumes.

This awesome combination takes mobile connectivity to places previously out of reach, triggering a wave of a billion IoT devices, all with SmartBond TINY at the heart.

The low system cost is achieved through the high level of integration in SmartBond TINY: a complete Bluetooth low energy system can be achieved with the addition of 6 tiny external passives, a crystal and power source. And to lower the barrier of entry, SmartBond TINY will also be available in an easy-to-use tiny module incorporating all the needed components, making the addition of Bluetooth low energy to any application a simple drop-in.

Record low hibernation and active power consumption ensure long operating and shelf life with even the tiniest, disposable batteries. Based on a powerful 32-bit arm Cortex M0+ with integrated memories and a complete set of analog and digital peripherals, SmartBond TINY is extremely power efficient, delivering a record score of 18300 on the latest EEMBC benchmark for IoT connectivity, IoTMark™. Available in a tiny 2.0 x 1.7 mm package, the DA14531 is half the size of its predecessor, or any offering from other leading manufacturers. And it is complemented by a flexible SDK supporting major compilers such as Keil and GCC out of the box. The DA14530 is pin for pin compatible with DA14531 in a 2.2x3.0mm FCGQFN24 package and provides cost savings by operating from an internal LDO, eliminating the cost of a DC-DC inductor.

Lifecycle status

● Active

Benefits

Future proof, compliant with Bluetooth 5.1 (core)

Optimized for disposable products in connected medical, connected consumer

  • Designed to work with disposable, even printed batteries
  • Works well with smallest capacity batteries, <<30mAh
  • Supports multiple years of shelf life
  • Inrush current can be limited for disposable batteries with high internal resistance
  • Package design allows for low cost manufacturing with smallest possible footprint

Only requiring a single 32MHz crystal

In bypass mode no DC-DC inductor required

No boost converter required when working with 1.5V batteries

Production Line Tool for accelerated production ramp up, resulting in faster time to market and shortest production test time per device

Applications

Connected consumer:
Beacons, Smart labels, Remote controls, Proximity tags, Connected watches, Stylus pens, Mouse, Toys, Low power sensors, Bluetooth LE add on “BLE pipe” to existing applications

Connected medical:
Connected injectors, Inhalers, Glucose monitors, Smart patches, Blood pressure meters, Thermometers

Automotive:
Tire Pressure, Monitoring Systems and low power wireless sensors

Package

FCGQFN24, 2.2x3x0.4

WLCSP17, 1.7x2.05x0.5

Every quarter, we bundle up the best technical info on our products, software development topics, trainings, events and deliver it to your inbox.

Sign me up
Check out previous editions

Stay connected

Get in touch with us directly through our worldwide sales offices, or contact one of our global distributors and representatives.

Inquiries Distributors and Representatives Register for newsletters
Datasheet
Name Date Version
AN-B-088: DA145xx Flash Selector Guide (163.89 KB) 30/06/2021 1.3
DA14530 datasheet (4.26 MB) 30/08/2021 3.3
DA14531 Datasheet (4.72 MB) 30/08/2021 3.4
Product Brief
Name Date Version
DA14531 SmartBond TINY Product Brief (1.66 MB) 04/11/2019 1.0
DA14531 Smartbond Tiny Product Brief (Chinese) (1.76 MB) 04/11/2019 1.0
SDK
Name Date Version
SDK6.0.14.1114 for DA14531 and DA14585/6 (9.45 MB) (Registered users only) 29/04/2020 SDK6.0.14.1114
SDK_6.0.14.1114_hotfix_001 (6.31 MB) (Registered users only) 15/07/2020 SDK_6.0.14.1114_hotfix_001
SW-B-002 DA14531 SDK Release Notes v.6.0.14.1114 (315.84 KB) (Registered users only) 29/04/2020 SDK6.0.14.1114
SDK User Manual
Name Date Version
DA145xx SDK6 API Documentation (Doxygen) (5.42 MB) 29/04/2020 SDK6.0.14.1114
SDK6 Known Limitations List (25.09 KB) 29/04/2021 1.0
UM-B-117: DA14531 Getting Started with the Pro Development Kit (HTML) (25.09 KB) 30/03/2020 1.2
UM-B-117: [Chinese] DA14531 Getting Started with the Pro Development Kit (HTML) (25.09 KB) 30/03/2020 1.2
UM-B-118: DA14585-DA14531 SDK Porting Guide (25.09 KB) 29/04/2020 1.2
UM-B-119: DA14585-DA14531 SW Platform Reference (25.09 KB) 10/04/2020 2.0
UM-B-143 Dialog External Processor Interface (6.15 MB) 11/12/2020 0.2
UM-B-146-DA14585-DA14531-HCI Commands (778.48 KB) 10/11/2020 1.0
UM-B-151: Extending flash support for DA14531 (25.09 KB) 22/04/2021 1.0
Development Tools
Name Date Version
Dialog Smartbond Flash Programmer for Linux OS (8.13 KB) 28/04/2021 1.0.6.3884
Dialog Smartbond Flash Programmer for mac OS (623.67 KB) 28/04/2021 1.0.6.3884
Dialog Smartbond Flash Programmer for Windows OS (4.57 MB) 10/08/2021 1.0.6.3886
SmartSnippets Studio Release Notes (304.81 KB) 04/02/2021 2.0.16
SmartSnippets Studio V2.0.16 for Linux OS (872.03 MB) 04/02/2021 2.0.16
SmartSnippets Studio V2.0.16 for macOS (497.78 MB) 04/02/2021 2.0.16
SmartSnippets Studio V2.0.16 for Windows OS (707.61 MB) 04/02/2021 2.0.16
SmartSnippets Toolbox Release Notes (461.34 KB) 04/02/2021 5.0.16
SmartSnippets Toolbox V5.0.16 for for Linux OS (163.27 MB) 04/02/2021 5.0.16
SmartSnippets Toolbox V5.0.16 for Windows OS (123.77 MB) 04/02/2021 5.0.16
UM-B-057 SmartSnippets Studio User Manual (3.07 MB) 04/02/2021 2.0.16
UM-B-083 SmartSnippets Toolbox User Manual (HTML) (25.09 KB) 04/02/2021 5.0.16
UM-B-138: Programming flash User Manual (HTML) (25.09 KB) 24/03/2020 1.0
Software Applications & Examples
Name Date Version
Clone Github example Repository (25.09 KB)
DA14531 SUOTA via STM32 (25.09 KB) 11/01/2021 1.1
Dialog Serial Port Service (DSPS) (7.58 KB)
SmartBond™ - CodeLess AT Commands (7.58 KB)
Social Distancing Tags (25.09 KB)
Hardware Design Examples
Name Date Version
DA14531 QFN/Boost Hardware Design Example (505.61 KB) 29/07/2020 1.0
DA14531 QFN/Buck Hardware Design Example (487.49 KB) 29/07/2020 1.0
DA14531 QFN/BypassHardware Design Example (484.73 KB) 29/07/2020 1.0
DA14531 WLCSP /Boost Hardware Design Example (527.56 KB) 15/09/2020 1.0
DA14531 WLCSP/ Buck Hardware Design Example (511.04 KB) 15/09/2020 1.0
DA14531 WLCSP/Bypass Hardware Design Example (505.63 KB) 15/09/2020 1.0
Hardware design example guide (25.09 KB) 15/09/2020 1.1
Mobile Apps
Name Date Version
Dialog SUOTA - Source Code - Android (3.03 MB) (Registered users only) 04/05/2020 3.190.18
Dialog SUOTA - Source Code - iOS (4.11 MB) (Registered users only) 04/05/2020 3.200.14
Production Line Tool Kit
Name Date Version
Production Line Tool documents (7.58 KB)
Application Notes
Name Date Version
AN-B-027: Designing Printed Antennas for Bluetooth Smart (1.64 MB) 25/06/2020 2.3
AN-B-027: Designing Printed Antennas: DXF files (12.38 KB) 04/04/2017 1.0
AN-B-072: DA14531 Booting from OTP and Serial Interfaces (1.99 MB) 02/09/2021 1.8
AN-B-073: DA14531 Filter for Spurious Emissions Reduction (660.23 KB) 04/11/2019 1.2
AN-B-075: DA14531 Hardware Guidelines (2.77 MB) 17/09/2021 1.6
AN-B-077: DA14531 Bluetooth Direct Test Mode (1.88 MB) 17/03/2020 1.2
White Papers
Name Date Version
Implementing Bluetooth LE Data Pumps (514.18 KB) 04/11/2019 Rev A
Implementing Bluetooth LE Data Pumps (Chinese) (613.3 KB) 04/11/2019 1.0
Motion aware thin Bluetooth LE beacon solution for smart labels (984.86 KB) 13/07/2021 1.1
Tutorials
Name Date Version
BLE Advertising Tutorial (HTML) (25.09 KB) 25/10/2019 1.0
BLE Security on DA145x devices (25.09 KB) 28/04/2020 2.0
BLE SUOTA Update on DA14585/DA14586 and DA14531 Devices (25.09 KB) 13/07/2021 2.2
CHINESE DA14531 FAQs (HTML) (25.09 KB) 24/03/2021 1.1
CHINESE DA14531 FAQs (PDF) (1.12 MB) 24/03/2021 1.1
Create a Custom GATT Profile Characteristic on DA14531 and DA14585/DA14586 devices (25.09 KB) 01/04/2020 2.0
DA14531 Sleep Mode Tutorial (HTML) (25.09 KB) 08/04/2021 1.3
DA14531_FAQs (HTML) (25.09 KB) 24/03/2021 1.1
DA14531_FAQs (PDF) (701.88 KB) 24/03/2021 1.1
Getting Started with SDK6 (HTML) (25.09 KB) 07/05/2021 2.1
Tutorial 6 : SUOTA TOOL ZIP FILE (92.68 KB) 24/05/2018 1.0
Using SDK6 Peripheral Drivers (HTML) (25.09 KB) 05/03/2021 1.6
Hardware Design Collateral
Name Date Version
DA14531 17-XFBGA, WLCSP Symbols & footprints (25.09 KB) 13/03/2020 1.0
DA14531 FCGQFN24 Symbols & footprints (25.09 KB) 13/03/2020 1.0
Known limitation list
Name Date Version
DA14531 Errata DataSheet (182.04 KB) 01/11/2019 1.0
FCC, ETSI certifications
Name Date Version
DA14531 EN 300 328 certification test report (WLCSP) (1.2 MB) 04/11/2019 1.0
DA14531 EN 300 328 certification test report (QFN) (1.21 MB) 04/11/2019 1.0
DA14531 FCC certification test report (QFN) (1.85 MB) 09/04/2019 1.0
DA14531 FCC certification test report (WLCSP) (1.84 MB) 09/05/2019 1.0
BT SIG certifications
Name Date Version
DA14530: Profile Subsystem (7.58 KB) 25/08/2020 D051783
DA14531: QDID Controller Subsystem (7.58 KB) 08/08/2019 D047135
DA14531: QDID Host Subsystem (7.58 KB) 27/08/2019 D047136
DA14531: QDID Profile Subsystem (7.58 KB) 31/10/2019 D048316
Other Certifications
Name Date Version
DA14531: Bluetooth Low Energy RF-PHY Test Specification (1.04 MB) 08/08/2019 62000RBT.001
RoHS and Reach
Name Date Version
DA14531 REACH declaration (163.83 KB) 04/11/2019 1.0
DA14531 RoHS declaration (163.83 KB) 04/11/2019 1.0
Previous Software Releases
Name Date Version
SmartSnippets Toolbox V5.0.12 for Windows OS (1 byte) 14/03/2020 5.0.12
Archive
Name Date Version
Dialog SUOTA - Source Code - Android (2.86 MB) (Registered users only) 24/10/2019 3.190.16
Dialog SUOTA - Source Code - iOS (4.09 MB) (Registered users only) 29/10/2019 3.200.12
SDK_6.0.12.1020.2 for DA14531 and DA14585/6 [Including SDK APIs Documentation] (9.18 MB) (Registered users only) 12/12/2019 6.0.12.1020.2
SDK_6.0.12.1020.2_hotfix_001 (90.61 KB) (Registered users only) 06/03/2020 6.0.12.1020.2
SmartSnippets Studio V2.0.10 for Linux OS (810.84 MB) 02/10/2019 2.0.10
SmartSnippets Studio V2.0.10 for Windows OS (575.68 MB) 02/10/2019 2.0.10
SmartSnippets Studio V2.0.12 for Linux OS (1 byte) 14/03/2020 2.0.12
SmartSnippets Studio V2.0.12 for Windows OS (1 byte) 14/03/2020 2.0.12
SmartSnippets Studio V2.0.14 for Linux OS (870.09 MB) 28/05/2020 2.0.14
SmartSnippets Studio V2.0.14 for macOS (496.8 MB) 28/05/2020 2.0.14
SmartSnippets Studio V2.0.14 for Windows OS (705.78 MB) 28/05/2020 2.0.14
SmartSnippets Toolbox V5.0.10 for for Linux OS (205.02 MB) 02/10/2019 5.0.10
SmartSnippets Toolbox V5.0.10 for Windows OS (137.45 MB) 02/10/2019 5.0.10
SmartSnippets Toolbox V5.0.12 for for Linux OS (1 byte) 14/03/2020 5.0.12
SmartSnippets Toolbox V5.0.14 for for Linux OS (162.73 MB) 28/05/2020 5.0.14
SmartSnippets Toolbox V5.0.14 for Windows OS (123.2 MB) 28/05/2020 5.0.14
SW-B-002 DA14531 SDK Release Notes v.6.0.12.1020.2 (179.09 KB) 12/12/2019 6.0.12.1020.2

Development Kits and Reference Designs

Hardware Development Kits based on DA14531
Development Kit – USB
Development Kit – Pro
SmartBond Wireless Ranging SDK
Video thumbnail, click to open and play

DA14531 product overview video

Video thumbnail, click to open and play

Production Line Tool Kit Webinar

Video thumbnail, click to open and play

MikroBUS Click Board Webinar

Video thumbnail, click to open and play

IoT Podcast

Module Key features  
DA14531 / SmartBond TINY Module
  • Bluetooth 5.1 core qualified
  • Integrated antenna
  • Worldwide certification
  • Cortex-M0+ @16MHz
  • IoTMark™-BLE score of 18300
  • 23.75uA/MHz MCU current
  • Memory: 48kB RAM, 32kB OTP &1Mb FLASH
  • 1.8-3.3V Supply Range
  • +2.2dBM max output power
  • -93dBm sensitivity
  • Rx current 2mA at 3V
  • Tx current 4mA at 3V at 0dBm
  • Interfaces: 2xUART, SPI, I2C
  • 4-channel 10-bit ADC
  • 8 GPIO
  • Built-in temperature sensor
  • Operating temperature: -40°C to +85°C
  • Dimensions: 12.5x14.5x2.8 mm
Buy now from Digikey
Buy now from Avnet
DA16600 Modules
  • Low Power Wi-Fi
  • Low Power BLE
  • Ultra Low Power
  • Superior Range
Contact us
DA14531 BDE-BLEM301
  • Bluetooth 5.1 qualified (Bluetooth DID: D050903)
  • FCC/CE/RoHS certified
  • Integrated high efficiency Antenna
  • Supports up to 3 BLE connections
  • 16 MHz 32-bit Arm® Cortex® M0+
  • Memories: 1Mbit Flash, 48KB RAM, 144KB ROM, 32KB OTP
  • Rx current 2mA at 3V
  • Tx current 4mA at 3V at 0dBm
  • 1.8uA at sleep with all RAM retained
  • Programmable Tx power from -19dBm to +2.2 dBm
  • -93 dBm receiver sensitivity
  • Quadrature decoder with 3 channels
  • 4 channel 11-bit ENOB ADC
  • 2 timers with PWM capabilities
  • Real Time Clock
  • Built in temperature sensor
  • Interfaces: 9 GPIOs, SPI, 2xUART, I2C
  • Operation: 1.8V - 3.3V, -40°C to +85°C
  • Dimensions: 12.5x14.5x2.1 mm
  • Compatible with Dialog DA14531MOD
Contact your local Dialog sales representative or email BDE: info@bdecomm.com  
DA14531 Hongjia HJ-531IMF
  • Size: 5 x 4.75 x 1.3mm
  • Package: LGA25
  • GPIOs: 12
  • Supply voltage: 1.1V-3.6V
  • TX < 3.5mA; RX < 2.2 mA
  • Built-in high-performance antenna (External antenna can also be used)
  • On-board antenna range: 10-20m; External antenna range: 30-80m
  • Support BLE 5.1, support WeChat, MiSDK and user develop
  • Built-in 1Mb FLASH, support OTA, Store user data
  • Operating temperature: - -40℃ to +85℃
Buy Now
DA14531 Honjia HJ-131IMH
  • Size: 4 x 4 x 1.3mm
  • Built-in high-performance antenna (External antenna can also be used)
  • Package: LGA17
  • GPIOs: 6
  • Supply voltage: 1.1V-3.6V
  • TX < 3.5mA; RX < 2.2 mA
  • On-board antenna range: 10-20m; External antenna range: 30-80m
  • Support BLE 5.1, support WeChat, MiSDK and user develop
  • Built-in 1Mb FLASH, support OTA, Store user data
Buy Now

Buy now

Product Shop
DA14531-00000OG2 WLCSP17 package Mouser Digikey
DA14531-00000FX2 FCGQFN24 package Avnet US Mouser Digikey
DA14531-00FXDEVKT-P Mouser Digikey
DA14531-00OGDB-P Mouser Digikey
DA14531-00FXDB-P Mouser Digikey
DA14531-00FXDEVKT-U Mouser Digikey
Back to results

DA14530 and DA14531

2 months ago

Multiple files, which contain SPI_DI_PIN macro (#define)

Posted by joachimkr 20 points 4 replies
0 upvotes

Hello,

I am in hardware verification for an own board, being home for a DA14531 and some SPI hardware.
During this process I needed to define, where my SPI interface pads have to be.
Here is, what I understood:

During a flash memory boot, the Pin 1 of  Port 0 is the CS (chip select) for a flash memory. I need this flash memory. Currently, I never burned content, but debugged with the segger chip interface.

For my peripheral, I therefore needed to use a different port pin, to get a working CS for that. I used pin 7. Because my peripheral is compatible to the macronix flash, I can use the same polarities and frequency, no trouble.

Now, during verification, I came into some trouble and tried to use a different port pin. What popped up was, that I find 3 locations in the 'BLE peripheral' example file set, where Pins are mapped by using macros and I get into trouble to understand that.

I found these three files to contain a macro set for defining pads for SPI_EN, SPI_DI, SPI_DO,SPI_CLK pins  :

1. user_periph_setup.h

2. user_spi_periph_setup.h

3. user_peripheral.h

Initially, the CS was defined to be Port 0 Pin 1 and I just changed that to pin 7, in order to get my debugging job done.
But now, I need to really understand the steps and usage. So at first, I am confused, where I need to set the #define macro to set the used pin. 

During boot, I understood (is it correct?) the CPU uses CS on pin 1 and I can expect flash content is copied to RAM and executed. I cannot alter that, so I wired this CS from flash to port pin 1.
During my program run, I need port pin 7 to be used for my peripheral.

But what, if I need to write something to flash during program run? I have just one macro name but 3 locations, where this is defined. 
What I saw, looked like a use of this pin number to be written to some structure, which is used by the SPI driver. 

Please explain to me, what is the correct way, to define a second device, using a different pin then pin 1 as CS. How can I switch between devices?

I would be lucky, to finally understand that,
Best regards,
Joachim

2 months ago

PM_Dialog

Hi Joachim,

Thanks for posting our public forums.

The DA14531 boots from standard pins as described in the Booting sequence. Please see Table 1 in the following application note : https://www.dialog-semiconductor.com/sites/default/files/2021-01/AN-B-072-DA14531_Booting_options_v1.5.pdf

Booting from an external SPI Slave is step # 5 from the Booting sequence and so the chips boots from the pins below :

MOSI - P0_0

SCS - P0_1

MISO - P0_3

SCK - P0_4

So, if you would like to boot from flash, it should be populated in those pins.

After the DA14531 boots, this depends on the application. Do you need to interact with the SPI Flash? If yes, you should configure those pins for the flash ( same as in the BLE peripheral project)

For the SPI Peripheral device, you should configure in the SW the SPI pins that is connected to the DA14531.

So, if I understood correctly, your question is in which pins you should place the SPI Peripheral and how you can configure them in your SW?  

You can select any of the available GPIOs. For example, if it is connected to those pins :

PERIPHERAL_MOSI – P0_5

PERIPHERAL_SCS – P_7

PERIPHERAL_MISO –P0_6

PERIPHERAL_SCK - P0_8

In user_periph_setup.h :

    #define SPI_EN_ PERIPHERAL_PORT             GPIO_PORT_0

    #define SPI_EN_ PERIPHERAL_PIN              GPIO_PIN_7

 

    #define SPI_CLK_PERIPHERAL_PORT            GPIO_PORT_0

    #define SPI_CLK_ PERIPHERAL_PIN             GPIO_PIN_8

 

    #define SPI_DO_ PERIPHERAL_PORT             GPIO_PORT_0

    #define SPI_DO_ PERIPHERAL_PIN              GPIO_PIN_5

 

    #define SPI_DI_ PERIPHERAL_PORT             GPIO_PORT_0

    #define SPI_DI_ PERIPHERAL_PIN              GPIO_PIN_6

 

And then configure then accordingly in set_pad_functions() and GPIO_reservations().

If I misunderstood what is your exact requirement, please let me know.

Thanks, PM_Dialog

2 months ago

joachimkr 20 points

Hello, Thanks for prompt response!

I understood, what you wrote. You propose, to introduce a new set of macros. 

What I do not understand is, how I select at runtime, in my device drivers, the sets of pins. I need access to both. So I need to apply something like a switch between both sets.

In fact, the pins for MOSI, MISO, SCK are the same. Select needs to be different.

Why is the definition repeated in 3 files? How can I force the use of the correct select pin?

Thanks,

Joachim

1 month ago

PM_Dialog

Hi joachimkr,

Apologies for the delay. Can you please clarify this statement?

What I do not understand is, how I select at runtime, in my device drivers, the sets of pins. I need access to both.

>>Please take a look at the following SW example from our GHIT repo. This example demonstrates how to use SPI or I2C to interface with the LIS2DH accelerometer I assume this is similar to your application.

“Why is the definition repeated in 3 files? How can I force the use of the correct select pin? “”

>>Can you please indicate which SDK project you are using? Normally, we declare the Pin / Port in user_periph_setup.h and configure the GPIO accordingly in set_pad_functions() and GPIO_reservations().

http://lpccs-docs.dialog-semiconductor.com/Tutorial_SDK6/digital_out.html

http://lpccs-docs.dialog-semiconductor.com/Tutorial_SDK6/digital_in.html

Thanks, PM_Dialog

1 month ago

joachimkr 20 points

Hello, 

Thanks to answering my questions.

I started with an BLE project, I remember it's name, it was ble_app_peripheral.

It included driving the flash memory and an LED on the base-board, while offering different BLE services, including client notifications.

SDK version is 6.0.14.1114

Check it out, you will find the pin *number* usage macros in three files

1. user_periph_setup.h

2. user_spi_periph_setup.h

3. user_peripheral.h

I did not create them, they are part of the sdk example. I would be happy, to clean this up, not loosing the flash memory functions.

I additionally use more pins on my board and modified set_pad_functions() and GPIO_reservations().

Greetings,

Joachim