雷竞技电竞平台Dialog半导体客户支持-DA14681 https://support.dialog-semiconductor.com/resource-keywords/da14681 DA14681睡眠和唤醒定时器模式? https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-软件/da14681睡眠和唤醒定时器模式
论坛:
dialog smartbond蓝牙低能–软件=“隐藏摘要字段标签的字段名称正文字段类型文本”>

Hi dialog

我正在开发基于DA14681的定制baord。我想知道如何进入睡眠模式,以及如何设置同步计时器以自动唤醒。

实际上,我的应用程序需要该设备在每分钟后自动唤醒SUP,读取ADC温度,写入闪存并返回睡眠。我想知道有没有实现这种睡眠的示例代码。或者,如果您能帮我做这件事?

第二,该设备也必须可用于SUOTA更新或数据传输。如何管理字段div>

2020年9月23日星期三09:48:40+0000 马哈梅德106 379305年https://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-软件/da14681睡眠和唤醒定时器模式#注释 端口DA14681可穿戴项目至SDK10,用于DA14697 https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-硬件设备参考设计/端口da14681

是否有任何关于如何将DA14681可穿戴项目移植到SDK10以在DA14697上使用的指南=“字段名称字段论坛关键字字段类型分类法术语参考字段标签上方”>

关键字:
移植“>da14681
da14697=“field field name field device field type taxonomy term reference field label Upper”>
设备:
所有 星期一,2019年8月26日14:31:40 +0000 纳兹 320210 athttps://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-硬件设备参考设计/端口da14681#注释 DA14681进入冬眠,但在2醒来后就不再去了? https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-软件/da14681-goes-hibernation-after-2 < div class = "字段field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >论坛:,< / div > < div class = "字段条目" > < div class =”field-item甚至“rel = " sioc: has_container " > < a href = " /论坛/ dialog-smartbond-bluetooth-low-energy - % E2 % 80% 93 -软件”“=“sioc:容器sioc:论坛”属性= " rdfs: label skos: prefLabel”数据类型= " " >对话框Smartbond蓝牙低能量-软件< / > < / div > < / div > < / div > < div class =”字段field-name-body field-type-text-with-summary field-label-hidden”> < div class = "字段条目" > < div class =”field-item甚至“财产=“内容:编码”> < p >嗨对话框< / p > < p >我在自定义基于DA1468x我am using command

pm_resume_sleep();
pm_set_sleep_mode(pm_mode_hibernation);

to put it in hibernation. It goes into hiberanation and wakeups with external GPIO interrupt but after waking up 2 times it do not go into hibernation.

Is it related to that logic that hibernation mode is for ship devices to customer . When customer on the device then this piecce of code is disabled?

Is my understanding right?

Device: 
2019年8月26日星期一13:11:12 +0000 马哈梅德106 320186年https://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-软件/da14681-goes-hibernation-after-2#注释 如何通过BLE发送负值? https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/how-can-we-send-negative-value-ble
论坛:
dialog smartbond蓝牙低能–软件=“隐藏摘要字段标签的字段名称正文字段类型文本”>

Hi dialog

我正在基于DA14681和sdk为1.0.14.1081的定制板上工作。
在ble_gatts.c文件中,所有函数都将输入作为uint16_t。
我的问题是,我是否要发送像int8或int16这样的负值数据。我怎样才能寄出去?因为,因为Able-UU GATTTs.c是一个sdk文件,我不想更改。

<因为因为因为Able-U GATTTs.c是一个我不想更改的sdk文件。c是一个sdk文件,是一个sdk文件,我不想更改。

/p>

版权所有(c)2015-2017 Dialog Semiconductor。
*此计算机程序包含Dialog Semiconductor的机密专有信息。版权所有。
************************************************************************************************************************************************************************
/

包括<;标准h>
包括<;字符串.h><(b)包括,包括,包括,包括,包括,雷竞技电竞平台包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括“普通.普通.h”
(br)包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,包括,配置的,包括,包括,包括,包括,包括,包括,包括,配置的,包括,包括,包括,包括,包括,配置的。服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服服务(const att\u uuid\u t*uuid,const gatt\u service\u type,
uint16\u num\u attrs)
{ble\u mgr\u gatts\u service\u add\u cmd\u cmd;
ble\u mgr\u gatts\u service\u add\u rsp\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r






>>CMP>>CMP>>CMP><
CMP>
CMP>
CMP>
CMP>
CMP>
CMP>

CMP>


CMP>CMP>CMP>CMP>CMP>CMP><

CMP>

CMP>

CMP>若若若(

若(

p>p>p>若(

p>p>若(

p>p>p>p>p>p>若若若(

若_包括(uint16\u t handle,uint16\u t*h\u offset)
{
ble\u mgr\u gatts\u service\u add\u include\u cmd\u t*cmd;
ble\u mgr\u gatts\u service\u add\u include\u rsp\u rsp;
ble\u error\u ret ble\u error\u FAILED;

/*创建新命令并填充它*/
cmd alloc\u ble\u msg(gatble\mgr\cmd service\u add
cmd->;handle=handle;

如果(!ble_cmd_execute(cmd,(void**)&rsp,ble_mgr_gatts_service_add_include_cmd_handler){
返回ret

ble\U error\U t ble\U gatts\U add\U特征(常量att\U uuid\U t*uuid,gatt\U prop\t prop,att perm\U perm,
uint16\U max\U len,gatts\U标志,uint16\U t*h\U偏移,
uint16\U*h\U val\U偏移量)
{
ble_-mgr_-gatts_-service_-add_-characteristic_-cmd_-gt*cmd;
ble_-mgr_-gatts_-service_-add_-characteristic_-rsp_-t*rsp;
ble-error_-ret=ble_-error_-error_失败;

/*创建新命令并填充它*/
cmd
cmd->;uuid=*uuid;
cmd->;prop=prop;
cmd->;perm=perm;
cmd->;max\u len=max\u len;
cmd->;flags=flags;

如果(!ble\u cmd\u执行(cmd,(void**)rsp,ble\u管理器\u gatts服务\u添加特性\u cmd处理程序){br/>返回ret《p>

<

如果(h>p>>p>如果p>>p

p>p>p>p>p>p>p>p>p>p>p>p>p>p>由于由于错误,我们的错误,我们的错误,我们的错误,我们的错误,我们是在测试,我们的错误,我们在在测试测试中,_标志_t标志,uint16_t*h_偏移量)
{
ble\u mgr\u gatts\u service\u add\u descriptor\u cmd\u t*cmd;
ble\u mgr\u gatts\u service\u add\u descriptor\u rsp\u t*rsp;
ble\u error\u ret=ble\u error\u失败;

/*创建新命令并填充它*/
cmd alloc\u sible\u msg(ble\u mgr\u gatts\u service\u descriptor,EOF cmd)

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>cmd>>>>>>>>>
>>>>>
>>>>>>>cmd>>>>>cmd>cmd>cmd>cmd>>cmd>cmd>难难难难难难>难难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>难>/>}

/*免费信息*/
OS_FREE(rsp);

return ret;
}

ble_error_t ble_gatts_register_service(uint16_t *handle, ...)
{
va_list ap;
ble_mgr_gatts_service_register_cmd_t *cmd;
ble_mgr_gatts_service_register_rsp_t *rsp;
ble_error_t ret = BLE_ERROR_FAILED;

/* Create new command and fill it */
cmd = alloc_ble_msg(BLE_MGR_GATTS_SERVICE_REGISTER_CMD, sizeof(*cmd));

if (!ble_cmd_execute(cmd, (void **) &rsp, ble_mgr_gatts_service_register_cmd_handler)) {
return ret;
}

ret = rsp->status;

if (handle) {
*handle = rsp->handle;
}

va_start(ap, handle);
for (;;) {
uint16_t *h = va_arg(ap, uint16_t*);

if (!h) {
break;
}

*h = *h + rsp->handle;
}
va_end(ap);

/* free message */
OS_FREE(rsp);

return ret;
}

ble_error_t ble_gatts_enable_service(uint16_t handle)
{
ble_mgr_gatts_service_enable_cmd_t *cmd;
ble_mgr_gatts_service_enable_rsp_t *rsp;
ble_error_t ret = BLE_ERROR_FAILED;

/* Create new command and fill it */
cmd = alloc_ble_msg(BLE_MGR_GATTS_SERVICE_ENABLE_CMD, sizeof(*cmd));
cmd->handle = handle;

if (!ble_cmd_execute(cmd, (void **) &rsp, ble_mgr_gatts_service_enable_cmd_handler)) {
return ret;
}

ret = rsp->status;

/* free message */
OS_FREE(rsp);

return ret;
}

ble_error_t ble_gatts_disable_service(uint16_t handle)
{
ble_mgr_gatts_service_disable_cmd_t *cmd;
ble_mgr_gatts_service_disable_rsp_t *rsp;
ble_error_t ret = BLE_ERROR_FAILED;

/* Create new command and fill it */
cmd = alloc_ble_msg(BLE_MGR_GATTS_SERVICE_DISABLE_CMD, sizeof(*cmd));
cmd->handle = handle;

if (!ble_cmd_execute(cmd, (void **) &rsp, ble_mgr_gatts_service_disable_cmd_handler)) {
return ret;
}

ret = rsp->status;

/* free message */
OS_FREE(rsp);

return ret;
}

ble_error_t ble_gatts_get_characteristic_prop(uint16_t handle, gatt_prop_t *prop, att_perm_t *perm)
{
ble_mgr_gatts_service_characteristic_get_prop_cmd_t *cmd;
ble_mgr_gatts_service_characteristic_get_prop_rsp_t *rsp;
ble_error_t ret = BLE_ERROR_FAILED;

/* Create new command and fill it */
cmd = alloc_ble_msg(BLE_MGR_GATTS_SERVICE_CHARACTERISTIC_GET_PROP_CMD, sizeof(*cmd));
cmd->handle = handle;

if (!ble_cmd_execute(cmd, (void **) &rsp,
ble_mgr_gatts_service_characteristic_get_prop_cmd_handler)) {
return ret;
}

ret = rsp->status;

if (ret == BLE_STATUS_OK) {
if (prop) {
*prop = rsp->prop;
}

if (perm) {
*perm = rsp->perm;
}
}

/* free message */
OS_FREE(rsp);

return ret;
}

ble_error_t ble_gatts_set_characteristic_prop(uint16_t handle, gatt_prop_t prop, att_perm_t perm)
{
ble_mgr_gatts_service_characteristic_set_prop_cmd_t *cmd;
ble_mgr_gatts_service_characteristic_set_prop_rsp_t *rsp;
ble_error_t ret = BLE_ERROR_FAILED;

/* Create new command and fill it */
cmd = alloc_ble_msg(BLE_MGR_GATTS_SERVICE_CHARACTERISTIC_SET_PROP_CMD, sizeof(*cmd));
cmd->handle = handle;
cmd->prop = prop;
cmd->perm = perm;

if (!ble_cmd_execute(cmd, (void **) &rsp,
ble_mgr_gatts_service_characteristic_set_prop_cmd_handler)) {
return ret;
}

ret = rsp->status;

/* free message */
OS_FREE(rsp);

return ret;
}

ble_error_t ble_gatts_get_value(uint16_t handle, uint16_t *length, void *value)
{
ble_mgr_gatts_get_value_cmd_t *cmd;
ble_mgr_gatts_get_value_rsp_t *rsp;
ble_error_t ret = BLE_ERROR_FAILED;
uint16_t copy_length;

/* Create new command and fill it */
cmd = alloc_ble_msg(BLE_MGR_GATTS_GET_VALUE_CMD, sizeof(*cmd));
cmd->handle = handle;
cmd->max_len = *length;
copy_length = *length; // save for later

if (!ble_cmd_execute(cmd, (void **) &rsp, ble_mgr_gatts_get_value_cmd_handler)) {
return ret;
}

/*
* Update length with actual attribute value length.
* Copy as much data as will fit in buffer or what was returned (if buffer provided).
*/
*length = rsp->length;
if (value) {
if (rsp->length < copy_length) {
copy_length = rsp->length;
}
memcpy(value, rsp->value, copy_length);
}

ret = rsp->status;
/* free message */
OS_FREE(rsp);

return ret;
}

ble_error_t ble_gatts_set_value(uint16_t handle, uint16_t length, const void *value)
{
ble_mgr_gatts_set_value_cmd_t *cmd;
ble_mgr_gatts_set_value_rsp_t *rsp;
ble_error_t ret = BLE_ERROR_FAILED;

/* Create new command and fill it */
cmd = alloc_ble_msg(BLE_MGR_GATTS_SET_VALUE_CMD, sizeof(*cmd) + length);
cmd->handle = handle;
cmd->length = length;
memcpy(cmd->value, value, length);

if (!ble_cmd_execute(cmd, (void **) &rsp, ble_mgr_gatts_set_value_cmd_handler)) {
return BLE_ERROR_FAILED;
}

ret = rsp->status;
OS_FREE(rsp);

return ret;
}

ble_error_t ble_gatts_read_cfm(uint16_t conn_idx, uint16_t handle, att_error_t status,
uint16_t length, const void *value)
{
ble_mgr_gatts_read_cfm_cmd_t *cmd;
ble_mgr_gatts_read_cfm_rsp_t *rsp;
ble_error_t ret = BLE_ERROR_FAILED;

if (length && !value) {
return ret;
}

/* Create new command and fill it */
cmd = alloc_ble_msg(BLE_MGR_GATTS_READ_CFM_CMD, sizeof(*cmd) + length);
cmd->conn_idx = conn_idx;
cmd->handle = handle;
cmd->status = status;
cmd->length = length;
if (value) {
memcpy(cmd->value, value, length);
}

if (!ble_cmd_execute(cmd, (void **) &rsp, ble_mgr_gatts_read_cfm_cmd_handler)) {
return BLE_ERROR_FAILED;
}

ret = rsp->status;
OS_FREE(rsp);

return ret;
}

ble_error_t ble_gatts_write_cfm(uint16_t conn_idx, uint16_t handle, att_error_t status)
{
ble_mgr_gatts_write_cfm_cmd_t *cmd;
ble_mgr_gatts_write_cfm_rsp_t *rsp;
ble_error_t ret = BLE_ERROR_FAILED;

/* Create new command and fill it */
cmd = alloc_ble_msg(BLE_MGR_GATTS_WRITE_CFM_CMD, sizeof(*cmd));
cmd->conn_idx = conn_idx;
cmd->handle = handle;
cmd->status = status;

if (!ble_cmd_execute(cmd, (void **) &rsp, ble_mgr_gatts_write_cfm_cmd_handler)) {
return BLE_ERROR_FAILED;
}

ret = rsp->status;
OS_FREE(rsp);

return ret;
}

ble_error_t ble_gatts_prepare_write_cfm(uint16_t conn_idx, uint16_t handle, uint16_t length,
att_error_t status)
{
ble_mgr_gatts_prepare_write_cfm_cmd_t *cmd;
ble_mgr_gatts_prepare_write_cfm_rsp_t *rsp;
ble_error_t ret = BLE_ERROR_FAILED;

/* Create new command and fill it */
cmd = alloc_ble_msg(BLE_MGR_GATTS_PREPARE_WRITE_CFM_CMD, sizeof(*cmd));
cmd->conn_idx = conn_idx;
cmd->handle = handle;
cmd->length = length;
cmd->status = status;

if (!ble_cmd_execute(cmd, (void **) &rsp, ble_mgr_gatts_prepare_write_cfm_cmd_handler)) {
return BLE_ERROR_FAILED;
}

ret = rsp->status;
OS_FREE(rsp);

return ret;
}

ble_error_t ble_gatts_send_event(uint16_t conn_idx, uint16_t handle, gatt_event_t type,
uint16_t length, const void *value)
{
ble_mgr_gatts_send_event_cmd_t *cmd;
ble_mgr_gatts_send_event_rsp_t *rsp;
ble_error_t ret = BLE_ERROR_FAILED;

/* Create new command and fill it */
cmd = alloc_ble_msg(BLE_MGR_GATTS_SEND_EVENT_CMD, sizeof(*cmd) + length);
cmd->conn_idx = conn_idx;
cmd->handle = handle;
cmd->type = type;
cmd->length = length;
memcpy(cmd->value, value, length);

if (!ble_cmd_execute(cmd, (void **) &rsp, ble_mgr_gatts_send_event_cmd_handler)) {
return BLE_ERROR_FAILED;
}

ret = rsp->status;
OS_FREE(rsp);

return ret;
}

ble_error_t ble_gatts_service_changed_ind(uint16_t conn_idx, uint16_t start_handle,
uint16_t end_handle)
{
ble_mgr_gatts_service_changed_ind_cmd_t *cmd;
ble_mgr_gatts_service_changed_ind_rsp_t *rsp;
ble_error_t ret = BLE_ERROR_FAILED;

/* Create new command and fill it */
cmd = alloc_ble_msg(BLE_MGR_GATTS_SERVICE_CHANGED_IND_CMD, sizeof(*cmd));
cmd->conn_idx = conn_idx;
cmd->start_handle = start_handle;
cmd->end_handle = end_handle;

if (!ble_cmd_execute(cmd, (void **) &rsp, ble_mgr_gatts_service_changed_ind_cmd_handler)) {
return BLE_ERROR_FAILED;
}

ret = rsp->status;
OS_FREE(rsp);

return ret;
}
#endif /* (dg_configBLE_GATT_SERVER == 1) */

Device: 
周二,2019年8月20日11:36:20 +0000 马哈梅德106 319306 athttps://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-软件/我们如何发送负面评论 如何从firmwrare重新启动/重置DA14681。 https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/how-rebootreset-da14681-firmwrare < div class = "字段field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >论坛:,< / div > < div class = "字段条目" > < div class =”field-item甚至“rel = " sioc: has_container " > < a href = " /论坛/ dialog-smartbond-bluetooth-low-energy - % E2 % 80% 93 -软件”“=“sioc:容器sioc:论坛”属性= " rdfs: label skos: prefLabel”数据类型= " " >对话框Smartbond蓝牙低能量-软件< / > < / div > < / div > < / div > < div class =”字段field-name-body field-type-text-with-summary field-label-hidden”> < div class = "字段条目" > < div class =”field-item甚至“财产=“内容:编码”> < p >嗨对话框中,< / p > < p >我在自定义基于DA14681,工作正常。在固件中,我想使逻辑重新启动681,因为它重新启动时,重置按钮被击中。
那么是否有任何软件命令可以重置它?由于< / p > < br / > < / div > < / div > < / div > < div class =”字段field-name-field-forum-keywords field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >关键词:,< / div > < div class = "字段条目" > < div class =”field-item甚至“> < a href = " / resource-keywords / da14681”“=“skos:概念”属性=“rdfs: label skos: prefLabel”数据类型= " " > DA14681 < / > < / div > < / div > < / div > < div class =”字段field-name-field-device field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >设备:,< / div > < div class = "字段条目" > < div class =”field-item甚至“> < a href = " / forum-post-device / da1468x”“=“skos:概念”属性=“rdfs: label skos: prefLabel”数据类型= " " > DA1468x < / > < / div > < / div > < / div >
2019年8月19日星期一11:45:54+0000 马哈梅德106 319151 athttps://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-软件/how-rebootreset-da14681-firmwrare#注释
DA14681功耗高 https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-hardware-device-reference-designs/da14681-power < div class = "字段field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >论坛:,< / div > < div class = "字段条目" > < div class =”field-item甚至“rel = " sioc: has_container " > < a href = " /论坛/ dialog-smartbond-bluetooth-low-energy - % E2 % 80% 93 -硬件-设备-引用-设计”“= " sioc:容器sioc:Forum" property="rdfs:label skos:prefLabel" datatype="">Dialog Smartbond Bluetooth Low Energy - Hardware (device &

Hi,

我的PCB使用DA14681等外围芯片,由DA14681的GPIO驱动。

当DA14681处于扩展睡眠模式时,GPIO电源关闭,电池输出电流为102uA。DA14681休眠模式下,电池输出电流为1.4uA。

PCB部分扩展休眠电源异常,电池输出电流1.9mA,但休眠电源正常。

我想知道功率异常是否与DA14681有关。< / p > < / div > < / div > < / div > < div class =”字段field-name-field-forum-keywords field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >关键词:,< / div > < div class = "字段条目" > < div class =”field-item甚至“> < a href = " / resource-keywords / da14681”“=“skos:概念”属性=“rdfs: label skos: prefLabel”数据类型= " " > DA14681 < / > < / div > < / div > < / div > < div class =”字段field-name-field-device field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >设备:,< / div > < div class = "字段条目" > < div class =”field-item甚至“> < a href = " / forum-post-device / da1468x”“=“skos:概念”属性=“rdfs: label skos: prefLabel”数据类型= " " > DA1468x < / > < / div > < / div > < / div > 2019年6月21日星期五10:50:57+0000 歌曲 311344年https://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-硬件设备参考设计/da14681电源#注释 保税信息定位 https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/bonded-information-location

论坛:
dialog smartbond蓝牙低能–软件=“field field name body field type text with summary field label hidden”>

Hello Dialog team

我正在DA14681 MCU上工作。我的应用程序是存储一个绑定信息(对等设备MAC地址)。还使用“ad_nvms_write”存储传感器数据“API。我使用了ad_nvms_open(nvms_通用部分)。“NVMS_GENERIC_PART”分区用于数据存储。
现在的问题是,设备可以成功绑定对等设备并存储信息,我可以在每次电源循环后获得绑定信息。但是如果我写入传感器数据样本,则信息会被擦除/覆盖(?)

以下是我的问题:
1。我们如何知道存储的绑定信息存储位置?
2。我的应用程序是否使用相同的内存位置来存储绑定信息和传感器数据?
3。如果是这样,我如何将两者分开?

任何帮助或建议都将不胜感激。

感谢Jit

关键字:
设备:
2019年2月6日星期三20:25:43+0000 Jitendraprasad 283173年https://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-软件/保税信息位置#评论 无法将代码调试到设备DA14681-01 https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-软件/unable-debug-code-device-da14681-01
论坛:
dialog smartbond蓝牙低能–软件=“隐藏摘要字段标签的字段名称正文字段类型文本”>

我正在使用DA14681-01设备进行研究工作。我们购买了DA14681用于创建原型。然而,我在将代码加载到芯片时遇到了一个问题。最初,我用基本代码开始闪烁D2 led。但是我得到了以下错误。我试图在您的论坛上找到此错误,但无法得到任何答案。

请帮助我,提前感谢。以下是错误信息。

SEGGER J-Link GDB Server V6.42a命令行版本

JLinkARM.dll V6.42a(dll于2019年2月1日18:00:08编译)

命令行:-如果swd-设备DA14681-endian little-speed 1000-端口2331-SWOPort2332-telnetport 2333-vd-ir-localhostonly 1-singlerun-strict-超时0-nogui
GDB服务器启动设置------GDB文件:无
GDB服务器侦听端口:2331
SWO原始输出侦听端口:2332
终端I/O端口:2333
接受远程连接:仅本地主机
生成日志文件:关闭
验证下载:打开
启动时初始化注册表:打开
静默模式:关闭
单一运行模式:打开
目标连接超时:0毫秒
----与J-Link相关的设置----
J-Link主机接口:USB
J-Link脚本:无
J-Link设置文件:无
----目标相关设置----
目标设备:DA14681
目标接口:SWD
目标接口速度:1000kHz
目标端:little

连接到J-Link…
J-Link已连接。
固件:J-Link OB-SAM3U128 V3编译于2019年1月7日14:06:26
硬件:V3.00
S/N:483000924
功能:RDI
检查目标电压…
目标电压:3.30 V
侦听TCP/IP端口2331
连接到目标…连接到目标
等待GDB连接…连接到127.0.0.1
读取所有寄存器
读取地址0x00000000的4个字节(数据=0x07FE0428)
接收到的监视器命令:速度1000
目标接口速度设置为1000 kHz
接收到的监视器命令:clrbp
接收到的监视器命令:重置目标
接收到的监视器命令:停止目标CPU…
…目标停止(PC=0x07F000D4)
收到的监视器命令:regs
R0=FFFFFFFF,R1=FFFFFFFF,R2=FFFFFFFF,R3=FFFFFFFF
R4=FFFFFFFF,R5=ffffffffff,R6=ffffffffff,R7=ffffffffff
R8=ffffffffffffffff,R9=ffffffffffffff,R10=ffffffffffffff,R11=ffffffffffffffffffff
R12=ffffffffffffffffffffffffffffff,R13=07FE0428,MSP=07FE0428,PSP=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff(fc)fffffffff=07F000D4
XPSR C1000000、APSR C0000000、EPSR 01000000、IPSR 00000000
CFBP 00000000、控件00、故障掩码00、BASEPRI 00、PRIMASK 00
读取所有寄存器
读取地址0x07F000D4(数据=0x47804804)的4个字节
接收到的监控命令:速度自动
选择自动目标接口速度(2000 kHz)
收到的监视器命令:闪存断点1
已启用闪存断点
收到的监视器命令:已启用半托管
已启用半托管(BKPT上的句柄)
收到的监视命令:半托管IOClient 1
半托管I/O设置为TELNET客户端
收到的监视命令:SWO DisableTarget 0xFFFFFF
成功禁用SWO。
收到的监视命令:SWO EnableTarget 0 0x1 0
错误:无法检测CPU时钟速度。将测试代码下载到RAM失败。
在CPU时钟频率检测后恢复原始RAM内容失败

未能启用SWO。无法测量目标CPU频率。
读取地址0x07F000D4处的4个字节(数据=0x47804804)
下载736字节@地址0x08000000-验证失败
下载32字节@地址0x080002E0-验证失败
下载32字节@地址0x08000300-验证失败
下载4096字节@地址0x08000320-验证失败
下载4096字节@地址0x08001320-验证失败
下载4096字节@地址0x08002320-验证失败
下载4096字节@地址0x08003320-验证失败
下载844字节@地址0x08004320-验证失败
下载8字节@地址0x0800466C-验证失败
下载16字节@地址0x08004680-验证失败
下载4096字节@地址0x08004690-验证失败
下载2320字节@地址0x08005690-验证写入失败
register (PC = 0x 8000134)
Read 4 bytes @ address 0x08000134 (Data = 0xFFFFFFFF)
Read 2 bytes @ address 0x0800410A (Data = 0xFFFF)
Read 2 bytes @ address 0x08004108 (Data = 0xFFFF)
Received monitor command: clrbp
Received monitor command: reset
Resetting target
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x07F000D4)
Read 2 bytes @ address 0x0800410A (Data = 0xFFFF)
Read 2 bytes @ address 0x0800410A (Data = 0xFFFF)
Read 2 bytes @ address 0x08004108 (Data = 0xFFFF)
Received monitor command: regs
R0 = FFFFFFFF, R1 = FFFFFFFF, R2 = FFFFFFFF, R3 = FFFFFFFF
R4 = FFFFFFFF, R5 = FFFFFFFF, R6 = FFFFFFFF, R7 = FFFFFFFF
R8 = FFFFFFFF, R9 = FFFFFFFF, R10= FFFFFFFF, R11= FFFFFFFF
R12= FFFFFFFF, R13= 07FE0428, MSP= 07FE0428, PSP= FFFFFFFC
R14(LR) = FFFFFFFF, R15(PC) = 07F000D4
XPSR C1000000, APSR C0000000, EPSR 01000000, IPSR 00000000
CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
Reading all registers
Read 4 bytes @ address 0x07F000D4 (Data = 0x47804804)
Setting breakpoint @ address 0x08004108, Size = 2, BPHandle = 0x0001
Starting target CPU...
ERROR: Can not read register 15 (R15) while CPU is running
Reading all registers
ERROR: Can not read register 0 (R0) while CPU is running
ERROR: Can not read register 1 (R1) while CPU is running
ERROR: Can not read register 2 (R2) while CPU is running
ERROR: Can not read register 3 (R3) while CPU is running
ERROR: Can not read register 4 (R4) while CPU is running
ERROR: Can not read register 5 (R5) while CPU is running
ERROR: Can not read register 6 (R6) while CPU is running
ERROR: Can not read register 7 (R7) while CPU is running
ERROR: Can not read register 8 (R8) while CPU is running
ERROR: Can not read register 9 (R9) while CPU is running
ERROR: Can not read register 10 (R10) while CPU is running
ERROR: Can not read register 11 (R11) while CPU is running
ERROR: Can not read register 12 (R12) while CPU is running
ERROR: Can not read register 13 (R13) while CPU is running
ERROR: Can not read register 14 (R14) while CPU is running
ERROR: Can not read register 15 (R15) while CPU is running
ERROR: Can not read register 16 (XPSR) while CPU is running
ERROR: Can not read register 17 (MSP) while CPU is running
ERROR: Can not read register 18 (PSP) while CPU is running
ERROR: Can not read register 24 (PRIMASK) while CPU is running
ERROR: Can not read register 25 (BASEPRI) while CPU is running
ERROR: Can not read register 26 (FAULTMASK) while CPU is running
ERROR: Can not read register 27 (CONTROL) while CPU is running
WARNING: Failed to read memory @ address 0xDEADBEEE
Removing breakpoint @ address 0x08004108, Size = 2
WARNING: Failed to read memory @ address 0xDEADBEEE
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEEE
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEEE
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEF0
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEF0
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEAA
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEAA
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEAC
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEAC
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEAE
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEAE
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEB0
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEB0
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEB2
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEB2
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEB4
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEB4
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEB6
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEB6
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEB8
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEB8
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEBA
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEBA
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEBC
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEBC
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEBE
Reading 64 bytes @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBE80
WARNING: Failed to read memory @ address 0xDEADBEBE
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC2
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC2
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC4
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC4
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC6
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC6
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC8
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC8
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBECA
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBECA
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBECC
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBECC
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBECE
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBECE
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBED0
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBED0
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBED2
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBED2
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBED4
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBED4
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBED6
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBED6
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBED8
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBED8
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEDA
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEDA
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEDC
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEDC
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEDE
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEDE
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEE0
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEE0
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEE2
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEE2
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEE4
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEE4
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEE6
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEE6
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEE8
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEE8
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEEA
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEEA
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEEC
Reading 64 bytes @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEC0
WARNING: Failed to read memory @ address 0xDEADBEEC

Attachment: 
Device: 
2019年2月5日星期二17:17:15+0000 Mohammedhusen 282808 athttps://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-软件/unable-debug-code-device-da14681-01#注释 da14681自定义充电电池配置 https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software-dialog-%E2%80%9Csmartbond%E2%80%9D%E7%B3%BB%E5%88%97%E4%BD%8E%E5%8A%9F%E8%80%97%E8%93%9D%E7%89%99%E2%80%94%E8%BD%AF%E4%BB%B6-72
论坛:

你好,请问下关于充电电池的几个问题:
1、pxp例子里关于充电电池配置文件自定义电池配置文件.h文件内的vol_chg_0_0=3067;//120mA充电这个值是怎么算出来的,有公式吗,看了UM-B-075_DA1468x_状态_收费功能_v1.2_0.pdf文档,需要一个硬件设备连接后才能使用,目前没有这个设备;
2、柴油发电机配置蓄电池充电电压和dg_配置电池_类型_定制_ADC_电压这两个有什么区别?
3、音量低0和音量显示高0必须通过UM-B-075这个文档中应用程序测出吗,有其它方式吗?
4、闪光灯存储布局,看了文档DA1468x_闪存_适配器_教程_v2_1.pdf后,结合到DA14681_WRBL这个案例后,有个疑问,用户的数据是保存在NVMS_通用零件这块的,在DA14681_WRBL案例里的用户存储的最大上限空间是16K单独定义的,而在分区表.h里定义的空间比这个定义大,如果我这边使用,那上限可以配置到分区表.h里那么大的或者是其它的大小?
5、我这边按照pxp示例增加了i2c数据读取,每隔一秒读取然后通过ble自定义服务发送,但是发现程序有时候运行一段时间后会死机,不是每次都有,有时候很正常,有时候会连着几次死机,但是,而i2c读取写入都是用同步的方式,看到另外一个朋友提问里说用异步就没问题,这个会有影响吗?
6、程序运行后配置的是pm_模式_延长睡眠这个配置后,就已经是低功耗下运行的是吗,后面还需要使用什么来激活模式?
7、现在可以使用usb做数据传输吗还是只能充电?
非常感谢

电池
设备:
星期三,2019年1月23日07:10:14 +0000 Linchaoran 278809年https://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software-dialog-%E2%80%9Csmartbond%E2%80%9D%E7%B3%BB%E5%88%97%E4%BD%8E%E5%8A%9F%E8%80%97%E8%93%9D%E7%89%99%E2%80%94%E8%BD%AF%E4%BB%B6-72#comments da14681自定义充电电池配置 https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-软件/da14681%E8%87%AA%E5%AE%9A%E4%B9%89%E5%85%85%E7%94%B5%E7%94%B5%E6%B1%A0%E9%85%8D%E7%BD%AE < div class = "字段field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >论坛:,< / div > < div class = "字段条目" > < div class =”field-item甚至“rel = " sioc: has_container " > < a href = " /论坛/ dialog-smartbond-bluetooth-low-energy - % E2 % 80% 93 -软件”“=“sioc:容器sioc:论坛”属性= " rdfs: label skos: prefLabel”数据类型= " " >对话框Smartbond蓝牙低能量-软件< / > < / div > < / div > < / div > < div class =”字段field-name-body field-type-text-with-summary field-label-hidden”> < div class = "字段条目" > < div class =”field-item甚至“财产=“内容:编码”> < p >你好,请问下关于充电电池的几个问题:< br / > 1, pxp例子里关于充电电池配置文件custom_socf_battery_profile.h文件内的vol_chg_0_0 = 3067;/ / 120毫安的充电,这个值是怎么算出来的,有公式吗,看了嗯- b - 075 - _da1468x_state_of_charge_functionality_v1.2_0.pdf文档,需要一个硬件设备连接后才能使用,目前没有这个设备,< br / > 2, dg_configBATTERY_CHARGE_VOLTAGE和dg_configBATTERY_TYPE_CUSTOM_ADC_VOLTAGE这两个有什么区别吗?< br / > 3, vol_dis_low_0和vol_dis_high_0必须通过嗯- b - 075这个文档中应用程序测出吗,有其它方式吗?< br / >谢谢< / p > < / div > < / div > < / div > < div class =”字段field-name-field-forum-keywords field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >关键词:,< / div > < div class = "字段条目" > < div class =”field-item甚至“> < a href = " / resource-keywords / da14681”“=“skos:概念”属性=“rdfs: label skos: prefLabel”数据类型= " " > DA14681 < / > < / div > < div class = " field-item古怪”> < a href = " / resource-keywords /电池”“=“skos:概念”属性=“rdfs: label skos: prefLabel”数据类型= " " >电池< / > < / div > < / div > < / div > < div class =”字段field-name-field-device field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >设备:< / div > < divclass="field-items">
. 2019年1月22日星期二01:08:15+0000 Linchaoran 278283 athttps://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/da14681%E8%87%AA%E5%AE%9A%E4%B9%89%E5%85%85%E7%94%B5%E7%94%B5%E6%B1%A0%E9%85%8D%E7%BD%AE#comments