Documentation/Maemo 5 Developer Guide/Development Environment/Maemo Flasher-3.5 - Revision history

203.188.107.64: Emphasize broken link

2016-02-03T03:36:19Z

Emphasize broken link

← Older revision		Revision as of 03:36, 3 February 2016
Line 1:		Line 1:
	The Maemo Flasher-3.5 tool is used to flash data to the Maemo device internal 256 MB of NAND, which is where the bootloader, kernel, and rootfs (all of which make up the operating system) are stored. For N900 it is also used to format and flash the eMMC internal storage card (32GB). Flasher-3.5 can be used to upgrade to a new firmware, wipe the Maemo device and start from scratch, flash certain specific components, or change a number of hardware flags. It also can load and start a kernel and auxiliary system to RAM, e.g for recovery purposes, see [http://wiki.meego.com/ARM/N900/Using_Rescue_Initrd]		The Maemo Flasher-3.5 tool is used to flash data to the Maemo device internal 256 MB of NAND, which is where the bootloader, kernel, and rootfs (all of which make up the operating system) are stored. For N900 it is also used to format and flash the eMMC internal storage card (32GB). Flasher-3.5 can be used to upgrade to a new firmware, wipe the Maemo device and start from scratch, flash certain specific components, or change a number of hardware flags. It also can load and start a kernel and auxiliary system to RAM, e.g for recovery purposes, see [http://wiki.meego.com/ARM/N900/Using_Rescue_Initrd]

	Maemo Flasher-3.5 Tools ~~can~~ be downloaded from the [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php Maemo Development Environment Downloads] page.		Maemo Flasher-3.5 Tools could be downloaded from the [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php Maemo Development Environment Downloads] page in the past.

	== Release details ==		== Release details ==

86.2.102.56: /* Flasher-3.5 usage examples */

2015-01-31T18:34:12Z

Flasher-3.5 usage examples

← Older revision		Revision as of 18:34, 31 January 2015
Line 160:		Line 160:
	To enable R&D mode for Maemo device, run:		To enable R&D mode for Maemo device, run:

	$ flasher-3.5 –-enable-rd-mode		$ flasher-3.5 --enable-rd-mode

	To warm flash an image to the Maemo device, run:		To warm flash an image to the Maemo device, run:

imported_>stefanl: /* Tips & troubleshooting */

2012-07-28T15:14:25Z

Tips & troubleshooting

← Older revision		Revision as of 15:14, 28 July 2012
Line 196:		Line 196:
	== Tips & troubleshooting ==		== Tips & troubleshooting ==

	* It appears that Windows 7 64 bit doesn't handle USB in the same manner, and this causes problems (http://talk.maemo.org/showpost.php?p=489976&postcount=4). Workaround by using another PC, or creating a virtual machine of the appropriate type (http://talk.maemo.org/showpost.php?p=490152&postcount=5).		* It appears that Windows 7 64 bit doesn't handle USB in the same manner, and this causes problems (http://talk.maemo.org/showpost.php?p=489976&postcount=4). Workaround by using another PC, or creating a virtual machine of the appropriate type (http://talk.maemo.org/showpost.php?p=490152&postcount=5). There is a fix that works for Windows7 (works on 64bit) here: http://talk.maemo.org/showpost.php?p=849980&postcount=20.
	* If you get a "Permission denied" error, then make sure you have execution rights to the Flasher-3.5 binary executable.		* If you get a "Permission denied" error, then make sure you have execution rights to the Flasher-3.5 binary executable.
	* You need to have administrator rights or run command with sudo in Linux if you get errors like this: ''Error claiming USB interface: Operation not permitted''		* You need to have administrator rights or run command with sudo in Linux if you get errors like this: ''Error claiming USB interface: Operation not permitted''

imported_>andre: Reverted edits by 188.167.43.219 (Talk); changed back to last version by Joerg rw

2012-05-17T09:14:37Z

Reverted edits by 188.167.43.219 (Talk); changed back to last version by Joerg rw

← Older revision		Revision as of 09:14, 17 May 2012
Line 225:		Line 225:
	*** export LD_LIBRARY_PATH=/opt/libusb/lib		*** export LD_LIBRARY_PATH=/opt/libusb/lib
	*** flasher-3.5 ...		*** flasher-3.5 ...
	* On Windows host PC if Nokia PC Suite has been installed to the environment once Windows has started also PC Suite starts running. If Nokia PC Suite is running when N900 is plugged in to the PC with USB cable and with the u key ~~hold~~ down, Nokia PC Suite gives an error message and Flasher-3.5 does not see the device.		* On Windows host PC if Nokia PC Suite has been installed to the environment once Windows has started also PC Suite starts running. If Nokia PC Suite is running when N900 is plugged in to the PC with USB cable and with the u key held down, Nokia PC Suite gives an error message and Flasher-3.5 does not see the device.
	** workaround is to exit Nokia PC Suite before plugging in N900 with USB cable and starting Flasher-3.5		** workaround is to exit Nokia PC Suite before plugging in N900 with USB cable and starting Flasher-3.5

188.167.43.219: /* Known issues */

2012-05-17T08:29:11Z

Known issues

← Older revision		Revision as of 08:29, 17 May 2012
Line 225:		Line 225:
	*** export LD_LIBRARY_PATH=/opt/libusb/lib		*** export LD_LIBRARY_PATH=/opt/libusb/lib
	*** flasher-3.5 ...		*** flasher-3.5 ...
	* On Windows host PC if Nokia PC Suite has been installed to the environment once Windows has started also PC Suite starts running. If Nokia PC Suite is running when N900 is plugged in to the PC with USB cable and with the u key ~~held~~ down, Nokia PC Suite gives an error message and Flasher-3.5 does not see the device.		* On Windows host PC if Nokia PC Suite has been installed to the environment once Windows has started also PC Suite starts running. If Nokia PC Suite is running when N900 is plugged in to the PC with USB cable and with the u key hold down, Nokia PC Suite gives an error message and Flasher-3.5 does not see the device.
	** workaround is to exit Nokia PC Suite before plugging in N900 with USB cable and starting Flasher-3.5		** workaround is to exit Nokia PC Suite before plugging in N900 with USB cable and starting Flasher-3.5

imported_>joerg_rw: Undo revision 45642 by 216.149.195.4 (Talk) vandalism

2011-10-31T04:23:17Z

Undo revision 45642 by 216.149.195.4 (Talk) vandalism

@@ Line 83: / Line 83: @@
 {{ambox|text=Never flash/reflash the eMMC content after you bootup the N900 device with new FIASCO image because all the optified content that gets automatically moved from rootfs to eMMC during first device bootup will be lost.}}
-Heck yeah this is eaxtcly what I needed.
+=== Setting Maemo device to flashing mode ===
 === Command line options ===

216.149.195.4: /* Setting Maemo device to flashing mode */

2011-10-31T04:17:03Z

Setting Maemo device to flashing mode

@@ Line 83: / Line 83: @@
 {{ambox|text=Never flash/reflash the eMMC content after you bootup the N900 device with new FIASCO image because all the optified content that gets automatically moved from rootfs to eMMC during first device bootup will be lost.}}
-=== Setting Maemo device to flashing mode ===
+Heck yeah this is eaxtcly what I needed.
 === Command line options ===

imported_>joerg_rw: /* N900 flasher */ SSU

2011-06-06T05:18:37Z

N900 flasher: SSU

← Older revision		Revision as of 05:18, 6 June 2011
Line 230:		Line 230:
	== N900 flasher ==		== N900 flasher ==

	The same tool is located on N900 itself under name "flasher" (<code>/usr/bin/flasher</code>) and can be used for changing R&D mode, etc. Package name is [http://maemo.org/packages/view/flasher/ flasher].		The same tool is located on N900 itself under name "flasher" (<code>/usr/bin/flasher</code>) and can be used for changing R&D mode, etc.
			SSU also is using this local flasher, to update kernels. Package name is [http://maemo.org/packages/view/flasher/ flasher].

	[[Category:Development]]		[[Category:Development]]

imported_>joerg_rw: /* Tips & troubleshooting */ do not coldflash

2011-06-06T05:12:05Z

Tips & troubleshooting: do not coldflash

← Older revision		Revision as of 05:12, 6 June 2011
Line 202:		Line 202:
	* Flash always the FIASCO image first and after that immediately the latest available eMMC image, if needed. '''Never flash/reflash the eMMC content after you bootup the device.''' Reason: All the optified content that is moved from rootfs to eMMC will be lost. The eMMC image does not need to be flashed every time when a new FIASCO image is flashed. Flashing the eMMC image also overwrites all data from the internal memory card. (Notice this recommendation has changed to eMMC first, then powerdown and flash rootfs. Rationale: a system will recover from accidental boots this way. If user is confident about avoiding intermediate boot, the original sequence works as well and is more convenient)		* Flash always the FIASCO image first and after that immediately the latest available eMMC image, if needed. '''Never flash/reflash the eMMC content after you bootup the device.''' Reason: All the optified content that is moved from rootfs to eMMC will be lost. The eMMC image does not need to be flashed every time when a new FIASCO image is flashed. Flashing the eMMC image also overwrites all data from the internal memory card. (Notice this recommendation has changed to eMMC first, then powerdown and flash rootfs. Rationale: a system will recover from accidental boots this way. If user is confident about avoiding intermediate boot, the original sequence works as well and is more convenient)
	* If warm flashing fails, try to switch off the power from the Maemo device, remove the USB cable and try again from the beginning.		* If warm flashing fails, try to switch off the power from the Maemo device, remove the USB cable and try again from the beginning.
	* If cold flashing fails, try to warm flash the Maemo device first using the same FIASCO image. After that try cold flashing again.		* If cold flashing fails, try to warm flash the Maemo device first using the same FIASCO image. After that try cold flashing again. NB cold flashing is rarely ever needed and not recommended for end users. It's meant only to recover from a defect or outdated NOLO bootloader.
	* If Flasher-3.5 is not supported on your operating system you can try to install Maemo SDK Virtual Image from [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php Maemo Development Environment Downloads] page and flash Maemo device from Virtual Image (which includes Ubuntu). This may or may not work for you depending on how well virtualization technology you use supports USB on your HW.		* If Flasher-3.5 is not supported on your operating system you can try to install Maemo SDK Virtual Image from [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php Maemo Development Environment Downloads] page and flash Maemo device from Virtual Image (which includes Ubuntu). This may or may not work for you depending on how well virtualization technology you use supports USB on your HW.
	* If you use 64-bit Linux, Flasher may work on it.		* If you use 64-bit Linux, Flasher may work on it.

imported_>joerg_rw: /* Tips & troubleshooting */ emmc/rootfs sequence

2011-06-06T05:07:22Z

Tips & troubleshooting: emmc/rootfs sequence

← Older revision		Revision as of 05:07, 6 June 2011
Line 200:		Line 200:
	* You need to have administrator rights or run command with sudo in Linux if you get errors like this: ''Error claiming USB interface: Operation not permitted''		* You need to have administrator rights or run command with sudo in Linux if you get errors like this: ''Error claiming USB interface: Operation not permitted''
	* It may help to connect the USB cable directly to the computer USB ports, avoiding the use of a hub. Using the USB ports in the back of a computer can also work better than using those in the front.		* It may help to connect the USB cable directly to the computer USB ports, avoiding the use of a hub. Using the USB ports in the back of a computer can also work better than using those in the front.
	* Flash always the FIASCO image first and after that immediately the latest available eMMC image, if needed. '''Never flash/reflash the eMMC content after you bootup the device.''' Reason: All the optified content that is moved from rootfs to eMMC will be lost. The eMMC image does not need to be flashed every time when a new FIASCO image is flashed. Flashing the eMMC image also overwrites all data from the internal memory card. (Notice this recommendation has changed to ~~rootfs~~ first, then ~~eMMC~~. ~~Except for Nokia's download page~~, ~~where~~ the ~~comment~~ is ~~still wrong on that~~)		* Flash always the FIASCO image first and after that immediately the latest available eMMC image, if needed. '''Never flash/reflash the eMMC content after you bootup the device.''' Reason: All the optified content that is moved from rootfs to eMMC will be lost. The eMMC image does not need to be flashed every time when a new FIASCO image is flashed. Flashing the eMMC image also overwrites all data from the internal memory card. (Notice this recommendation has changed to eMMC first, then powerdown and flash rootfs. Rationale: a system will recover from accidental boots this way. If user is confident about avoiding intermediate boot, the original sequence works as well and is more convenient)
	* If warm flashing fails, try to switch off the power from the Maemo device, remove the USB cable and try again from the beginning.		* If warm flashing fails, try to switch off the power from the Maemo device, remove the USB cable and try again from the beginning.
	* If cold flashing fails, try to warm flash the Maemo device first using the same FIASCO image. After that try cold flashing again.		* If cold flashing fails, try to warm flash the Maemo device first using the same FIASCO image. After that try cold flashing again.