SmartBond™ DA14585 and DA14586
SmartBond 5.0: smarter, more flexible, and even lower power
Connected devices are constantly evolving. New generations appear that are smarter, more full featured and have longer battery lifetimes. To enable this, SmartBond has evolved too. The DA14585 and DA14586 offer designers all the benefits of the industry-leading DA14580 but with even greater flexibility to create more advanced applications from the smallest footprints and power budgets.
为对话框的一部分SmartBond家庭,DA14585&6 are the smallest, lowest power and most integrated Bluetooth® solutions available. This versatile SoC’s are ideal for adding Bluetooth low energy to products like remote controls, proximity tags, beacons, connected medical devices and smart home nodes. It supports all Bluetooth developments up to and including Bluetooth 5 and Bluetooth low energy Mesh. Plus, with 96 kB of RAM, the DA14585&6 have double the memory for user applications of its predecessor to take full advantage of the standard’s features. It also includes an integrated microphone interface for voice support at low additional cost. The wide supply voltage range (0.9 –3.6 V) covering a larger choice of energy sources and gives full design flexibility.
SmartBond™ DA14586 combines the benefits of the lowest power, smallest size and lowest system cost Bluetooth low energy System-on-Chip with an integrated flash. Furthermore the DA14586 is pin to pin compatible with the DA14585 thereby offering a unique cost down path from flash to OTP.
Like all SmartBond solutions, the DA14585&6 are easy to design-in and supports standalone as well as hosted applications. It is supported by a complete development environment and Dialog’s SmartSnippets™ software that helps you optimize your software for power consumption.
Features
Complies to the Bluetooth 5 core specification
Integrated One-Time-Programmable memory
2 Mb Flash (DA14586)
Extended user RAM (96 kB)
Low operating voltage (1.8 V to 3.6 V)
I2C and PDM audio interfaces
Benefits
Large memory to build complex applications
Longest battery life
Suitable for Bluetooth Mesh
Low system Bill of Materials
亚博国际官网平台网址
Remote controls
Proximity tags and trackers
Beacons
Connected medical devices
Smart home
Human Interface Devices
VR controllers
Connected sensors
无线充电
Packages
QFN-40 (5.0 x 5.0 x 0.9 mm)
WLCSP-34 (2.4 x 2.66 x 0.39 mm)
Every quarter, we bundle up the best technical info on our products, software development topics, trainings, events and deliver it to your inbox.
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 newslettersDevelopment Kits and Reference Designs
Hardware Development Kits based on DA14585 and DA14586 |
---|
DA14585 Development Kit – Basic |
DA14585 Development Kit – Pro |
Hardware Application focused Development Kits based on DA14585 and DA14586 |
---|
DA14585 Voice RCU Development Kit |
DA14585 IoT Multi Sensor Development Kit |
Reference designs based on DA14585 and DA14586 |
---|
DA14585 Range Extender |
DA14585 Tile Reference Design |
Dialog SmartBond™ DA14586
Smallest, lowest power and most integrated Bluetooth 5 SoC with integrated Flash
SmartBond™ DA14585 Development Kit Basic
In this video, you can see how to set up the DA14585 Development Kit Basic and view some of it’s important features.
SmartBond™ DA14585 Development Kit Pro
Getting started with SmartBond™ DA14585 Development Kit Pro. This Development Kit gives you all the flexibility you need to develop your product with confidence, creating more advanced connected applications with the smallest footprints.
DA14585 IoT Multi Sensor Kit
Connect sensors to the cloud at the lowest power and smallest footprint with Dialog’s DA14585 IoT Multi Sensor Kit
SmartBond™ DA14585开发套件专业版
从此开始了解SmartBond™ DA14585开发套件专业版。这个开发套件为您提供了开发产品需要的所有灵活性,有助于您开发具有最小尺寸和最低功耗的更先进的连网应用。在此视频中,您将会了解开发套件专业版的内容和若干重要功能,以及了解Dialog开发工具和如何建立开发环境。
Production Line Tool Kit Webinar
Module | Key features | |
---|---|---|
DA14585 / AzureWave AW-CU362 |
|
Buy now |
DA14585 / Inventek ISM14585-L35 |
|
Buy now from Digi-Key Buy now from Mouser |
DA14585 / Panasonic / PAN1740A |
|
Buy now |
Buy now
Product | Shop | |||
---|---|---|---|---|
DA14585 | Digikey | Mouser | Avnet Silica | Avnet US |
DA14586 | Digikey | Mouser | Avnet Silica | Avnet US |
Production Line Tool Kit (PLT) | Avnet US |
2 weeks ago
DA14585 change Mac-Address if it's on OTP header
Posted byDarthdas10 points 1 replyGreetings!
The title is more a less self-explanatory. I have a BLE Device with DA14585 on it. And the Mac-Address is burned into OTP header.
Is there any way to bypass or ignore OTP Mac-Address programmatically in SmartSnippet or any other way?
Ideally, right now Im seeking a way to implement Random Mac-adress on these devices.
Is there any way to do this in current conditions?
2 weeks ago
Hi Darthdas,
Thanks for your question online. Since the BD address is hardcoded in the OTP Header and so the Bluetooth Device Address filed is not empty, there are the following probable solutions :
1. Use a hardcoded BDA in the SW, but some SDK modifications are needed. Please check the system-init() and line 1253 - otp_hdr_get_bd_address(). This function reads the BDA address from the OTP Header. Then, the nvds_get_func() will check if the there is a BD address in the OTP (case NVDS_TAG_BD_ADDRESS). If yes, (the dev_bdaddr is not blank), then the fw will use the BDA that is stored in the OTP. Otherwise, it will take the BDA from the NVDS( CFG_NVDS_TAG_BD_ADDRESS). So, a possible solution might be to explicitly set the dev_bdaddr to 0xFF (blank), so the fw will take the BD from the NVDS (CFG_NVDS_TAG_BD_ADDRESS).
2. Use Static Random BDA that is generated from a unique number in OTP. In this case you should set the USER_CFG_ADDRESS_MODE macro to APP_CFG_ADDR_STATIC in the user_config.h header file and place the default_app_generate_unique_static_random_addr() API in .app_on_generate_static_random_addr callback in user_callback_config.h file.
3. Use a public BDA in the OTP Header (in a different location). Again some modification are needed in the otp_hdr_get_bd_address(), as it reads from 0x7F87FD4. You will have to modify this address.
Thanks, PM_Dialog