If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.

0
U

Property:EVA

From BoxMatrix


BoxMatrix >> Lexicon >> FRITZ-Terms >> EVA @ BoxMatrix   -   IRC-Chat   -   Translate: de es fr it nl pl
News Selectors Models Accessories Components Environment Config Commands System Webif Software Develop Lexicon Community Project Media

Computer FRITZ I18N Telephony Smarthome Internet Protocols Multimedia Formats Hardware Software Research

Term

Goto:   FRITZ!OS   -   Features  -  Compression  -  Versions  -  Multi-EVA  -  Environment  -  Config  -  Weblinks  -  SMW-Browser

Details

EVA is a proprietary Bootloader developed from scratch by AVM. It is the backward compatible successor of ADAM2.

FRITZ!OS

This article covers the AVM developed EVA, for the predecessor by TI see the ADAM2 article.

Features

Features of EVA:

Compression

EVA was developed when the AR7 Kernel was ported to version 2.6, which increased the Kernel size by approx. 35%.
Since Flash space was very limited back then better compression methods were needed. AVM decided to use LZMA.

ADAM2 did not directly support any Kernel compression at all, see the Compression section of its article.
The decompressor had to be prepended to the compressed Kernel, a workaround which wasted partition space.

LZMA compresses way better and AVM decided to implement the decompressor in EVA, so Kernels now can be plain LZMA.

A good example is the FRITZ!Box Fon, which was introduced with Kernel 2.4, and later updated to Kernel 2.6.
Fw 04.27 was the last zimage compressed 2.4 Kernel, fw 4.30 came with LZMA Kernel 2.6 and an EVA urlader.image.

Kernel 2.4 compiles to 1,454,080 bytes, zimage compressed 675,072 bytes including the prepended decompressor.
Kernel 2.6 compiles to 2,064,518 bytes, LZMA compressed 666,880 bytes with no need for a prepended decompressor.

Early EVA still fitted in the 64 KB ADAM2 partition, including LZMA decompressor, so AVM did the core upgrade at no cost.
However, some Kernel-Modules reside in filesystem, some of which are huge:

Also here the Kernel upgrade sums up to zero cost. Together with all improvements the LZMA compressed squashfs filesystem
only grew by 11% from 2,740,232 to 3,047,432 bytes. Complete FRITZ!OS only grew by 8.8%. Well done AVM!

Versions

Excerpt from the FRITZ!Box 7490 boot log captured by the Serial-Console:

(AVM) EVA Revision: 1.1964 Version: 2964
(C) Copyright 2005 AVM Date: Nov 27 2013 Time: 14:33:10 (1) 3 0x0-0x740D

ADAM2 Revision always was 0.18.01, so AVM decided to start EVA with Revision 1.x, with x being a counter which never
increases the leading 1. The 1,x value is stored in the bootloaderVersion variable, x + 1000 in urlader-version.

From the Shell:

# grep -e bootloader -e urlader -e prompt /proc/sys/urlader/environment

bootloaderVersion    1.1964
prompt               Eva_AVM
urlader-version      2964

The values of these 3 variables differ for ADAM2.

In recent models AVM stopped using the urlader-version variable. Example from a 7530ac:

# grep -e bootloader -e urlader -e prompt /proc/sys/urlader/environment

bootloaderVersion    1.11581
prompt               Eva_AVM

For some of these models the minor number of the bootloaderVersion jumped above 10.000, see this comparison.
This appears to be a symbol for a special type of EVA or the presence of a wrapper for Multi-EVA:

Multi-EVA

There's now a separate Multi-EVA article.

Environment

All ADAM2 and all EVA bootloaders before 1.163 were developed by model and had compiled in model specific defaults.
With EVA 1.163 AVM merged all EVA code and splitted model inependent and model specific builtin defaults.

This is research in progress and may be partially or completely wrong.

Collected from EVA probes 1.153/2031, 1.174/7150, more to come:

Compiled in model independent:

reserved              00:04:0E:FF:FF:00   # removed in 1.174
maca                  00:04:0E:FF:FF:01
macb                  00:04:0E:FF:FF:02
macwlan               00:04:0E:FF:FF:03
macdsl                00:04:0E:FF:FF:04
usb_board_mac         00:04:0E:FF:FF:05
usb_rndis_mac         00:04:0E:FF:FF:06
bluetooth             00:04:0E:FF:FF:07   # removed in 1.174
my_ipaddress          192.168.178.1
autoload              yes
modetty0              38400,n,8,1,hw
modetty1              38400,n,8,1,hw
bootserport           tty0
prompt                Eva_AVM
SerialNumber          0000000000000000
bootloaderVersion     1.153               # build parameter
urlader-version       1153                # build parameter

Computed at runtime:

cpufrequency          150000000           # gathered platform specific
req_fullrate_freq     125000000           # gathered platform specific
sysfrequency          125000000           # gathered platform specific
firstfreeaddress      0x946AE450          # pointer to end of EVA in RAM

Model specific computed from the Config section:

mtd0                  0x90000000,0x90000000
mtd1                  0x90010000,0x903C0000
mtd2                  0x90000000,0x90010000
mtd3                  0x903C0000,0x903E0000
mtd4                  0x903E0000,0x90400000
memsize               0x01000000
flashsize             0x00400000

Model specific variables from the Config section:

# Present in 1.153 probe:
HWRevision            113
ProductID             Fritz_Box_2031
usb_device_id         0x3702
usb_revision_id       0x0200
usb_device_name       USB DSL Device
usb_manufacturer_name AVM
annex                 B

# Additionally in 1.174 probe:
SerialNumber          0000000000000000
reserved              <empty>
bluetooth             <empty>
usb_rndis_mac         00:1A:4F:*
usb_board_mac         00:1A:4F:*
macdsl                00:1A:4F:*
macwlan               00:04:0E:*
macb                  00:1A:4F:*
maca                  00:1A:4F:*

....

Never clear the TFFS partitions even if 1000 postings and tools recommend it. It always was a stupid messup!
Using the same MAC addresses everywhere is as stupid as opening an unprotected WLAN because of clearing the key.

Config

EVA introduces a Config structure located at 0x580 - 0x97C, which contains parameters which are unique for this very device.

Version 2

Version 3

6490 uses ...

Weblinks

SMW-Browser

Information is currently being retrieved from the backend.
 

Synonyms

Showing 1 related property.

E