yabo国际娱乐对话框半导体客户支持-超时 https://support.dialog-semiconductor.com/resource-keywords/timeout I2C适配器异步写:挂起事务问题 https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/i2c-adapter-async-write-pending < 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 >我使用i2c适配器(在主模式下)做的异步写或读,永远等待一个OS_EVENT从回调信号。
然而,我想要能够设置一个超时值,以便它不会卡住,如果说在总线上没有设备。
但是在超时之后,如果我尝试启动另一个异步读写适配器挂起,因为有(例如2)未完成的挂起事务。我如何取消这些挂起的事务,或者更好的是,如何使用ad_i2c_async_read或ad_i2c_async_write超时。< / 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 / i2c”“=“skos:概念”属性=“rdfs: label skos: prefLabel”数据类型= " " > i2c < / > < / div > < div类= " field-item奇怪" > < a href = " / resource-keywords / adi2c”“=“skos:概念”属性=“rdfs: label skos: prefLabel”数据类型= " " > ad_i2c < / > < / div > < div class =”field-item甚至“> < a href = " / resource-keywords /大师”“=“skos:概念”属性=“rdfs: label skos: prefLabel”数据类型= " " >主< / > < / div > < div class = " field-item古怪”> 超时< / > < / div > < div class =”field-item甚至“> < a href = " / resource-keywords / freertos”“=“skos:概念”属性=“rdfs: label skos: prefLabel”数据类型= " " > freertos < / > < / div > < div class = " field-item古怪”> < a href = " / resource-keywords /异步”typeof = " skos:概念”属性= " rdfs: label skos: prefLabel”异步数据类型= " " > < / > < / 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">
Device: 
2018年2月28日星期三14:38:44 +0000 rajames 155272年https://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/i2c-adapter-async-write-pending#comments
iOS 10和iOS 9的断连进程不同。 https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/disconnection-process-differs-between < 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:论坛”

1. jpg (72.34 kb,下载频率:0)

从iOS发出连接请求(connection request)。< br / > 2。外设发出连接请求指示。< br / > 3。从外设发出一个断开连接的进程。
在ios9中它将被识别为断开并立即断开。
然而,iOS 10将其识别为超时并需要时间断开连接。
Is this a problem with iOS?
是外围设备的问题吗?< / p > < p >静态int gapc_connection_req_ind_handler (ke_msg_id_t const是否,< br / > struct gapc_connection_req_ind const *参数,< br / > ke_task_id_t const dest_id, < br / > ke_task_id_t const src_id) < br / > {< br / > uint8_t connection_idx = KE_IDX_GET (src_id); < / p > < p > / / iOS 9将确定为立即断开连接和断开连接。
//然而,iOS 10将其识别为超时并需要时间断开连接。< br / > app_easy_gap_disconnect (connection_idx); < / p > < p >返回(KE_MSG_CONSUMED); < 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 / ios10”typeof="skos:Concept" property="rdfs:label skos:prefLabel" datatype="">iOS10
Device: 
2017年6月22日星期四01:00:32 +0000 y-takamine 53831年https://support.dialog-semiconductor.com https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/disconnection-process-differs-between#comments