This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

cannot create bt0 in raspberry pi3

Hello all,

Environment:

  • Rpi with Raspbian Stretch (Release 9.8)
  • Kernel 4.14.8-v7+
  • Architecture armv7l

I have followed the below links to build BLE 6LoWPAN environment on my Rpi3

All commands were working fine until echo "connect <mac address of other device> 1" > /sys/kernel/debug/bluetooth/6lowpan_control. As seen from the websites, after this command execution, there should be bt0 interface created. But it is not visible in ifconfig -a.

Also the 6lowpan_control file is empty. But when I try to connect the other device using the command hcitool con after executing above command, I am able to see the desired connections in the terminal, still no bt0 device available. I have even tried with the command ifconfig bt0 add 2001:db8::1/64 but resulted with the error SIOGIFINDEX: No such device.

How to resolve this problem?

Note: I think I am facing this same issue.

Parents Reply Children
  • Yes I made sure. Output of commands attached below. The radvd.service status throws error after I added the lines in radvd.conf as suggested in this link.

    I just have a doubt. As Rpi3 have a built-in Bluetooth module, I did not use any external Bluetooth LE USB dongles. I assume Rpi3 has in-built functionality of Bluetooth dongles. Am I wrong or is it fine to use built-in Bluetooth module?

  • Hey,

    A small update. The connection I am seeing in hcitool conn command disappear after a few seconds (around 30 sec). Also the Bluetooth indicator LED in the device is not turned ON after echo "connect <mac address of other device> 1" > /sys/kernel/debug/bluetooth/6lowpan_control command.  From this, I clearly know that the above command was not able to connect my other Bluetooth device

    But I was able to connect the same device and able to see the Bluetooth indicator LED ON while using bluetoothctl commands.

    Please help me to resolve this problem at the earliest.

  • I have used the built-in BLE of RPi3 for this purpose before, you should not need any external Bluetooth module.

    Can you provide a sniffer trace of the connection between the device and the RPi? You can use the nRFSniffer v2 for doing the capture.

    Which firmware are you running on the device that you are trying to connect?

  • Hey Jorgen,

    I have followed these steps by loading the wrong firmware. When I used UDP Client IoT example, I am able to see the bt0 interface. Thank you so much for your support.

    Running UDP client on nRF, I am able to verify both ping and UDP packets on eth0 interface of Rpi3. I have a Windows PC connected to that eth0 of my Rpi3 and I can't ping that PC from my nRF kit.

    I have set eth0 of RPi3 and Ethernet interface of PC (Windows) in the same IPv6 subnet i.e., 2004:db8::/64. Also I removed the radvd.conf from Rpi3 as I know that UDP example of nRF does not send router solicitation messages.

    Am I missing anything here or should I need to do some more steps to make the communication (ping and UDP) success between nRF and my Windows PC.

  • Is the Windows PC connected directly to the RPi through a cable, or does it go through a switch/router?

    Are you able to ping the Windows PC from the RPi using ping6 command?

Related