Felipe Neves / Mbed OS TEN_mbedos_mempool_queue

TEN MBED OS Course mempool_queue lab

README.md@0:89c82c16102e, 2017-01-29 (annotated)

Committer:
uLipe
Date:
Sun Jan 29 20:41:14 2017 +0000
Revision:
0:89c82c16102e
first

Who changed what in which revision?

UserRevisionLine numberNew contents of line
uLipe 0:89c82c16102e 1 # Getting started with Blinky on mbed OS
uLipe 0:89c82c16102e 2
uLipe 0:89c82c16102e 3 This is a very simple guide, reviewing the steps required to get Blinky working on an mbed OS platform.
uLipe 0:89c82c16102e 4
uLipe 0:89c82c16102e 5 Please install [mbed CLI](https://github.com/ARMmbed/mbed-cli#installing-mbed-cli).
uLipe 0:89c82c16102e 6
uLipe 0:89c82c16102e 7 ## Get the example application!
uLipe 0:89c82c16102e 8
uLipe 0:89c82c16102e 9 From the command line, import the example:
uLipe 0:89c82c16102e 10
uLipe 0:89c82c16102e 11 ```
uLipe 0:89c82c16102e 12 mbed import mbed-os-example-blinky
uLipe 0:89c82c16102e 13 cd mbed-os-example-blinky
uLipe 0:89c82c16102e 14 ```
uLipe 0:89c82c16102e 15
uLipe 0:89c82c16102e 16 ### Now compile
uLipe 0:89c82c16102e 17
uLipe 0:89c82c16102e 18 Invoke `mbed compile` specifying the name of your platform and your favorite toolchain (`GCC_ARM`, `ARM`, `IAR`). For example, for the ARM Compiler 5:
uLipe 0:89c82c16102e 19
uLipe 0:89c82c16102e 20 ```
uLipe 0:89c82c16102e 21 mbed compile -m K64F -t ARM
uLipe 0:89c82c16102e 22 ```
uLipe 0:89c82c16102e 23
uLipe 0:89c82c16102e 24 Your PC may take a few minutes to compile your code. At the end you should get the following result:
uLipe 0:89c82c16102e 25
uLipe 0:89c82c16102e 26 ```
uLipe 0:89c82c16102e 27 [snip]
uLipe 0:89c82c16102e 28 +----------------------------+-------+-------+------+
uLipe 0:89c82c16102e 29 | Module | .text | .data | .bss |
uLipe 0:89c82c16102e 30 +----------------------------+-------+-------+------+
uLipe 0:89c82c16102e 31 | Misc | 13939 | 24 | 1372 |
uLipe 0:89c82c16102e 32 | core/hal | 16993 | 96 | 296 |
uLipe 0:89c82c16102e 33 | core/rtos | 7384 | 92 | 4204 |
uLipe 0:89c82c16102e 34 | features/FEATURE_IPV4 | 80 | 0 | 176 |
uLipe 0:89c82c16102e 35 | frameworks/greentea-client | 1830 | 60 | 44 |
uLipe 0:89c82c16102e 36 | frameworks/utest | 2392 | 512 | 292 |
uLipe 0:89c82c16102e 37 | Subtotals | 42618 | 784 | 6384 |
uLipe 0:89c82c16102e 38 +----------------------------+-------+-------+------+
uLipe 0:89c82c16102e 39 Allocated Heap: unknown
uLipe 0:89c82c16102e 40 Allocated Stack: unknown
uLipe 0:89c82c16102e 41 Total Static RAM memory (data + bss): 7168 bytes
uLipe 0:89c82c16102e 42 Total RAM memory (data + bss + heap + stack): 7168 bytes
uLipe 0:89c82c16102e 43 Total Flash memory (text + data + misc): 43402 bytes
uLipe 0:89c82c16102e 44 Image: .\.build\K64F\ARM\mbed-os-example-blinky.bin
uLipe 0:89c82c16102e 45 ```
uLipe 0:89c82c16102e 46
uLipe 0:89c82c16102e 47 ### Program your board
uLipe 0:89c82c16102e 48
uLipe 0:89c82c16102e 49 1. Connect your mbed device to the computer over USB.
uLipe 0:89c82c16102e 50 1. Copy the binary file to the mbed device .
uLipe 0:89c82c16102e 51 1. Press the reset button to start the program.
uLipe 0:89c82c16102e 52
uLipe 0:89c82c16102e 53 You should see the LED of your platform turning on and off.
uLipe 0:89c82c16102e 54
uLipe 0:89c82c16102e 55 Congratulations if you managed to complete this test!
uLipe 0:89c82c16102e 56
uLipe 0:89c82c16102e 57 ## Export the project to Keil MDK and debug your application
uLipe 0:89c82c16102e 58
uLipe 0:89c82c16102e 59 From the command line, run the following command:
uLipe 0:89c82c16102e 60
uLipe 0:89c82c16102e 61 ```
uLipe 0:89c82c16102e 62 mbed export -m K64F -i uvision
uLipe 0:89c82c16102e 63 ```
uLipe 0:89c82c16102e 64
uLipe 0:89c82c16102e 65 To debug the application:
uLipe 0:89c82c16102e 66
uLipe 0:89c82c16102e 67 1. Start uVision.
uLipe 0:89c82c16102e 68 1. Import the uVision project generated earlier.
uLipe 0:89c82c16102e 69 1. Compile your application and generate an `.axf` file.
uLipe 0:89c82c16102e 70 1. Make sure uVision is configured to debug over CMSIS-DAP (From the Project menu > Options for Target '...' > Debug tab > Use CMSIS-DAP Debugger).
uLipe 0:89c82c16102e 71 1. Set breakpoints and start a debug session.
uLipe 0:89c82c16102e 72
uLipe 0:89c82c16102e 73 ![Image of uVision](img/uvision.png)
uLipe 0:89c82c16102e 74
uLipe 0:89c82c16102e 75 ## Troubleshooting
uLipe 0:89c82c16102e 76
uLipe 0:89c82c16102e 77 1. Make sure `mbed-cli` is working correctly and its version is greater than `0.8.9`
uLipe 0:89c82c16102e 78
uLipe 0:89c82c16102e 79 ```
uLipe 0:89c82c16102e 80 mbed --version
uLipe 0:89c82c16102e 81 ```
uLipe 0:89c82c16102e 82
uLipe 0:89c82c16102e 83 If not, you can update it easily:
uLipe 0:89c82c16102e 84
uLipe 0:89c82c16102e 85 ```
uLipe 0:89c82c16102e 86 pip install mbed-cli --upgrade
uLipe 0:89c82c16102e 87 ```
uLipe 0:89c82c16102e 88
uLipe 0:89c82c16102e 89 2. If using Keil MDK, make sure you have a license installed. [MDK-Lite](http://www.keil.com/arm/mdk.asp) has a 32KB restriction on code size.