Isl3893-Y.A.R.C - Yet another ReCovery-HOWTO - Revision history

83.18.142.219: /* Flashing new Firmware */

2006-06-29T13:55:07Z

Flashing new Firmware

← Older revision		Revision as of 13:55, 29 June 2006
Line 49:		Line 49:
	binary		binary
	put imginstall		put imginstall
	put <another firmware image-file>		put <another firmware image-file.img>
	quit		quit

Line 55:		Line 55:
	cd /var		cd /var
	chmod +x imginstall		chmod +x imginstall
	imginstall -k <firmware image-file>		/var/imginstall -k /var/ <firmware image-file.img>
	</pre>		</pre>

Stefan at 15:16, 28 March 2006

2006-03-28T15:16:32Z

← Older revision		Revision as of 15:16, 28 March 2006
Line 34:		Line 34:
	===Recovery-Upload===		===Recovery-Upload===
	For recovery get a small firmware-image like [http://isl3893.sourceforge.net/download/firmware/siemens-wlanap600rp/apfw.minimal.img apfw.minimal.img]		For recovery get a small firmware-image like [http://isl3893.sourceforge.net/download/firmware/siemens-wlanap600rp/apfw.minimal.img apfw.minimal.img]

			You will also need [http://www.student.kuleuven.ac.be/~s0169612/isl3893/imginstall imginstall]

	apfw.minimal.img usually fits even if the partitions are misconfigured. Upload it as described in section		apfw.minimal.img usually fits even if the partitions are misconfigured. Upload it as described in section

Stefan at 15:01, 28 March 2006

2006-03-28T15:01:13Z

← Older revision		Revision as of 15:01, 28 March 2006
Line 2:		Line 2:

	You can recover either using Safe Mode or a recovery image		You can recover either using Safe Mode or a recovery image

	==Method 1: Safe Mode==		==Method 1: Safe Mode==
	Turn AP off, press the reset-button, keep it pressed and switch back on. The AP will then respond to IP 192.0.2.93, TFTP and ping only. You can then upload a firmware image. (Set you PCs IP accordingly, of course :-)		Turn AP off, press the reset-button, keep it pressed and switch back on. The AP will then respond to IP 192.0.2.93, TFTP and ping only. You can then upload a firmware image. (Set you PCs IP accordingly, of course :-)

134.176.160.168: /* Flashing new Firmware */

2006-03-28T15:00:46Z

Flashing new Firmware

← Older revision		Revision as of 15:00, 28 March 2006
Line 42:		Line 42:

	===Flashing new Firmware===		===Flashing new Firmware===
			<pre>
	Then FTP 192.168.24.23		Then FTP 192.168.24.23
	cd /var		cd /var
Line 53:		Line 54:
	chmod +x imginstall		chmod +x imginstall
	imginstall -k <firmware image-file>		imginstall -k <firmware image-file>
			</pre>

	You should get a message like "programming block N" every few seconds.		You should get a message like "programming block N" every few seconds.

134.176.160.168 at 14:59, 28 March 2006

2006-03-28T14:59:41Z

← Older revision		Revision as of 14:59, 28 March 2006
Line 6:		Line 6:
	Turn AP off, press the reset-button, keep it pressed and switch back on. The AP will then respond to IP 192.0.2.93, TFTP and ping only. You can then upload a firmware image. (Set you PCs IP accordingly, of course :-)		Turn AP off, press the reset-button, keep it pressed and switch back on. The AP will then respond to IP 192.0.2.93, TFTP and ping only. You can then upload a firmware image. (Set you PCs IP accordingly, of course :-)

	<~~code~~>		<pre>
	On windows:		On windows:
	tftp -i 192.0.2.93 PUT <name of firmware imagefile>		tftp -i 192.0.2.93 PUT <name of firmware imagefile>
Line 17:		Line 17:
	put <name of firmware imagefile>		put <name of firmware imagefile>
	quit		quit
	</~~code~~>		</pre>

	Uploading this way takes 1-2 minutes, the LAN-LED flashes very fast during that time. Then the AP should automatically reboot. It may then take another 2-3 minutes before the AP responds again.		Uploading this way takes 1-2 minutes, the LAN-LED flashes very fast during that time. Then the AP should automatically reboot. It may then take another 2-3 minutes before the AP responds again.

134.176.160.168: /* Method 1: Safe Mode */

2006-03-28T14:59:17Z

Method 1: Safe Mode

← Older revision		Revision as of 14:59, 28 March 2006
Line 6:		Line 6:
	Turn AP off, press the reset-button, keep it pressed and switch back on. The AP will then respond to IP 192.0.2.93, TFTP and ping only. You can then upload a firmware image. (Set you PCs IP accordingly, of course :-)		Turn AP off, press the reset-button, keep it pressed and switch back on. The AP will then respond to IP 192.0.2.93, TFTP and ping only. You can then upload a firmware image. (Set you PCs IP accordingly, of course :-)

			<code>
	On windows:		On windows:
	tftp -i 192.0.2.93 PUT <name of firmware imagefile>		tftp -i 192.0.2.93 PUT <name of firmware imagefile>
Line 16:		Line 17:
	put <name of firmware imagefile>		put <name of firmware imagefile>
	quit		quit
			</code>

	Uploading this way takes 1-2 minutes, the LAN-LED flashes very fast during that time. Then the AP should automatically reboot. It may then take another 2-3 minutes before the AP responds again.		Uploading this way takes 1-2 minutes, the LAN-LED flashes very fast during that time. Then the AP should automatically reboot. It may then take another 2-3 minutes before the AP responds again.

Stefan at 14:49, 28 March 2006

2006-03-28T14:49:54Z

← Older revision		Revision as of 14:49, 28 March 2006
Line 63:		Line 63:
	* section "Flashing large firmware images"		* section "Flashing large firmware images"
	* section "Recovering the AP from a bad firmware image"		* section "Recovering the AP from a bad firmware image"

			==[[ISL3893\|Back to ISL3893]]==

Stefan at 14:48, 28 March 2006

2006-03-28T14:48:22Z

← Older revision		Revision as of 14:48, 28 March 2006
Line 1:		Line 1:
	=Recovering an isl3893-AP after a bad firmware-flash=		=Recovering an isl3893-AP after a bad firmware-flash=

			You can recover either using Safe Mode or a recovery image
	You can ~~use~~ either Safe Mode or a recovery image

	==Method 1: Safe Mode==		==Method 1: Safe Mode==

134.176.160.168 at 14:46, 28 March 2006

2006-03-28T14:46:20Z

← Older revision		Revision as of 14:46, 28 March 2006
Line 4:		Line 4:
	You can use either Safe Mode or a recovery image		You can use either Safe Mode or a recovery image

	==Safe Mode==		==Method 1: Safe Mode==
	Turn AP off, press the reset-button, keep it pressed and switch back on. The AP will then respond to IP 192.0.2.93, TFTP and ping only. You can then upload a firmware image. (Set you PCs IP accordingly, of course :-)		Turn AP off, press the reset-button, keep it pressed and switch back on. The AP will then respond to IP 192.0.2.93, TFTP and ping only. You can then upload a firmware image. (Set you PCs IP accordingly, of course :-)

Line 24:		Line 24:
	You may get the error-message "firmware image exceeds flash-size". In that case see section [[isl3893-Y.A.R.C - Yet another ReCovery-HOWTO#Recovery Image\|Recovery Image]]		You may get the error-message "firmware image exceeds flash-size". In that case see section [[isl3893-Y.A.R.C - Yet another ReCovery-HOWTO#Recovery Image\|Recovery Image]]

	==Recovery Image==		==Method 2: Recovery Image==
	The error-message "firmware image exceeds flash-size" means the the previously flashed firmware has repartitioned the flash-memory of the AP. The partition for the firmware can then be too small for any other image, often even including the one that reset the partitions.		The error-message "firmware image exceeds flash-size" means the the previously flashed firmware has repartitioned the flash-memory of the AP. The partition for the firmware can then be too small for any other image, often even including the one that reset the partitions.

Line 31:		Line 31:
	The publicly available firmware-sources usually have pre-set partition-sizes 10000/1b0000/200000. The can be changed before compiling the sources, see make menuconfig. Try for example 10000/200000/360000. That helps avoid the "exceeds flash-size"-error.		The publicly available firmware-sources usually have pre-set partition-sizes 10000/1b0000/200000. The can be changed before compiling the sources, see make menuconfig. Try for example 10000/200000/360000. That helps avoid the "exceeds flash-size"-error.

			===Recovery-Upload===
	For recovery get a small firmware-image like [http://isl3893.sourceforge.net/download/firmware/siemens-wlanap600rp/apfw.minimal.img apfw.minimal.img]		For recovery get a small firmware-image like [http://isl3893.sourceforge.net/download/firmware/siemens-wlanap600rp/apfw.minimal.img apfw.minimal.img]

Line 39:		Line 40:
	After upload, reboot and another 2 minutes (use sniffer to monitor) you should be able to telnet 192.168.24.23. FTP should also work.		After upload, reboot and another 2 minutes (use sniffer to monitor) you should be able to telnet 192.168.24.23. FTP should also work.

			===Flashing new Firmware===
	Then FTP 192.168.24.23		Then FTP 192.168.24.23
	cd /var		cd /var

134.176.160.168 at 14:34, 28 March 2006

2006-03-28T14:34:37Z

← Older revision		Revision as of 14:34, 28 March 2006
Line 1:		Line 1:
	=Recovering an isl3893-AP after a bad firmware-flash=		=Recovering an isl3893-AP after a bad firmware-flash=

	~~See Ruben's page: http://www.student.kuleuven.ac.be/~s0169612/isl3893.html~~
	* section "Flashing large firmware images"
	* section "Recovering the AP from a bad firmware image"


Line 61:		Line 57:

	The AP should then behave according the features of the firmware.		The AP should then behave according the features of the firmware.

			==Other Links==
			See Ruben's page: http://www.student.kuleuven.ac.be/~s0169612/isl3893.html
			* section "Flashing large firmware images"
			* section "Recovering the AP from a bad firmware image"