bluetooth 5 TCP application stream between nrf52840 DK and nrf52840 Dongle on debian stretch

RE: bluetooth 5 TCP application stream between nrf52840 DK and nrf52840 Dongle on debian stretch

Mttrinh — Tue, 23 Oct 2018 13:18:39 GMT

[quote user="rtisys"]Also, since I want to use bluetooth 5, don't understand impact of open hci "only supporting" ble - if, indeed, that statement is correct? [/quote]

Not sure what you mean by this, but zephyr is Bluetooth 5.0 compliant. Have a look at the documentation here.

RE: bluetooth 5 TCP application stream between nrf52840 DK and nrf52840 Dongle on debian stretch

rtisys — Wed, 17 Oct 2018 17:56:40 GMT

Mttrinh,

Thanks for your note. Pretty much committed to zephyr at this point, so won't look further into softdevices. Have not been able to get hci0 to init...."cannot assign requested address (99)". Also, since I want to use bluetooth 5, don't understand impact of open hci "only supporting" ble - if, indeed, that statement is correct? Looking into alternatives for communicating between debian platform and nrf52840 dongle if I can't get open HCI to init link.

Cheers,

Chuck

RE: bluetooth 5 TCP application stream between nrf52840 DK and nrf52840 Dongle on debian stretch

Mttrinh — Wed, 17 Oct 2018 15:48:22 GMT

Hi,

Sorry for the late reply, have you had any progress on this issue?

[quote user="rtisys"]So, if I intend to stick w/Zephyr, soft devices won't be a part of my project (Is that correct?).[/quote]

Yes, that is correct.

RE: bluetooth 5 TCP application stream between nrf52840 DK and nrf52840 Dongle on debian stretch

rtisys — Thu, 11 Oct 2018 18:24:42 GMT

I've done a bit more digging and have cleared up some of my misconceptions about what layers do what functions......this may all be "old news" to most BT developers, but the following - and, particularly, comments and corrections - may be of help to other new comers. Thanks in advance.

-Some of my pca10059 download issues might be due to lack of JTAG support chip on that board. Several posts discuss using a pca10056 (DK) to address that problem. WIll get a flash cable and try to "play through" the pca10056 to program the pca10059 once I get a handle on the software issues (see below).

- I found a white paper that describes the role of softdevices (Nordic) vs Zephyr stack (Nordic contributed). So, if I intend to stick w/Zephyr, soft devices won't be a part of my project (Is that correct?). Also, since I need to get a reliable byte stream into my Linux platform, I will need an exposed HCI interface for the hci daemon and higher stack levels. That's another reason to focus on the hci firmware.

- The Zephyr hci-usb seems to be a placeholder at present waiting for further development. Don't know if anyone is currently working in that area.

-Looks like I should be using Zephyr hci-uart. Without doing some rewire on the pca10059, I'm guessing the best thing to do is use a pca10056 DK to run the hci-uart firmware. Luckily, I have several of these, so no problem. It builds and runs on the DK. (cmake -DBOARD=nrf52840_pca10056 ,,/,,/ in Zephyr tool chain). There was at least one note that hci-uart would only support BT 4.2 and not BT 5...don't know just what this means-or if its accurate.

-hciattach (or btattach) appears to find the pca10056 runing hci-uart firmware on linux device /dev/ttyACM0. But, hciconfig shows it as DOWN. Attempts to bring it up with "hciconfig hc0 up" yield an error 99 - see below.

sudo hciconfig dev

hci0:   Type: Primary Bus: UART
   BD Address: 00:00:00:00:00:00 ACL MTU: 27:7 SCO MTU: 0:0
   DOWN
   RX bytes:231 acl:0 sco:0 events:16 errors:0
   TX bytes:88 acl:0 sco:0 commands:16 errors:0

sudo hciconfig hci0 up

Can't init device hci0: Cannot assign requested address (99)

OS is Debian Stretch

4.9.0-4-amd64

But, intend to move to Raspberry PI Debian Stretch once things work.

Regards,

Chuck McP