netzer_dev:bootloader

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
netzer_dev:bootloader [2014/02/09 14:32] – Externe Bearbeitung 127.0.0.1netzer_dev:bootloader [2025/06/11 21:16] (current) – Sven Schlender
Line 44: Line 44:
  
 The Netzer MAC address (6 bytes) is part of the EEPROM space but lives in the bottom of the EEPROM space which is not writable. The Netzer MAC address (6 bytes) is part of the EEPROM space but lives in the bottom of the EEPROM space which is not writable.
 +
 +<WRAP clear/>
  
 <imgcaption bootloader_addresses|The detailed structure of the bootloader and its addresses.>{{:netzer_dev:bootloader_addresses.png?400 |}}</imgcaption> <imgcaption bootloader_addresses|The detailed structure of the bootloader and its addresses.>{{:netzer_dev:bootloader_addresses.png?400 |}}</imgcaption>
Line 55: Line 57:
 Last but not least the version field stores the current bootloaders version (currently 4). Last but not least the version field stores the current bootloaders version (currently 4).
  
 +<WRAP clear/>
  
 ===== Uploading chunks ===== ===== Uploading chunks =====
Line 65: Line 68:
 In <imgref bootloader_chunk> such a TFTP stream is shown, as they arrive in the bootloader. In <imgref bootloader_chunk> such a TFTP stream is shown, as they arrive in the bootloader.
 In the stream there can be a lot of small chunks. In the stream there can be a lot of small chunks.
-The chunks are decrypted (if decryption is supported) on the fly.+The chunks are decrypted (if decryption is enabled) on the fly.
  
 All chunks have a unique header structure. All chunks have a unique header structure.
Line 92: Line 95:
 It ensures a jump to the bootloader code which is located at 0x1e800. It ensures a jump to the bootloader code which is located at 0x1e800.
  
- +<WRAP clear/>
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +