Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
en:netzer:boot3 [2011/12/06 21:55] – created holtmann | en:netzer:boot3 [2025/06/11 20:42] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Bootloader Version 3 ====== | + | ====== Bootloader Version 3 / 4 ====== |
Up to now, all Netzers supplied had the Bootloader in version 2. | Up to now, all Netzers supplied had the Bootloader in version 2. | ||
+ | |||
This Bootloader accepted intel hex files via TFTP standard. | This Bootloader accepted intel hex files via TFTP standard. | ||
- | Instead of intel hex files, the new version 3 of the Bootloaders | + | Instead of intel hex files, the new versions |
- | <note important> | + | <note important> |
- | The advantage is that particularly for professional use not any image may be flashed up. Moreover, it is impossible to readily disassamble these images. | + | <note tip> |
+ | The Bootloader | ||
+ | </ | ||
- | The Bootloader may be also provided | + | From the outside, a Netzer |
- | From the outside, a Netzer with Bootloader version 3 recognizable by the **left** LED blinking fastly | + | ===== Advantages ===== |
+ | * Not not any image may be flashed up, the used key must match. | ||
+ | | ||
+ | | ||
+ | | ||
+ | * Plausiblity and CRC check of flashed image. | ||
+ | |||
+ | |||
+ | ===== Advantages Bootloader 4 ===== | ||
+ | * Independent data chunks can be flashed at different times (with different start addresses). | ||
+ | * Gently usage of the flash memory: Only the flash areas are erased where new data is written to. | ||
+ | * Dedicated functions of the bootloader can be used from a flashed application, | ||
===== Update ===== | ===== Update ===== | ||
- | If a [[http:// | + | If a [[@/shop_netzer_license_en.htm|license]] for the pro-version has been acquired, an update from Bootloader 2 to version 3 is first of all required. The update is sent as an intel hex file via e-mail. Each update is signed with the MAC-address of the target Netzer. When acquiring the license, stating the MAC-address of the Netzter is required. |
The most important thing at first: In general, Boot updates function on all Netzers of this world. But the version 1.4 can be exclusively installed on the Netzer with the stated MAC-address later! Hence, please apply the correct boot update only for the correct Netzer. During the flashing process, please do not switch the Netzer off! | The most important thing at first: In general, Boot updates function on all Netzers of this world. But the version 1.4 can be exclusively installed on the Netzer with the stated MAC-address later! Hence, please apply the correct boot update only for the correct Netzer. During the flashing process, please do not switch the Netzer off! | ||
- | The Boot update using TFTP according to this [[de: | + | The Boot update using TFTP according to this [[en: |
===== Updates during operation ===== | ===== Updates during operation ===== | ||
Line 29: | Line 45: | ||
Since version 1.3, the firmware update is required to be explicitely activated via the Netzer web interface (logged in as the administrator). This closes a potential security hole of the Netzer. For this, there is a radio button in the general settings: | Since version 1.3, the firmware update is required to be explicitely activated via the Netzer web interface (logged in as the administrator). This closes a potential security hole of the Netzer. For this, there is a radio button in the general settings: | ||
- | {{ :de:netzer:webinterface_permit_firmware_upload_de.jpg? | + | {{ :en:netzer:webinterface_permit_firmware_upload.jpg? |
After that, the file is transferred to Netzer by TFTP PUT-instruction. Netzer is activated via the IP-address or the network name. Under Windows, a TFTP call of the command line for example looks as follows: | After that, the file is transferred to Netzer by TFTP PUT-instruction. Netzer is activated via the IP-address or the network name. Under Windows, a TFTP call of the command line for example looks as follows: | ||
+ | |||
< | < | ||
- | <note important> | + | <note important> |
Netzer is automatically set in update mode and transferred in the file. A running transfer is recognizable by the network activity LED, ligthing up for about ten to twenty seconds. At the end, the tftp-client displays a message similar to the following one: | Netzer is automatically set in update mode and transferred in the file. A running transfer is recognizable by the network activity LED, ligthing up for about ten to twenty seconds. At the end, the tftp-client displays a message similar to the following one: | ||
+ | |||
< | < | ||
+ | |||
===== Updates in Bootloader mode ===== | ===== Updates in Bootloader mode ===== | ||
- | For about two seconds, the Bootloader mode is active directly after plug-in of the power supply. It is recognizable by the fastly blinking left LED. In Bootloader mode, Netzer always has a fix, not changeable IP-address 192.168.97.60 as well as MAC-address 00-04-A3-00-00-00. It is important that the IP is not occupied by another device in the network. The update process is analog to the first variant. | + | For about two seconds, the Bootloader mode is active directly after plug-in of the power supply. It is recognizable by the fastly blinking left LED. In Bootloader mode, Netzer always has a fix, not changeable IP-address 192.168.97.60 as well as MAC-address 00-04-A3-00-00-00. |
+ | |||
+ | <note important> | ||
+ | |||
+ | It is important that the IP is not occupied by another device in the network. The update process is analog to the first variant. | ||
<note important> | <note important> | ||
+ |