Flashing the Neo 1973

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(Files to download)
m
Line 3: Line 3:
 
{{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'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 upload rootfs image that is smaller that previous one it won't work - you need to attach to bootloader, erase NAND and then upload your rootfs first}}
+
{{warning|If you upload rootfs image that is smaller that previous one it won't work - you need to attach to bootloader, [[Nand_erase|erase NAND]] and then upload your rootfs first}}
  
 
== Files to download ==
 
== Files to download ==

Revision as of 10:23, 21 August 2007

This describes how to update your openmoko to the latest software. We'll update the kernel, the root filesystem and optionally u-boot.

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 upload rootfs image that is smaller that previous one it won't work - you need to attach to bootloader, erase NAND and then upload your rootfs first


Contents

Files to download

MacOS X users: please refer to MacOS_X. Users without Linux please refer to No_Linux for the moment.

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 "moko123" in the error message example above indicates the openmoko patchset version.

Necessary files are at:

A list of download locations can be found at Repositories. See Phase 1 Software Testing for a list of tested images.

Get:

  • dfu-util (the precompiled binary on http://buildhost.openmoko.org is for Linux/i386)
    • (this is the part that runs on the PC, that pushes the files across the USB to the phone)
  • openmoko-devel-image-fic-gta01-2007********.rootfs.jffs2
  • uImage-2.6.21.*-moko*-r*_0_****_0-fic-gta01.bin
  • for phase 0 (Bv03) phones:
    • Tested by a few people:
      u-boot-gta01bv3-r8_70124c2602ae2d4c5d3dba05b482d91548242de8_0_2040.bin
      MD5SUM: 60c5aeba1bd6642b05b3a5e6f2dafe83
    • Tested by hrw:
      u-boot-gta01bv3-r8_70124c2602ae2d4c5d3dba05b482d91548242de8_0_2062.bin
      MD5SUM: 716f1eba9b0f2be4a0a3be4a56724935
  • for phase 1 phones, uboot update should not be necessary.

Preparing the device for DFU mode

You'll need to boot your openmoko into uboot menu. To do this:

  • Unplug all usb devices from the host.
  • Hold Neo1973 AUX Button while pressing POWER button.
  • The uboot menu should appear.
  • Plug Neo1973 into host with supplied USB cable. (Plug the phone directly into the host not via a hub.)

Note: Some devices have been reported to turn off after a short period of inactivity while on the uboot menu. To avoid this, simply press the AUX button every 30 seconds or so.

No further navigation is needed in u-boot - the device will automatically start flashing the images when told to do so by dfu-util below. After flashing all the files, you can choose the "Boot" option to boot the newly flashed stuff.

Actually flashing things into the device

Double check that u-boot matches your hardware version. Flashing u-boot is really a critical part. You probably only want to do that on phase0 phones.

Note: It may be necessary to run the application as root (at least in ubuntu).

Note: Option -a also accepts symbolic names ("u-boot", "u-boot_env", "kernel", "splash", "rootfs")

Note: In case there are more than one available usb devices use -d 0x1457:0x5119 option.

To update u-boot:

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! Note especially that image below is for GTA01B_v03, not GTA01B_v04

./dfu-util -a 1 -R -D u-boot-gta01bv3-r8_70124c2602ae2d4c5d3dba05b482d91548242de8_0_2040.bin

To update the kernel:

./dfu-util -a 3 -R -D ./uImage-2.6.21.1-moko10-r0_0_1883_0-fic-gta01.bin

To update the root filesystem:

./dfu-util -a 5 -R -D ./openmoko-devel-image-fic-gta01-20070501054014.rootfs.jffs2

Notice that it's not normally needed to update the modules anymore. It's just for people with special needs. ...now, you'll end up with system that boots, but does not see audio/SD card. You'll need to download corresponding modules.tgz and copy them over to openmoko. - UPDATE: GTA01 phones appear to not need this step, as long as you have installed a kernel that matches the version of the modules contained in the root image ('uname -r' will show the kernel version, and 'ls /lib/modules/' will show the modules that are present).

VERY IMPORTANT NOTE (I would consider that as a design flaw - either dfu-util should do it automatically): If you upload rootfs image that is smaller that previous one it won't work - you need to attach to bootloader, erase NAND and then upload your rootfs first:

cu -l /dev/ttyACM0
GTA01Bv3 # nand erase rootfs

Old versions of uboot are buggy: You may have to press the aux button few times so that machine does not sleep while flashing. It also does not erase rootfs before flashing it... to do that, do minicom /dev/ttyACM0, then nand erase clean rootfs . Unfortunately, old versions of uboot are not really usable, because they fail to enable high 64MB of RAM, and you get nasty crashes after kernel boots.


Good luck!

Troubleshooting notes

If you're facing errors in seemingly random places during the flashing of images, most likely the USB hub or cable through which your Neo1973 is connected is of too poor quality. It is recommended that you always connect the phone directly to the host when using dfu-util.

If dfu-util reports a message like the following, before it starts flashing:
Resetting USB...
not at least 2 device changes found ?!?
Lost device after RESET?
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.

dfu-util does not seem to be able to download files if run from linux running under VMWare on a Windows OS host.

See other notes on Dfu-util page.

Personal tools

This describes how to update your openmoko to the latest software. We'll update the kernel, the root filesystem and optionally u-boot.

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 upload rootfs image that is smaller that previous one it won't work - you need to attach to bootloader, erase NAND and then upload your rootfs first


Files to download

MacOS X users: please refer to MacOS_X. Users without Linux please refer to No_Linux for the moment.

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 "moko123" in the error message example above indicates the openmoko patchset version.

Necessary files are at:

A list of download locations can be found at Repositories. See Phase 1 Software Testing for a list of tested images.

Get:

  • dfu-util (the precompiled binary on http://buildhost.openmoko.org is for Linux/i386)
    • (this is the part that runs on the PC, that pushes the files across the USB to the phone)
  • openmoko-devel-image-fic-gta01-2007********.rootfs.jffs2
  • uImage-2.6.21.*-moko*-r*_0_****_0-fic-gta01.bin
  • for phase 0 (Bv03) phones:
    • Tested by a few people:
      u-boot-gta01bv3-r8_70124c2602ae2d4c5d3dba05b482d91548242de8_0_2040.bin
      MD5SUM: 60c5aeba1bd6642b05b3a5e6f2dafe83
    • Tested by hrw:
      u-boot-gta01bv3-r8_70124c2602ae2d4c5d3dba05b482d91548242de8_0_2062.bin
      MD5SUM: 716f1eba9b0f2be4a0a3be4a56724935
  • for phase 1 phones, uboot update should not be necessary.

Preparing the device for DFU mode

You'll need to boot your openmoko into uboot menu. To do this:

  • Unplug all usb devices from the host.
  • Hold Neo1973 AUX Button while pressing POWER button.
  • The uboot menu should appear.
  • Plug Neo1973 into host with supplied USB cable. (Plug the phone directly into the host not via a hub.)

Note: Some devices have been reported to turn off after a short period of inactivity while on the uboot menu. To avoid this, simply press the AUX button every 30 seconds or so.

No further navigation is needed in u-boot - the device will automatically start flashing the images when told to do so by dfu-util below. After flashing all the files, you can choose the "Boot" option to boot the newly flashed stuff.

Actually flashing things into the device

Double check that u-boot matches your hardware version. Flashing u-boot is really a critical part. You probably only want to do that on phase0 phones.

Note: It may be necessary to run the application as root (at least in ubuntu).

Note: Option -a also accepts symbolic names ("u-boot", "u-boot_env", "kernel", "splash", "rootfs")

Note: In case there are more than one available usb devices use -d 0x1457:0x5119 option.

To update u-boot:

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! Note especially that image below is for GTA01B_v03, not GTA01B_v04

./dfu-util -a 1 -R -D u-boot-gta01bv3-r8_70124c2602ae2d4c5d3dba05b482d91548242de8_0_2040.bin

To update the kernel:

./dfu-util -a 3 -R -D ./uImage-2.6.21.1-moko10-r0_0_1883_0-fic-gta01.bin

To update the root filesystem:

./dfu-util -a 5 -R -D ./openmoko-devel-image-fic-gta01-20070501054014.rootfs.jffs2

Notice that it's not normally needed to update the modules anymore. It's just for people with special needs. ...now, you'll end up with system that boots, but does not see audio/SD card. You'll need to download corresponding modules.tgz and copy them over to openmoko. - UPDATE: GTA01 phones appear to not need this step, as long as you have installed a kernel that matches the version of the modules contained in the root image ('uname -r' will show the kernel version, and 'ls /lib/modules/' will show the modules that are present).

VERY IMPORTANT NOTE (I would consider that as a design flaw - either dfu-util should do it automatically): If you upload rootfs image that is smaller that previous one it won't work - you need to attach to bootloader, erase NAND and then upload your rootfs first:

cu -l /dev/ttyACM0
GTA01Bv3 # nand erase rootfs

Old versions of uboot are buggy: You may have to press the aux button few times so that machine does not sleep while flashing. It also does not erase rootfs before flashing it... to do that, do minicom /dev/ttyACM0, then nand erase clean rootfs . Unfortunately, old versions of uboot are not really usable, because they fail to enable high 64MB of RAM, and you get nasty crashes after kernel boots.


Good luck!

Troubleshooting notes

If you're facing errors in seemingly random places during the flashing of images, most likely the USB hub or cable through which your Neo1973 is connected is of too poor quality. It is recommended that you always connect the phone directly to the host when using dfu-util.

If dfu-util reports a message like the following, before it starts flashing:
Resetting USB...
not at least 2 device changes found ?!?
Lost device after RESET?
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.

dfu-util does not seem to be able to download files if run from linux running under VMWare on a Windows OS host.

See other notes on Dfu-util page.