Silicon Labs EFR32BG21 蓝牙SoC RCP模式测试-扫描设备
SILICON LABS EFR32BG系列蓝牙SoC芯片支持RCP模式(Radio Co-Processor),RCP模式简单说就是BG21运行蓝牙控制器(即仅链路层),蓝牙协议栈在主机上运行,主机通过UART连接BG21,使用标准HCI(主机控制器接口)对其访问控制实现蓝牙BLE功能。
本文介绍测试EFR32BG21 蓝牙RCP模式工作在主模式,用于扫描蓝牙从设备,建立蓝牙连接和收发数据。首先需要准备一台电脑并且已经安装好了linux系统。也可以是windows系统下安装的linux虚拟机。并且已经安装好了蓝牙BlueZ协议栈。
1、首先可以通过命令查询当前bluez的版本,检查linux环境下BlueZ是否正确安装:
bluetoothctl --version
例如:
Linux@RCP:~/bluez_5_60$ bluetoothctl --version
bluetoothctl: 5.60
可以看到已经正确的返回了BlueZ版本号,说明BlueZ已经安装正确了。
烧录bootloader和蓝牙RCP固件到EFR32BG21以后,可以使用windows环境下的串口工具测试串口和固件是否正常运行。串口工具发送(hex值):01 03 0C 00(这条是复位命令),BG21会回复:04 0E 04 01 03 0C 00。如果正确的收到返回数据。说明RCP和串口都正常运行了。示例:
发送:01 03 0C 00
接收:04 0E 04 01 03 0C 00
或者使用这条设置扫描参数的命令来测试:
发送:01 0B 20 07 01 30 00 30 00 00 00
接收:04 0E 04 01 0B 20 00
2、然后需要准备一个能正常工作的BLE蓝牙从设备。本文测试使用的是采用EFR32BG系列的蓝牙评估板,烧录Bluetooth - SoC Thermometer固件。相关的设备信息是:[NEW] Device 60:A4:23:C9:6D:11 Thermometer Example,其中Temperature Measurement特征字具备notify属性。会周期上报测量的温度值。Characteristic发现的示例:
Characteristic (Handle 0xfcb4)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a
00002a1c-0000-1000-8000-00805f9b34fb
Temperature Measurement
3、本文测试用到的命令:
Linux@Linux:~$ sudo hciattach /dev/ttyACM0 any 115200 noflow
(命令说明:如果RCP带串口流控,可以把noflow去掉)
Linux@Linux:~$ hciconfig -a
Linux@Linux:~$ bluetoothctl
[bluetooth]# scan on
[bluetooth]# scan off
[bluetooth]# connect 60:A4:23:C9:6D:11 (找到需要连接的蓝牙设备地址填入到此)
[Thermometer Example]# info
[Thermometer Example]# pair
[Thermometer Example]# menu gatt
[Thermometer Example]# list-attributes
[Thermometer Example]# select-attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a
(选择需要操作的Characteristic)
[Thermometer Example:/service0019/char001a]# notify on
[Thermometer Example:/service0019/char001a]# notify off
[Thermometer Example:/service0019/char001a]# select-attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001d
[Thermometer Example:/service0019/char001d]# read
[Thermometer Example:/service0019/char001d]# quit
4、以下是完整的测试log,对应前面介绍的每一条命令下发之后,RCP端返回给linux的数据和信息等:
Linux@Linux:~$ sudo hciattach /dev/ttyACM0 any 115200 noflow
[sudo] Linux 的密码:
Device setup complete
Linux@Linux:~$ hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: 00:0D:6F:0A:3B:E3 ACL MTU: 251:3 SCO MTU: 0:0
UP RUNNING
RX bytes:269 acl:0 sco:0 events:21 errors:0
TX bytes:155 acl:0 sco:0 commands:21 errors:0
Features: 0x00 0x00 0x00 0x00 0x60 0x00 0x00 0x00
Packet type: DM1 DH1 HV1
Link policy:
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Input/output error (5)
Linux@Linux:~$ bluetoothctl
Agent registered
[CHG] Controller 00:0D:6F:0A:3B:E3 Pairable: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:0D:6F:0A:3B:E3 Discovering: yes
[NEW] Device 60:A4:23:C9:6D:11 Thermometer Example
[NEW] Device 10:38:1F:60:12:97 10-38-1F-60-12-97
[NEW] Device 10:38:1F:5F:E5:37 10-38-1F-5F-E5-37
[NEW] Device 6C:0D:C4:25:A1:B3 6C-0D-C4-25-A1-B3
[NEW] Device 4D:26:80:F6:09:5F 4D-26-80-F6-09-5F
[NEW] Device 10:38:1F:60:13:7B 10-38-1F-60-13-7B
[CHG] Device 6C:0D:C4:25:A1:B3 UUIDs: 0000fdaa-0000-1000-8000-00805f9b34fb
[CHG] Device 6C:0D:C4:25:A1:B3 ManufacturerData Key: 0x038f
[bluetooth]# scan off
Discovery stopped
[CHG] Controller 00:0D:6F:0A:3B:E3 Discovering: no
[CHG] Device 5C:46:B0:39:66:94 RSSI is nil
[CHG] Device A4:C1:38:10:F6:0B RSSI is nil
[CHG] Device F0:5E:CD:C8:67:2C RSSI is nil
[CHG] Device 10:38:1F:60:13:7B RSSI is nil
[CHG] Device 4D:26:80:F6:09:5F RSSI is nil
[CHG] Device 6C:0D:C4:25:A1:B3 RSSI is nil
[CHG] Device 10:38:1F:5F:E5:37 RSSI is nil
[CHG] Device 10:38:1F:60:12:97 RSSI is nil
[CHG] Device 60:A4:23:C9:6D:11 RSSI is nil
[bluetooth]# connect 60:A4:23:C9:6D:11
Attempting to connect to 60:A4:23:C9:6D:11
[CHG] Device 60:A4:23:C9:6D:11 Connected: yes
Connection successful
[NEW] Primary Service (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0001
00001801-0000-1000-8000-00805f9b34fb
Generic Attribute Profile
[NEW] Characteristic (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0001/char0002
00002a05-0000-1000-8000-00805f9b34fb
Service Changed
[NEW] Descriptor (Handle 0x0cb4)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0001/char0002/desc0004
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0001/char0005
00002b2a-0000-1000-8000-00805f9b34fb
Database Hash
[NEW] Characteristic (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0001/char0007
00002b29-0000-1000-8000-00805f9b34fb
Client Supported Features
[NEW] Primary Service (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service000e
0000180a-0000-1000-8000-00805f9b34fb
Device Information
[NEW] Characteristic (Handle 0x1a8d)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service000e/char000f
00002a29-0000-1000-8000-00805f9b34fb
Manufacturer Name String
[NEW] Characteristic (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service000e/char0011
00002a24-0000-1000-8000-00805f9b34fb
Model Number String
[NEW] Characteristic (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service000e/char0013
00002a27-0000-1000-8000-00805f9b34fb
Hardware Revision String
[NEW] Characteristic (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service000e/char0015
00002a26-0000-1000-8000-00805f9b34fb
Firmware Revision String
[NEW] Characteristic (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service000e/char0017
00002a23-0000-1000-8000-00805f9b34fb
System ID
[NEW] Primary Service (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019
00001809-0000-1000-8000-00805f9b34fb
Health Thermometer
[NEW] Characteristic (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a
00002a1c-0000-1000-8000-00805f9b34fb
Temperature Measurement
[NEW] Descriptor (Handle 0x5a34)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a/desc001c
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001d
00002a1d-0000-1000-8000-00805f9b34fb
Temperature Type
[NEW] Characteristic (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001f
00002a1e-0000-1000-8000-00805f9b34fb
Intermediate Temperature
[NEW] Descriptor (Handle 0x8314)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001f/desc0021
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Characteristic (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char0022
00002a21-0000-1000-8000-00805f9b34fb
Measurement Interval
[NEW] Descriptor (Handle 0x88f4)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char0022/desc0024
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Descriptor (Handle 0x9204)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char0022/desc0025
00002906-0000-1000-8000-00805f9b34fb
Valid Range
[NEW] Primary Service (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0026
1d14d6ee-fd63-4fa1-bfa4-8f47b42119f0
Vendor specific
[NEW] Characteristic (Handle 0x1461)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0026/char0027
f7bf3564-fb6d-4e53-88a4-5e37e0326063
Vendor specific
[CHG] Device 60:A4:23:C9:6D:11 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device 60:A4:23:C9:6D:11 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device 60:A4:23:C9:6D:11 UUIDs: 00001809-0000-1000-8000-00805f9b34fb
[CHG] Device 60:A4:23:C9:6D:11 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device 60:A4:23:C9:6D:11 UUIDs: 1d14d6ee-fd63-4fa1-bfa4-8f47b42119f0
[CHG] Device 60:A4:23:C9:6D:11 ServicesResolved: yes
[Thermometer Example]# info
Device 60:A4:23:C9:6D:11 (public)
Name: Thermometer Example
Alias: Thermometer Example
Paired: no
Trusted: no
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Health Thermometer (00001809-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (1d14d6ee-fd63-4fa1-bfa4-8f47b42119f0)
[Thermometer Example]# pair
Attempting to pair with 60:A4:23:C9:6D:11
Request authorization
[agent] Accept pairing (yes/no): yes
[CHG] Device 60:A4:23:C9:6D:11 Paired: yes
Pairing successful
[Thermometer Example]# menu gatt
Menu gatt:
Available commands:
-------------------
list-attributes [dev/local] List attributes
select-attribute <attribute/UUID> Select attribute
attribute-info [attribute/UUID] Select attribute
read [offset] Read attribute value
write <data=xx xx ...> [offset] [type] Write attribute value
acquire-write Acquire Write file descriptor
release-write Release Write file descriptor
acquire-notify Acquire Notify file descriptor
release-notify Release Notify file descriptor
notify <on/off> Notify attribute value
clone [dev/attribute/UUID] Clone a device or attribute
register-application [UUID ...] Register profile to connect
unregister-application Unregister profile
register-service <UUID> [handle] Register application service.
unregister-service <UUID/object> Unregister application service
register-includes <UUID> [handle] Register as Included service in.
unregister-includes <Service-UUID><Inc-UUID> Unregister Included service.
register-characteristic <UUID> <Flags=read,write,notify...> [handle] Register application characteristic
unregister-characteristic <UUID/object> Unregister application characteristic
register-descriptor <UUID> <Flags=read,write...> [handle] Register application descriptor
unregister-descriptor <UUID/object> Unregister application descriptor
back Return to main menu
version Display version
quit Quit program
exit Quit program
help Display help about this program
export Print environment variables
[Thermometer Example]# list-attributes
Primary Service (Handle 0x0009)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0001
00001801-0000-1000-8000-00805f9b34fb
Generic Attribute Profile
Characteristic (Handle 0x52a4)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0001/char0002
00002a05-0000-1000-8000-00805f9b34fb
Service Changed
Descriptor (Handle 0x0015)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0001/char0002/desc0004
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0xa818)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0001/char0005
00002b2a-0000-1000-8000-00805f9b34fb
Database Hash
Characteristic (Handle 0xa818)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0001/char0007
00002b29-0000-1000-8000-00805f9b34fb
Client Supported Features
Primary Service (Handle 0xf920)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service000e
0000180a-0000-1000-8000-00805f9b34fb
Device Information
Characteristic (Handle 0xbed4)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service000e/char000f
00002a29-0000-1000-8000-00805f9b34fb
Manufacturer Name String
Characteristic (Handle 0xbed4)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service000e/char0011
00002a24-0000-1000-8000-00805f9b34fb
Model Number String
Characteristic (Handle 0xbed4)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service000e/char0013
00002a27-0000-1000-8000-00805f9b34fb
Hardware Revision String
Characteristic (Handle 0xbed4)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service000e/char0015
00002a26-0000-1000-8000-00805f9b34fb
Firmware Revision String
Characteristic (Handle 0xbed4)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service000e/char0017
00002a23-0000-1000-8000-00805f9b34fb
System ID
Primary Service (Handle 0xf920)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019
00001809-0000-1000-8000-00805f9b34fb
Health Thermometer
Characteristic (Handle 0xfcb4)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a
00002a1c-0000-1000-8000-00805f9b34fb
Temperature Measurement
Descriptor (Handle 0x0015)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a/desc001c
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x1748)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001d
00002a1d-0000-1000-8000-00805f9b34fb
Temperature Type
Characteristic (Handle 0x1748)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001f
00002a1e-0000-1000-8000-00805f9b34fb
Intermediate Temperature
Descriptor (Handle 0x0015)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001f/desc0021
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Characteristic (Handle 0x3a68)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char0022
00002a21-0000-1000-8000-00805f9b34fb
Measurement Interval
Descriptor (Handle 0x0015)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char0022/desc0024
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
Descriptor (Handle 0x0015)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char0022/desc0025
00002906-0000-1000-8000-00805f9b34fb
Valid Range
Primary Service (Handle 0xf920)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0026
1d14d6ee-fd63-4fa1-bfa4-8f47b42119f0
Vendor specific
Characteristic (Handle 0x9254)
/org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0026/char0027
f7bf3564-fb6d-4e53-88a4-5e37e0326063
Vendor specific
[Thermometer Example]# select-attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a
[DEL] Device 10:38:1F:60:12:97 10-38-1F-60-12-97
[DEL] Device 10:38:1F:5F:E5:37 10-38-1F-5F-E5-37
[DEL] Device 6C:0D:C4:25:A1:B3 6C-0D-C4-25-A1-B3
[DEL] Device 4D:26:80:F6:09:5F 4D-26-80-F6-09-5F
[DEL] Device 10:38:1F:60:13:7B 10-38-1F-60-13-7B
[DEL] Device F0:5E:CD:C8:67:2C BYD BLE3
[DEL] Device A4:C1:38:10:F6:0B LYWSD03MMC
[DEL] Device 5C:46:B0:39:66:94 4802512SZHL221216370
[Thermometer Example:/service0019/char001a]# notify on
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Notifying: yes
Notify started
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 da 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 f0 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 da 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 f0 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 f0 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 fb 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 f0 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 f0 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 fb 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 f0 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 05 4b 00 fd ..K..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 e5 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 fb 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 fb 4a 00 fd ..J..
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Value:
00 05 4b 00 fd ..K..
[Thermometer Example:/service0019/char001a]# notify off
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001a Notifying: no
Notify stopped
[Thermometer Example:/service0019/char001a]# select-attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001d
[Thermometer Example:/service0019/char001d]# read
Attempting to read /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001d
[CHG] Attribute /org/bluez/hci0/dev_60_A4_23_C9_6D_11/service0019/char001d Value:
02 .
02 .
[Thermometer Example:/service0019/char001d]# quit
Linux@Linux:~$
- |
- +1 赞 0
- 收藏
- 评论 0
本文由John提供,版权归世强硬创平台所有,非经授权,任何媒体、网站或个人不得转载,授权转载时须注明“来源:世强硬创平台”。
相关推荐
【经验】STUDIO V5中蓝牙SoC EFR32BG22添加串口LOG打印的方法
在调试Silicon Labs蓝牙SoC EFR32BG22时,一般需要添加LOG打印信息,通过串口的方式来判断代码运行是否正常。由于使用RTT功能在打印信息时无法再次在线调试和代码下载,所以直接采用串口的方式更加便捷。
设计经验 发布时间 : 2021-06-30
【经验】Silicon Labs的蓝牙SoC EFR32BG22如何进行在线的OTA升级?
Silicon Labs的蓝牙SOC EFR32BG目前已经能够支持到蓝牙5.2,工艺升级后的EFR32BG22的功耗能够达到接收4.1mA,0dbm发射功耗3.6mA,休眠功耗低至1.4uA,如此低的功耗,能够大幅延长蓝牙设备的电池续航时间。本文介绍蓝牙SoC EFR32BG22如何进行在线的OTA升级。
设计经验 发布时间 : 2020-06-07
如何读取EFR32BG24系列SoC代码运行PC指针
介绍在EFR32BG24程序运行的过程通过外部方法读取PC指针的方法。
设计经验 发布时间 : 2024-07-01
研讨会2024高算力SOC/MCU新技术研讨会
描述- 9月26日直播,带来SOC,DSP,MCU,AFE,IMU等高算力及周边产品,分享在机器人,多模态感知,AI,低空无人机,自动驾驶,视觉惯性里程计,微型逆变器,光伏储能,智慧医疗,数字健康,光模块等领域应用,点击了解报名
议题- SOC,DSP,MCU,AFE | IMU,传感器,激光雷达 | USB转换,图像处理,电机,连接器等周边产品 | 机器人:多模态感知,电子皮肤,服务机器人,机械手臂, 灵巧手,人形机器人,应用机器人 | AI:视觉AI,AI割草机 | 智能出行:低空无人机,自动驾驶,视觉惯性里程计 | 新能源:微型逆变器,光伏储能 | IoT&医疗:智慧医疗,数字健康,智能电表,光模块 | 全球电子成就奖●年度微控制器/接口产品奖获得者——国民技术(Nations) | MEMS传感器平台的全球领先供应商——TDK InvenSense | 机器人智能计算平台——地平线(Horizon Robotics) | Melexis(迈来芯)——全球五大汽车半导体传感器供应商之一 | 高性能MCU产品及应用解决方案供应商——先楫半导体(HPMicro) | 进芯电子——国内唯一可批量供货的32位工业控制DSP供应商 | 芯片出货量累计130亿颗专注混合SoC制造商:中微半导体(CMSemicon) | 青稞RISC-V内核的MCU和自研PHY的USB/蓝牙/以太网接口芯片——沁恒(WCH) | 全球高性能微控制器单元、显示IC产品的领先半导体公司——Bridgetek(碧洁特) | 全球优秀的USB桥接解决方案专家——FTDI Chip(飞特蒂亚微电子) |
活动 发布时间 : 2024-07-04
选对了针对医疗和可穿戴设备的小型蓝牙芯片,设计毫不费力!
芯科科技一直为医疗设备和可穿戴设备制造商提供小型、专为应用而优化的蓝牙解决方案。以下展示了芯科科技提供的八款小型蓝牙芯片以及快速比较表,可以帮助您为应用程序选择最佳蓝牙解决方案!
应用方案 发布时间 : 2024-02-04
芯科科技EFR32BG27蓝牙SoC助力持续性血糖监测CGM设备长达21天续航时间
在当今医疗领域,持续性血糖监测(CGM)成为人们关注的焦点,特别是对于糖尿病患者而言,实时了解血糖水平变化对于治疗和生活质量的提升具有举足轻重的意义。Silicon Labs提供的极小型、超低功耗EFR32BG27(BG27)蓝牙SoC在CGM中的应用显得尤为突出。本文将详细介绍BG27蓝牙SoC在CGM中的应用及其突出特点。
应用方案 发布时间 : 2024-07-12
【应用】EFR32BG22蓝牙SoC用做CGM连续血糖仪主控,单芯片集成MCU和蓝牙5.2
CGM连续血糖仪为了用户体验更好,要做到小而轻,续航时间长,可以通过手机蓝牙连接获取血糖测量数据。Silicon Labs的蓝牙SoC EFR32BG22在单芯片中集成了MCU和蓝牙5.2,可以作为CGM的主控芯片并实现蓝牙数据收发,有丰富的外设。
应用方案 发布时间 : 2021-07-20
芯科科技提供多款无线连接和控制芯片产品及解决方案,BG2x系列蓝牙SoC成就多样医疗物联网用例,
Silicon Labs(亦称“芯科科技”)的无线SoC和MCU助力全球客户的医疗物联网应用创新,持续打造更智能、高效、安全和便捷的健康监测设备。智能和网联技术近年来一直是医疗和健康保障领域内的热门技术,许多厂商都在利用医疗物联网(IoMT)技术开发更加智能和互联的健康监测设备,以利用物联网、云计算、人工智能和可穿戴等新一代信息通信技术,来帮助用户时刻监控自己的健康状况、降低医疗费用和就医麻烦。
厂牌及品类 发布时间 : 2023-06-29
洞悉标准化蓝牙ESL应用潜力,芯科科技全系列低功耗、高性能蓝牙SoC和模块现已支持最新蓝牙5.4版本
随着蓝牙标准的推陈出新,Silicon Labs(亦称“芯科科技”)也持续升级蓝牙解决方案,全系列低功耗、高性能蓝牙SoC和模块现已支持最新蓝牙5.4版本,以满足开发人员的需求。
厂牌及品类 发布时间 : 2023-08-10
蓝牙可以应用到哪些领域?
蓝牙应用非常广泛,低功耗、广播模式、支持蓝牙5.0、支持UART接口是BLE蓝牙模块或SOC的基本特征,目前蓝牙已经广泛应用于定位标签,资产跟踪,运动及健身传感器,医疗传感器,智能手表,遥控器,玩具等产品中,更多蓝牙模块应用选型可直接在平台搜索查阅。推荐查阅“EFR32无线通信模块优选器件方案”,基于Silicon Labs 蓝牙SOC设计的通信模块,支持蓝牙多协议,zigbee,thread,sub-G,私有协议等。https://www.sekorm.com/doc/808561.html
技术问答 发布时间 : 2018-11-07
BG24蓝牙SoC具备低功耗、小型化等特性,为CoreHW提供蓝牙RTLS的先进解决方案
Silicon Labs(亦称“芯科科技”)的BG24蓝牙SoC具备低功耗、小型化等特性,并支持蓝牙定位技术包括蓝牙到达角(AoA)和蓝牙信道探测(Channel Sounding),为CoreHW公司提供了最先进的实时定位服务(RTLS) 解决方案,以开发出创新的CoreTag和CoreLocator定位应用产品。
应用方案 发布时间 : 2024-06-21
芯科科技全新xG26系列记忆体容量和GPIO翻倍,扩展Matter开发支持
SILICON LABS宣布推出新的xG26系列无线片上系统(SoC)和微控制器(MCU),这是迄今为止物联网行业领先企业性能最高的系列产品。该新系列产品包括多协议MG26 SoC、低功耗蓝牙(Bluetooth LE)BG26 SoC和PG26 MCU。这三款产品的闪存和RAM容量都是芯科科技其他多协议产品的两倍,旨在满足未来物联网(IoT)的需求,以应对一些要求严苛的新兴应用,如Matter。
厂牌及品类 发布时间 : 2024-04-11
2024年版国民技术N32 MCU选型,全面覆盖新能源、工控、汽车、消费、医疗、物联网等各主流应用场景
N32系列MCU是国民技术基于安全SoC技术平台架构,采用32位Arm® Cortex®-M处理器内核,创新打造的以高性能、高集成度、安全、低功耗、高可靠性为特色的MCU产品。产品内置嵌入式高速加密闪存、低功耗电源管理,集成数模混合电路,以及多种密码算法硬件加速引擎和安全单元,全面覆盖新能源、工控、汽车、消费、医疗、物联网等各主流应用场景。
器件选型 发布时间 : 2024-05-16
【经验】蓝牙SoC EFR32BG22的高精度ADC配置步骤与注意事项
Silicon Labs的EFR32BG22系列蓝牙SoC内部集成高精度ADC功能,采用内部1.21V作为Vref,ADC真实有效位数可达13.5bit,使用外部1.25V基准源作为Vref,精度可达14.3bit。本文介绍ADC配置相关步骤以及注意项目。
设计经验 发布时间 : 2020-11-04
【经验】基于studio v5蓝牙SOC EFR32BG22添加OTA的注意事项
本文主要讲解Silicon Labs的基于studio v5蓝牙SOC EFR32BG22添加OTA的注意事项,适用于内部Flash或者外部SPI Flash的OTA升级。
设计经验 发布时间 : 2021-09-20
电子商城
品牌:SILICON LABS
品类:Wireless Gecko SoC
价格:¥15.1445
现货: 16,249
现货市场
品牌:SILICON LABS
品类:Switch Hall Effect Magnetic Position Sensor
价格:¥2.2924
现货:150,000
服务
根据用户的蓝牙模块,使用Bluetooth 蓝牙测试装置MT8852B,测试蓝牙1.0至5.1,包括传输速率、功率、频率、调制和接收机灵敏度,生成测试报告。支持到场/视频直播测试,资深专家全程指导。
实验室地址: 深圳 提交需求>
提供语音芯片、MP3芯片、录音芯片、音频蓝牙芯片等IC定制,语音时长:40秒~3小时(外挂flash),可以外挂TF卡或U盘扩容。
最小起订量: 1pcs 提交需求>
登录 | 立即注册
提交评论