manual:uart_demo
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
manual:uart_demo [2018/07/02 13:28] voorburg [Using BootCommander] |
manual:uart_demo [2018/07/04 14:50] voorburg [Using MicroBoot] |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| - | ===== Using Microboot ===== | + | ===== Using MicroBoot ===== |
| - | The Microboot utility needs to be configured to connect to the correct COM-port and to communication at the correct baudrate: | + | The MicroBoot utility needs to be configured to connect to the correct COM-port and to communication at the correct baudrate: |
| - | * 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 RS232**" from the "Interface selection" dropdown box. | * Click the "**Settings**"-button and select "**XCP on RS232**" from the "Interface selection" dropdown box. | ||
| * Select the PC's communication device that the board is connected to. | * Select the PC's communication device that the board is connected to. | ||
| * Select the baudrate to the value specified by macro BOOT_COM_UART_BAUDRATE in "blt_conf.h". Typically, this is **57600** bits/sec for the demo programs. | * Select the baudrate to the value specified by macro BOOT_COM_UART_BAUDRATE in "blt_conf.h". Typically, this is **57600** bits/sec for the demo programs. | ||
| - | 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.png?|}} | {{:manual:olimex_stm32p405_download.png?|}} | ||
| Line 42: | Line 42: | ||
| Depending on the configuration of the bootloader, there might be a delay between a system reset and the actual start of the user program. This is needed by design for the bootloader's backdoor functionality. Check configurable BOOT_BACKDOOR_ENTRY_TIMEOUT_MS in "blt_conf.h" for the exact delay time. | Depending on the configuration of the bootloader, there might be a delay between a system reset and the actual start of the user program. This is needed by design for the bootloader's backdoor functionality. Check configurable BOOT_BACKDOOR_ENTRY_TIMEOUT_MS in "blt_conf.h" for the exact delay time. | ||
| + | To prevent having to run MicroBoot/BootCommander with super user privileges under Linux, add yourself to the **dialout** group. Example for Debian/Ubuntu distributions: | ||
| + | <code> | ||
| + | sudo usermod -G dialout -a $USER | ||
| + | </code> | ||
Page Tools
