HOWTO:Backup your router - Revision history

Kpersohn: /* JTAG */

2011-06-21T17:59:20Z

JTAG

Kpersohn: /* CFE */

2011-06-21T17:49:26Z

CFE

Kpersohn: /* CFE */

2011-06-21T17:48:03Z

CFE

Kpersohn: /* CFE */

2011-06-21T17:46:00Z

CFE

Kpersohn: /* dd-wrt */

2011-06-21T16:47:15Z

dd-wrt

Kpersohn: Created page with 'When experimenting with kernels, you may find yourself corrupting the router and having to recover from a known good state. It is a good idea to make a copy of the CFE when i...'

2011-06-21T16:41:01Z

Created page with 'When experimenting with kernels, you may find yourself corrupting the router and having to recover from a known good state. It is a good idea to make a copy of the CFE when i...'

New page

When experimenting with kernels, you may find yourself corrupting the router and having to recover from a known good state. It is a good idea to make a copy of the [[CFE]] when it is in its original factory configuration for if and when. Here are a few different methods depending on your resources:

= dd-wrt =

= CFE =

= JTAG =

← Older revision		Revision as of 17:59, 21 June 2011
Line 40:		Line 40:

	= JTAG =		= JTAG =
		+	For this method to work, we assume you have a working [[EJTAG]] interface to your router. For details, check out our [[Router Recovery]] page.
		+
		+	Use the <tt>-probeonly</tt> option to figure out what options TJTAG needs for your particular setup.
		+
		+	Backup the CFE with TJTAG:
		+	<code><pre>user@host:tjtag$ ./tjtag -backup:cfe /wiggler /noemw /noreset</pre></code>
		+
		+	TJTAG will create a CFE.BIN file with some sort of timestamp identifier appended to the filename. Rename and store somewhere safe.

@@ Line 8: / Line 8: @@
 = CFE =
-To backup the CFE from within the CFE itself you need an active [[HOWTO:Connect_to_a_modified_router|serial console] and a live network connection to a [[HOWTO:Deploy_Xinu|TFTP server]]. On the TFTP server, create a file for the backup image. It must be world writable. If you do not pre-create the file for the TFTP client, the backup may fail. We name and label our routers to keep them straight.  Consider naming the backup image after each router's hostname if you have many of them.
+To backup the CFE from within the CFE itself you need an active [[HOWTO:Connect_to_a_modified_router|serial console]] and a live network connection to a [[HOWTO:Deploy_Xinu|TFTP server]]. On the TFTP server, create a file for the backup image. It must be world writable. If you do not pre-create the file for the TFTP client, the backup may fail. We name and label our routers to keep them straight.  Consider naming the backup image after each router's hostname if you have many of them.
 Example:

@@ Line 37: / Line 37: @@
 </pre></code>
-Note: You can also save the entire flash image (CFE+Kernel+NVRAM) by passing 400000 as the length instead of 40000.  This isn't really necessary, but you might find it referenced elsewhere.  If you have to [[Router recovery|recover]] via JTAG it will take a LONG time to restore the entire flash image. It is much more efficient to load just the CFE, then upload the kernel via TFTP and use a factory reset to restore NVRAM.
+Note: You can also save the entire flash image (CFE+Kernel+NVRAM) by passing 400000 as the length instead of 40000.  This isn't really necessary, but you might find it referenced elsewhere.  If you have to [[Router Recovery|recover]] via JTAG it will take a LONG time to restore the entire flash image. It is much more efficient to load just the CFE, then upload the kernel via TFTP and use a factory reset to restore NVRAM.
 = JTAG =

@@ Line 7: / Line 7: @@
 <code><pre>http://ROUTER_IP/backup/cfe.bin</pre></code>
 = CFE =
 = JTAG =

@@ Line 1: / Line 1: @@
 When experimenting with kernels, you may find yourself corrupting the router and having to recover from a known good state. It is a good idea to make a copy of the [[CFE]] when it is in its original factory configuration for if and when. Here are a few different methods depending on your resources:
 = dd-wrt =
 = CFE =
 = JTAG =