Y P / Mbed OS NucleoF767-mbed-os-example-blinky

Unmodified blinky example for Nucleo F767ZI. When exporting the project with Export Target: NUCLEO-F767ZI, Export Toolchain: GCC (ARM Embedded), Export All Files: any, an alert is displayed: "An error occured during export. Please contact support." No file is downloaded.

README.md@0:e75f32a698b8, 2017-02-23 (annotated)

Committer:
yp
Date:
Thu Feb 23 15:15:49 2017 +0000
Revision:
0:e75f32a698b8
Export to gcc error

Who changed what in which revision?

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