hcitool scan diz Não existe esse dispositivo


11

Usando o Raspberry Pi 3, teste do Linux 4.4.9-v7 + # 884 SMP sexta-feira, 6 de maio 17:28:59 BST 2016 armv7l GNU / Linux

root@raspberry:/home/user# hcitool scan
Device is not available: No such device

Qual pode ser o problema aqui?

Eu atualizei para o mais recente

#sudo rpi-update

Eu instalei o rpi-bluetooth

#sudo apt-get install rpi-bluetooth

Isso pode ser visto no dmesg:

root@raspberry:/home/user# dmesg | grep Blue
[   43.442353] Bluetooth: Core ver 2.21
[   43.442453] Bluetooth: HCI device and connection manager initialized
[   43.442477] Bluetooth: HCI socket layer initialized
[   43.442494] Bluetooth: L2CAP socket layer initialized
[   43.442528] Bluetooth: SCO socket layer initialized
[   73.520196] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   73.520215] Bluetooth: BNEP filters: protocol multicast
[   73.520238] Bluetooth: BNEP socket layer initialized

EDITAR:

Isso também pode ser interessante, por que o Bluetooth não está aqui ?:

root@raspberry:/home/user# rfkill list
0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no

EDIT 2: Tentei reinstalar o pi-bluetooth

user@raspberry:~ $ sudo apt-get purge bluez-firmware
[sudo] password for user: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  bluez-firmware* pi-bluetooth*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 240 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 47373 files and directories currently installed.)
Removing pi-bluetooth (0.1.0) ...
Purging configuration files for pi-bluetooth (0.1.0) ...
Removing bluez-firmware (1.2-3+rpi1) ...

user@raspberry:~ $ sudo apt-get install pi-bluetooth
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  bluez-firmware
The following NEW packages will be installed:
  bluez-firmware pi-bluetooth
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/92.8 kB of archives.
After this operation, 240 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Selecting previously unselected package bluez-firmware.
(Reading database ... 47354 files and directories currently installed.)
Preparing to unpack .../bluez-firmware_1.2-3+rpi1_all.deb ...
Unpacking bluez-firmware (1.2-3+rpi1) ...
Selecting previously unselected package pi-bluetooth.
Preparing to unpack .../pi-bluetooth_0.1.0_armhf.deb ...
Unpacking pi-bluetooth (0.1.0) ...
Setting up bluez-firmware (1.2-3+rpi1) ...
Setting up pi-bluetooth (0.1.0) ...
Job for hciuart.service failed. See 'systemctl status hciuart.service' and 'journalctl -xn' for details.

Suspeito que o último erro tenha algo a ver com isso: O trabalho do hciuart.service falhou. Consulte 'status do systemctl hciuart.service' e 'journalctl -xn' para obter detalhes.

user@raspberry:~ $ sudo journalctl -xn
-- Logs begin at Sun 2016-05-08 19:48:33 CEST, end at Sun 2016-05-08 19:58:07 CEST. --
May 08 19:52:46 raspberry systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
-- Subject: Unit hciuart.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit hciuart.service has failed.
-- 
-- The result is failed.
May 08 19:52:46 raspberry systemd[1]: Unit hciuart.service entered failed state.
May 08 19:52:46 raspberry hciattach[1279]: Can't initialize device: Success
May 08 19:52:46 raspberry hciattach[1279]: bcm43xx_init


user@raspberry:~ $ systemctl status hciuart.service
● hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; enabled)
   Active: failed (Result: exit-code) since Sun 2016-05-08 19:52:46 CEST; 6min ago
  Process: 1279 ExecStart=/usr/bin/hciattach /dev/ttyAMA0 bcm43xx 921600 noflow - (code=exited, status=1/FAILURE)
user@raspberry:~ $ 

Não deve fazer diferença, mas e se você chamar hcitool com sudo?
rob

Nenhuma diferença, já Gerido sudo festa, então eu estou em um shell de root
www.jensolsson.se

Você resolveu esse problema? Eu me pergunto como você resolveu isso
mozcelikors

11
Vejo o mesmo problema no meu Pi 3 Modelo B V1.2 e descobri que colocar exatamente o mesmo cartão SD no meu Pi 3 B + funcionou sem problemas. Se você tiver outro Pi 3, talvez tente e veja se funciona? Outros já relataram esse problema no passado, mas as correções de software funcionaram para eles e continuam falhando para mim. Não consigo conectar ao módulo BT. github.com/raspberrypi/linux/issues/1314#issuecomment-190788662 , stackoverflow.com/questions/44554255/… , archlinuxarm.org/forum/viewtopic.php?f=60&t=10770
Will Haley

Respostas:


4

Eu tive o mesmo problema

pi@jarvis:~ $ hcitool dev
Devices:

com um hciuart.service inativo

pi@jarvis:~ $ systemctl status hciuart.service
● hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; enabled)
   Active: inactive (dead)

Após um

pi@jarvis:~ $ sudo systemctl start hciuart.service

eu tenho

pi@jarvis:~ $ systemctl status hciuart.service
● hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; enabled)
   Active: active (running) since Sat 2017-05-20 17:42:40 CEST; 2s ago

e

pi@jarvis:~ $ hcitool dev
Devices:
    hci0    B8:27:EB:E5:7C:B0

2

Verifique seu arquivo /boot/config.txt para uma entrada como

dtoverlay=pi3-disable-bt 

e verifique se essa linha é comentada adicionando um # no início da linha. Se não for comentado, esta linha desconectará o bluetooth do UART e conectará o UART aos pinos GPIO. Espero que funcione para você!


0

Não usar BerryBoot, e tentar sudo apt-get updatee sudo apt-get upgrade. Ou você pode reinstalar o mais novo raspbiando site oficial.


11
Como você sabe que o OP usa o BerryBoot e por que ele não deveria usá-lo?
Dmitry Grigoryev
Ao utilizar nosso site, você reconhece que leu e compreendeu nossa Política de Cookies e nossa Política de Privacidade.
Licensed under cc by-sa 3.0 with attribution required.