Differences

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

Link to this comparison view

manual:net_demo [2018/08/03 15:20]
voorburg [Notes]
manual:net_demo [2018/08/03 15:21] (current)
voorburg [Notes]
Line 61: Line 61:
 The initialization of the TCP/IP network stack, up to the point where the bootloader can accept firmware update requests, can take several seconds. This delay occurs after each reset event, before your user program is started. Because such a long delay is typically not desired, the demo programs have the so called deferred initialization functionality enabled. This was done via configuration macro BOOT_COM_NET_DEFERRED_INIT_ENABLE in “blt_conf.h”. The initialization of the TCP/IP network stack, up to the point where the bootloader can accept firmware update requests, can take several seconds. This delay occurs after each reset event, before your user program is started. Because such a long delay is typically not desired, the demo programs have the so called deferred initialization functionality enabled. This was done via configuration macro BOOT_COM_NET_DEFERRED_INIT_ENABLE in “blt_conf.h”.
  
-With the deferred initialization enabled, the TCP/IP stack initialization is skipped during a normal reset event, unless: (athere is no valid user program present, or (bthe 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: [athere is no valid user program present, or [bthe 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 (cwas 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 [cwas 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: 2018/08/03 15:21 by voorburg
 
Powered by PHP Driven by DokuWiki