Isl3893-Y.A.F.H - Yet another Firmware-HOWTO - Revision history

84.147.24.41: /* Config and Building */

2006-08-07T12:50:03Z

Config and Building

← Older revision		Revision as of 12:50, 7 August 2006
Line 51:		Line 51:
	<pre>		<pre>
	unzip AP-600RP_GNU_source-code.zip		unzip AP-600RP_GNU_source-code.zip
			#the source tree expects the tools that were compiled by the toolchain in
			# /opt/uclinux_tools_1.6.0.0/bin so you should link them there
	tar -xvzf Code.tgz		tar -xvzf Code.tgz
	cd v1010		cd v1010

Stefan at 15:05, 28 March 2006

2006-03-28T15:05:24Z

← Older revision		Revision as of 15:05, 28 March 2006
Line 67:		Line 67:
	cd ../apfw # Software/firmware/apfw		cd ../apfw # Software/firmware/apfw
	make image		make image
	* takes a few minutes. You should then have a new firmware-image in file 'apfirmware.img'		# takes a few minutes. You should then have a new firmware-image in file 'apfirmware.img'
	* DO NOT UPLOAD THIS YET		# DO NOT UPLOAD THIS YET
	</pre>		</pre>

Stefan at 15:04, 28 March 2006

2006-03-28T15:04:52Z

← Older revision		Revision as of 15:04, 28 March 2006
Line 28:		Line 28:
	(both dated Mar 21 2006)		(both dated Mar 21 2006)

			<pre>
	unpack		unpack
	cd tools		cd tools
Line 34:		Line 35:
	# takes a few minutes ...		# takes a few minutes ...
	# that was easy, wasn't it ? :-)		# that was easy, wasn't it ? :-)
			</pre>

	==Building the firmware==		==Building the firmware==
Line 48:		Line 49:

	===Config and Building===		===Config and Building===
			<pre>
	unzip AP-600RP_GNU_source-code.zip		unzip AP-600RP_GNU_source-code.zip
	tar -xvzf Code.tgz		tar -xvzf Code.tgz
Line 65:		Line 67:
	cd ../apfw # Software/firmware/apfw		cd ../apfw # Software/firmware/apfw
	make image		make image
	# takes a few minutes. You should then have a new firmware-image in file 'apfirmware.img'		* takes a few minutes. You should then have a new firmware-image in file 'apfirmware.img'
	# DO NOT UPLOAD THIS YET		* DO NOT UPLOAD THIS YET
			</pre>

	===Patching===		===Patching===
Line 72:		Line 75:

	So now some patches:		So now some patches:
			<pre>
	cd ../uClinux/romfs/etc # Software/firmware/uClinux/romfs/etc/		cd ../uClinux/romfs/etc # Software/firmware/uClinux/romfs/etc/
	vi startup.list		vi startup.list
Line 89:		Line 92:
	cd init.d # Software/firmware/uClinux/romfs/etc/init.d/		cd init.d # Software/firmware/uClinux/romfs/etc/init.d/
	vi network		vi network
	# after the line 'ifconfig lo 127.0.0.1 up' add these lines		after the line 'ifconfig lo 127.0.0.1 up' add these lines
	a) for having the AP get its IP by dhcp:		a) for having the AP get its IP by dhcp:
	ifup eth0 autoip		ifup eth0 autoip
Line 107:		Line 110:
	make image		make image
	# wait a while ...		# wait a while ...
			</pre>

	===Upload to the AP===		===Upload to the AP===
Line 113:		Line 117:
	To upload put your AP in safe mode by turning on the power with the reset-button pressed. The AP now has the IP 192.0.2.93 and no firmware. It responds only to tftp and ping.		To upload put your AP in safe mode by turning on the power with the reset-button pressed. The AP now has the IP 192.0.2.93 and no firmware. It responds only to tftp and ping.

			<pre>
	Connect it to your PC and		Connect it to your PC and

Line 127:		Line 132:
	# then:		# then:
	ifconfig eth0 192.168.1.99		ifconfig eth0 192.168.1.99
			</pre>

	The AP should come up and get an IP by dhcp or respond to ping 192.168.1.253. You can monitor what is happening if you start a sniffer on eth0.		The AP should come up and get an IP by dhcp or respond to ping 192.168.1.253. You can monitor what is happening if you start a sniffer on eth0.

Stefan at 14:49, 28 March 2006

2006-03-28T14:49:37Z

← Older revision		Revision as of 14:49, 28 March 2006
Line 136:		Line 136:
	==Recovery==		==Recovery==
	Just in case something went wrong, see [[isl3893-Y.A.R.C - Yet another ReCovery-HOWTO]] http://www.smiley-channel.de/grafiken/smiley/idee/smiley-channel.de_idee004.gif		Just in case something went wrong, see [[isl3893-Y.A.R.C - Yet another ReCovery-HOWTO]] http://www.smiley-channel.de/grafiken/smiley/idee/smiley-channel.de_idee004.gif

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

Stefan at 14:47, 28 March 2006

2006-03-28T14:47:44Z

← Older revision		Revision as of 14:47, 28 March 2006
Line 1:		Line 1:
	=Isl3893-Y.A.F.H - Yet another Firmware-HOWTO=		=Isl3893-Y.A.F.H - Yet another Firmware-HOWTO=


	This is a step-by-step-HOWTO on "from scratch"-compiling the firmware for the AP-600. It has been tested several times on two different SuSE-10-PCs, each time deleting the source-tree and starting over.		This is a step-by-step-HOWTO on "from scratch"-compiling the firmware for the AP-600. It has been tested several times on two different SuSE-10-PCs, each time deleting the source-tree and starting over.

134.176.160.168 at 14:44, 28 March 2006

2006-03-28T14:44:20Z

← Older revision		Revision as of 14:44, 28 March 2006
Line 45:		Line 45:
	Also this HOWTO is not meant to be finished. You will have some basic functionality including shell-access. Then you can start making your own mods.		Also this HOWTO is not meant to be finished. You will have some basic functionality including shell-access. Then you can start making your own mods.

			===Sources===
	Get AP-600RP_GNU_source-code.zip. That should be the firmware-sources as released by Fujitsu-Siemens.		Get AP-600RP_GNU_source-code.zip. That should be the firmware-sources as released by Fujitsu-Siemens.

			===Config and Building===
	unzip AP-600RP_GNU_source-code.zip		unzip AP-600RP_GNU_source-code.zip
	tar -xvzf Code.tgz		tar -xvzf Code.tgz
Line 67:		Line 69:
	# DO NOT UPLOAD THIS YET		# DO NOT UPLOAD THIS YET

			===Patching===
	Unfortunately there are a few bugs in the sources. I do not speculate on whether ZCom or Fujitsu-Siemens or whoever else might have planted these intentionally :-(		Unfortunately there are a few bugs in the sources. I do not speculate on whether ZCom or Fujitsu-Siemens or whoever else might have planted these intentionally :-(

Line 106:		Line 109:
	# wait a while ...		# wait a while ...

			===Upload to the AP===
	Then you can hopefully upload apfirmware.img. This is also known as the "Load-And-Pray"-Mode :-)		Then you can hopefully upload apfirmware.img. This is also known as the "Load-And-Pray"-Mode :-)

134.176.160.168 at 14:42, 28 March 2006

2006-03-28T14:42:00Z

← Older revision		Revision as of 14:42, 28 March 2006
Line 132:		Line 132:

	==Recovery==		==Recovery==
	Just in case something went wrong, see [[isl3893-Y.A.R.C - Yet another ReCovery-HOWTO]]		Just in case something went wrong, see [[isl3893-Y.A.R.C - Yet another ReCovery-HOWTO]] http://www.smiley-channel.de/grafiken/smiley/idee/smiley-channel.de_idee004.gif

134.176.160.168 at 14:38, 28 March 2006

2006-03-28T14:38:44Z

← Older revision		Revision as of 14:38, 28 March 2006
Line 1:		Line 1:
			=Isl3893-Y.A.F.H - Yet another Firmware-HOWTO=


	This is a step-by-step-HOWTO on "from scratch"-compiling the firmware for the AP-600. It has been tested several times on two different SuSE-10-PCs, each time deleting the source-tree and starting over.		This is a step-by-step-HOWTO on "from scratch"-compiling the firmware for the AP-600. It has been tested several times on two different SuSE-10-PCs, each time deleting the source-tree and starting over.


	It assumes fair Linux-knowledge on your part, and of course NO CLAIM of any kind concerning these instructions shall be made. There is NO CLAIM that these instructions will work in any beneficial way, nor that you will not completely fuck up your AP if you try them. If you do not have at least a basic idea on what to do if you toast you AP, then don't do anything described below. And don't bother your dealer or the customersupport if you blew it. OK?		It assumes fair Linux-knowledge on your part, and of course NO CLAIM of any kind concerning these instructions shall be made. There is NO CLAIM that these instructions will work in any beneficial way, nor that you will not completely fuck up your AP if you try them. If you do not have at least a basic idea on [[isl3893-Y.A.R.C - Yet another ReCovery-HOWTO\|what to do if you toast you AP]], then don't do anything described below. And don't bother your dealer or the customersupport if you blew it. OK?


Line 10:		Line 13:
	* wet54gs5: See http://www.student.kuleuven.ac.be/~s0169612/isl3893.html for more info.		* wet54gs5: See http://www.student.kuleuven.ac.be/~s0169612/isl3893.html for more info.

			==Software/Tools==
	Used current version of the linux-platform and linux-tools:		Used current version of the linux-platform and linux-tools:
	* Linux opensuse 10.0 (german)		* Linux opensuse 10.0 (german)
Line 19:		Line 22:


	Building the toolchain		==Building the toolchain==

	After Arco did some serious patching to the sources on sf.net this should work out of the box:		After Arco did some serious patching to the sources on sf.net this should work out of the box:
Line 34:		Line 37:


	Building the firmware		==Building the firmware==

	Some steps may be unnecessary for the AP-600-sources, but can become necessary for other source-trees. They will not do any damage though.		Some steps may be unnecessary for the AP-600-sources, but can become necessary for other source-trees. They will not do any damage though.
Line 127:		Line 130:

	There may be trouble getting the webserver boa (/etc/init.d/boa and /bin/boa) running, and a webfilesystem has to be added later.		There may be trouble getting the webserver boa (/etc/init.d/boa and /bin/boa) running, and a webfilesystem has to be added later.

			==Recovery==
			Just in case something went wrong, see [[isl3893-Y.A.R.C - Yet another ReCovery-HOWTO]]

134.58.253.131 at 21:15, 26 March 2006

2006-03-26T21:15:27Z

← Older revision		Revision as of 21:15, 26 March 2006
Line 6:		Line 6:

	The steps in this document have been tested by starting "from scratch", if necessary by deleting or renaming an already existing source-tree.		The steps in this document have been tested by starting "from scratch", if necessary by deleting or renaming an already existing source-tree.
	* Tried, not tested: The firmware-sources from Medion are very similar and should work too.		* Tried, not tested: The firmware-sources from Medion are very similar and should work too. The building path has been hardcoded into the Makefile however (intentionally to harden homebrew development?), so the sources can only be compiled when installed in /home/paulfh.
	* Tried, not tested: The sources for the Sitecom WET-122-v1 can be compiled too, but you have to get the apps-nongpl-subtree elsewhere, for example from the AP-600-sources. Build the WL-122-v1-sources, then you will see where to copy the missing sub-tree.		* Tried, not tested: The sources for the Sitecom WET-122-v1 can be compiled too, but you have to get the apps-nongpl-subtree elsewhere, for example from the AP-600-sources. Build the WL-122-v1-sources, then you will see where to copy the missing sub-tree.
	* wet54gs5: See http://www.student.kuleuven.ac.be/~s0169612/isl3893.html for more info.		* wet54gs5: See http://www.student.kuleuven.ac.be/~s0169612/isl3893.html for more info.

84.174.2.249 at 16:52, 25 March 2006

2006-03-25T16:52:30Z

← Older revision		Revision as of 16:52, 25 March 2006
Line 21:		Line 21:
	Building the toolchain		Building the toolchain

	After Arco did some serious patching to the sources on sf.net this should work out of the box: http://appeltaart.mine.nu/isl3893-tools-~~20060319~~.tar.bz2		After Arco did some serious patching to the sources on sf.net this should work out of the box:
			http://osdn.dl.sourceforge.net/sourceforge/isl3893/isl3893-tools-20060321.tar.bz2
			or: http://appeltaart.mine.nu/isl3893/isl3893-tools-20060321.tar.bz2
			(both dated Mar 21 2006)

	unpack		unpack