Beetle is a small daemon that provides simplified access to a bluetooth interface. It listens on a local port (usually 6969) and uses a line-oriented text protocol described in detail in the commands list.
RELEASE 1.4 of the sama5 and bbgw Potenco Fixes Null string was not forwarded from Hubby to Client Callback function. OTA Record integrated into Yocto Build OTA Uploader http 409 Was not being handled correctly. Watcher script failed to restart if ps was not present.
There are three ways to build beetle:
yocto (cross-compiled for raspi)
$ cd ../rpi-build; bitbake beetle
cmake (local Linux)
$ ./build-linux-x86.sh
autoconf (local Linux)
$ ./build-local.sh
If you've built using autoconf recently, you may need to cd pkg; make distclean before doing another yocto build.
The local builds deposit a beetle in pkg/src/. The yocto build deposits it in your yocto build folder.
There are two fundamental "modes" for beetle:
central mode (mod cen) -- as a hub that relays peripheral advertisements and may open connections to one or more peripherals at once central.c
peripheral mode (mod per) -- as a peripheral with characteristics (attributes) that can be read or written peripheral.c
It starts in central mode, and switches to peripheral mode by request. Hubby (the hub software) uses peripheral mode for configuring wifi.
Both modes use a simple event loop and command parser. The bluetooth interface is abstracted as much as possible into the HCI layer.