Firmware/V5/Update Description

From Snom User Wiki

< Firmware | V5(Difference between revisions)
Jump to: navigation, search
m (English Update Description for Release 5)
m (Text replace - 'Category:Update' to 'Category:Firmware')
 
(36 intermediate revisions not shown)
Line 1: Line 1:
-
=== Deutsche Update Beschreibung für Release 5 ===
+
'''With release 5 we are changing the format of the following images: -b (bootloader), -r (rootfs formerly named ramdisk) and -j (application).'''
-
'''Mit dem Release 5 haben wir das Firmwareformat folgender Imagetypen geändert: -b (Bootloader), -r (rootfs vorher ramdisk genannt) und -j (Aplikation).'''
+
That is because we do not want the phone user accidently downgrading to an "older" version. And this is because we replaced the linux rootfs, which was a ramdisk before, with a jffs2 filesystem, which is saving 2 MB of RAM. If you were allowed to downgrade as usual, the phone would not bootup anymore, because of incompatibilities of bootloader and rootfs.
-
Das wurde gemacht, um zu verhindern, daß der Nutzer aus versehen auf eine ältere Firmware "downgradet" und das Gerät damit unbrauchbar macht. Eben das würde passieren, weil wir das Linux rootfs (Root Filesystem), das vorher als Ramdisk angelegt war, durch ein jffs2 Filesystem ersetzt haben, welches 2 MB Hauptspeicher spart. Und wenn wir wie bisher das einfache Downgrading erlauben würden, würde das Telefon nicht mehr booten, da Bootloader und Rootfs nicht mehr zusammen passen.
+
''In other words, we made sure that you cannot destroy your snom phone with these updates by using the wrong order!''
-
Ein vollständiges Update auf das Release 5 benötigt also folgendes:
+
A full process of updating to release 5 needs the following:
-
# '''snom3X0-5.0a-SIP-j.bin''': Das ist der Applikationsteil von Release 5, der das neue Firwareformat einführt, alle Funktionen außer der Ethernetswitch-Eigenschaftenkontrolle sind hier enthalten. Manuelles Downgrading via TFTP ist weiterhin möglich.
+
# '''snom3X0-5.X-SIP-j.bin''': Application part of release 5 which introduces the new image formats, everything except the ethernet switch properties control is working. Downgrading manually via TFTP is still possible.
-
# '''snom3X0-ramdiskToJffs2-br.bin''': Hier sind neuer Bootloader und das neue Rootfilesystem jeweils mit neuem Firmwareformat enthalten, die nur mit dem Applikationsteil des Releases 5 oder höher (siehe oben), geupdatet werden können. Es bringt eine Einsparung von 2MB Haupspeicher und eine neue TFTP Updateapplikation mit, die nur Applikationsupdates von Release 5 oder höher durchführen kann. Damit können Sie also nicht mehr so einfach ein manuelles Downgrade via TFTP durchführen.
+
# '''snom3X0-ramdiskToJffs2-br.bin''': New bootloader and rootfs with new image format each, which can be updated by application part release 5 or above only. This saves 2MB of RAM and brings a TFTP update application which is able to update application images with version 5 or above only. Nevertheless it will be possible to downgrade your phone, but this is a more complex procedure, see [[Firmware/Downgrade|here]]. '''It is highly recommended to not use PoE (power over ethernet) for this specific update session!'''
-
# '''snom3X0-3.25-l.bin''': Dieses Linuxupdate wird benötigt, um die Ethernetswitcheigenschaften kontrollieren zu können. Es wird trotzdem weiterhin möglich sein Ihr Telefon manuell "downzugraden", aber das ist eine Prozedur in 2 Schritten.
+
# '''snom3X0-3.25-l.bin''': This linux is needed to make the ethernet switch properties control work.
-
Wenn Sie nur 1) und 3) ohne 2) updaten, dann bringt Ihnen das neben der vollen Funktionalität weiterhin die Option eines einfacheren manuellen Downgrades via TFTP.
+
So 1) and 3) without 2) will give you full functionality and the option of a usual manual downgrade via TFTP. 1) and 3) can be loaded in arbitrary order. 2) can loaded after 1) only.
-
1) und 3) können in beliebiger Reihenfolge geladen werden. 2) kann nur nach 1) geladen werden.
+
We are suggesting this order: 1), 2), 3). All three updates can be made consecutively via the ''Firmware'' field of the Update web interface page, see
 +
update via [[Firmware/Update/Update_Description#Update_via_Web_interface_.28HTTP.29|web interface]].
-
==== Erklärung von '''a'''/'''b''' im Namen der Applikationsfirmware ====
+
''The phone is making sure, that you cannot destroy your phone by using a wrong order of those updates. If the order is wrong it will show '''Wrong Image''' at the display!''
-
'''a'''=erstmals updaten auf 5.0, '''b'''=Updaten wenn schon 5.0 benutzt wird.
+
How to downgrade via manual [[Firmware/Update/TFTP_Update|TFTP]] is described [[Firmware/Downgrade|here]].
-
 
+
-
So wie hier: snom3X0-5.0a-SIP-j.bin und snom3X0-5.0b-SIP-j.bin
+
-
 
+
-
=== English Update Description for Release 5 ===
+
-
 
+
-
'''With release 5 we are changing the format of the following images: -b (bootloader), -r (rootfs formerly named ramdisk) and -j (application).'''
+
-
 
+
-
That is because we do not want the phone user accidently downgrading to an "older" version. And this is because we replaced the linux rootfs, which was a ramdisk before, with a jffs2 filesystem, which is saving 2 MB of RAM. If you were allowed to downgrade as usual, the phone would not bootup anymore, because of incompatibilities of bootloader and rootfs.
+
-
 
+
-
A full process of updating to release 5 needs the following:
+
-
 
+
-
# '''snom3X0-5.0a-SIP-j.bin''': Application part of release 5 which introduces the new image formats, everything except the ethernet switch properties control is working. Downgrading manually via TFTP is still possible.
+
-
# '''snom3X0-ramdiskToJffs2-br.bin''': New bootloader and rootfs with new image format each, which can be updated by application part release 5 or above only. This saves 2MB of RAM and brings a TFTP update application which is able to update application images with version 5 or above only. So now you cannot downgrade in one step via manual TFTP update anymore.
+
-
# '''snom3X0-3.25-l.bin''': This linux is needed to make the ethernet switch properties control work.
+
-
Nevertheless it will be possible to downgrade your phone, but this is a more complicated two step procedure.
+
Meaning of '''a'''/'''b''' application firmware versions
 +
Both '''a'''/'''b''' files include the same firmware version! (Item 1 above: where "X" is the minor verision number followed by either an "a" or a "b". For example: "snom3X0-5.2a-SIP-j.bin" would be the "a" version of firmware 5.2 )
-
So 1) and 3) without 2) will give you full functionality and the option of a usual manual downgrade via TFTP.
+
"'''a'''" must be used once in order to update from version 3 or 4 to version 5. Most retail phones as of March 20th, 2006 ship with version 4.X pre-installed.
-
1) and 3) can be loaded in arbitrary order. 2) can loaded after 1) only.
+
"'''b'''" must be used for updating if there is already version 5 on the phone.  
-
==== Meaning of '''a'''/'''b''' application firmware versions ====
+
Once you are on version 5.x, use '''b''' versions for updating only. Functionality wise '''a''' and '''b''' versions are 100% identical.
-
'''a'''=first time moving to 5.0, '''b'''=Already on 5.0
+
(Naming with ''a'' and ''b'' in snom3X0-5.0a-SIP-j.bin and snom3X0-5.0b-SIP-j.bin)
-
Like in: snom3X0-5.0a-SIP-j.bin and snom3X0-5.0b-SIP-j.bin
+
[[Category:V5]][[Category:Firmware]]

Latest revision as of 12:09, 9 April 2009

With release 5 we are changing the format of the following images: -b (bootloader), -r (rootfs formerly named ramdisk) and -j (application).

That is because we do not want the phone user accidently downgrading to an "older" version. And this is because we replaced the linux rootfs, which was a ramdisk before, with a jffs2 filesystem, which is saving 2 MB of RAM. If you were allowed to downgrade as usual, the phone would not bootup anymore, because of incompatibilities of bootloader and rootfs.

In other words, we made sure that you cannot destroy your snom phone with these updates by using the wrong order!

A full process of updating to release 5 needs the following:

  1. snom3X0-5.X-SIP-j.bin: Application part of release 5 which introduces the new image formats, everything except the ethernet switch properties control is working. Downgrading manually via TFTP is still possible.
  2. snom3X0-ramdiskToJffs2-br.bin: New bootloader and rootfs with new image format each, which can be updated by application part release 5 or above only. This saves 2MB of RAM and brings a TFTP update application which is able to update application images with version 5 or above only. Nevertheless it will be possible to downgrade your phone, but this is a more complex procedure, see here. It is highly recommended to not use PoE (power over ethernet) for this specific update session!
  3. snom3X0-3.25-l.bin: This linux is needed to make the ethernet switch properties control work.

So 1) and 3) without 2) will give you full functionality and the option of a usual manual downgrade via TFTP. 1) and 3) can be loaded in arbitrary order. 2) can loaded after 1) only.

We are suggesting this order: 1), 2), 3). All three updates can be made consecutively via the Firmware field of the Update web interface page, see update via web interface.

The phone is making sure, that you cannot destroy your phone by using a wrong order of those updates. If the order is wrong it will show Wrong Image at the display!

How to downgrade via manual TFTP is described here.

Meaning of a/b application firmware versions Both a/b files include the same firmware version! (Item 1 above: where "X" is the minor verision number followed by either an "a" or a "b". For example: "snom3X0-5.2a-SIP-j.bin" would be the "a" version of firmware 5.2 )

"a" must be used once in order to update from version 3 or 4 to version 5. Most retail phones as of March 20th, 2006 ship with version 4.X pre-installed.

"b" must be used for updating if there is already version 5 on the phone.

Once you are on version 5.x, use b versions for updating only. Functionality wise a and b versions are 100% identical.

(Naming with a and b in snom3X0-5.0a-SIP-j.bin and snom3X0-5.0b-SIP-j.bin)

Personal tools
Interoperability