manual:net_demo
Differences
This shows you the differences between two versions of the page.
|
manual:net_demo [2018/07/04 14:51] voorburg [Using Microboot] |
manual:net_demo [2019/09/24 22:03] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Firmware updates using the TCP/IP communication interface ====== | ||
| - | ===== Bootloader configuration ===== | ||
| - | |||
| - | In order to perform firmware updates with the OpenBLT through a TCP/IP network, double-check that the network communication interface is configured in "blt_conf.h". The following macro should have a value of 1. If this macro did not yet have a value of 1, the bootloader should be rebuild after making the change. | ||
| - | |||
| - | <code> | ||
| - | #define BOOT_COM_NET_ENABLE (1) | ||
| - | </code> | ||
| - | |||
| - | ===== Using MicroBoot ===== | ||
| - | |||
| - | The MicroBoot utility needs to be configured to connect to the correct IP address and port: | ||
| - | |||
| - | * Start MicroBoot by double-clicking "\Host\**MicroBoot.exe**" (on Linux it is "\Host\**MicroBoot**"). | ||
| - | * Click the "**Settings**"-button and select "**XCP on TCP/IP**" from the "Interface selection" dropdown box. | ||
| - | * Set the IP address (or fully qualified domain name) of your microcontroller system on the network. Note that the IP address is also specified by the macro's BOOT_COM_NET_IPADDR in "blt_conf.h". | ||
| - | * Set the port on which the bootloader listens for firmware update connection requests. This is specified by the macro BOOT_COM_NET_PORT in "blt_conf.h". Typically, this is **1000** for the demo programs. | ||
| - | |||
| - | 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. | ||
| - | |||
| - | {{:manual:ti_eklm3s6965_download_net.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. Just set the “**-a**” option to the IP address or hostname of the target to connect to and set the "**-p**" option to the TCP port number that the target listens on.. | ||
| - | |||
| - | <code> | ||
| - | BootCommander -s=xcp -t=xcp_net -a=192.168.178.23 -p=1000 demoprog_ek_lm3s6965.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 ===== | ||
| - | |||
| - | 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. Note that this delay is configured relatively long (several seconds) for the TCP/IP demo programs. This is because it can take quite some time after the bootloader got re-activated for the system to become responsive on the network. Feel free to fine-tune this value to your needs. Basically, reset your system and measure how much time is needed for it to respond to PING-requests. | ||
manual/net_demo.txt · Last modified: 2019/09/24 22:03 (external edit)
Page Tools
