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