|author||Andrzej Kaczmarek <email@example.com>||Tue Apr 13 14:36:29 2021 +0200|
|committer||Andrzej Kaczmarek <firstname.lastname@example.org>||Wed Apr 14 09:47:08 2021 +0200|
transport/cmac: Fix race on LL event write HCI commands are processed in LL task context and thus CS/CC events are written to mbox in the same context. This can lead to following race: - CS/CC is written to mbox - interrupt in handled on CMAC *before* command buffer is freed - M33 reads CS/CC and writes next command to mbox - CMAC reads new command This triggers an assert in code because we do not have free buffer for new command because we were busy handling interrupts and did not free it yet. To fix this we should write and free in critical section.
Apache NimBLE is an open-source Bluetooth 5.1 stack (both Host & Controller) that completely replaces the proprietary SoftDevice on Nordic chipsets. It is part of Apache Mynewt project.
Controller supports Nordic nRF51 and nRF52 chipsets. Host runs on any board and architecture supported by Apache Mynewt OS.
If you are browsing around the source tree, and want to see some of the major functional chunks, here are a few pointers:
nimble/controller: Contains code for controller including Link Layer and HCI implementation (controller)
nimble/drivers: Contains drivers for supported radio transceivers (Nordic nRF51 and nRF52) (drivers)
nimble/host: Contains code for host subsystem. This includes protocols like L2CAP and ATT, support for HCI commands and events, Generic Access Profile (GAP), Generic Attribute Profile (GATT) and Security Manager (SM). (host)
nimble/host/mesh: Contains code for Bluetooth Mesh subsystem. (mesh)
nimble/transport: Contains code for supported transport protocols between host and controller. This includes UART, emSPI and RAM (used in combined build when host and controller run on same CPU) (transport)
porting: Contains implementation of NimBLE Porting Layer (NPL) for supported operating systems (porting)
ext: Contains external libraries used by NimBLE. Those are used if not provided by OS (ext)
kernel: Contains the core of the RTOS (kernel/os)
There are also some sample applications that show how to Apache Mynewt NimBLE stack. These sample applications are located in the
apps/ directory of Apache Mynewt repo. Some examples:
If you are having trouble using or contributing to Apache Mynewt NimBLE, or just want to talk to a human about what you're working on, you can contact us via the developers mailing list.
Although not a formal channel, you can also find a number of core developers on the #mynewt channel on Freenode IRC or #general channel on Mynewt Slack
Also, be sure to checkout the Frequently Asked Questions for some help troubleshooting first.
Anybody who works with Apache Mynewt can be a contributing member of the community that develops and deploys it. The process of releasing an operating system for microcontrollers is never done: and we welcome your contributions to that effort.
More information can be found at the Community section of the Apache Mynewt website, located here.
Apache Mynewt welcomes pull request via Github. Discussions are done on Github, but depending on the topic, can also be relayed to the official Apache Mynewt developer mailing list email@example.com.
If you are suggesting a new feature, please email the developer list directly, with a description of the feature you are planning to work on.
Bugs can be filed on the Apache Mynewt NimBLE Issues. Please label the issue as a “Bug”.
Where possible, please include a self-contained reproduction case!
Feature requests should also be filed on the Apache Mynewt NimBLE Bug Tracker. Please label the issue as a “Feature” or “Enhancement” depending on the scope.
We love getting newt tests! Apache Mynewt is a huge undertaking, and improving code coverage is a win for every Apache Mynewt user.
The code in this repository is all under either the Apache 2 license, or a license compatible with the Apache 2 license. See the LICENSE file for more information.