P422_Labs / Mbed OS accel

lab5

Dependencies:   ADXL362

README.md@1:839c14f3143c, 2018-03-02 (annotated)

Committer:
m0t0
Date:
Fri Mar 02 18:06:26 2018 +0000
Revision:
1:839c14f3143c
Parent:
0:cf970e75e1ae 
lab6;

Who changed what in which revision?

UserRevisionLine numberNew contents of line
kfricker 0:cf970e75e1ae 1 # Getting started with Blinky on mbed OS
kfricker 0:cf970e75e1ae 2
kfricker 0:cf970e75e1ae 3 This guide reviews the steps required to get Blinky working on an mbed OS platform.
kfricker 0:cf970e75e1ae 4
kfricker 0:cf970e75e1ae 5 Please install [mbed CLI](https://github.com/ARMmbed/mbed-cli#installing-mbed-cli).
kfricker 0:cf970e75e1ae 6
kfricker 0:cf970e75e1ae 7 ## Import the example application
kfricker 0:cf970e75e1ae 8
kfricker 0:cf970e75e1ae 9 From the command-line, import the example:
kfricker 0:cf970e75e1ae 10
kfricker 0:cf970e75e1ae 11 ```
kfricker 0:cf970e75e1ae 12 mbed import mbed-os-example-blinky
kfricker 0:cf970e75e1ae 13 cd mbed-os-example-blinky
kfricker 0:cf970e75e1ae 14 ```
kfricker 0:cf970e75e1ae 15
kfricker 0:cf970e75e1ae 16 ### Now compile
kfricker 0:cf970e75e1ae 17
kfricker 0:cf970e75e1ae 18 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:
kfricker 0:cf970e75e1ae 19
kfricker 0:cf970e75e1ae 20 ```
kfricker 0:cf970e75e1ae 21 mbed compile -m K64F -t ARM
kfricker 0:cf970e75e1ae 22 ```
kfricker 0:cf970e75e1ae 23
kfricker 0:cf970e75e1ae 24 Your PC may take a few minutes to compile your code. At the end, you see the following result:
kfricker 0:cf970e75e1ae 25
kfricker 0:cf970e75e1ae 26 ```
kfricker 0:cf970e75e1ae 27 [snip]
kfricker 0:cf970e75e1ae 28 +----------------------------+-------+-------+------+
kfricker 0:cf970e75e1ae 29 | Module | .text | .data | .bss |
kfricker 0:cf970e75e1ae 30 +----------------------------+-------+-------+------+
kfricker 0:cf970e75e1ae 31 | Misc | 13939 | 24 | 1372 |
kfricker 0:cf970e75e1ae 32 | core/hal | 16993 | 96 | 296 |
kfricker 0:cf970e75e1ae 33 | core/rtos | 7384 | 92 | 4204 |
kfricker 0:cf970e75e1ae 34 | features/FEATURE_IPV4 | 80 | 0 | 176 |
kfricker 0:cf970e75e1ae 35 | frameworks/greentea-client | 1830 | 60 | 44 |
kfricker 0:cf970e75e1ae 36 | frameworks/utest | 2392 | 512 | 292 |
kfricker 0:cf970e75e1ae 37 | Subtotals | 42618 | 784 | 6384 |
kfricker 0:cf970e75e1ae 38 +----------------------------+-------+-------+------+
kfricker 0:cf970e75e1ae 39 Allocated Heap: unknown
kfricker 0:cf970e75e1ae 40 Allocated Stack: unknown
kfricker 0:cf970e75e1ae 41 Total Static RAM memory (data + bss): 7168 bytes
kfricker 0:cf970e75e1ae 42 Total RAM memory (data + bss + heap + stack): 7168 bytes
kfricker 0:cf970e75e1ae 43 Total Flash memory (text + data + misc): 43402 bytes
kfricker 0:cf970e75e1ae 44 Image: .\.build\K64F\ARM\mbed-os-example-blinky.bin
kfricker 0:cf970e75e1ae 45 ```
kfricker 0:cf970e75e1ae 46
kfricker 0:cf970e75e1ae 47 ### Program your board
kfricker 0:cf970e75e1ae 48
kfricker 0:cf970e75e1ae 49 1. Connect your mbed device to the computer over USB.
kfricker 0:cf970e75e1ae 50 1. Copy the binary file to the mbed device.
kfricker 0:cf970e75e1ae 51 1. Press the reset button to start the program.
kfricker 0:cf970e75e1ae 52
kfricker 0:cf970e75e1ae 53 The LED on your platform turns on and off.
kfricker 0:cf970e75e1ae 54
kfricker 0:cf970e75e1ae 55 ## Troubleshooting
kfricker 0:cf970e75e1ae 56
kfricker 0:cf970e75e1ae 57 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.