en:netzer:boot2

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
en:netzer:boot2 [2011/12/19 12:51] – Code stub translation sveschen:netzer:boot2 [2025/06/11 20:42] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Bootloader Version 2 ====== ====== Bootloader Version 2 ======
- 
- 
  
 All delivered Netzer have an installed bootloader version 2. All delivered Netzer have an installed bootloader version 2.
- 
 This bootloader excepts standard IntelHex files per TFTP. This bootloader excepts standard IntelHex files per TFTP.
- 
 The blinking **right** LED of the RJ45 jack indicates an installed bootloader 2. The blinking **right** LED of the RJ45 jack indicates an installed bootloader 2.
- 
- 
  
 The Intel hex file of the bootloader for installing (in case of accidentally deletion or malicious installation): The Intel hex file of the bootloader for installing (in case of accidentally deletion or malicious installation):
  
 <WRAP center round download 60%> <WRAP center round download 60%>
- + {{:bins:boot2.zip|Bootloader 2}}. Only installable with an external programmer device like ICD!
- {{:bins:boot2.hex|Bootloader 2}}. Only installable with an external programmer device like ICD! +
 </WRAP> </WRAP>
- 
- 
  
 Here is a list of already published releases: Here is a list of already published releases:
  
 <WRAP center round download 60%> <WRAP center round download 60%>
- +  * {{:bins:140104_netzer_base.tar.gz|Version 1.5 base Build 1157}} (2014-01-04)}} 
-  * {{:bins:111014_netzer.tar.gz|Version 1.4 base Build 198 (Release 2011-11-10)}} +  * {{:bins:120309_netzer.tar.gz|Version 1.4 base Build 222 (Release 2012-03-09)}} 
- +  * {{:bins:120102_netzer.tar.gz|Version 1.4 base Build 220 (Release 2012-01-02)}} 
-  * {{:bins:111014_netzer.tar.gz|Version 1.3 Build 132 (Release 2011-04-25)}} +  * {{:bins:111223_netzer.tar.gz|Version 1.4 base Build 219 (Release 2011-12-23)}} 
- +  * {{:bins:111221_netzer.tar.gz|Version 1.4 base Build 214 (Release 2011-12-21)}} 
-  * {{:bins:110425_netzer.tar.gz|Version 1.3 Build 129 (Release 2011-04-13)}} +  * {{:bins:111014_netzer.tar.gz|Version 1.4 base Build 198 (Release 2011-10-14)}} 
 +  * {{:bins:110425_netzer.tar.gz|Version 1.3 Build 132 (Release 2011-04-25)}} 
 +  * {{:bins:110413_netzer.tar.gz|Version 1.3 Build 129 (Release 2011-04-13)}}
   * {{:bins:110315_netzer.tar.gz|Version 1.3 Build 128 (Release 2011-03-15)}}   * {{:bins:110315_netzer.tar.gz|Version 1.3 Build 128 (Release 2011-03-15)}}
- 
   * {{:bins:110222_netzer.tar.gz|Version 1.3 Build 122 (Release 2011-02-22)}}   * {{:bins:110222_netzer.tar.gz|Version 1.3 Build 122 (Release 2011-02-22)}}
- +  * {{:bins:110108_netzer.tar.gz|Version 1.2 Build 103 (Release 2011-01-08)}} 
-  * {{:bins:110108_netzer.tar.gz|Version 1.2 Build 103 (Release 2011-08-01)}} +  * {{:bins:101102_netzer.zip|Version 1.1 Build 83 (Elektor Release 2010-11-02)}}
- +
-  * {{:bins:101102_netzer.zip|Version 1.1 Build 83 (Elektor-Release 2011-11-02)}} +
 </WRAP> </WRAP>
  
 +The Releases can be flashed without programming device if bootloader is installed. It is described in the next section. The IntelHex files also can be programmed directly into the microcontroller with an external programmer device like ICD. 
  
  
 ===== Updates in operation mode ===== ===== Updates in operation mode =====
  
 +The update is done with a PC via the network. The hex file should be stored to hard disk before. The file is transfered to the Netzer via tftp. For the update therefore a tftp client is needed. At the most operating systems such a client is included.
  
 +Since Version 1.3 the Firmware update has to be explicitly activated via the Netzer web interface (logged in as administrator). This eliminates a potential security risk of Netzer. In the common settings a radio group can be found: 
  
-The update is done with a PC via the network. The hex file should be stored to hard disk before. The file is transfered to the Networker via tftp. For the update therefore a tftp client is needed. At the most operating systems such a client is included.+{{ webinterface_permit_firmware_upload.jpg?nolink& |Webinterface screenshot}}
  
 +There is also the possibility to activate the Firmware uploads from command line with **curl**: 
 +<code>curl --data "ubf=1&O=Save" http://user:password@netzer_name.local/common.htm</code> 
 +//netzer_name// must be the MDNS name of Netzer. Fill in administrator accounts data for //user// and //password//. Installed firmware without access control can simply use the following command:
 +<code>curl --data "ubf=1&O=Save" http://ne2c3519.local/common.htm</code> 
  
  
-Since Version 1.3 the Firmware update has to be explicitly activated via the Networker web interface (logged in as administrator). This eliminates a potential security risk of Networker. In the common settings a radio group can be found:  +The file is transfered to Netzer with the TFTP PUT command. Networker is accessed via the current IP address or the network name. Example for a tftp command in a shell box under Windows: 
- +
- +
- +
-{{ :en:netzer:webinterface_permit_firmware_upload_en.jpg?nolink& |Webinterface screenshot}} +
- +
- +
- +
-The file is transfered to Networker with the TFTP PUT command. Networker is accessed via the current IP address or the network name. Example for a tftp command in a shell box under Windows: +
  
 <code>tftp ne7C4000.local put "Netzer.hex"</code> <code>tftp ne7C4000.local put "Netzer.hex"</code>
  
- +Netzer goes into the update mode automatically and the file is transfered. A running transfer is indicated through the network activity LED, which is emitting for about 20 seconds. After the transfer has finished successfully the tftp client prints out that message:
- +
-Networker goes into the update mode automatically and the file is transfered. A running transfer is indicated through the network activity LED, which is emitting for about 20 seconds. After the transfer has finished successfully the tftp client prints out that message:+
  
 <code>Transmission successful: 335139 bytes in 16 seconds, 20946 Bytes/s</code> <code>Transmission successful: 335139 bytes in 16 seconds, 20946 Bytes/s</code>
- 
  
  
 ===== Updates in bootloader mode ===== ===== Updates in bootloader mode =====
  
 +The bootloader mode is active for aprox. 2 seconds after power on. After this time Networker enters the operation mode. The active mode is indicated due the fast blinking network LED. In bootloader mode Networker has the fixed IP address 192.168.97.60 and MAC address 00-04-A3-00-00-00. 
  
 +<note important>Netzer supports only ARP and TFTP in Bootloader mode, no ICMP. Hence, Netzer can **not** be pinged at 192.168.97.60.</note>
  
-The bootloader mode is active for aprox. 2 seconds after power on. After this time Networker enters the operation mode. The active mode is indicated due the fast blinking network LED. In bootloader mode Networker has the fixed IP address 192.168.97.60 and MAC address 00-04-A3-00-00-00. Updating only works if this IP address is not already occupied. The updating process works analog to the update in operation mode. +Updating only works if this IP address is not already occupied. The updating process works analog to the update in operation mode.
- +
  
-**Important: Only one Networker is allowed to be in Bootloader mode when starting the update.**+<note important>Only one Networker is allowed to be in Bootloader mode when starting the update.</note>