Category:Opensource Firmware Updater - Revision history

Sungod: Reverted edits by 124.53.159.169 (Talk) to last version by 82.69.11.137

Sungod — Sun, 04 Jan 2009 23:17:21 GMT

Reverted edits by 124.53.159.169 (Talk) to last version by 82.69.11.137

← Older revision		Revision as of 23:17, 4 January 2009
Line 1:		Line 1:
-	~~sitertrvit~~
	<table align=right><tr><td>http://www.kurobox.com/mwiki/images/thumb/0/04/Fujitsu_29PL32TM-90PFTN.jpg/180px-Fujitsu_29PL32TM-90PFTN.jpg </td></tr></table>		<table align=right><tr><td>http://www.kurobox.com/mwiki/images/thumb/0/04/Fujitsu_29PL32TM-90PFTN.jpg/180px-Fujitsu_29PL32TM-90PFTN.jpg </td></tr></table>
	In [[w:computing\|computing]], '''[[w:firmware\|firmware]]''' is [[w:software\|software]] that is [[w:Embedded system\|embedded]] in a [[w:hardware\|hardware]] device. It is often provided on [[w:flash ROM\|flash ROM]]s or as a [[w:Binary file\|binary]] image file that can be uploaded onto existing hardware by a user. Firmware is defined as: The [[w:computer program\|computer program]] in a [[w:Flash_memory\|Flash memory]] [[w:integrated circuit\|integrated circuit]] (a hardware part number or other [[w:computer configuration\|configuration]] identifier is usually used to represent the software)		In [[w:computing\|computing]], '''[[w:firmware\|firmware]]''' is [[w:software\|software]] that is [[w:Embedded system\|embedded]] in a [[w:hardware\|hardware]] device. It is often provided on [[w:flash ROM\|flash ROM]]s or as a [[w:Binary file\|binary]] image file that can be uploaded onto existing hardware by a user. Firmware is defined as: The [[w:computer program\|computer program]] in a [[w:Flash_memory\|Flash memory]] [[w:integrated circuit\|integrated circuit]] (a hardware part number or other [[w:computer configuration\|configuration]] identifier is usually used to represent the software)

124.53.159.169: trocnoz

124.53.159.169 — Sun, 04 Jan 2009 22:26:58 GMT

trocnoz

← Older revision		Revision as of 22:26, 4 January 2009
Line 1:		Line 1:
		+	sitertrvit
	<table align=right><tr><td>http://www.kurobox.com/mwiki/images/thumb/0/04/Fujitsu_29PL32TM-90PFTN.jpg/180px-Fujitsu_29PL32TM-90PFTN.jpg </td></tr></table>		<table align=right><tr><td>http://www.kurobox.com/mwiki/images/thumb/0/04/Fujitsu_29PL32TM-90PFTN.jpg/180px-Fujitsu_29PL32TM-90PFTN.jpg </td></tr></table>
	In [[w:computing\|computing]], '''[[w:firmware\|firmware]]''' is [[w:software\|software]] that is [[w:Embedded system\|embedded]] in a [[w:hardware\|hardware]] device. It is often provided on [[w:flash ROM\|flash ROM]]s or as a [[w:Binary file\|binary]] image file that can be uploaded onto existing hardware by a user. Firmware is defined as: The [[w:computer program\|computer program]] in a [[w:Flash_memory\|Flash memory]] [[w:integrated circuit\|integrated circuit]] (a hardware part number or other [[w:computer configuration\|configuration]] identifier is usually used to represent the software)		In [[w:computing\|computing]], '''[[w:firmware\|firmware]]''' is [[w:software\|software]] that is [[w:Embedded system\|embedded]] in a [[w:hardware\|hardware]] device. It is often provided on [[w:flash ROM\|flash ROM]]s or as a [[w:Binary file\|binary]] image file that can be uploaded onto existing hardware by a user. Firmware is defined as: The [[w:computer program\|computer program]] in a [[w:Flash_memory\|Flash memory]] [[w:integrated circuit\|integrated circuit]] (a hardware part number or other [[w:computer configuration\|configuration]] identifier is usually used to represent the software)

82.69.11.137: /* UBOOT-INSTALLER */

82.69.11.137 — Sun, 25 Feb 2007 21:28:07 GMT

UBOOT-INSTALLER

← Older revision		Revision as of 21:28, 25 February 2007
Line 38:		Line 38:
	== UBOOT-INSTALLER ==		== UBOOT-INSTALLER ==
	'''<font color=green>We should create an easy but failsave installer.</font>''' <br>		'''<font color=green>We should create an easy but failsave installer.</font>''' <br>
-	i mean...as linuxnotincluded already wrote this can be a bashscript...maybe like andre`s webinstaller. but there is one difference. flashing UBoot can get you in serious troubles if something fails....we have to make sure that we ue checksums and some checks so there is no chance that a broken u-boot.bin (internet can be very unreliable!) or the wrong uboot-image (LS1 / HG !) are flashed to the flash.	+	i mean...as linuxnotincluded already wrote this can be a bashscript...maybe like andre`s webinstaller. but there is one difference. flashing UBoot can get you in serious troubles if something fails....we have to make sure that we use checksums and some checks so there is no chance that a broken u-boot.bin (internet can be very unreliable!) or the wrong uboot-image (LS1 / HG !) are flashed to the flash.

	'''<font color=orange>the script should check for:</font>'''		'''<font color=orange>the script should check for:</font>'''

Rickb: /* FLASH-UPDATER */

Rickb — Sat, 27 Jan 2007 11:06:22 GMT

FLASH-UPDATER

← Older revision		Revision as of 11:06, 27 January 2007
Line 5:		Line 5:
	=== FLASH-UPDATER ===		=== FLASH-UPDATER ===
	Updating the firmimg.bin in the flash is needed as a base to allow updating with the planned HddRootFS-Updater described below.		Updating the firmimg.bin in the flash is needed as a base to allow updating with the planned HddRootFS-Updater described below.
-	We need a telnet + ftp-enabled Ramdisk (EM Mode) like the Kuroboxes have. mindbender already created some for the LS1/LS HG/LS HS. These new firmimg.bins will most likely be bundled with the future openlink / freelink releases when they are ready for that.	+	We need a telnet + ftp-enabled Ramdisk (EM Mode) like the Kuroboxes have. ''mindbender'' already created some for the LS1/LS HG/LS HS. These new firmimg.bins will most likely be bundled with the future openlink / freelink releases when they are ready for that.

	'''<font color=red>Status:</font>''' currently we only have 2.4.33.3 working for UBoot-images. the current kernels cannot be bundled with the standard releases as it would break the ability to use the buffalo firmware updater because there is no check for "OKOK" in flash of the LS1/HG anymore. either we have to integrate this check again especially for the standard releases who do not want to use UBoot or we have to use the stock firmware which does not allow to much (NFS for example). mindbender plans to create a seperate 2.4.33.3 with included check for "OKOK" in flash.		'''<font color=red>Status:</font>''' currently we only have 2.4.33.3 working for UBoot-images. the current kernels cannot be bundled with the standard releases as it would break the ability to use the buffalo firmware updater because there is no check for "OKOK" in flash of the LS1/HG anymore. either we have to integrate this check again especially for the standard releases who do not want to use UBoot or we have to use the stock firmware which does not allow to much (NFS for example). mindbender plans to create a seperate 2.4.33.3 with included check for "OKOK" in flash.

209.94.50.66: /* How everything should work together */

209.94.50.66 — Fri, 06 Oct 2006 04:04:23 GMT

How everything should work together

← Older revision		Revision as of 04:04, 6 October 2006
Line 56:		Line 56:

	== How everything should work together ==		== How everything should work together ==
-	[[Image:Design-updaters.jpg\|left\|~~701px~~]]	+	[[Image:Design-updaters.jpg\|left\|500px]]

193.170.75.207: /* UBOOT-INSTALLER */

193.170.75.207 — Thu, 05 Oct 2006 15:20:39 GMT

UBOOT-INSTALLER

← Older revision		Revision as of 15:20, 5 October 2006
Line 53:		Line 53:
	in my opinion it should ONLY allow installation from the (future) stock kernel! thats the only way to make sure that it will work.		in my opinion it should ONLY allow installation from the (future) stock kernel! thats the only way to make sure that it will work.

-	'''<font color=red>any other thoughts are highly appreciated as this can cause complications....we have to be very careful as all guys who later use this installer have to TRUST us...if a box gets bricked ~~that~~ it is our fault.</font>'''	+	'''<font color=red>any other thoughts are highly appreciated as this can cause complications....we have to be very careful as all guys who later use this installer have to TRUST us...if a box gets bricked then it is our fault.</font>'''

	== How everything should work together ==		== How everything should work together ==
	[[Image:Design-updaters.jpg\|left\|701px]]		[[Image:Design-updaters.jpg\|left\|701px]]

193.170.75.199: /* UBOOT-INSTALLER */

193.170.75.199 — Thu, 05 Oct 2006 11:54:44 GMT

UBOOT-INSTALLER

← Older revision		Revision as of 11:54, 5 October 2006
Line 51:		Line 51:
	(2.4.33.3 for example) then there needs to be another check somehow....but i suppose there won`t be many out there...this is only possible if you use 2.4.33.3 via loader.o for some reason..2.6 is better		(2.4.33.3 for example) then there needs to be another check somehow....but i suppose there won`t be many out there...this is only possible if you use 2.4.33.3 via loader.o for some reason..2.6 is better

-	in my opinion it should ONLY allow installation from the stock kernel! thats the only way to make sure that it will work.	+	in my opinion it should ONLY allow installation from the (future) stock kernel! thats the only way to make sure that it will work.

	'''<font color=red>any other thoughts are highly appreciated as this can cause complications....we have to be very careful as all guys who later use this installer have to TRUST us...if a box gets bricked that it is our fault.</font>'''		'''<font color=red>any other thoughts are highly appreciated as this can cause complications....we have to be very careful as all guys who later use this installer have to TRUST us...if a box gets bricked that it is our fault.</font>'''

Mindbender: added the concept.

Mindbender — Thu, 05 Oct 2006 10:11:14 GMT

added the concept.

← Older revision		Revision as of 10:11, 5 October 2006
Line 54:		Line 54:

	'''<font color=red>any other thoughts are highly appreciated as this can cause complications....we have to be very careful as all guys who later use this installer have to TRUST us...if a box gets bricked that it is our fault.</font>'''		'''<font color=red>any other thoughts are highly appreciated as this can cause complications....we have to be very careful as all guys who later use this installer have to TRUST us...if a box gets bricked that it is our fault.</font>'''
		+
		+	== How everything should work together ==
		+	[[Image:Design-updaters.jpg\|left\|701px]]

193.170.75.213: /* FLASH-UPDATER */

193.170.75.213 — Thu, 05 Oct 2006 09:33:50 GMT

FLASH-UPDATER

← Older revision		Revision as of 09:33, 5 October 2006
Line 7:		Line 7:
	We need a telnet + ftp-enabled Ramdisk (EM Mode) like the Kuroboxes have. mindbender already created some for the LS1/LS HG/LS HS. These new firmimg.bins will most likely be bundled with the future openlink / freelink releases when they are ready for that.		We need a telnet + ftp-enabled Ramdisk (EM Mode) like the Kuroboxes have. mindbender already created some for the LS1/LS HG/LS HS. These new firmimg.bins will most likely be bundled with the future openlink / freelink releases when they are ready for that.

-	'''<font color=red>Status:</font>''' currently we only have 2.4.33.3 working for UBoot-images. the current kernels cannot be bundled with the standard releases as it would break the ability to use the buffalo firmware updater because there is no check for "OKOK" in flash of the LS1/HG anymore. either we have to integrate this check again especially for the standard releases who do not want to use UBoot or we have to use the stock firmware which does not allow to much (NFS for example)	+	'''<font color=red>Status:</font>''' currently we only have 2.4.33.3 working for UBoot-images. the current kernels cannot be bundled with the standard releases as it would break the ability to use the buffalo firmware updater because there is no check for "OKOK" in flash of the LS1/HG anymore. either we have to integrate this check again especially for the standard releases who do not want to use UBoot or we have to use the stock firmware which does not allow to much (NFS for example). mindbender plans to create a seperate 2.4.33.3 with included check for "OKOK" in flash.

	=== HDDROOTFS-UPDATER ===		=== HDDROOTFS-UPDATER ===

193.170.75.213: /* HDDROOTFS-UPDATER */

193.170.75.213 — Thu, 05 Oct 2006 09:32:29 GMT

HDDROOTFS-UPDATER

← Older revision		Revision as of 09:32, 5 October 2006
Line 32:		Line 32:
	manually via executing write_ok (on stock bootloader boxes) or with UBoot simply by rebooting to the HDD.<br>		manually via executing write_ok (on stock bootloader boxes) or with UBoot simply by rebooting to the HDD.<br>

-	'''<font color=red>Status:</font>''' ~~mindbender plans to create a java app which automates 2 - 5..~~.he ~~chose java because~~ it is ~~platformindependent~~. ~~if someone knows a better way (''language?'') post your comments~~. ~~help IS needed~~. ~~maybe~~ it is ~~easier to automate all this with '''~~.~~NET'''~~ and ~~leave Linux/apple users with wiki instructions..~~.~~installing manually works~~ the same ~~way as~~ on the ~~kuroboxes~~...~~it depends on~~ the ~~help mindbender gets~~.	+	'''<font color=red>Status:</font>''' waite from kurobox.com pointed out that he already has coded an automatic installer for the kuroboxes. it is python based...so it is also platform independent. mindbender tested the base python script and his Linkstation was found. as the current telnet + ftp-enabled flash-images have the same functionallity (except included fdisk + mount-script for /dev/hda1 + /dev/hda3) it will work on the Linkstations also. good stuff because it already is coded. there might be some minor changes needed (for example the linkstation firmimg.bins do not request for a password) but they can be done in the short run.
		+
		+	http://www.kurobox.com/mwiki/index.php/Kuro_Auto_Installer

	== UBOOT-INSTALLER ==		== UBOOT-INSTALLER ==