You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Systematically use relative_url filter for links (#408)
This allows us to deploy with a base URL which is helpful for preview deployments. It's not ideal but it's a pragmatic way to sort out our review deployment setup.
This requires Jekyll to be upgraded to the latest 3.x for relative_url support. Note if you don't install the latest it just silently fails to work.
Copy file name to clipboardExpand all lines: accessories/making-accessories.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,14 +14,14 @@ A [list of available accessories](https://microbit.org/buy/accessories/) is main
14
14
15
15
## Using the Edge Connector
16
16
17
-
The micro:bit[card edge connector](/hardware/edgeconnector), commonly referred to as the 'edge connector' or the 'pins', is compatible with a standard 1.27mm, 2x40 edge connector socket.
17
+
The micro:bit[card edge connector]({{ "/hardware/edgeconnector" | relative_url }}), commonly referred to as the 'edge connector' or the 'pins', is compatible with a standard 1.27mm, 2x40 edge connector socket.
18
18
19
19
Where possible your accessory design should implement this socket, making it simple for your users to plug in and remove the micro:bit board.
20
20
21
-
There are [limitations to the current that can be drawn from the micro:bit](/hardware/powersupply), accessories must be designed carefully to ensure they do not damage the micro:bit, or that the micro:bit cannot damage them.
21
+
There are [limitations to the current that can be drawn from the micro:bit]({{ "/hardware/powersupply" | relative_url }}), accessories must be designed carefully to ensure they do not damage the micro:bit, or that the micro:bit cannot damage them.
22
22
23
-
-[micro:bit edge connector and pinout](/hardware/edgeconnector)
24
-
-[powering accessories from the micro:bit](/hardware/powersupply)
23
+
-[micro:bit edge connector and pinout]({{ "/hardware/edgeconnector" | relative_url }})
24
+
-[powering accessories from the micro:bit]({{ "/hardware/powersupply" | relative_url }})
25
25
26
26
### V2 revision
27
27
@@ -31,7 +31,7 @@ The edge connector on the <span class="V2">V2</span> board revision is backwards
31
31
32
32
There are two rounded rectangular pads on the back of the micro:bit. These allow you to connect a battery holder via a mechanism other than the JST connector.
33
33
34
-
34
+
![Picture of the two rounded rectangular pads]({{ "/docs/accessories/assets/making-accessories-d7c25.png" | relative_url }})
35
35
36
36
The upper pad is 0V or GND and the lower pad is 3V.
Copy file name to clipboardExpand all lines: blog/latest-revision-announcement.md
+9-10Lines changed: 9 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,8 +13,7 @@ lang: en
13
13
Today we’re [announcing a new version of the BBC micro:bit](https://microbit.org/new-microbit/), adding a speaker, a microphone and the CPU power to run AI and Machine Learning workloads. With these additional capabilities, we are opening up the world of AI and ML to the same collaborative design and innovation that led to the original micro:bit’s success.
14
14
15
15
This article is a more technical companion to the [news over at microbit.org](https://microbit.org/new-microbit/).
Although the latest micro:bit isn’t available to buy yet, we’re talking about it now because the micro:bit isn’t about one organisation, or the official editors, or even one device.
20
19
@@ -34,7 +33,7 @@ At the Micro:bit Educational Foundation we are working with Lancaster University
34
33
35
34
## We’re building this together, not alone
36
35
37
-
{: width="600"}
36
+
![A wall of micro:bit accessories]({{ "/docs/blog/assets/latest-revision/accessory-wall-bett.jpg" | relative_url }}){: width="600"}
38
37
*The wall of accessories displayed at BETT*
39
38
40
39
We recognise and support the huge contribution the wider micro:bit ecosystem makes to our community, and so we are making available all [key technical information about the new micro:bit](https://support.microbit.org/support/solutions/articles/19000119052-details-of-micro-bit-v2), and open source tools to make it easy to support in advance of the device being available to users.
@@ -49,11 +48,11 @@ We’ve compiled all this information on an updated version of tech.microbit.org
49
48
50
49
## Creating code for the latest micro:bit
51
50
52
-
The latest micro:bit supports all features of the original version so there are many cases where a user won’t need to distinguish between the devices; every tutorial or programme that already exists today is supported on the latest hardware. However, as the machine code that runs on the two devices is different, the latest micro:bit supports a new kind of hex. We’re calling it ‘[universal hex](/software/hex-format/)’: this contains the machine code for both versions of the micro:bit. Thanks to the fantastic support of NXP who have worked on [DAPLink](https://github.com/ARMmbed/DAPLink), the Arm project that enables the micro:bit USB interface, the latest micro:bit is able to choose which code it should use from the universal hex. The files are designed so the original micro:bits do not need any update to use them.
53
-
51
+
The latest micro:bit supports all features of the original version so there are many cases where a user won’t need to distinguish between the devices; every tutorial or programme that already exists today is supported on the latest hardware. However, as the machine code that runs on the two devices is different, the latest micro:bit supports a new kind of hex. We’re calling it ‘[universal hex]({{ "/software/hex-format/" | relative_url }})’: this contains the machine code for both versions of the micro:bit. Thanks to the fantastic support of NXP who have worked on [DAPLink](https://github.com/ARMmbed/DAPLink), the Arm project that enables the micro:bit USB interface, the latest micro:bit is able to choose which code it should use from the universal hex. The files are designed so the original micro:bits do not need any update to use them.
52
+
![Creation of a Universal Hex]({{ "/docs/blog/assets/latest-revision/uhex2.png" | relative_url }})
54
53
55
54
To make the experience of developing programs for these universal hexes as seamless as possible we’ve deepened our collaboration with Arm, Lancaster University and [Microsoft Research](https://www.microsoft.com/en-us/research/project/the-bbc-microbit-and-microsoft/), who were [co-creators of the original micro:bit,](https://www.lancaster.ac.uk/news/articles/2016/lancaster-university-helps-bbc-get-kids-coding/). Because of the open source nature of [Lancaster’s CODAL](https://github.com/lancaster-university/codal), the evolution of the original microbit-dal, we had a ready platform to make the latest micro:bit work. We have also included a full compatibility layer for [microbit-dal](https://github.com/lancaster-university/microbit-dal), so that existing projects and environments can be easily recompiled to work on the latest board. On top of the careful compatibility work there’s plenty of exciting new features designed for the latest hardware, like an advanced SoundExpressions synthesiser and audio pipeline architecture.
56
-
{: width="600"}
55
+
![micro:bit Software Architecture with CODAL]({{ "/docs/blog/assets/latest-revision/software-overview-v2.svg" | relative_url }}){: width="600"}
57
56
58
57
MakeCode, MicroPython and Scratch are using CODAL to support the new device, and we recommend that anyone building software to run on the micro:bit do the same to ensure consistent experience across micro:bit editors. This will also ensure that as new features get added they can be incorporated easily and made available to users (it’s easy to forget that micro:bit radio wasn’t in the original micro:bit release!)
59
58
@@ -63,7 +62,7 @@ When it launched in 2015, one of the key goals of the original micro:bit was to
63
62
64
63
Part of ensuring this was putting the same hardware that real developers were using at the time into the hands of students. This is what has enabled some of the more incredible uses of the micro:bit: [Handwriting recognition using an optical mouse sensor](https://www.cs.ox.ac.uk/teaching/studentprojects/630.html); [use in a BLE mesh](https://docs.zephyrproject.org/latest/samples/bluetooth/mesh_demo/README.html), a [presentation remote](https://os.mbed.com/teams/microbit/code/microbit_presenter/), or a [custom piece of assistive technology.](https://hackaday.io/project/26143-handshake)
65
64
66
-
{: width="600"}
65
+
![Creation of a Universal Hex]({{ "/docs/blog/assets/latest-revision/nrf52833.jpg" | relative_url }}){: width="600"}
67
66
68
67
With the latest micro:bit, we’re doing this again: the [nRF52833](https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52833) is a modern, exciting part recently released by Nordic, and being used across the industry for new designs. It’s capable of running machine learning workloads, and so opens up a new realm of possibilities, both for applications of the device, but especially for helping to expose and demonstrate what machine learning really is: not magic, but sufficiently advanced application of technology.
69
68
@@ -73,21 +72,21 @@ The original micro:bit elegantly demonstrated the technology in a phone (the scr
73
72
74
73
Music and sound on the micro:bit were pioneered in MicroPython as part of the original community effort around the BBC micro:bit – not least thanks to Nicholas Tollervey and Mark Shannon for introducing things like the [speech synthesizer](https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52833)! Now with the addition of a speaker to the latest micro:bit it is really coming into its own. If you connect headphones or an amplified speaker, you get even better quality sound. Just as the 5x5 display on the micro:bit is perfect for getting started, but a colour LCD is still a welcome way to extend your projects, the sound driver written by Lancaster University is capable of reproducing high quality sound on the edge connector. We don’t expect to see the end of crocodile clips connecting headphone jack sockets just yet!
But beyond music, sound is the way many of us communicate. Our voice and our accent is part of our identity and personality. When adding ‘sound’ as a feature of the micro:bit we wanted to make sure we gave it a personality too. The careful thought put into the visual and structural elements of the micro:bit, led by Technology Will Save Us in 2015 showed how paying careful attention to design of a device had a huge impact its approachability, and the ease with which people could make an emotional connection to hardware. The sounds for the micro:bit learn from this, and are there to make the micro:bit’s voice friendly and approachable. We’ve been working on a synthesiser to make these amazing sounds, with lots of input from a sound designer to tune it and make it useful.
79
78
80
79
The microphone, like the microphones on a smart speaker or digital assistant, allows the device to respond to sound and sense the noise around the micro:bit. Paired with the greater capability of the new micro:bit this is opening up fantastic potential around AI and machine learning with sound. Exemplifying the thought given to educational environments, the microphone’s dedicated ‘operating’ indicator doesn’t interfere with the visual design of the board when off, but makes it clear when the microphone is on and sensing sound. This allows teachers to engage with students about privacy issues and the impact of listening devices.
Within days of getting a device, Gordon Williams, lead developer of [Espruino](https://www.espruino.com/) had the micro:bit supported in their online platform. This allowed JavaScript programs to run on the device, including Espruino’s gesture recognition libraries that were originally designed for bangle.js and use Tensorflow Lite. Unlike the "gestures" you might be used to on the micro:bit, like "shake", this demo allows you to train a machine learning model to recognise any gestures you can collect data for - it takes recordings of the gestures being performed, and builds a model that can recognise them. This means you can have much more complex, subtle gestures, and even customise them for yourself or something you’ve attached the micro:bit to.
87
86
88
87
[Edge Impulse](https://www.edgeimpulse.com/), working similarly fast, took a video recording of each member of the micro:bit team saying “micro:bit” three times (what better way to conclude the weekly team meeting?) and used the Edge Impulse cloud service to create a model that could recognise the word “micro:bit” being said. [You can read more about this demo here](https://www.edgeimpulse.com/blog/voice-activated-microbit), but it clearly shows the possibility of training micro:bits to recognise unique sounds!
Copy file name to clipboardExpand all lines: bluetooth/index.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ The micro:bit supports Bluetooth via a single, custom-developed, BBC micro:bit p
33
33
34
34
A pre-compiled hex file is available to download for <spanclass="v2">V2</span> that enables all Bluetooth services.
35
35
36
-
[Bluetooth all services CODAL](/docs/bluetooth/assets/BLE_All_Services_CODAL_0-2-40-ABDLIMTU-P.hex){: .btn.sm-btn download}
36
+
[Bluetooth all services CODAL]({{ "/docs/bluetooth/assets/BLE_All_Services_CODAL_0-2-40-ABDLIMTU-P.hex" | relative_url }}){: .btn.sm-btn download}
37
37
38
38
The source for this can be found in the [microbit-v2-samples](https://github.com/lancaster-university/microbit-v2-samples/blob/master/source/samples/BLETest.cpp) repository.
39
39
@@ -43,9 +43,9 @@ The BBC micro:bit <span class="v1">V1</span> [Bluetooth profile is defined in th
43
43
44
44
You can flash one of two pre-compiled Hex files to the micro:bit <spanclass="v1">V1</span> that enable bluetooth services. As Bluetooth is memory intensive, these are supplied as either 'without Magnetometer Service' or 'without DFU Service':
The DAL contains the [C++ source for the BLE service files](https://github.com/lancaster-university/microbit-samples/blob/master/source/examples/bluetooth-services/main.cpp).
51
51
@@ -103,7 +103,7 @@ As an example, the tools at [ML Machine](https://ml-machine.org/) have been buil
103
103
Note: on micro:bit V1, there is very limited memory available when also using the Bluetooth extension.
104
104
105
105
Here is an example of how to add and use the Bluetooth extension in MakeCode:
106
-
106
+
![adding makecode bluetooth extension]({{ "/docs/bluetooth/assets/add_bluetooth_extension.gif" | relative_url }})
@@ -29,9 +29,9 @@ The interface processor does not connect to any of the micro:bit peripherals.
29
29
30
30
Two key pieces of information to help understand the internals of the micro:bit are:
31
31
32
-
- The [schematics](../schematic), which shows the detailed component data and connectivity of the device.
32
+
- The [schematics]({{ "/hardware/schematic/" | relative_url }}), which shows the detailed component data and connectivity of the device.
33
33
34
-
- The [reference design](../reference-design), which is a complete module design of a compatible micro:bit, and is designed to be a starting point for anyone interested in understanding the micro:bit or designing their own variant.
34
+
- The [reference design]({{ "/hardware/reference-design/" | relative_url }}), which is a complete module design of a compatible micro:bit, and is designed to be a starting point for anyone interested in understanding the micro:bit or designing their own variant.
35
35
36
36
## Hardware Description
37
37
@@ -48,7 +48,7 @@ There is an on-board 2.4GHz radio engine used to provide Bluetooth capabilities
48
48
| RAM | 16KB
49
49
| Speed | 16MHz
50
50
| Debug | SWD, jlink/OB
51
-
| More Info | [here](/software)
51
+
| More Info | [here]({{ "/software" | relative_url }})
52
52
53
53
### Bluetooth Wireless Communication
54
54
@@ -65,7 +65,7 @@ This allows the micro:bit to communicate with a wide range of Bluetooth devices,
65
65
| Role | [GAP Peripheral](https://bluetooth-developer.blogspot.com/2016/07/microbit-and-bluetooth-roles.html)
66
66
| Congestion avoidance | Adaptive Frequency Hopping
0 commit comments