代码拉取完成，页面将自动刷新
同步操作将从 ARMmbed/mbed-os-example-bootloader 强制同步，此操作会覆盖自 Fork 仓库以来所做的任何修改，且无法恢复！！！
确定后同步将在后台操作，完成时将刷新页面，请耐心等待。
Please note: This repository is deprecated and it is no longer actively maintained.
This example shows how to create a bootloader.
To read more about the bootloader, please visit the bootloader tutorial.
From the command-line, import the example:
mbed import mbed-os-example-bootloader
cd mbed-os-example-bootloader
This example uses the onboard SD card port for the K64F and the u-blox EVK-ODIN-W2.
Other targets use the following Arduino form-factor SPI pins by default:
D11 - MOSI
D12 - MISO
D13 - SCK
D10 - CS
To use different SPI pins, you need to modify the mbed_app.json file. Add a key for your target to the target_overrides section with the following data (replace <TARGET_NAME> with your target's name):
{
...
"target_overrides": {
...
"<TARGET_NAME>": {
"sd_card_mosi": "<MOSI_PIN>",
"sd_card_miso": "<MISO_PIN>",
"sd_card_sck": "<SCK_PIN>",
"sd_card_cs": "<CS_PIN>"
}
...
}
...
}
All supported targets mentioned above are set up to build as a bootloader image. To add support for a new target, you must specify the size of the bootloader.
To do this, set the target value restrict_size to the maximum bootloader size in mbed_app.json (replace <TARGET_NAME> with your target name):
"target_overrides": {
...
"<TARGET_NAME>": {
"target.restrict_size": "0x20000"
},
...
Note: restrict_size pads the build image to the requested size.
Invoke mbed compile, and specify the name of your target and your favorite toolchain (GCC_ARM, ARM, IAR). For example, for the ARM Compiler:
mbed compile -m <TARGET_NAME> -t ARM
Your PC may take a few minutes to compile your code. At the end, you see the following result:
Merging Regions:
Filling region application with .\BUILD\<TARGET_NAME>\ARM\mbed-os-example-bootloader_application.bin
Padding region application with 0x11420 bytes
Space used after regions merged: 0x20000
+-----------------------------+-------+-------+-------+
| Module | .text | .data | .bss |
+-----------------------------+-------+-------+-------+
| Misc | 18481 | 24 | 1268 |
| drivers | 2132 | 8 | 184 |
| features/FEATURE_LWIP | 46 | 0 | 12560 |
| features/filesystem | 12756 | 12 | 540 |
| hal | 414 | 8 | 0 |
| hal/TARGET_FLASH_CMSIS_ALGO | 520 | 28 | 0 |
| platform | 2759 | 32 | 380 |
| rtos | 144 | 8 | 0 |
| rtos/rtx | 6954 | 100 | 8396 |
| targets/TARGET_STM | 15560 | 568 | 736 |
| Subtotals | 59766 | 788 | 24064 |
+-----------------------------+-------+-------+-------+
Allocated Heap: unknown
Allocated Stack: unknown
Total Static RAM memory (data + bss): 24852 bytes
Total RAM memory (data + bss + heap + stack): 24852 bytes
Total Flash memory (text + data + misc): 60554 bytes
Image: .\BUILD\<TARGET_NAME>\ARM\mbed-os-example-bootloader.bin
After the build completes, the build system creates two binary images in the BUILD/<TARGET_NAME>/<TOOLCHAIN_NAME> directory: <project-name>.bin and <project-name>_application.bin. <project-name>.bin is the padded bootloader (used for combining with applications). <project-name>_application.bin is the original unpadded bootloader.
In this example, main.cpp defines the update binary for the bootloader as mbed-os-example-blinky_application.bin (specified under the config update_file in mbed_app.json). The bootloader looks for this file in the root of the SD card, flashes it to memory and then jumps to the application.
The next step is to build an application you can combine with your bootloader to create a loadable image.
Note: Updating an application to use a bootloader currently does not work with the Arm Mbed Online Compiler because .bin and .hex files can't be uploaded.
Instruct the build system to use the newly created padded bootloader image (named <project-name>.bin in the previous section). To do this, create a target_overrides section in your application's mbed_app.json file, and add a key for your target (see <TARGET_NAME> in the example below). If mbed_app.json does not already exist in your application, create one.
Set the target value bootloader_img in mbed_app.json to the file path of the padded bootloader image. For the below example, copy the padded bootloader image to the project directory.
{
"target_overrides": {
...
"<TARGET_NAME>": {
"target.bootloader_img": "<path to padded bootloader binary>"
},
...
}
Invoke mbed compile, and specify the name of your target and the toolchain you are using (GCC_ARM, ARM, IAR). For example, for the ARM Compiler:
mbed compile -m <TARGET_NAME> -t ARM
After the build completes, the build system creates two binary images in the BUILD/<TARGET_NAME>/<TOOLCHAIN_NAME> directory: <project-name>.bin and <project-name>_application.bin. <project-name>.bin is the combined bootloader and application (suitable for flashing to the device's ROM directly). <project-name>_application.bin is the update binary (the one you place on the SD card). By default the bootloader built in the previous step looks for an application built from the project from mbed-os-example-blinky and having the name mbed-os-example-blinky_application.bin.
Follow these steps to program the target with the combined bootloader and application image. You then can update the application from the SD card.
<project-name>.bin in the previous section) to the Mbed device.Note: You must first flash the combined bootloader and application image or just the bootloader image (padded or unpadded) before proceeding with the following steps.
<project-name>_application.bin in the previous section) to the root of the SD card.If a terminal is open, the following prints at a baud rate of 9600:
Firmware update found
Starting application
If you have problems, you can review the documentation for suggestions on what could be wrong and how to fix it.
The software is provided under Apache-2.0 license. Contributions to this project are accepted under the same license. Please see contributing.md for more info.
This project contains code from other projects. The original license text is included in those source files. They must comply with our license guide.
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。
马建仓 AI 助手
