打开APP
userphoto
未登录

开通VIP,畅享免费电子书等14项超值服

开通VIP
Forums

I have made the changes from the Wiki 128 bit UUID example to my working app and now cannot send data from central to peripheral.

I am sending the data using the correct handle for SIMPLEPROFILE_CHAR1 using GATT_WriteCharValue.

The packet arrives at the peripheral but the 2 bytes of the UUID which should be FF F1 and actually 00 00.

It would help to diagnose this problem if I knew how it worked. The UUID does not appear in the data as shown in the sniffer, only the handle does as far as I can see. Where does the UUID come from? The relevant bytes are pAttr->type.uuid[0], pAttr->type.uuid[1] on the peripheral. I am not clear on where these are populated from and why they are 00 instead of FF F1.

If I remove the define to revert to 16 bit UUID everything works again.

本站仅提供存储服务,所有内容均由用户发布,如发现有害或侵权内容,请点击举报
打开APP,阅读全文并永久保存 查看更多类似文章
猜你喜欢
类似文章
【热】打开小程序,算一算2024你的财运
MIPI 系列之 DSI
BLE GATT 介绍
linux 查看硬件信息的命令
使用文件设备
Linux基础:如何找出你的系统所支持的最大内存
JPEG 简易文档 V2.14
更多类似文章 >>
生活服务
热点新闻
分享 收藏 导长图 关注 下载文章
绑定账号成功
后续可登录账号畅享VIP特权!
如果VIP功能使用有故障,
可点击这里联系客服!

联系客服