Differences

This shows you the differences between two versions of the page.

--- manual:usb_demo [2018/07/03 12:56]
voorburg [Using Microboot]
+++ manual:usb_demo [2018/07/04 14:51]
voorburg [Using Microboot]
@@ Line 14: / Line 14: @@
 Once the bootloader is programmed and running on your microcontroller system, you will be prompted to install the USB driver, after connecting the system to your PC's USB port. The driver installation is described on a seperate page: [[manual:demos:usb_driver_install|OpenBLT USB driver installation instructions]].
-===== Using Microboot =====
+===== Using MicroBoot =====
-The Microboot utility needs to be configured to communicate via USB:
+The MicroBoot utility needs to be configured to communicate via USB:
-  * Start Microboot by double-clicking "\Host\**MicroBoot.exe**" (on Linux it is "\Host\**MicroBoot**").
+  * Start MicroBoot by double-clicking "\Host\**MicroBoot.exe**" (on Linux it is "\Host\**MicroBoot**").
   * Click the "**Settings**"-button and select "**XCP on USB**" from the "Interface selection" dropdown box.
-Once you saved the settings by clicking the "**OK**"-button, Microboot is now ready for action!
+Once you saved the settings by clicking the "**OK**"-button, MicroBoot is now ready for action!
-After building your user program, its S-record formatted firmware file can be downloaded to the remaining flash memory using the bootloader. In **Microboot** click the "**Browse**"-button and select your user program's firmware file. For the demo programs, this one is located in the ".\**Prog**\bin\" directory. Once the firmware file was selected, the download should automatically start.
+After building your user program, its S-record formatted firmware file can be downloaded to the remaining flash memory using the bootloader. In **MicroBoot** click the "**Browse**"-button and select your user program's firmware file. For the demo programs, this one is located in the ".\**Prog**\bin\" directory. Once the firmware file was selected, the download should automatically start.
 {{:manual:olimex_stm32p405_download_usb.png?|}}
 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 =====

OpenBLT Bootloader

User Tools

Site Tools

Differences

Page Tools