Mbed Colombia Meetup
/
MBC001-DigitalOut
MBC001 - DigitalOut This example use the DigitalOut function
README.md@0:54f0e2724f0e, 2018-05-14 (annotated)
- Committer:
- leandropg
- Date:
- Mon May 14 15:14:15 2018 +0000
- Revision:
- 0:54f0e2724f0e
MBC001 - DigitalOut; This example use the DigitalOut function
Who changed what in which revision?
User | Revision | Line number | New contents of line |
---|---|---|---|
leandropg | 0:54f0e2724f0e | 1 | # Getting started with Blinky on mbed OS |
leandropg | 0:54f0e2724f0e | 2 | |
leandropg | 0:54f0e2724f0e | 3 | This guide reviews the steps required to get Blinky working on an mbed OS platform. |
leandropg | 0:54f0e2724f0e | 4 | |
leandropg | 0:54f0e2724f0e | 5 | Please install [mbed CLI](https://github.com/ARMmbed/mbed-cli#installing-mbed-cli). |
leandropg | 0:54f0e2724f0e | 6 | |
leandropg | 0:54f0e2724f0e | 7 | ## Import the example application |
leandropg | 0:54f0e2724f0e | 8 | |
leandropg | 0:54f0e2724f0e | 9 | From the command-line, import the example: |
leandropg | 0:54f0e2724f0e | 10 | |
leandropg | 0:54f0e2724f0e | 11 | ``` |
leandropg | 0:54f0e2724f0e | 12 | mbed import mbed-os-example-blinky |
leandropg | 0:54f0e2724f0e | 13 | cd mbed-os-example-blinky |
leandropg | 0:54f0e2724f0e | 14 | ``` |
leandropg | 0:54f0e2724f0e | 15 | |
leandropg | 0:54f0e2724f0e | 16 | ### Now compile |
leandropg | 0:54f0e2724f0e | 17 | |
leandropg | 0:54f0e2724f0e | 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: |
leandropg | 0:54f0e2724f0e | 19 | |
leandropg | 0:54f0e2724f0e | 20 | ``` |
leandropg | 0:54f0e2724f0e | 21 | mbed compile -m K64F -t ARM |
leandropg | 0:54f0e2724f0e | 22 | ``` |
leandropg | 0:54f0e2724f0e | 23 | |
leandropg | 0:54f0e2724f0e | 24 | Your PC may take a few minutes to compile your code. At the end, you see the following result: |
leandropg | 0:54f0e2724f0e | 25 | |
leandropg | 0:54f0e2724f0e | 26 | ``` |
leandropg | 0:54f0e2724f0e | 27 | [snip] |
leandropg | 0:54f0e2724f0e | 28 | +----------------------------+-------+-------+------+ |
leandropg | 0:54f0e2724f0e | 29 | | Module | .text | .data | .bss | |
leandropg | 0:54f0e2724f0e | 30 | +----------------------------+-------+-------+------+ |
leandropg | 0:54f0e2724f0e | 31 | | Misc | 13939 | 24 | 1372 | |
leandropg | 0:54f0e2724f0e | 32 | | core/hal | 16993 | 96 | 296 | |
leandropg | 0:54f0e2724f0e | 33 | | core/rtos | 7384 | 92 | 4204 | |
leandropg | 0:54f0e2724f0e | 34 | | features/FEATURE_IPV4 | 80 | 0 | 176 | |
leandropg | 0:54f0e2724f0e | 35 | | frameworks/greentea-client | 1830 | 60 | 44 | |
leandropg | 0:54f0e2724f0e | 36 | | frameworks/utest | 2392 | 512 | 292 | |
leandropg | 0:54f0e2724f0e | 37 | | Subtotals | 42618 | 784 | 6384 | |
leandropg | 0:54f0e2724f0e | 38 | +----------------------------+-------+-------+------+ |
leandropg | 0:54f0e2724f0e | 39 | Allocated Heap: unknown |
leandropg | 0:54f0e2724f0e | 40 | Allocated Stack: unknown |
leandropg | 0:54f0e2724f0e | 41 | Total Static RAM memory (data + bss): 7168 bytes |
leandropg | 0:54f0e2724f0e | 42 | Total RAM memory (data + bss + heap + stack): 7168 bytes |
leandropg | 0:54f0e2724f0e | 43 | Total Flash memory (text + data + misc): 43402 bytes |
leandropg | 0:54f0e2724f0e | 44 | Image: .\.build\K64F\ARM\mbed-os-example-blinky.bin |
leandropg | 0:54f0e2724f0e | 45 | ``` |
leandropg | 0:54f0e2724f0e | 46 | |
leandropg | 0:54f0e2724f0e | 47 | ### Program your board |
leandropg | 0:54f0e2724f0e | 48 | |
leandropg | 0:54f0e2724f0e | 49 | 1. Connect your mbed device to the computer over USB. |
leandropg | 0:54f0e2724f0e | 50 | 1. Copy the binary file to the mbed device. |
leandropg | 0:54f0e2724f0e | 51 | 1. Press the reset button to start the program. |
leandropg | 0:54f0e2724f0e | 52 | |
leandropg | 0:54f0e2724f0e | 53 | The LED on your platform turns on and off. |
leandropg | 0:54f0e2724f0e | 54 | |
leandropg | 0:54f0e2724f0e | 55 | ## Export the project to Keil MDK, and debug your application |
leandropg | 0:54f0e2724f0e | 56 | |
leandropg | 0:54f0e2724f0e | 57 | From the command-line, run the following command: |
leandropg | 0:54f0e2724f0e | 58 | |
leandropg | 0:54f0e2724f0e | 59 | ``` |
leandropg | 0:54f0e2724f0e | 60 | mbed export -m K64F -i uvision |
leandropg | 0:54f0e2724f0e | 61 | ``` |
leandropg | 0:54f0e2724f0e | 62 | |
leandropg | 0:54f0e2724f0e | 63 | To debug the application: |
leandropg | 0:54f0e2724f0e | 64 | |
leandropg | 0:54f0e2724f0e | 65 | 1. Start uVision. |
leandropg | 0:54f0e2724f0e | 66 | 1. Import the uVision project generated earlier. |
leandropg | 0:54f0e2724f0e | 67 | 1. Compile your application, and generate an `.axf` file. |
leandropg | 0:54f0e2724f0e | 68 | 1. Make sure uVision is configured to debug over CMSIS-DAP (From the Project menu > Options for Target '...' > Debug tab > Use CMSIS-DAP Debugger). |
leandropg | 0:54f0e2724f0e | 69 | 1. Set breakpoints, and start a debug session. |
leandropg | 0:54f0e2724f0e | 70 | |
leandropg | 0:54f0e2724f0e | 71 | ![Image of uVision](img/uvision.png) |
leandropg | 0:54f0e2724f0e | 72 | |
leandropg | 0:54f0e2724f0e | 73 | ## Troubleshooting |
leandropg | 0:54f0e2724f0e | 74 | |
leandropg | 0:54f0e2724f0e | 75 | 1. Make sure `mbed-cli` is working correctly and its version is `>1.0.0` |
leandropg | 0:54f0e2724f0e | 76 | |
leandropg | 0:54f0e2724f0e | 77 | ``` |
leandropg | 0:54f0e2724f0e | 78 | mbed --version |
leandropg | 0:54f0e2724f0e | 79 | ``` |
leandropg | 0:54f0e2724f0e | 80 | |
leandropg | 0:54f0e2724f0e | 81 | If not, you can update it: |
leandropg | 0:54f0e2724f0e | 82 | |
leandropg | 0:54f0e2724f0e | 83 | ``` |
leandropg | 0:54f0e2724f0e | 84 | pip install mbed-cli --upgrade |
leandropg | 0:54f0e2724f0e | 85 | ``` |
leandropg | 0:54f0e2724f0e | 86 | |
leandropg | 0:54f0e2724f0e | 87 | 2. If using Keil MDK, make sure you have a license installed. [MDK-Lite](http://www.keil.com/arm/mdk.asp) has a 32 KB restriction on code size. |