Openmoko - User contributions [en]

Artwork

2008-10-19T07:51:19Z

Enaut: /* Application Themes */

== Icons ==
[[User:nenadgrujicic|Nenad Grujicic]]: some ideas, device and suite icons

=== Device Icon ===

Here is a 256x256 png device icon for fic neo1973

preview:

http://i18.tinypic.com/62n9sba.jpg

save as ..

http://i15.tinypic.com/5yd5onm.png

=== Openmoko "Suite" Icons Idea: ===
[[Image:Mainicon.png]]
[[Image:Openmokosync.png]]
[[Image:Mediatransfer.png]]
[[Image:Ghostbackup.png]]
[[Image:Filebrowser.png ]]

[http://i11.tinypic.com/4yii7io.jpg link My Desktop Screenshot with icons]

== Application Themes ==

See also [[Themes]]

* The Tango Theme: http://52grad.de/.stuff/freerunner/

== OpenMoko Wallpapers ==

Wallpapers for the FreeRunner!

See [[Changing wallpaper]]

== PC Wallpapers ==

OpenMoko themed wallpapers for your desktop/laptop!

See also [[Desktop wallpaper gallery]]

=== Logo Plain ===

preview:

[[Image:Moko_plain_black.png|300px|black]]
[[Image:Moko_plain_white.png|300px|white]]
[[Image:Moko_plain_transparent.png|300px|transparent]]

=== Logo Wired 3D ===

preview:

[[Image:Moko_wire_black.png|300px|black]]
[[Image:Moko_wire_white.png|300px|white]]

{{Languages|Artwork}}

[[Category:User Interfaces]]

TangoGPS/de

2008-08-26T21:20:37Z

Enaut: Translation of the english article

{{Languages|TangoGPS}}
{{Application|TangoGPS}}

__TOC__

TangoGPS ist Kartenprogramm das mittels eingebautem GPS die die eigene Position anzeigt.

[[Image:TangoGPS1.jpg]]

Website: [http://www.tangogps.org www.tangogps.org]

== Installation und Starten in [[Om 2008.8]] ==

{{note| Getestet mit [http://downloads.openmoko.org/releases/Om2008.8-update/ OM 2008.08 Update]}}

Auf dem Handy im Terminal oder via ssh ausführen: (Benötigt eine Internetverbindung)

opkg install gpsd
opkg install http://www.tangogps.org/downloads/tangogps_0.9.3-r1_armv4t.ipk

Falls der Fehler "* Could not obtain administrative lock" auftritt hilft meistens:

pkill packagekit

Jetzt muss Noch die Konfigurationsdatei nach folgender Anleitung geändert werden [[Gpsd#GPS_on_GTA02]].
Dann kann man gpsd starten:

/etc/init.d/gpsd start

Mit eingeschaltetem GPS sollte Tangogps jetzt die aktuelle Position anzeigen. Achtung, es kann eine ganze weile dauern, bis das GPS einen Fix bekommt. Mehr dazu bei [[GTA02_GPS]].

[[Category:GPS]]

TangoGPS

2008-08-26T21:19:44Z

Enaut:

{{Languages|TangoGPS}}
{{Application|TangoGPS}}

__TOC__

TangoGPS is a map application which can utilize Neo's built-in GPS to show your current location.

[[Image:TangoGPS1.jpg]]

Website: http://www.tangogps.org

== Running tangoGPS on [[Om 2008.8]] ==

{{note|There may be other steps because I remember it took a while before my TangoGPS started working, but these are the only things I remember installing}}

From the freerunner connected to the internet:

opkg install gpsd
opkg install http://www.tangogps.org/downloads/tangogps_0.9.3-r1_armv4t.ipk

If opkg complains about not being able to acquire a lock, try:

pkill packagekit

To get gpsd working on the Freerunner you have to change the configuration according to [[Gpsd#GPS_on_GTA02]].
Then start gpsd by:

/etc/init.d/gpsd start

Now you must power up the GPS-chip by opening the "Settings" application and setting the GPS entry to "on". Now you can run tangoGPS and wait until it get's a GPS fix. This can take up to a few minutes.

== Running TangoGPS on [[debian]] ==

Tangogps is a very nice GPS mapping application. The latest version is available in [[Debian]].

Unfortunately it depends on gpsd which conflicts with frameworkd in fso-frameworkd.

# apt-get install gpsd tangogps

Edit <code>/etc/frameworkd.conf</code>. In the section <code>[ogpsd]</code>, edit to read:
<pre>
# path = /dev/ttySAC1
path = /dev/null
</pre>

/etc/init.d/fso-frameworkd restart
/etc/init.d/zhone-session stop && sleep 2 && /etc/init.d/zhone-session start

# dpkg-reconfigure gpsd

* Start gpsd automatically on boot? Yes.
* Device the GPS receiver is attached to: /dev/ttySAC1
* Should gpsd handle attached USB GPS receivers automatically? Yes
** not certain what this answer should be
* Options to gpsd: none

Start tangogps like this:

# echo 1 >/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron
Turns the GPS on.

# DISPLAY=:0 tangogps

'''Issues:'''
* The different daemons for reading GPS data mean that both tangogps and the framework demo GPS application can't be configured to work at the same time. Reboots are probably necessary when switching between them.
** Both gpsd and the framework publish GPS data through dbus, though with different interfaces. This suggests a number of possible solutions.
*** gpsd or the framework could implement the other's interface (along with their own).
*** a translator could read one interface and emulate the other
*** the framework could have an option to read data from gpsd.
*** opgsd/gypsy could be extended to be backwards compatible with the majority of gps applications.

== Downloading Maps for offline use ==
tangoGPS can bunch-download the map images so you don't need an internet connection while walking around. By default tangoGPS stores downloaded maps to /tmp/. This folder is lost every time you reboo the device. But you can use the "Config" tab within tangoGPS to change the "Cache Dir" location to , for example, /osm/ . So downloaded maps will be kept in the Neos flash, also after reboot. This works fine on OM2007.2 and Debian. If this config gets lost during reboot file a bug against your distro.

Once you have set the location to a non-volatile path, you can connect your Neo to the internet by USB or WiFi at home and start downloading the maps of your area. Tap the map screen and select "map download". Now on-the-road tangoGPS will be able to show you maps in different zoom levels even though you are not connected to the inet.

== Downloading Maps via GPRS ==
I think TangoGPS may have started working after I followed the instructions to get GPRS working with GSM multiplexing here: [[Manually_using_GPRS#Option_1:_With_GSM_multiplexing_and_with_a_GUI]]

There are steps included in those instructions to improve GPS performance. The great thing is that once you get GPRS working, you can roam with TangoGPS running and have it download maps as needed over the GPRS connection!

== Importing Tracks into TangoGPS ==

TangoGPS is able to record and store a track in its native format, and [http://psung.blogspot.com/2008/07/sharing-gps-tracks-from-tangogps-on.html tools] exist to convert this to GPX.
However, TangoGPS does not support the import of tracks. You may help yourself by using [http://relet.net/frog/archives/68 this tool] to import GPX trackpoints as a series of POIs directly into the sqlite database which tangoGPS uses to store POIs.

== Using Google Maps with TangoGPS ==

Go to Config and change the url to http://mt1.google.com/mt?&x=%d&y=%d&zoom=%d and check the "Inverted Zoom" box. Press save Repository Configuration and you're ready to go.
:Automated map download will most certainly fail, as Google is very keen on keeping leechers out.
:It did work for me...

[[Category:GPS]]

Apm

2008-08-26T19:36:12Z

Enaut:

A Useful app in the terminal to get the state of the battery.

==Options==
Supported options are:

-V To display the current Version of apm.
-v Print the current bios version and kernel driver Version.
-m Display the time remaining in minutes.
-M Monitor changes
-s Suspend the phone.
-d get a detailed View.

==Examples==
An example run with a almost full battery:

root@om-gta02:~# apm
On-line, battery status high: 99% (45d+12:15:00)

And with details:
root@om-gta02:~# apm -d
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery status high: 99% (45d+12:15:00)
Using device 0x0a86, 1.13: 1.2
APM Flags = 0x02; Line Status = 0x01
Battery Status = 0x00; Battery Flags = 0x00
Battery %age = 99; Battery Time = 65535, use_mins=1

Apm

2008-08-26T19:33:49Z

Enaut: New page: A Useful app in the terminal to get the state of the battery. Supported options are: -V To display the current Version of apm. -v Print the current bios version and kernel driver Versi...

A Useful app in the terminal to get the state of the battery.

Supported options are:

-V To display the current Version of apm.
-v Print the current bios version and kernel driver Version.
-m Display the time remaining in minutes.
-M Monitor changes
-s Suspend the phone.
-d get a detailed View.

An example run with a almost full battery:

root@om-gta02:~# apm
On-line, battery status high: 99% (45d+12:15:00)

And with details:
root@om-gta02:~# apm -d
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery status high: 99% (45d+12:15:00)
Using device 0x0a86, 1.13: 1.2
APM Flags = 0x02; Line Status = 0x01
Battery Status = 0x00; Battery Flags = 0x00
Battery %age = 99; Battery Time = 65535, use_mins=1

Om 2008.8

2008-08-20T07:52:14Z

Enaut: /* Share */

{{Languages|Om 2008.8}}
{{Om 2008.8}}

{{Distributions|Om 2008.8}}

=Introduction=
'''Om 2008.8''' is the successor to [[Om 2007.2]] and had '''ASU''' as a codename. It was [http://lists.openmoko.org/pipermail/community/2008-August/025619.html launched] on '''August 08, 2008'''. Om 2008.8 uses EFL for the launcher, custom UI applications and [[QtopiaOnX11|Qtopia on X11]] for telephony. It is the first step from GTK+ on x11 to using multiple toolkits in combination. '''Om 2008.8''' now supports [http://www.enlightenment.org/ EFL], [http://trolltech.com/products/qtopia Qtopia] and [http://www.gtk.org GTK+] applications.

''To see how it all got started go to'' [[Om2008.8 Feature Plan|Om 2008.8 Feature Plan]].

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; width:100%;floating="center"; "
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Om2008 uboot.png|200px|center]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Om2008 home.png|200px|center]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Installer4.png|200px|center]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Om2008 installer1.png|200px|center]]
|-

! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Main.png|200px|center]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Edit1.png|200px|center]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:Om locations4.png|200px|center]]
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #222222; width:25% " |
[[Image:List.png|200px|center]]
|}

= What's New =
'''Om 2008.8''' was designed to be empty, for the very purpose of showcasing your ideas.

Think of our products as galleries. We're building the environment. Each one different from the next. You'll get all the free art supplies you could imagine because we want you to add your own meaning. You choose: consume, create, or both.

Either way you create your own meaning. It's about you.

== Customize ==
'''Om 2008.8''' allows you to customize your Neo in many aspects.

* '''Use the [[Om2008.8_Installer|Installer]]''' to find apps and modifications for your Neo.
* '''Re-design themes''' by customizing your own [[Edje]] files.
* '''Source Codes''' are publicly available, allowing for customization all the way down to low level systems.

== Share ==
* share your locations ([[Om2008.8_Locations|Locations]])
:you can use '''Locations''' to save your favorite spots and even send it to friends via sms. How cool is that?!
* share your applications ([[Om2008.8_Installer|Installer]])
:share your ideas with the world by adding packages to the [[CommunityRepository]]. It is a great database for all things openmoko and can easily be accessed by any user through the [[Om2008.8 Installer|Installer]].

== Om 2008.8 Guide ==
A guide for getting to know Om 2008.8 : [[Om 2008.8 Guide]]




= Installing =

If you want install this software distribution to your device, you have to follow these steps:
* Download the recent image of Om2008.8 on the [[Downloads#Openmoko_2008.8_images_.28ASU.29|Downloads]] page
* [[Flashing the Neo FreeRunner|Flash]] to your Neo FreeRunner

= Known Issues =
'''GSM'''

* [http://docs.openmoko.org/trac/ticket/1766 Cannot make calls or receive SMS messages]
* [http://docs.openmoko.org/trac/ticket/1662 GSM not working properly after x hours]
* [https://docs.openmoko.org/trac/ticket/1765 No Pin-Dialog is showing up and so GSM is not usable at all]

'''WiFi'''

* [http://docs.openmoko.org/trac/ticket/1625 WiFi can only connect once]

'''Audio quality'''

* [http://docs.openmoko.org/trac/ticket/1721 QT-Dialer Sometimes can not hear anything durring connecting call]
* [http://docs.openmoko.org/trac/ticket/1640 Improve overall audio]

'''System Software'''

* [http://docs.openmoko.org/trac/ticket/1736 Boot screen goes into sleep and never wake up if not touch during booting]
* [http://docs.openmoko.org/trac/ticket/1597 After long suspend, kernel thread events]
* [http://docs.openmoko.org/trac/ticket/1315 xglamo: performance decreases after a while]
* [http://docs.openmoko.org/trac/ticket/1682 Neo turns off before reaching x]

'''Networking'''
* No Updates/Installation are possible or pings to domains because dns is not working. This problem occurs because the /etc/resolv.conf is empty by default.Add this line in /etc/network/interfaces:

up echo nameserver 192.168.0.200 >/etc/resolv.conf
This is to be inserted below gateway address and above the bluetooth networking. After this rebooting is required. Then go to /etc/resolv.conf and fill it manually by just using the content of this file on your local machine, or DNS address.

This should solve most off your moko side networking issues. If you need any other help please refer to [[USB Networking]]

{{note| [http://en.wikipedia.org/wiki/Resolvconf resolvconf] is installed so should probably be used }}

* Usb-networking will not work until rebooted after initial boot.

'''Usabillity'''
* The Pin-Dialog by default just shows letters. You have to slide your finger up/down over the keyboard to make the numbers/uppercase/special characters appear.
* The installer app doesn't release administrative rights which results in not being able to use opkg. Solution: run "killall packagekitd" (on the freerunner or when ssh'ed in).
* The installer app doesn't release administrative rights which results in not being able to use opkg. Alternate Solution: On the FreeRunner, use the drop-down menu to close all open applications.

= Future updates =

{{note|As of August 20th, there are *NO* updates available for 2008.8 anywhere on buildhost.openmoko.org - the daily-feeds directory is incompatible with 2008.8 and will corrupt your software configuration if you use it.}}

Posterior to the Om2008.8 release, in August 2008 development is switching to a Debian-like model with three branches: stable, testing and unstable. To minimize chaos, breakage and confusion, official updates for 2008.8 will be made available only when the move is complete ([http://lists.openmoko.org/pipermail/community/2008-August/026491.html see this message] for more details.)

In the meantime, you may try at your own risk [[Download#Unofficial_builds_by_zecke]] or Raster's builds.

[[Category:Openmoko]]
[[Category:Om 2008.8]]

User:Enaut

2008-08-20T06:37:41Z

Enaut: New page: I'm living in Freiburg in Germany. to contact me try to encrypt. mailname: enaut.w mailprovider: googlemail My/our webpage: [http://biohof-silberberg.de/ Webpage] But be carefull it loo...

I'm living in Freiburg in Germany.

to contact me try to encrypt.

mailname: enaut.w
mailprovider: googlemail

My/our webpage: [http://biohof-silberberg.de/ Webpage] But be carefull it looks quiet ugly with Internetexplorer.

Openmoko Local Groups: Freiburg im Breisgau

2008-08-20T06:29:41Z

Enaut: added myself and changed some style :)

=== Participants ===
{| border="5" cellspacing="0" cellpadding="10" style="border-collapse:collapse;background:#ece9e4;"
!Name
!Skills
!Level of Interest
!Location
!Device
|-
|[[User:Deep-Thoug|Deep-Thought]]
|Perl, Package building, System design, possibly building UI with Python
|Mobile Communication, making OpenMoKo a luxuirious hacker tool
|Freiburg im Breisgau
|Neo1973 (GTA01Bv4) basic
|-
|[[User:radl|radl]]
|some bits of: Java, Python, computational linguistics; Time, curiosity.
|fun! playing with possible UIs for a pocket-size, touchscreen-only PC, tbc...
|Freiburg
|GTA02 (not yet: Pulster 25.07.)
|-
|[[User:enaut|enaut]]
|mhm some Java less C++ and the basics of a first year computerscience student.
|i don't know yet.
|Freiburg (/ Calw Wohnsitz meiner Familie)
|GTA02
|}

=== Notes ===
OpenmoKo developers are sparse at the time. If there would be someone in the region, i think it might be a good idea to come together some time.

[[Category:Openmoko Local Groups]]

Flashing the Neo FreeRunner

2008-08-19T18:13:33Z

Enaut: /* Download the DFU-util program */

Openmoko regularly releases updated versions of the Openmoko root filesystem, the [[kernel]], and the [[Bootloader| U-Boot]] as binary images. These may be programmed into the Flash memory (NAND) of Neo FreeRunner. For that, you can use the USB cable and another computer which will run an Openmoko provided tool to flash the Neo FreeRunner "through" USB.

== Overview ==
All the components of the software in the FreeRunner are bundled together into binary images.

On a desktop computer when you want to replace the operating system (OS), you would boot it from a CD-ROM drive, then copy OS files from the CD to the internal hard drive. The FreeRunner does not have a CD-ROM drive and files must typically be re-written/flashed directly into internal storage (NAND flash). It is also possible to load all the OS files to and boot from a microSD.

The FreeRunner has two kinds of internal program storage: NOR flash and NAND flash. The NOR flash is small and stores only a special boot program used when you need to re-write the contents of the NAND flash. NAND flash acts more like a hard drive.

The NAND Flash is divided into 3 partitions for the bootloader, kernel, and root filesystem - so each of these components can be flashed separately. For example if you are trying to install a modified kernel, you only have to follow the steps to flash the kernel image.

* '''bootloader''': a small program that runs first and starts everything else when the FreeRunner is powered on or reset (depending on [[Booting the Neo FreeRunner|how you reset it]], the version from NOR or NAND is booted).
* '''kernel''': the central component in the Linux operating system.
* '''root filesystem''': contains all the files that make up the commands and applications that you can run.

'''Before you start: Erasing the root filesystem or flashing the uboot are radical measures. Take the time to ponder the necessity. Sometimes problems can be fixed by updating only the kernel.'''

== Alternative : running from microSD card ==

You may install this distribution on the microSD card, in order to [[Booting from SD | boot from microSD card]]. That allows you to keep another distribution installed in NAND (for instance to test 2008.08 while still having 2007.2 for default boot).

== Collect the things you need ==

=== Download the DFU-util program ===

You will download that program on your desktop computer. It will allow you to connect to the FreeRunner through the USB cable and control its bootloader. That connection uses a special protocol which addresses the bootloader's interface, and differs from USB networking. There is a separate page to describe it in more detail: [[dfu-util]].

'''MacOS X:''' [[MacOS_X#Graphical_Flashing_with_Openmoko_Flasher]]

'''Linux:''' http://buildhost.openmoko.org/releases/Freerunner/dfu-util

Make sure it is executable by setting the permissions with this command: chmod a+x dfu-util

'''Note:''' dfu-util seems to consistently fail with a "-62" error on 64-bit Linux. If you have access to a 32-bit machine, use it instead!
There are some ubuntu64 interpid packages which work just fine for me in hardy too. So you might try at your own risk: [http://packages.ubuntu.com/de/intrepid/dfu-util]

'''Windows:''' http://projects.openmoko.org/frs/?group_id=166&release_id=162

See additional driver installation instructions for Windows at [[Dfu-util-windows]]

=== Download the image files that you will need ===

Exactly what files you need depends on what you are trying to install. In most cases you will need to install a Kernel (uImage) and a Root Filesystem (rootfs). In rare cases, when there is a bug you need fixed, you will also install a new bootloader.

Please read [[Distributions]] for choosing the distribution which fits your needs, and then see [[Download]] for downloading.

== Boot the FreeRunner from NOR Flash ==

[[Image:menu15.jpg|thumb|Booting from NOR Flash]]

# Read the other sections of this page first, because you will have 30 seconds to enter the flashing commands, come back here when ready.
# Do not connect the USB cable from the PC to your Neo FreeRunner yet (disconnect it).
# Boot your Neo Freerunner into the NOR uBoot menu for flashing.
## Press and hold AUX button
## Press the Power button until the boot menu comes up
## This menu is labelled '''*** BOOT MENU (NOR) ***'''
## See also [[Booting the Neo FreeRunner]]
# Stay in NOR uBoot menu, do not to select or enter any item in menu. Now you will be able to flash, make backups of your Freerunner or query the Freerunner with dfu-util.
# The FreeRunner only stays at the NOR boot prompt for about 30 seconds and then shuts off unless you do something.
# Connect your Neo to the GNU/Linux or Windows host via a USB cable.
# Now you can enter the dfu-util commands on your PC as described below.
# If the Neo FreeRunner turns off before you press start flashing ('''screen goes black'''), go back to step 2. If you start flashing in time, the phone will not turn off meanwhile.



Note that the dfu-util connection does '''not''' use Ethernet over USB - that is, you should not attempt to set up a usb0 network interface on your GNU/Linux host desktop (on Windows, you need a DFU class driver, or you can use the LibUSB-Win32 driver described on the [[Dfu-util-windows]] page). The dfu-util utility sets up its own connection to the FreeRunner. In fact, you will not be able to make an Ethernet-over-USB connection to the FreeRunner when it is at the uBoot menu; this type of connection is only available when the FreeRunner has booted fully.

After connecting the FreeRunner to your host via USB cable, you can test whether dfu-util "sees" the FreeRunner by executing:

dfu-util -l
If you get error messages from the dfu-util command then try again. Often it works on the second try.

== Do a backup ==

If you have a working image that you're happy with but want to try something different, you should probably do a [[Pre-Flash Backup]].

== Using dfu-util ==

dfu-util can be used to read flash memory, write memory, and get information from the device.

This is the general command format to write an image file to a (predefined) "partition name" (referred to as ''altsetting'' in dfu-util help/manual) :

dfu-util -a ''altsetting'' -R -D ''file_name''

where: 
-a ''altsetting'' : Specify the altsetting of the DFU interface by name or by number 
-R : Issue USB Reset signalling once we're finished 
-D ''file_name'' : Write firmware from ''file_name'' into device

On Linux, you run dfu-util from a command shell prompt. If you have not put it somewhere on your command path you probably need to prefix it with a "./" like this '''./dfu-util'''.
On some systems you need to be root before this will work and on Ubuntu you must preface the command with "sudo" or you will get the following error: "Cannot claim interface: could not claim interface 2: Operation not permitted"

On Windows, you need to open a command window and run from a command line. Use Start-Run Program and type "cmd" to open a Window.

More detailed manual for gfu-util is available here : [[Dfu-util]]

== Flashing the Kernel ==

Note: The phone needs to be in the U-boot bootup menu for this to work. Get there by holding down the aux button while powering up the device.

The command format is

dfu-util -a kernel -R -D ''/path/to/uImage''

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

Flashing may fail with an error -110. This indicates that the kernel is too big for the default kernel partition. uboot can be used to change the size of the default partitions on the device. It may also mean that you are trying to put the wrong thing in the kernel space.

== Flashing the Root Filesystem ==

The root filesystem has to be an image in jffs2 format. If the file you downloaded is zipped or compressed (has a .gz, bz2, .zip, tar, tar.gz or .tgz extension) you have to uncompress it first.

The command format is

dfu-util -a rootfs -R -D ''rootfs_filename.jffs2''

where ''rootfs_filename.jffs2'' is the name of the file containing the root filesystem.

When flashing succeeds the following will be shown:

status(0) = No error condition is present
Done!

== Flashing the boot loader to the NAND==

The boot loader (U-boot) file should have a .bin extension. As with the root filesystem, if the file you downloaded is zipped or compressed (has a .gz or .zip extension) you have to uncompress it first.

The command format is

dfu-util -a u-boot -R -D ''uboot.bin''

where ''uboot.bin'' is the name of the boot loader binary image file.

''Reminder'': You should have [[Flashing_the_Neo_FreeRunner#Boot_the_FreeRunner_from_NOR_Flash|boot from NOR first]], in order to flash the boot-loader in NAND. After flashing succesfully, make sure you reboot from NAND's newly flashed boot loader, to benefit from the updates.


(Optional) After an upgrade, you may wish to check that the u-boot version matches the one you have just flashed. You can use 'grep Bootloader /dev/mtdblock1' from a shell on the FreeRunner (and possibly the 1973 as well) to get the '''NAND''' u-boot version, like this:
root@om-gta02:~# grep Bootloader /dev/mtdblock1
Neo1973 Bootloader U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb

You can grep for the same string in /dev/mtdblock0 to retrieve the '''NOR''' u-boot version:
root@om-gta02:~# grep Bootloader /dev/mtdblock0
Neo1973 Bootloader U-Boot 1.3.2-moko12



== Reboot the FreeRunner from NAND ==

You should now be able to boot into the new images.

Pay attention '''to booting from the NAND flash this time''', in particular if you upgraded the boot-loader (in short: 1. press and hold ''power button'' down, and then 2. press ''aux button'')

The boot menu should be labelled '''*** BOOT MENU (NAND) ***''' this time (see [[Booting#Log_into_U-Boot_in_the_NAND_Flash|booting from NAND]] for more detailed instructions).

[[Category:Flashing Openmoko| ]]