manual:usb_demo
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
manual:usb_demo [2018/07/03 12:56] voorburg [Using Microboot] |
manual:usb_demo [2018/07/03 12:57] voorburg |
||
|---|---|---|---|
| Line 28: | Line 28: | ||
| Once the download completed, the newly programmed software will be started by the bootloader. For the demo program's you can verify this by checking that the LED blinks. Congratulations! That's all there is to using the bootloader. | Once the download completed, the newly programmed software will be started by the bootloader. For the demo program's you can verify this by checking that the LED blinks. Congratulations! That's all there is to using the bootloader. | ||
| + | |||
| + | ===== Using BootCommander ===== | ||
| + | |||
| + | The BootCommander command line interface (CLI) program allows you to configure all communication settings via options on the command line. The following example demonstrates how to call BootCommander for making a firmware update with one of the demo programs. | ||
| + | |||
| + | <code> | ||
| + | BootCommander -s=xcp -t=xcp_usb demoprog_olimex_stm32p405.srec | ||
| + | </code> | ||
| + | |||
| + | The example assumes that the S-record of the demo user program is located in the same directory as where the BootCommander executable itself resides. If not, then simply prepend the absolute (or relative) directory to the name of the S-record firmware file. | ||
| + | |||
| ===== Notes ===== | ===== Notes ===== | ||
manual/usb_demo.txt ยท Last modified: 2023/06/27 09:35 by voorburg
Page Tools
