Adding Sensors into DA14681 Wearable DK

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
4 posts / 0 new
Last post
Tue, 2019-09-24 18:49
#1
mrdobson
Offline
Last seen:1 year 4 months ago
Joined:2019-08-29 16:45
Adding Sensors into DA14681 Wearable DK

Hi,

To give some background, I'm working with the DA14681 Wearable Development Kit and version 1.0.8 of the wearable SDK. I am using the "target_apps\wrbl" project from the software dev kit as a template.

I am adding a new sensor via I2C and have built a working driver for the new device. I have been able to successfully read from (via printf statements to the UART) and write to registers on the sensor with a set of simple dummy functions that I run in main.c at boot.

I would like to activate the sensor and read from it on a timer, so I'm trying to add my sensor functions into the wrbl_task. I haven't been able to find where the existing sensors (ex. BME280, BMM150, etc.) perform their data read loops in the default wrbl project. Referencing revision 2.1 of the "DA14681 Wearable Development Kit Software Manual" shows where I can configure those devices, but no information on how they perform their data read in the wrbl_task heirarchy.

Are there any examples of adding sensors and other hardware to the wrbl template project? If not, where might I find the task implementation for the on-board peripherals such as the temp/hum/press sensor, gyro, etc?

Thanks very much!

Keywords:
wearable SDK DA14681
I2C peripheral
Device:
DA1468x
Wed, 2019-09-25 17:18
PM_Dialog
Offline
Last seen:2 days 12 hours ago
Staff
Joined:2018-02-08 11:03
Hi mrdobson,

Hi mrdobson,

Many thanks for your question online.

  1. For new designs, I would strongly recommend you the usage of DA14682 an d DA14683 SoCs. Please take a look at the support portal:

//www.xmece.com/products/connectivity/bluetooth-low-energy/smartbond-da14682-and-da14683

Secure boot is supported in DA14682/3 as well…

  1. As far as I understand, you have already started a new project based on DA14681 wearable reference application code which is on the top of SDK1.0.8. Please note that SDK1.0.8 is an old SDK version and it is not currently supported. To do so, I would suggest you to start a new project based on latest SDK version (SDK1.0.14). You can download it from our support website. You can read theStarting a Projectin order to find steps for starting a new project.
  2. 没有任何教程演示如何添加sensors and other hardware to the wrbl template project. Regarding the I2C, please take a look at theI2C Adapter Concept. If you need further steps for setting up a timer please let me know.

Thanks, PM_Dialog

Wed, 2019-09-25 19:13
(Reply to #2)
mrdobson
Offline
Last seen:1 year 4 months ago
Joined:2019-08-29 16:45
Hi PM_Dialog,

Hi PM_Dialog,

Thank you very much for your response and suggestions. I've gone ahead and ported my project over to the newer 1.0.14 SDK.

I did have a follow-up question to your response (3) if possible. In the "DA14681 Wearable Development Kit Software Manual" the Health Toolbox Task is described as a FreeRTOS-task-based framework that can coordinate control and data flow over included sensors.

The Health Care Service (HCS) is described as the primary service for controlling, configuring and reading output data from health care services, but also mentioned that only Health Toolbox compatible devices (the default devices) can be interfaced with through this. Where are the control and data loops for the Wearable Dev Kit sensors located within this framework? (for reading data, writing to registers, etc).

And just as a general question, is the Wearable Dev Kit intended to be modified through the inclusion of new sensors? Or is it primarily intended to be used as-is with the default hardware?

Thanks again

Thu, 2019-09-26 16:46
PM_Dialog
Offline
Last seen:2 days 12 hours ago
Staff
Joined:2018-02-08 11:03
Hi mrdobson,

Hi mrdobson,

Generally, the Wearable software is a reference design and my recommendation is to be used as-is with the default hardware. Could you please clarify your first question?

Thanks, PM_Dialog