![](/media/cache/img/default_profile.jpg.50x50_q85.jpg)
This is a very simple guide, reviewing the steps required to get Blinky working on an Mbed OS platform.
README.md
- Committer:
- mbed_official
- Date:
- 2018-01-18
- Revision:
- 57:98afe5d5ae5c
- Parent:
- 54:64a293b4da54
- Child:
- 82:abf1b1785bd7
File content as of revision 57:98afe5d5ae5c:
# Getting started with Blinky on mbed OS This guide reviews the steps required to get Blinky working on an mbed OS platform. Please install [mbed CLI](https://github.com/ARMmbed/mbed-cli#installing-mbed-cli). ## Import the example application From the command-line, import the example: ``` mbed import mbed-os-example-blinky cd mbed-os-example-blinky ``` ### Now compile Invoke `mbed compile`, and specify the name of your platform and your favorite toolchain (`GCC_ARM`, `ARM`, `IAR`). For example, for the ARM Compiler 5: ``` mbed compile -m K64F -t ARM ``` Your PC may take a few minutes to compile your code. At the end, you see the following result: ``` [snip] +----------------------------+-------+-------+------+ | Module | .text | .data | .bss | +----------------------------+-------+-------+------+ | Misc | 13939 | 24 | 1372 | | core/hal | 16993 | 96 | 296 | | core/rtos | 7384 | 92 | 4204 | | features/FEATURE_IPV4 | 80 | 0 | 176 | | frameworks/greentea-client | 1830 | 60 | 44 | | frameworks/utest | 2392 | 512 | 292 | | Subtotals | 42618 | 784 | 6384 | +----------------------------+-------+-------+------+ Allocated Heap: unknown Allocated Stack: unknown 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 ``` ### Program your board 1. Connect your mbed device to the computer over USB. 1. Copy the binary file to the mbed device. 1. Press the reset button to start the program. The LED on your platform turns on and off. ## Troubleshooting If you have problems, you can review the [documentation](https://os.mbed.com/docs/latest/tutorials/debugging.html) for suggestions on what could be wrong and how to fix it.