Packages console, log and stats allow to choose stub or full
implementation. All apps had either stub or full implementation
hardwired in pkg.yml file. Now it can be easily overriden in target.
This also changes defunct setting
of CONSOLE_MODE to CONSOLE_IMPLEMENTATION in all apps.
Transport package should not be included directly.
Instead, nimble/transport should be included and
BLE_HCI_TRANSPORT syscfg value should specify transport,
and this will include correct package.
This commit changes nimble/transport/ram to nimble/transport in
all applications that still have deprecated way of transport
selection.
Default value of BLE_HCI_TRANSPORT is ram so syscfg.yml for
targets does not need to be updated.
Replace store/ram with store/config in nimble apps dependencies.
Package store/ram is deprecated and store/config shall be used with
BLE_STORE_CONFIG_PERSIST set to 0.
This PR adds support for various log modules which is possible
thanks to modlog feature. With this feature we can specify
a logging level for each module separately which could have the
following advantages:
- Being able to filter out only the logs that we are interested in at
the moment
- Controlling log level in runtime
- Improved readability if we start printing module name in log header
- Ability to use color-coded log messages by mapping module to a
specific color
The Mesh specification doesn't support more than 32 transport layer
segments, the way the number was so far derived from the advertising
buffer count could result in a highre numbe than 32, thereby wasting
memory. Make the number of supported segments build-time configurable
through a new BT_MESH_TX_SEG_MAX configuration option.
Every sample nimble app used to register the `ble_hs_log` with the
console handler.
Now that the `ble_hs_log` doesn't exist, there is no need for apps to
register it.
Also, use the modlog package to write application log entries rather
than the log API.
Michal Gorecki