Skip to content

Commit 83287af

Browse files
Squashed 'docs/' changes from ae437c7..3f33b0f (#98)
3f33b0f add audio expression api 8ac53a3 update BLE profile roles 38464b4 Update Soft Device SD140 > SD113 (#198) 0f1b15d add new brand guidelines info 3d3c6ed fix links 8260131 fix links 504c6df remove link to uhex spec as it 404s bee772f remove link to python mailing list ce75bb4 remove duplicate MakeCode 21c6a16 update table 200mA > 190mA 9cffab0 Update info on MakeCode blocks cc01c0f Latest updates for MakeCode and DAPLink (#193) 18ff8f7 Update hex-format.md: add missing space (#190) af73c3c Update apps-and-examples.md: add missing space (#189) 1f7d600 Spelling mistake (#186) b24c88f Re-phrasing bluetooth section (#181) 4007b76 Rephrase "lozenge" to "rounded rectangular" (#180) f8ca9aa Merge pull request #179 from Gadgetoid/spelling afe3441 Spelling and consistency tweaks 7b0e132 Merge pull request #175 from Gadgetoid/doc-consistency ac8b131 Consistent use of whitespace and Markdown formatting 670d1f1 Remove hard linebreaks and trailing whitespace (#174) 6be457a update iOS beta instructions (#173) 1b2f2ec Update DAPLink error message (#171) 955cf1a spelling git-subtree-dir: docs git-subtree-split: 3f33b0f
1 parent 1164aba commit 83287af

File tree

6 files changed

+9
-10
lines changed

6 files changed

+9
-10
lines changed

bluetooth/index.md

+1-3
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,7 @@ The micro:bit processor has an on-board [Bluetooth](http://blog.bluetooth.com/a-
1616
## Bluetooth software stack
1717

1818
<span class="v1">v1</span> Nordic Semiconductor [Soft Device S110](https://www.nordicsemi.com/Software-and-Tools/Software/S110)
19-
<span class="v2">V2</span> Nordic Semiconductor [Soft Device S140](https://www.nordicsemi.com/Software-and-tools/Software/S140)
20-
21-
We may switch to [S113](https://www.nordicsemi.com/Software-and-tools/Software/S113) and [S122](https://www.nordicsemi.com/Software-and-tools/Software/S122) at compile time to save flash memory (if this affects anything you are working on please [contact micro:bit support](https://support.microbit.org/en/support/tickets/new)).
19+
<span class="v2">V2</span> Nordic Semiconductor [Soft Device S113](https://www.nordicsemi.com/Software-and-tools/Software/S113)
2220

2321
Using Bluetooth, you can connect to other devices and send and receive data from and to the micro:bit.
2422

bluetooth/profile.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -28,13 +28,13 @@ The DAL contains the [C++ source for the BLE service files](https://github.com/l
2828

2929
There are also some example programs in the [microbit-samples](https://github.com/lancaster-university/microbit-samples) repository:
3030

31-
- [bluetooth-eddystone-uid]https://github.com/lancaster-university/microbit-samples/tree/master/source/examples/bluetooth-eddystone-uid
31+
- [bluetooth-eddystone-uid](https://github.com/lancaster-university/microbit-samples/tree/master/source/examples/bluetooth-eddystone-uid)
3232

33-
- [bluetooth-eddystone-url]https://github.com/lancaster-university/microbit-samples/tree/master/source/examples/bluetooth-eddystone-url
33+
- [bluetooth-eddystone-url](https://github.com/lancaster-university/microbit-samples/tree/master/source/examples/bluetooth-eddystone-url)
3434

35-
- [bluetooth-uart]https://github.com/lancaster-university/microbit-samples/tree/master/source/examples/bluetooth-uart
35+
- [bluetooth-uart](https://github.com/lancaster-university/microbit-samples/tree/master/source/examples/bluetooth-uart)
3636

37-
The micro:bit has a Bluetooth 4.1 stack with Bluetooth Low Energy (BLE) and supports the [GAP Peripheral Role](https://bluetooth-developer.blogspot.com/2016/07/microbit-and-bluetooth-roles.html).
37+
The micro:bit has a <span class="v2">v2</span>Bluetooth 5.0/<span class="v1">v1</span>Bluetooth 4.1 stack with Bluetooth Low Energy (BLE) and supports the <span class="v1">v1</span>[GAP Peripheral Role](https://bluetooth-developer.blogspot.com/2016/07/microbit-and-bluetooth-roles.html) and <span class="v2">v2</span> GAP Peripheral and Central device roles.
3838

3939
It operates in the ISM (Industrial Scientific Medical) band, as per all Bluetooth devices. This starts at **2.4GHz and ends at 2.41GHz**. BLE divides the frequency band into 50 x 2MHz bands of which 40 are used. These are called **channels** and numbered **0 to 39**. Channels 37, 38 and 39 are used for "advertising".
4040

hardware/index.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ There is an on-board 2.4GHz radio peripheral used to provide Bluetooth and custo
5555

5656
### Bluetooth Wireless Communication
5757

58-
The on-board 2.4GHz supports Bluetooth communications via the [Nordic S140 SoftDevice](https://www.nordicsemi.com/Software-and-Tools/Software/S140), which provides a fully qualified Bluetooth low energy stack.
58+
The on-board 2.4GHz supports Bluetooth communications via the [Nordic S113 SoftDevice](https://www.nordicsemi.com/Software-and-Tools/Software/S113), which provides a fully qualified Bluetooth low energy stack.
5959
This allows the micro:bit to communicate with a wide range of Bluetooth devices, including smartphones and tablets.
6060

6161
| item | details

latest-revision/latest-revision-accessories.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ There are a few considerations for people who have made accessories.
3939

4040
## Denoting compatibility
4141

42-
The Foundation Brand Guidelines set out how to denote board compatibility for your accessory. An updated version will be published at https://microbit.org/brand-guidelines/. In the meantime, please [get in contact for an updated copy](mailto:[email protected]?subject=Request%20for%20access%20to%20brand%20book).
42+
The Foundation [Brand Guidelines](https://microbit.org/brand-guidelines/) set out how to denote board compatibility for your accessory.
4343

4444
## Board changes
4545

latest-revision/latest-revision-main.md

+1
Original file line numberDiff line numberDiff line change
@@ -115,6 +115,7 @@ When they are finalised, we will notify people via the [DAL, Editors and Devices
115115

116116
| API | Usage | Status | GitHub Issues |
117117
| ------------------------------------------ | ------------ | ---------------------------- | ------------- |
118+
| play sound expression (giggle, happy, hello, mysterious, sad, slide, soaring, spring, twinkle, yawn) | `audio.play("hello")`|| |
118119
| Choose music/pitch output pin | `music.play(music.JUMP_UP, pin=microbit.pin_speaker, wait=True)` || |
119120
| Stop music on pin | `music.stop(pin=microbit.pin_speaker)` || |
120121
| Set the volume 0-255 | `microbit.set_volume(128)` || |

software/runtime.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ micro:bit was based on the well-established Mbed 2.0 SDK, with which Mbed 5 is c
103103

104104
The Mbed abstraction for the Nordic chip is built on top of the Nordic nRF5 SDK https://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF5-SDK
105105

106-
Crucially, this includes Nordic's [Soft Device 110](https://www.nordicsemi.com/Software-and-Tools/Software/S110) <span class="v1">v1</span> / [Soft Device 140](https://www.nordicsemi.com/Software-and-tools/Software/S140) <span class="v2">V2</span>, a binary object that gets included into any hex file for the micro:bit that manages control of the radio to allow the micro:bit to use the industry standard Bluetooth Low Energy protocols.
106+
Crucially, this includes Nordic's [Soft Device 110](https://www.nordicsemi.com/Software-and-Tools/Software/S110) <span class="v1">v1</span> / [Soft Device 113](https://www.nordicsemi.com/Software-and-tools/Software/S113) <span class="v2">V2</span>, a binary object that gets included into any hex file for the micro:bit that manages control of the radio to allow the micro:bit to use the industry standard Bluetooth Low Energy protocols.
107107

108108
The SoftDevice runs on the same MCU as the user's code, and when using the Mbed BLE APIs (that the micro:bit runtime also uses), calls are made into SoftDevice. SoftDevice also occupies the highest priority interrupts, so that user code can be pre-empted by SoftDevice when this is required for the radio to function properly.
109109

0 commit comments

Comments
 (0)