Archiving JFFS2 Images - Revision history

Mdean: /* Procedure */ Fixed mistake made by MW

2014-09-10T00:42:15Z

‎Procedure: Fixed mistake made by MW

Bserrano at 16:17, 11 April 2014

2014-04-11T16:17:54Z

Bserrano at 21:21, 6 March 2014

2014-03-06T21:21:14Z

Bserrano at 21:03, 6 March 2014

2014-03-06T21:03:10Z

Mwelling at 21:22, 26 February 2014

2014-02-26T21:22:42Z

Mgloff: Modifed nand procedure

2014-02-13T17:57:01Z

Modifed nand procedure

Mdean: Hid category tag.

2014-01-02T18:40:14Z

Hid category tag.

Mdean: Undo revision 970 by Jgreene (talk)

2013-11-08T21:15:05Z

Undo revision 970 by Jgreene (talk)

Mdean: Undo revision 971 by Jgreene (talk)

2013-11-08T21:14:38Z

Undo revision 971 by Jgreene (talk)

Mdean: Undo revision 972 by Jgreene (talk)

2013-11-08T21:14:14Z

Undo revision 972 by Jgreene (talk)

@@ Line 35: / Line 35: @@
 <ol>
-  <li>Boot the system and log in as the root uumount /tmp/nfsser.</li>
+  <li>Boot the system and log in as the root user.</li>
   <li>Create a directory to use for the mount point of the NFS drive. For this example, <code>/tmp/nfs</code> will be used.</li>
   root@emac-oe:~# mkdir /tmp/nfs

@@ Line 1: / Line 1: @@
-{{todo|<strike>Polish this</strike> Review(11.05.13-17:33->JG+)(02.10.14-11:55->MG+)(02.26.14-15:19->MW+)(03.06.14-15:00->BS-)|Mike Dean|project=oe 4,oe 5,md,SEOKWTODO,mw,mg,bs}}
+{{todo|<strike>Polish this</strike> Review(11.05.13-17:33->JG+)(02.10.14-11:55->MG+)(02.26.14-15:19->MW+)(03.06.14-15:00->BS-);(04.11.14-11:15->BS+)|Mike Dean|project=oe 4,oe 5,md,SEOKWREV,mw,mg,bs}}
 === Background ===
 During the development process, which usually involves writing software for a board, various modifications are normally made to the filesystem to support the application:

← Older revision		Revision as of 21:21, 6 March 2014
Line 1:		Line 1:
−	{{todo\|<strike>Polish this</strike> Review(11.05.13-17:33->JG+)(02.10.14-11:55->MG+)(02.26.14-15:19->MW+)(03.06.14-15:00->BS+)\|Mike Dean\|project=oe 4,oe 5,md,SEOKWTODO,mw,mg,bs}}	+	{{todo\|<strike>Polish this</strike> Review(11.05.13-17:33->JG+)(02.10.14-11:55->MG+)(02.26.14-15:19->MW+)(03.06.14-15:00->BS-)\|Mike Dean\|project=oe 4,oe 5,md,SEOKWTODO,mw,mg,bs}}

	=== Background ===		=== Background ===

← Older revision		Revision as of 21:03, 6 March 2014
Line 1:		Line 1:
−	{{todo\|<strike>Polish this</strike> Review(11.05.13-17:33->JG+)(02.10.14-11:55->MG+)(02.26.14-15:19->MW+)\|Mike Dean\|project=oe 4,oe 5,md,~~Review~~,mw,mg}}	+	{{todo\|<strike>Polish this</strike> Review(11.05.13-17:33->JG+)(02.10.14-11:55->MG+)(02.26.14-15:19->MW+)(03.06.14-15:00->BS+)\|Mike Dean\|project=oe 4,oe 5,md,SEOKWTODO,mw,mg,bs}}

	=== Background ===		=== Background ===

@@ Line 1: / Line 1: @@
-{{todo|<strike>Polish this</strike> Review(11.05.13-17:33->JG+)(02.10.14-11:55->MG+)|Mike Dean|project=oe 4,oe 5,md,Review,mw,mg}}
+{{todo|<strike>Polish this</strike> Review(11.05.13-17:33->JG+)(02.10.14-11:55->MG+)(02.26.14-15:19->MW+)|Mike Dean|project=oe 4,oe 5,md,Review,mw,mg}}
 === Background ===
@@ Line 29: / Line 29: @@
 <ol>
-  <li>Boot the system and log in as the root user.</li>
+  <li>Boot the system and log in as the root uumount /tmp/nfsser.</li>
   <li>Create a directory to use for the mount point of the NFS drive. For this example, <code>/tmp/nfs</code> will be used.</li>
   root@emac-oe:~# mkdir /tmp/nfs
@@ Line 60: / Line 60: @@
 : For NAND devices, mount the NAND flash to a temporary mount point and use tar to create an archive.
   root@emac-oe:~# mkdir /tmp/flash
-  root@emac-oe:~# mount /dev/mtdblock0 /tmp/flash
+  root@emac-oe:~# mount -t jffs2 /dev/mtdblock0 /tmp/flash
   root@emac-oe:~# cd /tmp/flash
   root@emac-oe:~# tar czf /tmp/nfs/rootfs_backup.tar.gz .

@@ Line 72: / Line 72: @@
 After following the above steps, the JFFS2 filesystem image will be stored on the NFS server.  This image can then be edited on the server, or on a desktop computer's copy of the server's image, and can be programmed to other boards.  A developer may also choose to version control the images or send them to remote workers to deploy in the field.  See our other articles in this series for more information on how to perform these other tasks.
+<!--
 [[Category:Filesystems]]

@@ Line 14: / Line 14: @@
 * Custom drivers may be written for and added to the machine.
 <br />
-After months of effort (if not more than a year), the developer(s) will get to a point where the machine performs its task exactly as desired.  At this point, the developers will likely want to be able to capture an exact copy of the filesystem on the machine so that the same image can be programmed onto additional boards.  Additionally, developers will often wish to be able to make a backup copy of the filesystem during the course of development. Like version control, making these backup copies can enable a developer to try something out and roll back to a previous version if the experiment didn't pan out as hoped.
+After months of effort (if not more than a year), the developer(s) will get to a point where the machine performs its task exactly as desired.  At this point, the developers will likely want to be able to capture an exact copy of the filesystem on the machine so that the same image can be programmed onto additional boards.  Additionally, developers will often wish to be able to make a backup copy of the filesystem during the course of development; like version control, making these backup copies can enable a developer to try something out and roll back to a previous version if the experiment didn't pan out as hoped.
 This page describes how JFFS2 images can be made from the filesystem on the flash memory on a machine.  This enables developers to meet the needs outlined above and others which aren't mentioned here.

@@ Line 34: / Line 34: @@
   <li>Mount the NFS filesystem. The commands in this step assume that 10.0.2.60 is the IP address of the NFS server on the local network and that <code>/opt/nfs</code> is the exported directory on the server to which the image should be copied. These parameters will need to be adjusted to match the local network configuration. Also note that the <code>nolock</code> option is necessary because no portmap daemon is running on the default EMAC OE system.</li>
   root@emac-oe:~# mount -o nolock -t nfs 10.0.2.60:/opt/nfs /tmp/nfs
-  <li>Next, determine which MTD partition contains the JFFS2 image to be copied. In most cases, this will be the root filesystem but the same procedure can be used to archive any JFFS2 partition. The most helpful information can usually be found in the <code>/proc/mtd</code> file. The output of the <code>mount</code> command, <code>/etc/fstab</code> and other commands may also be used. The listing below shows the contents of <code>/proc/mtd</code> on a system where <code>/dev/mtd0</code> contains the root filesytem.  The name column tells us this, because the name for the <code>mtd0</code> partition is shown as "root."</li>
+  <li>Next, determine which MTD partition contains the JFFS2 image to be copied. In most cases, this will be the root filesystem but the same procedure can be used to archive any JFFS2 partition. The most helpful information can usually be found in the <code>/proc/mtd</code> file. The output of the <code>mount</code> command, <code>/etc/fstab</code>, and other commands may also be used. The listing below shows the contents of <code>/proc/mtd</code> on a system where <code>/dev/mtd0</code> contains the root filesytem.  The name column tells us this, because the name for the <code>mtd0</code> partition is shown as "root."</li>
   root@emac-oe:~# cat /proc/mtd
   dev:    size   erasesize  name

@@ Line 53: / Line 53: @@
 ;NOR Flash
-: For NOR flash, the <code>dd</code> command should be used. The MTD block device corresponding to the JFFS2 partition must be specified as the image source; <code>/dev/mtdblock0</code> in this case.
+: For NOR flash, the <code>dd</code> command should be used. The MTD block device corresponding to the JFFS2 partition must be specified as the image source: <code>/dev/mtdblock0</code> in this case.
   root@emac-oe:~# cd /tmp/nfs
   root@emac-oe:~# dd if=/dev/mtdblock0 of=rootfs_backup.jffs2
 -----
 ;NAND Flash
-: For NAND devices, the <code>nanddump</code> command is used to allow for correct bad block handling. The MTD device (not the block device) corresponding to the JFFS2 partion must be specified as the image source; <code>/dev/mtd0</code> in this case.
+: For NAND devices, the <code>nanddump</code> command is used to allow for correct bad block handling. The MTD device (not the block device) corresponding to the JFFS2 partion must be specified as the image source: <code>/dev/mtd0</code> in this case.
   root@emac-oe:~# cd /tmp/nfs
   root@emac-oe:~# nanddump /dev/mtd0 -o -n -f rootfs_backup.jffs2