IPv6 Compatible BLE dongle

[FormerMember]

I just started trying to get an IOT IPv6 application up and running. On the nrf51882 end, I have flashed the IPv6 COAP server. The LED on the device is happily flashing away, so it could be working. The next step is to set up the Linux end.

I'm using Ubuntu 15.04 which has the necessary modules 6lowpan and bluetooth_6lowpan. I believe I have set everything up correctly. One point troubles me:

In the directory

/sys/kernel/debug/bluetooth

I can see 6lowpan_control and 6lowpan_enable. I can't see the 6lowpan_psm file, which means the echo 35 > .... Command always fails. When I say fails, a permission denied error message appears regardless of using sudo or sudo us. I've tried different BLE dongles, with the same result. I have also read that a BLE dongle with a Broadcom chipset is necessary. I have ordered a Broadcom based dongle just to check this out. Hopefully I will receive it in the next couple of days.

[Lukasz Duda]

Hello Paul!

Linux implementation of bluetooth_6lowpan module for debugfs has been changed since Kernel version 4.0.

So right now to establish connection with the nRF51 kit you should use below set of commands:

# Load 6LoWPAN module.
modprobe bluetooth_6lowpan

# Enable the bluetooth_6lowpan module.
echo 1 > /sys/kernel/debug/bluetooth/6lowpan_enable

# Establish connection with device
echo "connect XX:XX:XX:XX:XX:XX 1" > /sys/kernel/debug/bluetooth/6lowpan_control

Please check documentation of our new release for nRF52 to get more details: nRF5 IoT SDK - Connecting devices to the router

Regarding to the BLE dongles issue - you should be able to use all dongles with Bluetooth 4.0 support.

[FormerMember]

It works nicely. The dongle as you say isn't an issue. On my work computer it didn't work, but at home on my home computer, it works perfectly. However there is one difference between the two systems. At home I'm using the RedBearLab nano with 32kb of ram. Hcitool lescan detects the COAP server with no problems. At work I was unable to detect the COAP server, perhaps indicating it was not running.