This shows you the differences between two versions of the page.
partitions [2011/08/29 13:22] |
partitions [2011/08/30 17:34] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== partition table ====== | ||
+ | ^ beginning ^ end ^ name ^ type ^ | ||
+ | | 0x00000000 | 0x00020000 | uboot | raw | | ||
+ | | 0x00020000 | 0x00040000 | customisation | cramfs | | ||
+ | | 0x00040000 | 0x00080000 | operator | cramfs | | ||
+ | | 0x00080000 | 0x000a0000 | ubootenv0 | ASCII | | ||
+ | | 0x000a0000 | 0x000c0000 | ubootenv1 | ASCII | | ||
+ | | 0x000c0000 | 0x002e0000 | recovery | kernel | | ||
+ | | 0x002e0000 | 0x00300000 | calibration | raw | | ||
+ | | 0x00300000 | 0x00580000 | kernelA | kernel | | ||
+ | | 0x00580000 | 0x01580000 | rootfsA | cramfs | | ||
+ | | 0x01580000 | 0x01f80000 | ubiqfsA | cramfs | | ||
+ | | 0x01f80000 | 0x02160000 | databaseA | jffs2 | | ||
+ | | 0x02180000 | 0x02400000 | kernelB | raw | | ||
+ | | 0x02400000 | 0x03400000 | rootfsB | cramfs | | ||
+ | | 0x03400000 | 0x03e00000 | ubiqfsB | cramfs | | ||
+ | | 0x03e00000 | 0x03fe0000 | databaseB | jffs2 | | ||
+ | |||
+ | ====== source ====== | ||
+ | |||
+ | the informations about the partitions can be found: | ||
+ | * it is partially printed on the serial while booting | ||
+ | * the information can be found in **recovery/usr/share/recover/env.devault** | ||
+ | * **env.default** is used to create **ubootenv0** and **ubootenv1** | ||
+ | * to see partitions | ||
+ | |||
+ | cat /proc/mtd | ||
+ | cat /etc/fstab | ||
+ | |||
+ | * mtd4,5,6,7 are always the current system kernel,rootfs,ubiqfs,database. uboot uses **ubootenv0** or **ubootenv1** to start //systemA// or //systemB//. Only the order of the partitions are swapped, the addresses of them stay the same. The kernel recognizes this if it is //systemA// or //systemB// using the information provided by uboot. | ||
+ | |||
+ | ====== remarks ====== | ||
+ | |||
+ | * **ubootenv0** and **ubootenv1** are similar, only the order of the partition is different | ||
+ | * alternate system is used after 3 reboot | ||
+ | * //systemB// can be the recovery kernel or a complete system (like //systemA//), depending on the [[recovery]] or [[webupdate]]. |