Keysight U3810 Series Getting Started Guide
97
If nothing is returned, there a known and common problem that the
rfkill
command blocking
Bluetooth was run, and it was not
unblock
ed before reboot. The way to fix this state is to
manually edit the
rfkill
file and enable it. Edit the file
/var/lib/systemd/rfkill/
platform-481a6000.serial:bluetooth
with root permissions—this will require the use of the
nano
editor
[1]
since the file will not be visible on WinSCP. This file has one character in it make
sure it is a “0” (Zero) A “1” (One) in this file will disable Bluetooth and cannot be enabled by the
rfkill
unblock
command if the device is not active. A Reboot is required after changing this file.
2
If the
hciconfig -a
command shows the Bluetooth is down. Check the
rfkill
status using
rfkill list all
.
debian@beaglebone:~$ hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: F0:45:DA:3B:6C:E0 ACL MTU: 1021:6 SCO MTU: 180:4
DOWN
RX bytes:1037 acl:0 sco:0 events:53 errors:0
TX bytes:3461 acl:0 sco:0 commands:53 errors:0
Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
debian@beaglebone:~$ rfkill list all
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3
To remove a blocked state, use the
rfkill unblock bluetooth
command.
Содержание U3810A
Страница 1: ...Keysight U3810A Advanced IoT Teaching Solution Getting Started Guide ...
Страница 78: ...Keysight U3810 Series Getting Started Guide 78 IMU Characteristics from the LSM9DS1 datasheet ...
Страница 131: ...Keysight U3810 Series Getting Started Guide 131 ...
Страница 132: ...Keysight U3810 Series Getting Started Guide 132 Disassembly ...