manual:net_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:net_demo [2018/08/03 15:18] voorburg |
manual:net_demo [2018/08/03 15:20] voorburg [Notes] |
||
|---|---|---|---|
| Line 63: | Line 63: | ||
| With the deferred initialization enabled, the TCP/IP stack initialization is skipped during a normal reset event, unless: (a) there is no valid user program present, or (b) the bootloader was forced to stay active. This latter case happens when the CpuUserProgramStartHook()-function is enabled and returns BLT_FALSE. | With the deferred initialization enabled, the TCP/IP stack initialization is skipped during a normal reset event, unless: (a) there is no valid user program present, or (b) the bootloader was forced to stay active. This latter case happens when the CpuUserProgramStartHook()-function is enabled and returns BLT_FALSE. | ||
| - | To be able to perform remote firmware updates without having to access the system, a third scenario was added in the demo programs for forcing the TCP/IP stack to be initialized. This is the case when the bootloader was started from the user program. The [[https://www.feaser.com/en/blog/?p=216|shared parameter module]] was integrated into both the demo bootloader and user program, to be able to pass information from the user program to the bootloader. After the user program detects a firmware update request from the TCP/IP network, it sets a shared parameter in RAM right before the bootloader is activated. Upon activation, the bootloader evaluates this shared parameter and initializes the TCP/IP stack when requested. | + | To be able to perform remote firmware updates without having to access the system, a third scenario (c) was added in the demo programs for forcing the TCP/IP stack to be initialized. This is the case when the bootloader was started from the user program. The [[https://www.feaser.com/en/blog/?p=216|shared parameter module]] was integrated into both the demo bootloader and user program, to be able to pass information from the user program to the bootloader. After the user program detects a firmware update request from the TCP/IP network, it sets a shared parameter in RAM right before the bootloader is activated. Upon activation, the bootloader evaluates this shared parameter and initializes the TCP/IP stack when requested. |
manual/net_demo.txt ยท Last modified: 2019/09/24 22:03 (external edit)
Page Tools
