Flashing the Neo 1973 - Revision history

Glenn: Exchg bootloader with U-Boot

2012-02-10T08:35:18Z

Exchg bootloader with U-Boot

Elishy: /* Actually flashing things into the device */

2011-10-12T02:22:16Z

‎Actually flashing things into the device

Glenn: topsort (again)

2010-03-04T20:34:44Z

topsort (again)

Glenn: wiki

2010-03-04T20:33:24Z

wiki

Marko Knöbl: /* Files to download */ removing outdated link

2009-12-09T13:19:04Z

‎Files to download: removing outdated link

Salahx: Update URL

2009-05-01T17:24:25Z

Update URL

Coolcat at 04:52, 13 February 2009

2009-02-13T04:52:50Z

Coolcat at 11:21, 19 November 2008

2008-11-19T11:21:18Z

Phobie: linkfix

2008-10-22T14:33:35Z

linkfix

Phobie: linkfix

2008-10-22T14:33:00Z

linkfix

@@ Line 12: / Line 12: @@
 {{warning|If you're updating u-boot and don't have a [[Debug Board]], you might render your unit unusable if the flashing procedure is interrupted}}
-{{warning|If you have U-boot from before 2008 and upload a rootfs image that is smaller than the previous one, or if you have written to the rootfs, just flashing may not work - you may need to run a "[[Nand_erase|nand erase rootfs]]" before you then upload your rootfs (details  [[Bootloader#Accessing_the_bootloader_prompt|here]]). Running "nand erase rootfs" before flashing a new rootfs, is quick and saves you the time of a second rootfs upload. <b>Attention:</b> If you [[Nand_erase|erase NAND]] without mentioning the partition to be erased, u-boot will be wiped out and the Neo will be bricked}}
+{{warning|If you have U-boot from before 2008 and upload a rootfs image that is smaller than the previous one, or if you have written to the rootfs, just flashing may not work - you may need to run a "[[Nand_erase|nand erase rootfs]]" before you then upload your rootfs (details  [[U-Boot#Accessing_the_bootloader_prompt|here]]). Running "nand erase rootfs" before flashing a new rootfs, is quick and saves you the time of a second rootfs upload. <b>Attention:</b> If you [[Nand_erase|erase NAND]] without mentioning the partition to be erased, u-boot will be wiped out and the Neo will be bricked}}
 == Files to download ==
@@ Line 63: / Line 63: @@
 * Plug Neo1973 into host with supplied USB cable. (Plug the phone directly into the host not via a hub.)
-'''Note:''' If the bootloader remains inactive for about 30 seconds, that is no keypresses or no use of the serial console, the device will automatically power down.
+'''Note:''' If the U-Boot remains inactive for about 30 seconds, that is no keypresses or no use of the serial console, the device will automatically power down.
-You can prevent this by just pressing the AUX button every 30 seconds or so or by telling the bootloader to not exhibit this behaviour.
+You can prevent this by just pressing the AUX button every 30 seconds or so or by telling the U-Boot to not exhibit this behaviour.
-To do so, please connect to the bootloader:
+To do so, please connect to the U-Boot bootloader:
 <pre>
@@ Line 80: / Line 80: @@
 == Actually flashing things into the device ==
-Double check that u-boot matches your hardware version. First determine what hardware revision you have [[finding hardware revision]], so that you can download and install the correct bootloader.
+Double check that u-boot matches your hardware version. First determine what hardware revision you have [[finding hardware revision]], so that you can download and install the correct U-Boot.
 You'll probably only want to update u-boot if you have the [[debug board]] for fixing failed u-boot updates. You can also check the current [[Neo 1973 Partitions|partitions]].
@@ Line 144: / Line 144: @@
 Some old U-Boot versions are very buggy:
-For U-Boot versions until somewhere in 2007 if you uploaded your rootfs image that is smaller that previous one it wouldn't work - you needed to attach to the u-boot bootloader first, erase NAND partition that would contain the rootfs later and then upload your rootfs:
+For U-Boot versions until somewhere in 2007 if you uploaded your rootfs image that is smaller that previous one it wouldn't work - you needed to attach to the U-Boot bootloader first, erase NAND partition that would contain the rootfs later and then upload your rootfs:
 <pre>
@@ Line 188: / Line 188: @@
 Lost device after RESET?</pre> just retry the command - it should work on a second run.
-This message can also occur if you connect the usb cable before you are in the bootloader menu.  You must carefully follow the sequence described at the beginning of this article and not connect the USB cable too early.
+This message can also occur if you connect the usb cable before you are in the U-Boot menu.  You must carefully follow the sequence described at the beginning of this article and not connect the USB cable too early.
 dfu-util does not seem to be able to download files if run from linux running under

@@ Line 92: / Line 92: @@
 {{Warning|Do not update u-boot unless you have [[debug board]] or are really sure about what you are doing. Flashing a wrong u-boot image will brick your device!}}
-I you own a FreeRunner don't be too scared, though: Unlike nearly any other device on the market the FreeRunner contains a second bootloader on a write protected chip - that is still there, even if flashing the original bootloader goes horribly wrong. You can always make the phone use this bootloader instead by pressing the power button whilst pressing the Aux button - and get a second and any successive try to flash the u-boot loader the right way. In theory it should therefore be impossible to brick your phone completely enough by flashing the bootloader that a debug board is needed to unbrick it.
+If you own a FreeRunner don't be too scared, though: Unlike nearly any other device on the market the FreeRunner contains a second bootloader on a write protected chip - that is still there, even if flashing the original bootloader goes horribly wrong. You can always make the phone use this bootloader instead by pressing the power button whilst pressing the Aux button - and get a second and any successive try to flash the u-boot loader the right way. In theory it should therefore be impossible to brick your phone completely enough by flashing the bootloader that a debug board is needed to unbrick it.
 * Download the newest u-boot binary from http://downloads.openmoko.org/distro/releases/Om2008.12
 * start the cellular phone by pressing power whilst pressing the aux button.

← Older revision		Revision as of 20:34, 4 March 2010
Line 199:		Line 199:
	DFUScript developed to assist users who have multiple devices in using dfu-util via the command line. Information on where to download and use DFUScript can be found on [[DFUScript]]		DFUScript developed to assist users who have multiple devices in using dfu-util via the command line. Information on where to download and use DFUScript can be found on [[DFUScript]]

−	[[Category:Flashing Openmoko]]	+	[[Category:Flashing Openmoko\| ]]

← Older revision		Revision as of 20:33, 4 March 2010
Line 199:		Line 199:
	DFUScript developed to assist users who have multiple devices in using dfu-util via the command line. Information on where to download and use DFUScript can be found on [[DFUScript]]		DFUScript developed to assist users who have multiple devices in using dfu-util via the command line. Information on where to download and use DFUScript can be found on [[DFUScript]]

−	[[Category:~~Flashing Openmoko\|~~Flashing Openmoko]]	+	[[Category:Flashing Openmoko]]

@@ Line 20: / Line 20: @@
 The "moko123" in the error message example above indicates the openmoko patchset version.
-A list of download locations can be found at [[Downloads]]. See [[Phase 1 Software Testing]] for a list of tested images.
+A list of download locations can be found at [[Download]].
-−
 Changelogs can be found at:

@@ Line 94: / Line 94: @@
 I you own a FreeRunner don't be too scared, though: Unlike nearly any other device on the market the FreeRunner contains a second bootloader on a write protected chip - that is still there, even if flashing the original bootloader goes horribly wrong. You can always make the phone use this bootloader instead by pressing the power button whilst pressing the Aux button - and get a second and any successive try to flash the u-boot loader the right way. In theory it should therefore be impossible to brick your phone completely enough by flashing the bootloader that a debug board is needed to unbrick it.
-* Download the newest u-boot binary from http://downloads.openmoko.org/releases/2008.9/
+* Download the newest u-boot binary from http://downloads.openmoko.org/distro/releases/2008.9/
 * start the cellular phone by pressing power whilst pressing the aux button.
 * Run the following command, but Note especially that the image used in the line below is for GTA02_v5.

@@ Line 16: / Line 16: @@
 == Files to download ==
-The rootfs & kernel images you download need to match. The loadable modules for the kernel are in /lib/modules/ on the rootfs [[partition]] - if you get the wrong combination, you will get some error messages during bootup that it cannot access /lib/modules/x.y.z-moko123 - in this case swap either the kernel or the rootfs to match the other's version. Unfortunately the rootfs filename does not seem to tell what kernel version it is compatible with, you just have to try a few. '''NOTE:''' At least some combinations seem to boot up fine even if the module versions mismatch so be sure to check the console while it's booting after flashing.
+The rootfs & kernel images you download need to match. The loadable modules for the kernel are in /lib/modules/ on the rootfs [[Neo 1973 Partitions|partition]] - if you get the wrong combination, you will get some error messages during bootup that it cannot access /lib/modules/x.y.z-moko123 - in this case swap either the kernel or the rootfs to match the other's version. Unfortunately the rootfs filename does not seem to tell what kernel version it is compatible with, you just have to try a few. '''NOTE:''' At least some combinations seem to boot up fine even if the module versions mismatch so be sure to check the console while it's booting after flashing.
 The "moko123" in the error message example above indicates the openmoko patchset version.
@@ Line 83: / Line 83: @@
 Double check that u-boot matches your hardware version. First determine what hardware revision you have [[finding hardware revision]], so that you can download and install the correct bootloader.
-You'll probably only want to update u-boot if you have the [[debug board]] for fixing failed u-boot updates. You can also check the current [[partitions]].
+You'll probably only want to update u-boot if you have the [[debug board]] for fixing failed u-boot updates. You can also check the current [[Neo 1973 Partitions|partitions]].
 Note: It may be necessary to run the application as root (at least in Ubuntu and Debian).

@@ Line 1: / Line 1: @@
 {{Languages|Flashing the Neo 1973}}
-This describes how to update your Neo1973 to the latest software. We'll update the kernel, the root filesystem and optionally u-boot [[partitions]] in the internal flash memory.
+This describes how to update your Neo1973 to the latest software. We'll update the kernel, the root filesystem and optionally u-boot [[Neo 1973 Partitions|partitions]] in the internal flash memory.
 {{Note|