Skip to content

Commit 0b1b914

Browse files
committed
Update documentation
1 parent 1a7f49d commit 0b1b914

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -45,24 +45,24 @@ The following targets have been tested and work with these examples:
4545

4646
It is possible to use the ST Nucleo shield on boards not directly supported by these examples as long as the board has an Arduino UNO R3 connector.
4747

48-
To makes the board compatible with the ST shield three things are required:
48+
To makes the board compatible with the ST shield three things are required:
4949
* Add the BLE feature to your target.
5050
* Add the BLE implementation for the ST shield to the list of modules which have to be compiled.
5151
* Indicate to the BLE implementation that your board use an Arduino connector.
5252

5353
All these operations can be done in the file `mbed_app.json` present in every example.
5454

55-
In the section `target_overrides` add a new object named after your target.
55+
In the section `target_overrides` add a new object named after your target.
5656
In this object two fields are required:
5757
* `"target.features_add": ["BLE"]` Add the BLE feature to the target.
58-
* `"target.extra_labels_add": ["ST_BLUENRG"]`: Add the BLE implementation of the ST shield to the list of the application modules.
58+
* `"target.extra_labels_add": ["CORDIO", "CORDIO_BLUENRG"]`: Add the BLE implementation of the ST shield to the list of the application modules.
5959

6060
As an example, this is the JSON bit which has to be added in the `target_overrides` section of `mbed_app.json` for a `NUCLEO_F411RE` board.
6161

6262
```json
6363
"NUCLEO_F411RE": {
6464
"target.features_add": ["BLE"],
65-
"target.extra_labels_add": ["ST_BLUENRG"]
65+
"target.extra_labels_add": ["CORDIO", "CORDIO_BLUENRG"]
6666
},
6767
```
6868

@@ -120,7 +120,7 @@ chosen. For Nordic Semiconductor targets, the following .hex files will be prese
120120
**Note:** On non Nordic targets, the file to flash can also be named `<module_name>.bin`. Refer to mbed-cli, mbed-os and your board vendor documentation for more informations.
121121

122122

123-
Known issues
123+
Known issues
124124
============
125125

126126
* [NUCLEO_F411RE]: Some BLE examples doesn't work with the X-NUCLEO BLE shield. See [#40](https://github.com/ARMmbed/mbed-os-example-ble/issues/40)

0 commit comments

Comments
 (0)