Go back to generic.flashing
One example of a bootloader containing a FTP-server is the ADAM2/EVA-bootloader, used by Texas Instruments hardware. One device, regarding to which this howto is written, is the AVM FRITZ!Box Fon WLAN 7570. No, this is not supported by OpenWrt, and probably will never be!
Said box has the default IP address of 192.168.1.1, but the bootloader has a different default IP address: 192.168.178.1. Since we connect to the bootloader, and not to the firmware, this is the one relevant here.
~/imagesand change into that directory
ftp -n 192.168.178.1
(read ftp for the meaning of the
adam2and the password is also
adam2. Enter them as prompted and then issue the following commands:
binary debug passive quote MEDIA FLSH put empty.file mtd3 put empty.file mtd4 put kernel.image mtd1 reboot
(On the AVM FRITZ!Box Fon WLAN 7170 the last command must be replaced by
Depending on what firmware you install, it may be necessary to additionally change a certain parameter in the bootloader environment:
quote SETENV firmware_version "hansenet"
Note0: In case of the AVM/Fritz! with EVA-bootloader, at least on the 7360, do
not change the environment-variable firmware-version. Doing so makes the ethernet interface fail (only access is via the console), some of the AVM-daemons crash and after 160 seconds the hardware watchdog kicks in, causing the box to reboot over and over. At least on the international version of the 7360, the correct value is
Eva_AVM >setenv firmware_version avme Eva_AVM >restart
Note1: In case of the EVA-bootloader, do not issue any other commands. This bootloader is broken by design, if you issue some harmless command like say
quote GETENV firmware_version, the upload process will not function any longer afterwards. You would need to disconnect from it, and connect again, and then try again. Such quirks are not very common, and thus a major PITA if you do not know about them. When using unmaintained and sloppily programed closed source software, like EVA, you really should expect anything
Note2: the files
kernel.image are the ones located in
~/images. In order for the FTP client to find them, you need to change into that directory either before starting the FTP client or after that by issuing
lcd ~/image into the ftp-client.
Note3: should you decide to use
ncftp instead of
ftp, you need to connect with
ncftp -u adam2 192.168.178.1. That is why, you should read the manpage for the software you are employing!