openmano-mpy/extmod/nimble, branch master

extmod/modbluetooth: Separate enabling of "client" from "central".

2021-02-19T06:53:43+00:00

Previously, the MICROPY_PY_BLUETOOTH_ENABLE_CENTRAL_MODE macro
controlled enabling both the central mode and the GATT client
functionality (because usually the two go together).

This commits adds a new MICROPY_PY_BLUETOOTH_ENABLE_GATT_CLIENT
macro that separately enables the GATT client functionality.
This defaults to MICROPY_PY_BLUETOOTH_ENABLE_CENTRAL_MODE.

This also fixes a bug in the NimBLE bindings where a notification
or indication would not be received by a peripheral (acting as client)
as gap_event_cb wasn't handling it. Now both central_gap_event_cb
and peripheral_gap_event_cb share the same common handler for these
events.

Signed-off-by: Jim Mussared

extmod/modbluetooth: Allow NimBLE to use Zephyr static address.

2021-02-17T00:25:02+00:00

Zephyr controllers can be queried for a static address (computed from the
device ID).  BlueKitchen already supports this, but make them both use the
same macro to enable the feature.

extmod/nimble/hal/hal_uart: Fix HCI_TRACE format specifiers.

2021-02-17T00:24:48+00:00

Makes this work consistently on unix and stm32 ports.

extmod/nimble: Ensure handle is set on read error.

2021-02-16T03:57:10+00:00

On error, the handle is only available on err->att_handle rather than
in attr->handle used in the non-error case.

Signed-off-by: Jim Mussared

extmod/nimble: Improve the flow control for l2cap recv path.

2021-01-30T02:22:40+00:00

If the _IRQ_L2CAP_RECV handler does the actual consumption of the incoming
data (i.e. via l2cap_recvinto), rather than setting a flag for
non-scheduler-context to handle it later, then two things can happen:

- It can starve the VM (i.e. the scheduled task never terminates).  This is
  because calling l2cap_recvinto will empty the rx buffer, which will grant
  more credits to the channel (an HCI command), meaning more data can
  arrive.  This means that the loop in hal_uart.c that keeps reading HCI
  data from the uart and executing NimBLE events as they are created will
  not terminate, preventing other VM code from running.

- There's no flow control (i.e. data will arrive too quickly).  The channel
  shouldn't be given credits until after we return from scheduler context.

It's preferable that no work is done in scheduler/IRQ context.  But to
prevent this being a problem this commit changes l2cap_recvinto so that if
it is called in IRQ context, and the Python handler empties the rx buffer,
then don't grant credits until the Python handler is complete.

Signed-off-by: Jim Mussared

extmod/modbluetooth: Add ble.hci_cmd(ogf, ocf, req, resp) function.

2021-01-22T07:15:12+00:00

This allows sending arbitrary HCI commands and getting the response.  The
return value of the function is the status of the command.

This is intended for debugging and not to be a part of the public API, and
must be enabled via mpconfigboard.h.  It's currently only implemented for
NimBLE bindings.

Signed-off-by: Jim Mussared

extmod/nimble: Don't assert on save-IRK failure.

2020-12-22T23:08:00+00:00

extmod/nimble: Reset NimBLE BSS in mp_bluetooth_init.

2020-12-22T23:07:49+00:00

Without this fix, each time service registration happened it would do an
increasingly large malloc() for service state.

See https://github.com/apache/mynewt-nimble/issues/896.

extmod/nimble: Generate and persist a unique IRK.

2020-12-02T03:44:39+00:00

This provides a workaround for
https://github.com/apache/mynewt-nimble/issues/887.

Without this, all devices would share a fixed default IRK.

Signed-off-by: Jim Mussared

extmod/modbluetooth: Add support for passkey authentication.

2020-12-02T03:43:32+00:00

Signed-off-by: Jim Mussared