ARMmbed
/
mbed-os
mirror of https://github.com/ARMmbed/mbed-os.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

BLE: Update cordio porting guide 

Remove the section "Include prebuilt libraries" as it is not applicable
anymore.
pull/6950/head
Vincent Coubard 2018-04-25 11:48:23 +01:00 committed by adbridge
parent feeb83a916
commit 26b5b0072f
1 changed files with 0 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
features/FEATURE_BLE/targets/TARGET_CORDIO/doc/PortingGuide.md
View File

@ -37,37 +37,6 @@ property of the target.
} }
``` ```
### Include prebuilt libraries
Last, the target shall also include the cordio libraries into the build.
Four prebuilt libraries are provided:
* `wscore`: which contains the base component used by the Cordio stack.
* `wsstack`: The BLE stack itself, if contains the GAP and GATT layer as well as
the Security manager implementation.
* `wssec`: The low level implementation of the security layer.
* `wshci`: The HCI layer.
The `wssec` and `wshci` libraries are delivered in feature folders. It allows
vendors to override those library if necessary. This can be required if the port
use specific crypto routine or require an highly modified HCI layer.
To include the default library in the target, the features have to be added in
this list of the features of the target:
* `WSSEC`: Include the default `wssec` library.
* `WSHCI`: Include the default `wshci` library.
The target should also compile the sources of the BLE Cordio port. It is
achieved by adding the string `CORDIO` in the list of the `extra_labels`
property of the target.
```json
"TARGET_NAME": {
"extra_labels": ["target extra labels ...", "CORDIO"],
"features": ["target features ...", "BLE", "WSHCI", "WSSEC"]
}
```
## CordioHCIDriver implementation: ## CordioHCIDriver implementation:
A port shall include an HCI driver for the BLE module used by the target and A port shall include an HCI driver for the BLE module used by the target and