Reflash.php - Revision history

Polto at 08:18, 22 April 2009

2009-04-22T08:18:19Z

← Older revision		Revision as of 08:18, 22 April 2009
Line 1:		Line 1:
	This script allows initiating camera firmware update from the NFS server. It allows to specify NFS server IP/directory in the GET request as well as the script name. Script uses default values if the parameters ("NFS=" and "SCRIPT=") are not specified.		This script allows initiating camera firmware update from the NFS server. It allows to specify NFS server IP/directory in the GET request as well as the script name. Script uses default values if the parameters ("NFS=" and "SCRIPT=") are not specified.
	Here are the usage examples:		Here are the usage examples:
	<nowiki>http://192.168.0.9~~:81~~/reflash.php</nowiki>		<nowiki>http://192.168.0.9/reflash.php</nowiki>
	<nowiki>http://192.168.0.9~~:81~~/reflash.php?NFS=192.168.0.15:/nfs/~~elphel353-2.10~~/</nowiki>		<nowiki>http://192.168.0.9/reflash.php?NFS=192.168.0.15:/nfs/latest80/</nowiki>
	<nowiki>http://192.168.0.9~~:81~~/reflash.php?NFS=192.168.0.15:/nfs/~~elphel353-2.10~~/&SCRIPT=nfs_update</nowiki>		<nowiki>http://192.168.0.9/reflash.php?NFS=192.168.0.15:/nfs/latest80/&SCRIPT=nfs_update</nowiki>
	They all do the same as the parameters specified are exactly the same as defaults.		They all do the same as the parameters specified are exactly the same as defaults.
	The script returns XML response with error message or status OK if it went as far as starting remote script on NFS server. After that response camera normally (while executing the default nfs_update script) shuts down web server, writes to flash memory and reboots. It is possible to watch the progress by monitoring log and lock files in the NFS directory on the server (both file names include MAC address/camera serial number). Log file is appended, lock one is created during reflash process and deleted when the software update procedure is finished.		The script returns XML response with error message or status OK if it went as far as starting remote script on NFS server. After that response camera normally (while executing the default nfs_update script) shuts down web server, writes to flash memory and reboots. It is possible to watch the progress by monitoring log and lock files in the NFS directory on the server (both file names include MAC address/camera serial number). Log file is appended, lock one is created during reflash process and deleted when the software update procedure is finished.

	It is possible to provide a name of a different remote script instead of the nfs_update - i.e the one that will just update some files (with/without reboot), not all the flash memory.		It is possible to provide a name of a different remote script instead of the nfs_update - i.e the one that will just update some files (with/without reboot), not all the flash memory.


	~~----~~
	~~Note: this script can't work from the default http port (80) - so be careful with URL for the web request.~~
	~~Update: New version of the reflash.php verifies it is run through the correct server.--[[User:Andrey.filippov\|Andrey.filippov]] 19:39, 19 November 2007 (CST)~~

Andrey.filippov at 01:32, 21 November 2007

2007-11-21T01:32:28Z

← Older revision		Revision as of 01:32, 21 November 2007
Line 1:		Line 1:
	This script allows initiating camera firmware update from the NFS server. It allows to specify NFS server IP/directory in the GET request as well as the script name. Script uses default values if the parameters ("NFS=" and "SCRIPT=") are not specified.		This script allows initiating camera firmware update from the NFS server. It allows to specify NFS server IP/directory in the GET request as well as the script name. Script uses default values if the parameters ("NFS=" and "SCRIPT=") are not specified.
	Here are the usage examples:		Here are the usage examples:
	<nowiki>http://192.168.0.9:81~~/var~~/reflash.php</nowiki>		<nowiki>http://192.168.0.9:81/reflash.php</nowiki>
	<nowiki>http://192.168.0.9:81~~/var~~/reflash.php?NFS=192.168.0.15:/nfs/elphel353-2.10/</nowiki>		<nowiki>http://192.168.0.9:81/reflash.php?NFS=192.168.0.15:/nfs/elphel353-2.10/</nowiki>
	<nowiki>http://192.168.0.9:81~~/var~~/reflash.php?NFS=192.168.0.15:/nfs/elphel353-2.10/&SCRIPT=nfs_update</nowiki>		<nowiki>http://192.168.0.9:81/reflash.php?NFS=192.168.0.15:/nfs/elphel353-2.10/&SCRIPT=nfs_update</nowiki>
	They all do the same as the parameters specified are exactly the same as defaults.		They all do the same as the parameters specified are exactly the same as defaults.
	The script returns XML response with error message or status OK if it went as far as starting remote script on NFS server. After that response camera normally (while executing the default nfs_update script) shuts down web server, writes to flash memory and reboots. It is possible to watch the progress by monitoring log and lock files in the NFS directory on the server (both file names include MAC address/camera serial number). Log file is appended, lock one is created during reflash process and deleted when the software update procedure is finished.		The script returns XML response with error message or status OK if it went as far as starting remote script on NFS server. After that response camera normally (while executing the default nfs_update script) shuts down web server, writes to flash memory and reboots. It is possible to watch the progress by monitoring log and lock files in the NFS directory on the server (both file names include MAC address/camera serial number). Log file is appended, lock one is created during reflash process and deleted when the software update procedure is finished.

Andrey.filippov at 01:39, 20 November 2007

2007-11-20T01:39:46Z

← Older revision		Revision as of 01:39, 20 November 2007
Line 12:		Line 12:
	----		----
	Note: this script can't work from the default http port (80) - so be careful with URL for the web request.		Note: this script can't work from the default http port (80) - so be careful with URL for the web request.
			Update: New version of the reflash.php verifies it is run through the correct server.--[[User:Andrey.filippov\|Andrey.filippov]] 19:39, 19 November 2007 (CST)

Spectr at 20:55, 19 November 2007

2007-11-19T20:55:41Z

← Older revision		Revision as of 20:55, 19 November 2007
Line 8:		Line 8:

	It is possible to provide a name of a different remote script instead of the nfs_update - i.e the one that will just update some files (with/without reboot), not all the flash memory.		It is possible to provide a name of a different remote script instead of the nfs_update - i.e the one that will just update some files (with/without reboot), not all the flash memory.


			----
			Note: this script can't work from the default http port (80) - so be careful with URL for the web request.

Andrey.filippov at 06:51, 8 November 2007

2007-11-08T06:51:07Z

← Older revision		Revision as of 06:51, 8 November 2007
Line 1:		Line 1:
	This script allows initiating camera firmware update from the NFS server. It allows to specify NFS server IP/directory in the GET request as well as the script name. Script uses default values if the parameters ("NFS=" and "SCRIPT=") are not specified.		This script allows initiating camera firmware update from the NFS server. It allows to specify NFS server IP/directory in the GET request as well as the script name. Script uses default values if the parameters ("NFS=" and "SCRIPT=") are not specified.
	Here are the usage examples:		Here are the usage examples:
	http://192.168.0.9:81/var/reflash.php?		<nowiki>http://192.168.0.9:81/var/reflash.php</nowiki>
	http://192.168.0.9:81/var/reflash.php?NFS=192.168.0.15:/nfs/elphel353-2.10/		<nowiki>http://192.168.0.9:81/var/reflash.php?NFS=192.168.0.15:/nfs/elphel353-2.10/</nowiki>
	http://192.168.0.9:81/var/reflash.php?NFS=192.168.0.15:/nfs/elphel353-2.10/&SCRIPT=nfs_update		<nowiki>http://192.168.0.9:81/var/reflash.php?NFS=192.168.0.15:/nfs/elphel353-2.10/&SCRIPT=nfs_update</nowiki>
	They all do the same as the parameters specified are exactly the same as defaults.		They all do the same as the parameters specified are exactly the same as defaults.
	The script		The script returns XML response with error message or status OK if it went as far as starting remote script on NFS server. After that response camera normally (while executing the default nfs_update script) shuts down web server, writes to flash memory and reboots. It is possible to watch the progress by monitoring log and lock files in the NFS directory on the server (both file names include MAC address/camera serial number). Log file is appended, lock one is created during reflash process and deleted when the software update procedure is finished.

			It is possible to provide a name of a different remote script instead of the nfs_update - i.e the one that will just update some files (with/without reboot), not all the flash memory.

Andrey.filippov at 06:39, 8 November 2007

2007-11-08T06:39:48Z

New page

This script allows initiating camera firmware update from the NFS server. It allows to specify NFS server IP/directory in the GET request as well as the script name. Script uses default values if the parameters ("NFS=" and "SCRIPT=") are not specified.
Here are the usage examples:
http://192.168.0.9:81/var/reflash.php?
http://192.168.0.9:81/var/reflash.php?NFS=192.168.0.15:/nfs/elphel353-2.10/
http://192.168.0.9:81/var/reflash.php?NFS=192.168.0.15:/nfs/elphel353-2.10/&SCRIPT=nfs_update
They all do the same as the parameters specified are exactly the same as defaults.
The script