This is a very simple guide, reviewing the steps required to get Blinky working on an Mbed OS platform.
Mbed OS Blinky
This example shows the use of a DigitalOut object to represent an LED and use of the nonblocking
Thread::wait() call. Using nonblocking calls is good practice because Mbed OS can schedule and run other threads while the first thread is waiting.
Building this example
Building with Arm Mbed CLI
To use Mbed CLI to build this example, follow the instructions in the documentation. The instructions here relate to using the Arm Online Compiler.
To use the Online Compiler, import this code into the Online Compiler, and select your platform from the top right. Compile the code using the compile button, load it onto your board and press the reset button on the board. The code will run on the board, and you will see the LED blink.
You can find more instructions for using the Mbed Online Compiler in the documentation.
--- a/README.md Thu Jul 28 13:52:35 2016 +0100 +++ b/README.md Thu Jul 28 16:32:52 2016 +0100 @@ -41,7 +41,7 @@ Total Static RAM memory (data + bss): 7168 bytes Total RAM memory (data + bss + heap + stack): 7168 bytes Total Flash memory (text + data + misc): 43402 bytes -Image: .\.build\K64F\ARM\mbed-os-example-blinky.bin +Image: .\.build\K64F\ARM\mbed-os-example-blinky.bin ``` ### Program your board @@ -59,7 +59,7 @@ From the command line, run the following command: ``` -mbed export -m K64F -i uvision -n mbed-os-example-blinky +mbed export -m K64F -i uvision ``` You should see the following output: