http://openmoko.org/api.php?action=feedcontributions&user=Rainglasz&feedformat=atomOpenmoko - User contributions [en]2024-03-29T08:52:38ZUser contributionsMediaWiki 1.19.24http://openmoko.org/wiki/Neo_FreeRunner_BatteryNeo FreeRunner Battery2012-07-15T06:44:29Z<p>Rainglasz: /* GTA02 1200 mAh Smart Battery */ Added another number</p>
<hr />
<div>{{Languages|Neo FreeRunner Battery}}<br />
<br />
{{Neo FreeRunner Menu}}<br />
<br />
For the latest information about batteries and battery compatibility please see [[Battery_Questions_and_Answers]].<br />
<br />
=== GTA02 1200 mAh Smart Battery ===<br />
<br />
*Internally, uses the SANYO 1200mAh cell (note that the Sanyo cell by itself does not have the Coulomb-counter and thus can not be used as a replacement for the Neo FreeRunner battery)<br />
*Battery Technical information: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf Detailed Battery Information]<br />
<br />
* 1200mAh Smart Battery with Coulomb-counter and protection circuit<br />
* The Smart Battery keeps track of maximum and current capacity for precise prediction of remaining battery power and time until shutdown, based on actual power dissipation.<br />
* Battery could be identified with part # HF084, HF086, ... (add others)<br />
<br />
For more information, see the GTA01 battery info at [[Neo1973 Battery]]<br />
<br />
=== Notes about expected battery life ===<br />
Battery life depends on your usage pattern. The maximum you can get is ~70h [[StandbyLifetime]], mostly in suspend, with multiple short wakeups.<br />
<br />
== Known Issues ==<br />
<br />
=== Make sure your battery never discharges completely. ===<br />
<br />
This is an issue for older FreeRunner [[GTA02_revisions]] because the internal charging circuitry cannot be turned on until the FreeRunner has booted, and booting through USB power alone does not work on A5 and early A6 devices.<br />
If your FreeRunner boots to the point of showing something on screen when it is connected to the OM-wallcharger or a PC's USB port with no [http://tobuybattery.com replacement battery] installed, your device isn't affected by this issue.<br />
<br />
Depending on NAND bootloader version there might also be a red light on AUX indicating postponed boot while charging battery to a required minimum - just keep your [[FR]] hooked up to the charger then until it boots. Or [[Booting_the_Neo_FreeRunner#Log_into_U-Boot_in_the_NOR_Flash|boot to NOR]] if it doesn't recover during some ten minutes.<br />
<br />
<br />
==== What to do if your battery has become completely discharged ====<br />
<br />
On more recent FreeRunners, this problem has been fixed and nothing special need be done. On older revisions, you can boot using a workaround listed <br />
[[Neo_FreeRunner_Hardware_Issues#Can.27t_boot_with_discharged_or_missing_battery_.28FIXED.29|here]].<br />
<br />
==== More tricks ====<br />
<br />
A trick to get a Freerunner with a flat battery up and running which seems to work for most people is to remove the battery and the charger plug, press and hold AUX, put in the battery and then plug in the wall charger while still holding the AUX button. Suggested by joerg, confirmed to work by user [http://wiki.openmoko.org/wiki/User:Azmodie azmodie], user [http://wiki.openmoko.org/wiki/User:Jhenkins jhenkins], user [[User:Aragorn|aragorn]] (worked even without battery).<br />
<br />
''Q: Does anyone know WHY it don't charge when it is off? My logic says that it is very important to have the option charge the battery when it is flat.''<br />
<br />
A: I can't give you a simple answer. Charging is controlled by the PCF50633 <br />
chip, based on configuration values that are written to it by u-boot, <br />
Linux, and userspace programs. Some of these settings are preserved <br />
across a power-cycle (the PCF50633 has a small backup battery that's <br />
also used to keep the RTC running) so the behavior at startup depends on <br />
the software that you used during your last session.<br />
<br />
Another complication is that some Freerunners (later A6) are capable of starting up <br />
without a battery while others (A5 and early A6) are not. This was fixed during the A6 release by changing the Vsys capacitor to 100uF. <br />
<br />
I can give a few hints:<br />
* The current (Sep. 2nd, 2008) u-boot has a bug that means it will not properly charge from the wall charger. Try a USB cable into a PC instead.<br />
** Feb. 2009 -- Is the preceding comment still correct? Bug number?<br />
* Try booting through NOR u-boot instead (hold aux and then power) with both the wall charger or a 500mA USB connection, then try booting Linux.<br />
* Try to boot into the NAND u-boot menu (hold power and then aux) and then select "power off". This may leave the device in a state were it will charge. Wait 15 minutes and then try to boot Linux.<br />
* If the device shuts off during one of the above attempts, let it sit for a few minutes and then try that same item once again<br />
<br />
Kudos to Mike Montour on the<br />
[http://lists.openmoko.org/pipermail/community/2008-September/029243.html Community mailing list].<br />
<br />
== Compatible Replacement Batteries ==<br />
<br />
Other known FreeRunner-compatible batteries include the BL-series (BL-4X, BL-5X) from Nokia, and their third-party equivalents.<br />
These may not work to revive a device and may not report charge information.<br />
It is probably a good idea to check that your battery is not greater than the stock battery's voltage of 3.7V (the above suggests that 4.5VDC should be fine) unless you know what you are doing.<br />
<br />
{| border="1" cellpadding="4" cellspacing="0"<br />
!Battery Model<br />
!Capacity (mAh)<br />
!Charge info reported<br />
!Notes<br />
|-<br />
|NOKIA BL-4<br />
|<br />
|no<br />
|<br />
|-<br />
|NOKIA BL-4C<br />
|750<br />
|no<br />
|Slightly thinner than original.<br />
|-<br />
|NOKIA BL-5B<br />
|760/890<br />
|<br />
|<br />
|-<br />
|NOKIA BL-5C<br />
|950<br />
|no<br />
|<br />
|-<br />
|NOKIA BL-6C<br />
|1070<br />
|no<br />
|<br />
|-<br />
|NOKIA BR-6C<br />
|?<br />
|no<br />
|<br />
|-<br />
|Garmin GPS 10x<br />
|1100<br />
|no<br />
|<br />
|}<br />
<br />
Also see [[Battery_Questions_and_Answers#Hardware_capabilities|Battery FAQ]] for a more up-to-date info<br />
<br />
== Alien Charging of Battery ==<br />
<br />
Nokia devices (phones and stand-alone chargers) usually will not charge<br />
non-Nokia batteries, most likely because they can't be sure they have<br />
the correct charging parameters (and of course Nokia isn't interested in supporting use of alien batteries with their phones).<br />
<br />
Most after-market or no-name brands of Nokia-compatible chargers don't<br />
test the make of the battery, most likely because adding the capability<br />
to perform this test would add to the cost of the charger and limit it's universal character (that's not the interest of second source manufacturers).<br />
<br />
Thus:<br />
* You can use a Nokia or Nokia-compatible BL-4C, BL-5C, or BL-6C in the Neo<br />
* You can charge the Neo battery in a Nokia-compatible charger that is not Nokia branded<br />
* You can NOT charge the Neo battery in a Nokia branded phone or charger<br />
<br />
Alternatively, the Garmin GPS 10X, a Bluetooth GPS device, uses a compatible battery to the OpenMoko FreeRunner. The device can be used to charge FreeRunner batteries at 100mA, 500mA or 1A over miniUSB (including deep-discharged batteries).<br />
<br />
The PIXO C-USB will charge any rechrgeable battery, including AA, AAA and the Freerunner's, from a USB port or from a wall-socket charger with a mini-USB connector.<br />
<br />
For more information about USB battery chargers that can be used with the Neo FreeRunner see<br />
{{main|USB charger}}<br />
<br />
== DIY external battery pack from a Minty case ==<br />
<br />
<br />
'''Mintyboost:'''<br />
<br />
Charge from a couple of AA batteries: [http://www.ladyada.net/make/mintyboost/ Minty Boost!], [http://www.millions.ca/~stacy/mintyboost/ report on a Neo FreeRunner application].<br />
<br />
Adding the 47k resistor to the minty boost so that the Freerunner fast charges at 1A is a poor idea for a couple reasons, the biggest one being that the minty boost can't supply 1A the max is 600mA. as far as I know, there is no magic resistor to identify a 500mA charger to the Freerunner, it depends on USB host telling it that it can provide 500mA. Second, the ID pin is in the USB micro connector, so you would either need to put a micro connector on your minty boost (with the correct resistor installed) or use a hacked cable.<br />
<br />
Even if the Linear Technology step up voltage converter is supposed to be able to do 600mA, the AA cells seem to have a problem with supplying 500mA. They get a little toasty :-). One powerpack built using D cells doesn't seem to have any issues with supplying 500mA.<br />
<br />
<br />
[[Category:Battery]]<br />
[[Category:Neo FreeRunner Hardware]]</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-02-01T12:34:47Z<p>Rainglasz: /* My Log */</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
It is very difficult to exactly name the version you can download for the various distributions; and sometimes there are different servers for the same distritbution with different versions (as far as I can see)<br />
<br />
=== uBoot ===<br />
Failed to boot from ext2, very curious. To boot from ext2 (as qi can) would make life easier<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS (maybe I did not wait long enough)<br />
<br />
=== OM 2008.9 ===<br />
Works (booted from SD), more to follow<br />
<br />
=== OM 2008.12 ===<br />
Does not boot from SD: <i>Only GTA01 Hardware supported by ASoc driver</i><br />
Found finally the hint that the root-fs must be mounted rw here: [[Community_Updates/January_12th,_2009#Tips_and_tricks]]. However, tricking with Uboot load is a hard requirement for a beginner, even with lots of system experience. I thought that testing from a SD card would be a wise thing!<br />
<br />
After 2nd boot, the system runs very unstable.<br />
<br />
=== Qtopia ===<br />
Works (booted from SD)<br />
* Telephony rather mature (can read adress list)<br />
* GPS functioning (usual long time if booted from SD)<br />
* WLAN not encrypted, because it is nearly impossible to enter any non-trivial key<br />
<br />
=== SHR ===<br />
Works fine (booted from SD), but latest version requires rw mount during boot.<br />
* Crashes WindowsXP-SP3 when connecting USB (VMware problem?)<br />
* Very slow (30% cpu time continuously in enlightenment)<br />
* WiFi access not yet working<br />
* Very quickly suspending<br />
* Phone calls working, even in suspend!<br />
* tangoGPS not yet working</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-02-01T11:37:33Z<p>Rainglasz: /* Qtopia */</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS<br />
<br />
=== OM 2008.9 ===<br />
Works (booted from SD), more to follow<br />
<br />
=== OM 2008.12 ===<br />
Does not boot from SD: <i>Only GTA01 Hardware supported by ASoc driver</i><br />
Found finally the hint that the root-fs must be mounted rw here: [[Community_Updates/January_12th,_2009#Tips_and_tricks]]. However, tricking with Uboot load is a hard requirement for a beginner, even with lots of system experience. I thought that testing from a SD card would be a wise thing!<br />
<br />
After 2nd boot, the system runs very unstable.<br />
<br />
=== Qtopia ===<br />
Works (booted from SD)<br />
* Telephony rather mature (can read adress list)<br />
* GPS functioning (usual long time if booted from SD)<br />
* WLAN not encrypted, because it is nearly impossible to enter any non-trivial key<br />
<br />
=== SHR ===<br />
Works fine (booted from SD), but latest version requires rw mount during boot.<br />
* Crashes WindowsXP-SP3 when connecting USB (VMware problem?)<br />
* Very slow (30% cpu time continuously in enlightenment)<br />
* WiFi access not yet working<br />
* Very quickly suspending<br />
* Phone calls working, even in suspend!<br />
* tangoGPS not yet working</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-02-01T11:31:02Z<p>Rainglasz: /* Qtopia */ some details</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS<br />
<br />
=== OM 2008.9 ===<br />
Works (booted from SD), more to follow<br />
<br />
=== OM 2008.12 ===<br />
Does not boot from SD: <i>Only GTA01 Hardware supported by ASoc driver</i><br />
Found finally the hint that the root-fs must be mounted rw here: [[Community_Updates/January_12th,_2009#Tips_and_tricks]]. However, tricking with Uboot load is a hard requirement for a beginner, even with lots of system experience. I thought that testing from a SD card would be a wise thing!<br />
<br />
After 2nd boot, the system runs very unstable.<br />
<br />
=== Qtopia ===<br />
Works (booted from SD)<br />
Telephony rather mature (can read adress list)<br />
GPS functioning (usual long time if booted from SD)<br />
WLAN not encrypted, because it is nearly impossible to enter any non-trivial key<br />
<br />
=== SHR ===<br />
Works fine (booted from SD), but latest version requires rw mount during boot.<br />
* Crashes WindowsXP-SP3 when connecting USB (VMware problem?)<br />
* Very slow (30% cpu time continuously in enlightenment)<br />
* WiFi access not yet working<br />
* Very quickly suspending<br />
* Phone calls working, even in suspend!<br />
* tangoGPS not yet working</div>Rainglaszhttp://openmoko.org/wiki/Android_on_FreerunnerAndroid on Freerunner2009-01-31T20:47:09Z<p>Rainglasz: /* Images */ Link to Uboot change added</p>
<hr />
<div>{{Languages|Android on Freerunner}}<br />
<br />
{|align=right<br />
|__TOC__<br />
|}<br />
[[Image:android.png]]<br />
= Introduction = <br />
This page is dedicated to the installation of Android on the [[Neo 1973]] and [[Neo FreeRunner]] handsets.<br />
<br />
You can find general informations (porting/development and day to day usage) about Android and Neo phones here : [[Android]]<br />
<br />
== Android on internal flash ==<br />
<br />
=== Images ===<br />
<br />
There are currently a few prebuild images:<br />
<br />
[http://panicking.kicks-ass.org/download/ Michael Trimarchi's images with latest fixes]<br />
[http://people.openmoko.org/sean_mcneil/ Sean McNeil images]<br />
<br />
To use the Kernel you have to either :<br />
<br />
* adjust your [[Uboot]] environment to support a Kernel of more then 2 MB [[http://meinopenmoko.blogspot.com/2008/12/prepare-uboot-to-boot-android.html]]<br />
* change to the [[Qi]] Bootloader . It supports 2MB kernels out of the box.<br />
<br />
I have placed an older 2.6.26 kernel with Android support at:<br />
<br />
[http://people.openmoko.org/sean_mcneil/uImage-android uImage-android]<br />
<br />
I have put up a jffs2 image that replaces rootfs on the Freerunner at:<br />
<br />
[http://people.openmoko.org/sean_mcneil/androidfs.jffs2 androidfs.jffs2]<br />
<br />
=== Installation on internal flash ===<br />
<br />
As noted above, this installation requires you to wipe out the existing kernel and rootfs in NAND on your Freerunner. You also must have an SDCARD and it needs to be configured with two (2) primary partitions: First is VFAT/MSDOS (16 or 32) which acts as the /sdcard storage area for pictures, movies, music, etc. and the Second is an ext3 primary partition for use of internal Android /data area to store settings, caches, etc.<br />
<br />
The first thing I suggest is to setup an SDCARD. You can flash the NAND first, but you must have an SDCARD with two partitions as stated before you'll be able to boot. I use a 2GB card which I have split in half. fdisk shows me:<br />
<br />
/dev/mmcblk0p1 1 2454 996310 6 FAT16<br><br />
/dev/mmcblk0p2 2455 4908 996324 83 Linux<br />
<br />
formatted as<br />
<br />
sudo mkfs.vfat /dev/mmcblk0p1<br><br />
sudo mkfs.ext3 /dev/mmcblk0p2<br />
<br />
There is no need to populate the ext3 partition at all. The VFAT partition can be populated with media content if you so desire.<br />
<br />
With your SDCARD all set, you are ready to flash the kernel and rootfs:<br />
<br />
sudo {path_to}/dfu-util -d 0x1d50:0x5119 -a kernel -D uImage-android<br><br />
sudo {path_to}/dfu-util -d 0x1d50:0x5119 -a rootfs -D androidfs.jffs2<br><br />
<br />
<br />
<br />
== Android on SDcard ==<br />
<br />
=== Images ===<br />
<br />
There are currently a few prebuild images:<br />
[http://activationrecord.net/radekp/openmoko/android/ Radek Polak's SD card images] (install on ext3, first partition on SD must be FAT16)<br />
<br />
=== Using jffs2 images ===<br />
<br />
You can also boot from the SD Card using the pre built images like so :-<br />
* Mount the image using [http://wiki.openmoko.org/images/8/82/Mntjffs.sh this] script like so <br />
sudo ./Mntjffs.sh freerunner-v5.jffs2 image/<br />
* Then copy (cp -R) the files in directory image/ to any of the first three partitions on the SD Card (if using Qi) eg cp -R /your-path/image/* /media/android/<br />
* cd /media/android.<br />
* wget http://activationrecord.net/radekp/openmoko/android/init.rc .<br />
* mkdir boot<br />
* copy the kernel here and name it uImage-GTA02.bin<br />
<br />
<br />
Some notes about booting android from sdcard : <br />
<br />
=== Setup ===<br />
<br />
* Build android from source. See [http://trac.koolu.org/ koolu website] for directions.<br />
* Use the first script in [http://lists.openmoko.org/pipermail/community/2008-December/036982.html this mail] (adapt to your filesystem) to stage your android install.<br />
* copy the contents of this directory on a ext3 partition on your sdcard.<br />
* add a /boot directory on your sdcard.<br />
* copy the uImage-android kernel (see above) and copy it inside your /boot with the exact name '''uImage-GTA02.bin'''<br />
* I changed the init.rc (in your root on the sd) to remove mounts that could be problematic (/data for example) :<br />
<pre><br />
--- filesystem/root/init.rc 2008-12-15 17:51:14.000000000 +0100<br />
+++ phyce.init.rc 2008-12-19 15:56:25.000000000 +0100<br />
@@ -24,7 +24,7 @@<br />
mkdir /sqlite_stmt_journals 01777 root root<br />
mount tmpfs tmpfs /sqlite_stmt_journals size=4m<br />
<br />
- mount rootfs rootfs / ro remount<br />
+ mount rootfs rootfs / rw remount<br />
<br />
write /proc/sys/kernel/panic_on_oops 1<br />
write /proc/sys/kernel/hung_task_timeout_secs 0<br />
@@ -38,14 +38,14 @@<br />
# mount yaffs2 mtd@system /system ro remount<br />
<br />
# We chown/chmod /data again so because mount is run as root + defaults<br />
- mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev<br />
- chown system system /data<br />
- chmod 0771 /data<br />
+# mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev<br />
+# chown system system /data<br />
+# chmod 0771 /data<br />
<br />
# Same reason as /data above<br />
- mount yaffs2 mtd@cache /cache nosuid nodev<br />
- chown system cache /cache<br />
- chmod 0770 /cache<br />
+# mount yaffs2 mtd@cache /cache nosuid nodev<br />
+# chown system cache /cache<br />
+# chmod 0770 /cache<br />
</pre><br />
<br />
* Install [[Qi]] on you NAND flash. You can still boot whatever distro you've got on internal flash using the NOR bootloader. You should try the magic file in /boot to show kernel messages.<br />
* boot the GTA02, and pray.<br />
<br />
<br />
== Status ==<br />
<br />
Most of the hardware on Freerunner seems to work on latest Android images, but not always perfectly.<br />
<br />
If you want to see details of what is already usable, please have a look at: [[Android_usage]]<br />
<br />
<br />
== Android Debug Bridge ==<br />
To assist in debugging and to gain shell access to the phone with Android, you can use the instructions found here: [[Android debug bridge]]<br />
<br />
= See also =<br />
* [[Android|Main Android page on this wiki]]<br />
<br />
<br />
[[category|Distribution]]<br />
[[Category:Flashing Openmoko]]</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-30T21:48:02Z<p>Rainglasz: /* SHR */ requirement to boot root rw</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS<br />
<br />
=== OM 2008.9 ===<br />
Works (booted from SD), more to follow<br />
<br />
=== OM 2008.12 ===<br />
Does not boot from SD: <i>Only GTA01 Hardware supported by ASoc driver</i><br />
Found finally the hint that the root-fs must be mounted rw here: [[Community_Updates/January_12th,_2009#Tips_and_tricks]]. However, tricking with Uboot load is a hard requirement for a beginner, even with lots of system experience. I thought that testing from a SD card would be a wise thing!<br />
<br />
After 2nd boot, the system runs very unstable.<br />
<br />
=== Qtopia ===<br />
Works fine (booted from SD), more to follow<br />
<br />
=== SHR ===<br />
Works fine (booted from SD), but latest version requires rw mount during boot.<br />
* Crashes WindowsXP-SP3 when connecting USB (VMware problem?)<br />
* Very slow (30% cpu time continuously in enlightenment)<br />
* WiFi access not yet working<br />
* Very quickly suspending<br />
* Phone calls working, even in suspend!<br />
* tangoGPS not yet working</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-30T21:46:55Z<p>Rainglasz: /* OM 2008.12 */</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS<br />
<br />
=== OM 2008.9 ===<br />
Works (booted from SD), more to follow<br />
<br />
=== OM 2008.12 ===<br />
Does not boot from SD: <i>Only GTA01 Hardware supported by ASoc driver</i><br />
Found finally the hint that the root-fs must be mounted rw here: [[Community_Updates/January_12th,_2009#Tips_and_tricks]]. However, tricking with Uboot load is a hard requirement for a beginner, even with lots of system experience. I thought that testing from a SD card would be a wise thing!<br />
<br />
After 2nd boot, the system runs very unstable.<br />
<br />
=== Qtopia ===<br />
Works fine (booted from SD), more to follow<br />
<br />
=== SHR ===<br />
Works fine (booted from SD)<br />
* Crashes WindowsXP-SP3 when connecting USB<br />
* Very slow (30% cpu time continuously in enlightenment)<br />
* WiFi access not yet working<br />
* Very quickly suspending<br />
* Phone calls working, even in suspend!<br />
* tangoGPS not yet working</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-30T21:43:48Z<p>Rainglasz: /* OM 2008.12 */</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS<br />
<br />
=== OM 2008.9 ===<br />
Works (booted from SD), more to follow<br />
<br />
=== OM 2008.12 ===<br />
Does not boot from SD: <i>Only GTA01 Hardware supported by ASoc driver</i><br />
Found finally the hint here: [[Community_Updates/January_12th,_2009#Tips_and_tricks]]. However, tricking with Uboot load is a hard requirement for a beginner, even with lots of system experience. I thought that testing from a SD card would be a wise thing!<br />
<br />
After 2nd boot, the system runs very unstable.<br />
<br />
=== Qtopia ===<br />
Works fine (booted from SD), more to follow<br />
<br />
=== SHR ===<br />
Works fine (booted from SD)<br />
* Crashes WindowsXP-SP3 when connecting USB<br />
* Very slow (30% cpu time continuously in enlightenment)<br />
* WiFi access not yet working<br />
* Very quickly suspending<br />
* Phone calls working, even in suspend!<br />
* tangoGPS not yet working</div>Rainglaszhttp://openmoko.org/wiki/Stable_Hybrid_ReleaseStable Hybrid Release2009-01-30T18:36:11Z<p>Rainglasz: /* Install */ updated to unstable, testing has no image</p>
<hr />
<div>{{Languages|SHR}}<br />
{{Distributions|SHR}}<br />
{{SHR}}<br />
<br />
== Why SHR exists ==<br />
The [[Stable Hybrid Release]] (SHR) is intended to be a community driven distribution composed of the [[OpenmokoFramework|FSO]] and some basic applications, that can be configured to use several different graphical toolkits, for example GTK or EFL. SHR is based on the FSO build. At first, SHR was introduced in order to use the [[Openmoko2007.2]] GTK software in combination with the new [[OpenmokoFramework|FSO]], but things have changed.<br />
<br />
====Why not just use plain FSO?====<br />
[[FSO]] is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br />
<br />
FSO is by far the most stable & usable release, if all you want is a phone. (I mean *all*. It just has a dialer, which is a demo application.)<br />
<br />
FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br />
<br />
Other people are supposed to put a front end on FSO. So that's what we're doing.<br />
<br />
== Install ==<br />
<br />
Installing SHR is very easy. I will explain how to install the testing version of SHR. It is stable enough for a daily use. Stable version will be available soon ([http://blog.shr-project.org/ Stable announcement]), [http://build.shr-project.org/shr-unstable/images/om-gta02/ unstable] (for the adventurous testers) is also available.<br />
<br />
I suppose that you know how to use [http://wiki.openmoko.org/wiki/NeoTool NeoTool]<br />
<br />
You need to download two files from [http://build.shr-project.org/shr-unstable/images/om-gta02/ unstable GTA02]<br />
<br />
- the kernel (uImage-om-gta02-latest.bin)<br />
<br />
- the root files system (<tt>shr-image-om-gta02.tar.gz</tt> or <tt>shr-image-om-gta02.jffs2</tt>)<br />
<br />
You can view the sources [http://git.shr-project.org/git/ here].<br />
<br />
== Connecting your FreeRunner to your computer ==<br />
For the next configuration steps, you will need to type some commands. It is much easier to type on a real keyboard than on a touch screen. <br />
So you need to connect your FR to you computer, and make a bridge to internet.<br />
Use [http://wiki.openmoko.org/wiki/USB_Networking this page]<br />
<br />
== Setting local time ==<br />
As any linux system, the UTC time is used by the system. First of all, adjust this time:<br />
date -u -s 010220052009<br />
Fri Jan 2 20:05:00 UTC 2009<br />
<br />
Then, you need to "localise" your system. <br />
Search for the appropriate country with:<br />
opkg list | grep tzdata<br />
<br />
then install the one corresponding to your area. <br />
opkg install tzdata-europe<br />
<br />
Then select your city (search the city availabled in /usr/share/zoneinfo/your-country)<br />
<br />
You can fully localise your system by installing the glibc-binary-localedata correponding to your langage. Search the ones available with:<br />
opkg list | grep glibc-binary-localedata<br />
<br />
install with<br />
<br />
opkg install glibc-binary-localedata-fr-fr<br />
<br />
(example for France)<br />
<br />
ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime<br />
<br />
== Changing root password ==<br />
SHR is shipped without root password (just press enter)<br />
<br />
This is very dangerous if you connect using wifi, or USB. You need to activate the root password:<br />
<br />
passwd<br />
<br />
and type your selected password (2 times)<br />
<br />
== Customize the RingTone ==<br />
You need to have a file containing the RingTone you want for your FR. You can find some at [http://wiki.openmoko.org/wiki/Ringtones#svn.openmoko.org_ringtones RingTone]<br />
<br />
Then transfer it to your FR (i.e on the SD card):<br />
scp file root@192.168.0.202:/media/card/<br />
<br />
Now you need to indicate that the FR must use this file for incoming calls. Modify /etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
== Sound Control ==<br />
<br />
Up to now, there is no graphical interface to control the sound<br />
=== Mic and HP ===<br />
The first idea is to use alsamixer; bad idea! There are 94 controls, and your modifications will be lost at the next reboot.Finding documentation is not easy. Here is my understanding: <br />
Scenari are used for each case. They are located in /usr/share/openmoko/scenarios/<br />
- capturehandset.state <br />
- gsmheadset.state <br />
- headset.state <br />
- voip-handset.state<br />
- gsmhandset.state<br />
- gsmspeakerout.state<br />
- stereoout.state<br />
<br />
Each file is a set of value for the 94 parameters. I have identified some:<br />
<br />
- Control 48: internal mic of the tel (set to 2 or 3)<br />
<br />
- Control 4 : internal speaker (set from 110 to 120)<br />
<br />
- Control 49: headset mic<br />
<br />
- Control 3 : headset speaker<br />
<br />
<br />
<br />
external link:<br />
<br />
http://wiki.openmoko.org/wiki/Neo_1973_audio_subsystem<br />
<br />
http://wiki.openmoko.org/wiki/Neo_alsamixer#Settings_Descriptions<br />
<br />
http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem<br />
<br />
=== Ringing ===<br />
<br />
<br />
You can define a short ringtone, repeated many time, or a long one, repeated 1 time<br />
<br />
File: /etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
Parameter: ring-volume # Ring Volume control 0 (mini) to ? maxi)<br />
Parameter: ring-length # min time for ringtone. Must be greater than the duration of you ringtone<br />
<br />
File: /etc/freesmartphone/opreferences/schema/phone.yaml<br />
Parameter: ring-loop # define the number of loop of ringtone to play<br />
<br />
=== Message alert ===<br />
File: /etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
Parameter: message-volume # Ring Volume control 0 (mini) to ? maxi)<br />
Parameter: message-length # min time for message alert. Must be greater than the duration of you message alert<br />
<br />
File: /etc/freesmartphone/opreferences/schema/phone.yaml<br />
Parameter: message-loop # define the number of loop of incoming message music to play<br />
<br />
<br />
<br />
<br />
== GPS ==<br />
GPS is not started automatically at boot. You need to switch it ON/OFF manually<br />
<br />
you need to modify the file /etc/init.d/fso-gpsd. Replace the line<br />
<br />
start-stop-daemon --start /usr/sbin/fso-gpsd -S localhost:gpsd -P /var/run/${NAME}.pid<br />
<br />
by <br />
<br />
start-stop-daemon --start --pidfile /var/run/${NAME}.pid --exec /usr/sbin/fso-gpsd -- -S localhost:gpsd -P /var/run/${NAME}.pid<br />
<br />
<br />
and then you can start fso-gpsd by<br />
<br />
/etc/init.d/fso-gpsd start<br />
<br />
<br />
=== using a GUI ===<br />
install [http://wiki.openmoko.org/wiki/ShortOm ShortOm] <br />
and configure it to start/stop fso-gps as above<br />
<br />
== Known Issues ==<br />
=== Phone ===<br />
<br />
GSM network is lost after one day of uptime: restart your FR once a day!<br />
<br />
=== Address Book ===<br />
<br />
SHR is not implementing a PIM (Personal Information Manager) yet. Work is in progress, but to included in SHR testing This has some consequences on daily use:<br />
<br />
- only contacts on the SIM card are available<br />
<br />
- it is not possible to import a Vcard file<br />
EDIT : It seems to be possible with a script written By Zem:<br />
[http://wiki.openmoko.org/wiki/User:Zem#DBus_Access_Scripts]<br />
<br />
- Incoming call only display phone number (not the name of the calling person)<br />
<br />
- it is not possible to send message (SMS) using the name of the receiver. You need to remember his phone number<br />
<br />
<br />
<br />
== More Information ==<br />
<br />
Visit:<br />
* Blog: http://blog.shr-project.org<br />
* Trac: http://trac.shr-project.org<br />
* Git: http://git.shr-project.org<br />
* Buildhost: http://build.shr-project.org<br />
<br />
[[Category:SHR]]</div>Rainglaszhttp://openmoko.org/wiki/Neo_FreeRunner_Hardware_IssuesNeo FreeRunner Hardware Issues2009-01-30T08:43:05Z<p>Rainglasz: /* Draws too much current from USB */ Completely rewritten</p>
<hr />
<div>{{Neo FreeRunner Menu}}<br />
<br />
This is a community-written page that discusses '''hardware issues''' with the FreeRunner/[[GTA02]] device. Information here is unofficial (and possibly incorrect) unless otherwise stated. Corrections and clarifications from Openmoko employees would be greatly appreciated.<br />
<br />
Please '''DON'T PANIC''' when reading this page. Please give Openmoko employees time to investigate these issues and to develop a solution. Some of the items may turn out to be non-issues, or may have software workarounds. The FreeRunner's software is still under heavily development and can help fix most of this problems.<br />
<br />
=== Active Issues ===<br />
<br />
==== Poor Audio Quality ====<br />
<br />
Issue: The person on the other end of a GSM phone call may experience poor audio quality, to the point where he/she cannot carry on a normal conversation.<br />
<br />
There are three related aspects to this issue:<br />
* Call is too quiet (mixer settings for mic and/or earpiece are set too low)<br />
* Caller hears a loud echo of their own voice [http://docs.openmoko.org/trac/ticket/1267 #1267]<br />
* Buzzing noise caused by GSM radio interference [http://docs.openmoko.org/trac/ticket/883 #883] [http://docs.openmoko.org/trac/ticket/1352 #1352]<br />
<br />
<br />
Affects: all devices but only some users (depending on many factors)<br />
<br />
The source of the GSM buzz has been [http://lists.openmoko.org/pipermail/hardware/2008-August/000415.html identified]. It's a mere hw-issue, depending on the way you hold the device, and the local situation created by network settings made by the GSM-provider (mainly 1800/1900 seems to be affected), as well as your position relative to basestation. There is no way to fix GSM buzz by mixer-setting modifications. So all suggested settings here may improve a little the volume of buzz during you're *not* speaking only, while relative ratio of buzz/voice level while speaking can't be changed by mixer settings.<br />
<br />
Some [http://lists.openmoko.org/pipermail/hardware/2008-August/000451.html hidden Calypso commands] may help with the echo problem.<br />
<br />
Workarounds:<br />
<br />
# Using a bluetooth headset is a possibility.<br />
# Using external GSM-antenna will stop buzz.<br />
<br />
<br />
Due to the multiple factors influencing the result of a single test, it's nearly impossible to find a setup that lets you compare for a decent "before / after" result. If you ever took an old analog TV portable to a place where you had to fiddle around with the antenna to try and make the snow and shadows vanish off the picture, you might have gotten a slight idea of what it's like to reproduce the same situation for decent tests. So probably most of the suggested alsa-improvements are mere random results. Even if they worked for provider A evidently, this doesn't mean there's any improvement by using same settings for provider B.<br />
<br />
This being said, here they are:<br />
<br />
The...<br />
<br />
# Better mixer settings: One confirmed good settings are here: http://www.mail-archive.com/support@lists.openmoko.org/msg00564.html. Please change accordingly in /usr/share/openmoko/scenarios/gsmhandset.state. Should eliminate/lessen echo and buzz problems. [[Neo alsamixer]] is the main article for setting the mixer settings.<br />
<br />
===== Better set of mixer settings =====<br />
<br />
Regarding 2. in the previous paragraph, here are my further tweaked settings:<br />
<br />
[mic volume & buzz problem]<br />
* 'Mono Playback Volume' (95)<br />
* 'Mono Sidetone Playback Volume' (2)<br />
* 'Mic2 Capture Volume' (3)<br />
[speaker volume & echo problem]<br />
* 'Speaker Playback Volume' (112)<br />
* 'Bypass Playback Volume' (5)<br />
<br />
Lowering Mono Sidetone eliminated the buzz problem better. Please try out and report if you have good success... --[[User:TimoJyrinki|TimoJyrinki]] 08:19, 16 October 2008 (UTC)<br />
<br />
==== Can't boot with discharged or missing battery ====<br />
<br />
Issue: Neo FreeRunner requires battery power to boot, because Neo FreeRunner consumes too much current while booting to boot with only a charger. Since charging isn't enabled until the Neo FreeRunner has booted, this means that a discharged battery can not be charged. One manifestation of this problem is a kernel panic (red LED flashes constantly) when trying to boot using the power button.<br />
<br />
Affects: Unknown.<br />
<br />
Status: By properly sequencing module power sequence, a software solution to this problem should exist.<br />
<br />
Fixed(?) with [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003799.html Werner Almesberger patches] - [http://lists.openmoko.org/pipermail/commitlog/2008-July/005403.html more here] [http://lists.openmoko.org/pipermail/community/2008-July/023392.html additional information]<br />
<br />
I think this patch finally fixes the problem:<br />
[http://www.abanet.ch/~hug/moko/uboot-battery/ Philipp Hugs patches]<br />
<br />
Workarounds:<br />
<br />
# Make sure that the battery never discharges completely<br />
# Use [[:Image:Nokia-charging-stand.jpg|external stand-alone charger]] (compatible with the Nokia BL-5C battery)<br />
# Boot the FreeRunner with an [[Neo_FreeRunner_Battery#Compatible_Replacement_Batteries|alternative battery]], or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.<br />
# Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.<br />
## Oscilloscope digital clip probes fit perfectly on the Freerunner's battery connectors. Make sure polarity is correct!<br />
# Some users have reported that Neo FreeRunner '''is''' able to boot on USB power alone using the NOR u-boot, thus: press AUX, plug USB power, select boot. Reports of success would be appreciated.<br />
## Does work with sequence described. If after pressing boot it just turns off again (happened a few times), then: press AUX, plug in USB power, cycle through the menu a few times to keep it from turning off without booting, after a minute or so press boot. [[User:Imrehg|Imrehg]] 08:34, 10 September 2008 (UTC)<br />
## This does indeed work with sequence described. After pressing boot, the screen went blank for a few seconds, but then the beast came to life again. That saved the day! [[User:Edictor|Edictor]]<br />
## Trifirmed. Neither USB connection nor wall charger was able to wake my phone. But in NOR u-boot it worked (connected to the computer). I think this trick hasn't failed to anyone. --[[User:Flamma|Flamma]] 12:11, 17 September 2008 (UTC)<br />
## Unfortunately this is not working for me. My FreeRunner has been off for a few weeks and completely dead. I tried various combinations of holding aux and plugging in to both wall and computer, no luck. Tried with and without the battery in place, no luck. Aux and power button / just power / aux then power. No luck... --[[User:Safire|Safire]] 6 November 2008<br />
## This is working ! It has prevent me from buying an external power charger. My freerunner had its battery discharged for about 2 weeks now, and I was able to boot and charge it. --[[User:JRD|JRD]] 23:37, 12 November 2008 (UTC)<br />
## It has worked for me ! I have booted to 2008.9 Om with discharged battery (after connecting the FR to power supply and waiting a few minutes until AUX button red light stopped flashing) using the NOR boot menu. Tried the same with NAND boot menu and worked also !!! Then I could charge the battery. -- [[User:Emsyr|Emsyr]] 3:23, 20 November 2008 (UTC)<br />
## I can boot to 2008.9 without battery and with USB connection = plug USB power (FR <-> PC) + press power button. However I cannot shutdown correctly. --[[User:Cynan|Cynan]] 13:43, 9 December 2008 (UTC)<br />
## I can boot to 2008.9 without battery and with USB connection: press AUX button, then plug USB power, then press power button (keeping AUX pressed). NOTE that battery was fully charged. The problem wasn't battery but corrupted environment in NAND u-boot: with battery IN, no access to NOR u-boot<br />
## Both my friend's freerunner and mine was completely discharged. This trick failed. Finally booted the freerunner with a BL-5C battery from an old nokia n-gage. With the power connected I then switched the batteries. --[[User:Unlotto|Unlotto]] 14:27, 25 January 2009 (UTC)<br />
See also:<br />
:[[Neo_FreeRunner_Battery|Neo FreeRunner Battery]]<br />
<br />
==== Battery discharges when charging completes ====<br />
<br />
Issue: If the Neo FreeRunner has been charging, when charging completes, it seems to drain the battery and not turn on charging again. This seems to be bug of PMU-registers setup, that shows up when PMU has to handle bat autonomously (=suspend). There might be issues our current scheme relies on wake-interrupt at bat-full which doesn't succeed, or something like that.<br />
<br />
Affects: Unknown.<br />
<br />
Status:<br />
<br />
Workarounds:<br />
<br />
# When the battery is full, disconnect the charger<br />
<br />
See also:<br />
<br />
==== Suspend/resume corrupts SD card's partition table ====<br />
<br />
Issue: Suspend/resume corrupts the partition table of the SD card<br />
<br />
Affects: Unknown.<br />
<br />
Status:<br />
<br />
[[https://docs.openmoko.org/trac/ticket/1802#comment:6 Patched kernel]] might solve the problem<br />
<br />
Workarounds:<br />
<br />
# [[https://docs.openmoko.org/trac/ticket/1802#comment:5 Script]] as a temporary workaround<br />
<br />
See also:<br />
<br />
:[[https://docs.openmoko.org/trac/ticket/1802 trac ticket]]<br />
<br />
==== Some SIMs Don't Work ====<br />
<br />
Issue: There are reports that some users cannot register with their GSM network when using certain SIM cards. See for example http://lists.openmoko.org/pipermail/community/2008-July/020370.html<br />
<br />
It is possible that there is more than one issue involved here. The observed problems ''might'' (i.e. some items are only speculation at this point) be caused by:<br />
<br />
* User error, not inserting the SIM in the correct orientation or not sliding the holder to the 'locked' position<br />
<br />
* Software issues that result in a locked SIM (not properly prompting the user for a PIN and then passing this to the SIM)<br />
<br />
* Mechanical issues with the SIM holder that prevent the pins from making reliable contact with the pads on the SIM. Note that only 6 of the 8 pins are used, and the remaining two are not connected.<br />
<br />
* Electrical incompatibility (some tests show problems with 1.8V SIMs while 2.9V ones work OK)<br />
<br />
* Firmware bugs in the TI Calypso GSM chipset. Note that one issue in this category was found and fixed on the GTA01 devices (#666 in Trac), and that specific problem should not affect the FreeRunner.<br />
<br />
* Defective SIMs, i.e. ones that do not comply with the applicable standards and are acknowledged as being defective by the carrier (even if they happen to work in some phones).<br />
<br />
* You may have true 3G operating at 2100 and your sim doesn't fallback to GSM. The Phone works on 850/1800/1900 or 900/1800/1900.<br />
<br />
See also:<br />
* http://wiki.openmoko.org/wiki/Carriers/ATT<br />
* http://wiki.openmoko.org/wiki/Carriers/Rogers<br />
<br />
Affects: Only a subset of users (details unknown).<br />
<br />
Status: Fixed in GSM firmware moko10-beta2 or later. See [[GSM/Flashing]] for instructions. Please add your information to [[FreeRunner_unable_to_work_with_3G_SIM_cards]] or [[GSM network registration]]<br />
<br />
Workarounds:<br />
<br />
# Please document your existing SIM card and provider in the table [[FreeRunner_unable_to_work_with_3G_SIM_cards|here]].<br />
# If the table mentioned above shows any SIM cards known to work with your provider, make note of these numbers.<br />
# Contact your network provider and request a new SIM card. You may wish to print out the table mentioned above and bring it with you to the store.<br />
# Add your experience with the new SIM card to the table mentioned above.<br />
<br />
=== Known/Accepted Issues ===<br />
<br />
This section lists items that are acknowledged as being less than ideal, but are considered to be acceptable in the shipping product. They will not be discussed in detail on this page.<br />
<br />
* Poor performance + slow bus speed of the Glamo GPU - discussed to death on the mailing lists and IRC.<br />
** stable-2.6.26 branch of kernel has wait states lowered, core speed increased from 50MHz to 80MHz and memory speed from 80MHz to 90MHz (the latter is also in stable branch) - these lessen the problem a bit, though it's slow still<br />
* [http://lists.openmoko.org/pipermail/hardware/2008-April/000055.html GPS antenna switch] driven out-of-spec - does not appear to have a significant effect on device performance<br />
* Poor low-frequency audio response with low-impedance headphones, e.g. as discussed in this thread: http://lists.openmoko.org/pipermail/openmoko-kernel/2008-March/001999.html (NOTE - this thread refers to pre-mass-production devices)<br />
** Can be fixed to an semi-acceptable level (if not high fidelity most probably) by adjusting "Bass Volume" to full (15) and "Bass Filter" to "100Hz @ 8kHz" (bass will be boosted <= 600Hz when playing back at 48kHz) or "200Hz @ 8kHz" (<= 1200Hz @ 48kHz). The default is 130Hz @ 48kHz and does not help much with the more wider scope of low frequencies.<br />
** Ideally someone would record output and find out which setting produces best output, ie. compensating for the loss of low frequencies without boosting too high frequencies with this "bass" boost.<br />
<br />
Actually with 16 Ohm headphones the cutoff frequency is more than 2kHz, so even 1200Hz @ 48kHz seems to be not appropriate.<br />
If you have 30 Ohm, it might be just correct setting.<br />
<br />
=== Resolved Issues ===<br />
<br />
These are issues that have been discussed in the past, but have been fixed (or turned out not to be a problem) for the mass-produced devices.<br />
<br />
* Excessive LED current - Some early units lacked a current-limiting resistor for the LEDs. This has been fixed for the production units.<br />
* Battery life - At this time it appears that the FreeRunner battery life will be acceptable once suspend/resume support has been implemented in software.<br />
* slow GPS TTFF - see [[GPS Problems]]<br />
==== Empty NOR Flash ====<br />
<br />
Issue: NOR flash (backup copy of u-boot) is not programmed. [http://docs.openmoko.org/trac/ticket/1568 #1568]<br />
<br />
Affects: Unknown - maybe only 1 or 2 devices? Also need to confirm that the bug report was from a mass-production unit rather than an earlier prototype.<br />
<br />
Status: Solved. The new devices are tested better if they have the NOR flashed programmed and aren't shipped if the test fail.<br />
<br />
Workarounds: Use the NAND copy of u-boot and be careful not to brick the device unless a debug-board is available.<br />
<br />
<br />
==== Debug board has wrong vendor/product ID ====<br />
<br />
Issue: A debug board is not reporting the expected USB Vendor/Product ID.<br />
<br />
Affects: Only [http://lists.openmoko.org/pipermail/device-owners/2008-July/001775.html one report] has been seen so far.<br />
<br />
Status: Probably a single case scenario.<br />
<br />
Workarounds: Edit configuration files (e.g. openocd.conf) to use the IDs that the board is reporting.<br />
<br />
== List of "Current issues" Imported from the "Community update page" ==<br />
(to be sorted)<br />
<br />
The information below has been collected from various sources, feel free to add questions and comments here.<br />
<br />
===GPS Performance of the FreeRunner===<br />
The poor GPS performance on the FreeRunner has been traced to an<br />
interaction between the microSD card and the GPS unit. A software<br />
and a hardware fixes are available, see [[GPS Problems]].<br />
<br />
===GTA02 battery status===<br />
While writing a device driver for the new battery which provides an accurate counter of the charge state of the [[GTA02]], the driver developer discovered that the device driver does not get a reading of the charge state due to a very long response time with only one I/O signal when trying to read the charge state. To be able to read the battery status properly, it has been written that it will be necessary to re-design that part of the GTA02 for hardware version GTA02A5 to use two I/O signals to reduce the response time (one for transmitting commands, one for receiving data?). This was fixed two months ago (see [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=957#c1 Bug 957]).<br />
<br />
===Delivery of a GSM firmware update for the 3G SIM bug ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666 #666])===<br />
<br />
A bug in the GSM firwmare of Neo 1973 caused some 3G SIM cards to not work with Neo 1973. This Neo 1973 GSM firmware update can only be installed by an Openmoko employee due to licensing issues.<br />
<br />
This fix is already present in the Neo FreeRunner firwmare, and thus the Neo 1973 GSM firmware update is not required for the Neo FreeRunner. In fact since the firmware differs between the Neo 1973 and the Neo FreeRunner, it would very likely make the GSM module unusable.<br />
<br />
There seem to be other GSM issues on the Neo FreeRunner. See [[#Some_SIMs_Don.27t_Work|Some SIMs Don't Work]] above.<br />
<br />
=== SMedia 3362 Documentation & OpenGL ES Drivers ===<br />
There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and Openmoko developers will not be writing one in the near future (although they have not ruled it out in the long-term).<br />
<br />
Documentation for the SMedia 3362 has been promised ([http://lists.openmoko.org/pipermail/community/2007-September/010175.html see this post]). However, this refers to documentation Openmoko developers will be writing themselves, not the technical documentation SMedia have provided Openmoko with. The Openmoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See [http://lists.openmoko.org/pipermail/community/2007-November/011349.html this post] for details)<br />
<br />
=== Power Management on the Neo1973/FreeRunner===<br />
The current battery life of the Neo1973 and FreeRunner is not satisfactory. A lot of changes seem to be necessary to the kernel, drivers and related user-space applications. Hopefully the situation will improve over time.<br />
<br />
=== Draws too much current from USB ===<br />
It may be that the Neo draws too much current from your USB host/hub, and that the USB host/hub switches off to prevent damages. <br />
<br />
The behaviour is controlled by a complex interaction between soft- and hardware, see [[Forcing fast charge mode]] and [[USB host]]. It may be that the host negotiates more power than the Hub is willing to provide. In case of problems, try to limit the current to e.g. 400mA.<br />
<br />
<br />
[[Category:Neo FreeRunner Hardware]]</div>Rainglaszhttp://openmoko.org/wiki/ToolchainToolchain2009-01-29T22:23:00Z<p>Rainglasz: /* Downloading and installing */ Link to BitBake page</p>
<hr />
<div>{{Languages|Toolchain}}<br />
<br />
<br />
= Introduction =<br />
<br />
A toolchain is a set of tools that allows you to compile code. For Openmoko, we have to differentiate between the following use-cases:<br />
<br />
;(a) Developing a single application<br />
:For this, you should use a prebuilt toolchain from the Openmoko project. On this page you can find a recipe to get started with this toolchain leading you through a series of steps to compile a project and run it on your target device. (You might have heard about ''OpenEmbedded'', however as an application programmer, you should '''not''' be using OpenEmbedded.)<br />
;(b) System Integration and customizing a distribution<br />
:For this task, you should use [[OpenEmbedded]] which builds its own cross compiler during the bootstrapping/build process. System Integration and customizing a distribution is out of scope of this page.<br />
<br />
=Basic toolchain usage=<br />
<br />
==Prerequisites==<br />
<br />
You should be reasonably familiar with Linux and its command line tools, have an x86-compatible computer with at least 1G of free disk space. You should have experience with compiling programs from source using your local compiler. The remainder of this document will also assume you have write access in your home directory (~) and <tt>/usr/local/</tt> (becoming root if needed). If any of this is not the case, please call your local administrator for help.<br />
<br />
Last but not least you should have a working setup that allows you to compile native software packages using the autotools build system (the triade of '''./configure, make, make install''').<br />
<br />
A (partial) list of required packages -- please append as necessary:<br />
<br />
* For most Linux version you might only need to install the packages<br />
** autoconf, automake<br />
** binutils, gcc, gcc-c++<br />
** libtool<br />
** ccache<br />
** intltool<br />
<br />
* For Ubuntu 8.04 ( Previous versions don't support libmokoui2 ) the following is required:<br />
sudo apt-get install gcc g++ autoconf automake binutils libtool libglib2.0-dev \<br />
ccache libxrender-dev intltool libmokoui2-dev libgconf2-dev mtools fakeroot alien check<br />
<br />
* For Ubuntu 8.10 the following is additionally required, install also those above:<br />
sudo apt-get install uboot-mkimage<br />
<br />
* For Fedora-Core the following is required, while logged in as <tt>root</tt>:<br />
yum install gcc gcc-c++ autoconf automake binutils libtool glib2-devel \<br />
ccache libXrender-devel intltool GConf2-devel mtools gettext-devel<br />
Fedora-Core does not appear to have <tt>libmokoui2</tt> available.<br />
<br />
* For Debian (Sid) do (as root): <br />
apt-get install build-essential ccache autoconf automake autotools-dev libtool \<br />
gettext intltool curl uboot-mkimage mtools fakeroot alien check libglib2.0-dev \<br />
libxrender-dev libgconf2-dev<br />
<br />
==Downloading and installing==<br />
<br />
{{Note|If you wish to improve an existing Openmoko application and you are running Debian or Ubuntu i386 (i.e. you can install a .deb), you may wish to skip the below and instead use:<br />
[http://andreasdalsgaard.blogspot.com/2008/07/openmoko-development-in-5-minutes.html Openmoko application development in 5 minutes] by Andreas Dalsgaard. (based on the 2007.2 stack)}}<br />
<br />
The prebuilt toolchain can be downloaded from [http://downloads.openmoko.org/toolchains downloads.openmoko.org]:<br />
<br />
* Creating a destination directory can be anywhere, but for example:<br />
<br />
mkdir ~/sources<br />
cd ~/sources<br />
<br />
* Depending on your CPU type (x86_64 or i686) download the proper package:<br />
<br />
wget http://downloads.openmoko.org/toolchains/openmoko-x86_64-arm-linux-gnueabi-toolchain.tar.bz2<br />
or<br />
wget http://downloads.openmoko.org/toolchains/openmoko-i686-arm-linux-gnueabi-toolchain.tar.bz2<br />
<br />
Next, you want to extract it on your filesystem. This toolchain is ''not'' relocatable, it needs to be installed into <tt>/usr/local/openmoko/</tt>.<br />
Now you have the following options:<br />
<br />
* Extract it directly as root, so use command "su" first (or prefix the tar command with "sudo" when you are using Debian/Ubuntu):<br />
<br />
cd /<br />
tar -xjvf ~/sources/openmoko-XYZ-arm-linux-gnueabi-toolchain.tar.bz2<br />
<br />
* On Debian-based systems (e.g. Ubuntu), you can use alien(+fakeroot) to create an easy-to-uninstall package from this .tar.bz2:<br />
<br />
bunzip2 openmoko-*-arm-linux-gnueabi-toolchain.tar.bz2<br />
gzip openmoko-*-arm-linux-gnueabi-toolchain.tar<br />
fakeroot alien -d openmoko-*-arm-linux-gnueabi-toolchain.tar.gz<br />
sudo dpkg -i openmoko_*-arm-linux-gnueabi-toolchain*.deb<br />
<br />
* The prebuilt toolchain is for x86_64 or i686. If you wanted, you could build it on your own with OE, using [[BitBake]]:<br />
<br />
bitbake meta-toolchain-openmoko<br />
<br />
Finally, everytime you want to use this toolchain, you need to alter some environment variables, so that your tools will be found. The toolchain provides a script to do that, so the only thing you need to do is to [http://learnlinux.tsf.org.za/courses/build/shell-scripting/ch10s02.html source] it.<br />
Note that if you are not using a "sh" or "bash" shell (check with "echo $SHELL") that you need<br />
to start "sh" or "bash" first.<br />
<br />
. /usr/local/openmoko/arm/setup-env<br />
<br />
* At least, you should add /usr/local/openmoko/arm/bin to your $PATH variable, otherwise the next steps won't work (om-conf and make). <br />
export PATH=$PATH:/usr/local/openmoko/arm/bin <br />
Note: This is will only last for your current session. Add it to your shell startup scripts to make it permenant (~/.bashrc for instance).<br />
<br />
==Installing New Libraries==<br />
<br />
Openmoko toolchain didn't include many libraries in default. However, it can download and install library what has already existed in Openmoko repository. (It refer to [http://downloads.openmoko.org/repository/testing/ Testing Repository] by default.)<br />
<br />
*You need to alter some environment variables before you download libraries.<br />
. /usr/local/openmoko/arm/environment-setup<br />
<br />
*First, update the opkg database (Notice, you should use alias '''opkg-target''' but not '''opkg'''. If you get an "Could not obtain administrative lock" error, try to become root with "sudo su" and don't forget to rerun the scripts to set your environment variables if necessary.)<br />
opkg-target update<br />
<br />
*Second, select a package what you want. Let's use edje as an example. If you want develop an project which use edje of Enlightenment, you can use '''opkg-target list''' to print out how many packages you can have. Of course, command '''grep''' will help you a lot.(Remember, you should install -dev package but not only libedje.)<br />
opkg-target list |grep edje-dev<br />
<br />
*Third, install it<br />
opkg-target install libedje-dev<br />
*Fourth, have a cup of coffee and wait.<br />
<br />
==Building a sample project==<br />
<br />
To build the sample project you need to install libmokoui2-dev and gconf-dbus-dev in your opkg environment. Setup your environment like described there [http://wiki.openmoko.org/wiki/Toolchain#Installing_New_Libraries]. Now install the libarys with the following command:<br />
opkg-target install libmokoui2-dev gconf-dbus-dev<br />
<br />
In a chosen destination directory (in this example ~/):<br />
<br />
* copy the downloaded sample application source:<br />
<br />
cp -r /usr/local/openmoko/source/openmoko-sample2 ~/<br />
<br />
* Remember to set the proper environment variables (again with "sh" or "bash") for openmoko:<br />
<br />
. /usr/local/openmoko/arm/setup-env<br />
<br />
* I came to the conclusion that more has to be done before the next step.<br />
<br />
opkg-target update<br />
opkg-target install libedje-dev<br />
opkg-target install packagekit-dev<br />
opkg-target install edbus-dev<br />
opkg-target install libetk-dev<br />
opkg-target install libts-dev<br />
<br />
* One can chown -R <your-name>.<your-name> /usr/local/openmoko/arm, and<br />
everything should work under the non-root account. Here is a useful link if you have problems with the command below ( https://kerneltrap.org/mailarchive/openmoko-devel/2008/9/17/3318834 )<br />
<br />
* You need to create a build configuration for this application. This also checks if all needed libraries, tools, etc.. is available on your system. If this fails see the notes about the needed packages in the section "Prerequisites" mentioned earlier.<br />
<br />
om-conf openmoko-sample2<br />
<br />
* Optionally now you can modify the source code in openmoko-sample2/src. Before the next step, go into the sample directory.<br />
<br />
cd openmoko-sample2<br />
<br />
* If you are using an older version of the toolchain, you may have to create the makefile by running "./autogen.sh". Otherwise, to build the application from the source code just type:<br />
<br />
make<br />
<br />
* If there are errors (i.e. "You need to install gnome-common from the GNOME CVS") deal with them. Also see "Troubleshooting" section at the end of this page for known issues.<br />
<br />
<br />
If you want to install this project on host for staging usage later, a shared library, for example, you can do the following to install it into a given configured prefix.<br />
om-conf --prefix=/usr/local/openmoko openmoko-sample2<br />
cd openmoko-sample2<br />
make install<br />
<br />
==How to create your own project from the sample project==<br />
<br />
In order to build your own project by using openmoko-sample2 files, some changes are needed:<br />
<br />
* copy the downloaded sample application source<br />
<br />
cp -r /usr/local/openmoko/source/openmoko-sample2 ~/<br />
<br />
* rename the folder with the name of your project (in this example your-project-name) and delete old sample files <br />
<br />
mv openmoko-sample2 your-project-name<br />
cd your-project-name<br />
cd src<br />
rm *.c<br />
<br />
* copy your sources (in this example your-sources) into src/<br />
<br />
cp your-sources .<br />
cd ..<br />
<br />
* now in the main folder modify autogen.sh by updating the following lines<br />
<br />
PKG_NAME="your-project-name"<br />
<br />
* modify configure.ac by updating the following lines ('main.c' should be the main file in your project)<br />
<br />
AC_INIT(your-project-name, 0.0.1, http://www.openmoko.org/) <br />
AC_CONFIG_SRCDIR(src/main.c)<br />
<br />
* go into data/ folder and rename these files with the name of your project<br />
<br />
cd data<br />
mv openmoko-sample.png your-project-name.png<br />
mv openmoko-sample.desktop your-project-name.desktop<br />
<br />
* modify Makefile.am inside data/ by updating the following lines<br />
<br />
dist_desktop_DATA = your-project-name.desktop<br />
dist_appicon_DATA = your-project-name.png<br />
<br />
* modify Makefile.in inside data/ by updating the following lines<br />
<br />
dist_desktop_DATA = your-project-name.desktop<br />
dist_appicon_DATA = your-project-name.png<br />
<br />
* modify your-project-name.desktop by updating the following lines<br />
<br />
Name=your-project-name<br />
Encoding=UTF-8<br />
Version=0.0.1<br />
Type=Application<br />
Exec=your-project-name<br />
<br />
* and by adding the following line<br />
<br />
Icon=your-project-name<br />
<br />
* move into src/ folder<br />
<br />
cd ..<br />
cd src<br />
<br />
* modify Makefile.am by updating the following lines<br />
<br />
bin_PROGRAMS = your-project-name <br />
your_project_name_SOURCES = \ <br />
main.c <br />
your_project_name_LDADD = @DEPENDENCIES_LIBS@<br />
<br />
* be sure to put instead of main.c all your .c and .h files and modify all the '-' characters with '_' in the variable names<br />
<br />
==Packaging your application==<br />
<br />
We have included a script to make an ipkg out of your application. Note that this is not needed to test your application on the Neo (for that you can just scp the resulting binary and data over), however it's very handy if you want to distribute your application to others.<br />
<br />
om-make-ipkg openmoko-sample2<br />
<br />
Now you got openmoko-sample2_0.1_armv4t.ipk , you can `scp' it to your<br />
Neo and install it:<br />
<br />
scp openmoko-sample2_0.1_armv4t.ipk root@192.168.0.202:<br />
ssh root@192.168.0.202 opkg install openmoko-sample2_0.1_armv4t.ipk<br />
<br />
Note that while you can redistribute the generated ipkg, be aware that this is a bare-bones ipk that contains no further information, i.e. you will lack library dependencies. See below how to fix this.<br />
<br />
You can also supply the version number, a description, and an author / contacts string in a control file:<br />
<br />
om-make-ipkg myapp myapp_control<br />
<br />
A template of myapp_control:<br />
<br />
Package: $appname<br />
Version: 0.1<br />
Description: package built by openmoko toolchain<br />
Section: openmoko/applications<br />
Priority: optional<br />
Maintainer: $USER<br />
Architecture: armv4t<br />
Homepage: http://www.openmoko.org/<br />
Depends: <br />
Source: ${SRC}<br />
<br />
==Where to go from here==<br />
<br />
Using the external toolchain is an easy way to build applications for your Neo. If you are familiar with this procedure, you might also want to look into<br />
* Using [[Qemu]] to test your applications in an emulated environment<br />
** Ubuntu users might prefer to look at [[Automatic_emulation_in_Ubuntu]]<br />
* Using [[Host-based_development_with_Xoo_and_Xephyr|host-based development]] to improve your efficiency<br />
* Using [[OpenEmbedded]] to customize your Openmoko distribution image<br />
<br />
=Advanced topics=<br />
==Building Openmoko Kernel from git repo using Toolchain==<br />
<br />
You may build the newest 2.6.28 kernel with these commands:<br />
<br />
git clone git://git.openmoko.org/git/kernel.git linux-2.6<br />
cd linux-2.6<br />
git checkout -b mystable origin/andy-tracking<br />
mkdir GTA02<br />
cp arch/arm/configs/gta02-moredrivers-defconfig GTA02/.config<br />
./build GTA02 dummy<br />
<br />
The ''dummy'' option is required for the modules to be nicely packaged into a .tar.gz package that can be extracted on the target, in addition to flashing/installing the kernel. The "dummy" just means "some parameter given", for which there is a check in the code eventually for some reason...<br />
<br />
You may need to edit the ./build script for the toolchain directory.<br />
<br />
Read more information about the different branches of Openmoko's Linux kernel at: http://git.openmoko.org/?p=kernel.git;a=summary<br />
<br />
=== Old troubleshooting information ===<br />
<br />
If it fails with error message "arm-angstrom-linux-gnueabi-ld: unrecognized option '-Wl,-rpath-link,/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/lib'" until /usr/local/openmoko/arm/setup-env is modified. LDFLAGS should be changed from:<br />
<br />
export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-rpath-link,${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-O1"<br />
<br />
to:<br />
<br />
export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -rpath-link ${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -O1"<br />
<br />
I also had to change the 'build' script to hardcode the path to the compiler.<br />
<br />
==Using toolchain provided libraries==<br />
Add the necessary libraries to the _LDADD field in src/Makefile.am, for example:<br />
openmoko_sample2_LDADD = @DEPENDENCIES_LIBS@ -lmokogsmd2<br />
<br />
make sure to run om-conf again after this.<br />
<br />
==Installing additional libraries into the toolchain==<br />
<br />
Sooner or later you will want to compile an application that has dependencies which can't be fulfilled by the precompiled toolchain, e.g. some obscure libraries.<br />
<br />
In that case, feel free to request the inclusion of additional libraries into the next release of the Openmoko toolchain. Until then, here is how you enhance your already installed toolchain. Say, we want to add the library called liburiparse:<br />
<br />
cd ~/source<br />
wget http://downloads.sourceforge.net/uriparser/uriparser-0.6.0.tar.bz2<br />
tar xjf uriparser-0.6.0.tar.bz2<br />
cd uriparser-0.6.0<br />
./configure --host=arm-angstrom-linux-gnueabi \<br />
--prefix=/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr<br />
make<br />
make install<br />
<br />
That's it.<br />
<br />
==Getting your application packaged by OE==<br />
<br />
If you have written a cool application which you want to share with others, the best way to do that is to<br />
<br />
# upload your application source code to a public location<br />
# submit a [[BitBake]] recipe to [[OpenEmbedded]], preferably via the [http://bugzilla.openembedded.org OpenEmbedded bugtracker].<br />
<br />
See also [[Customizing the Openmoko Distribution]].<br />
<br />
==Troubleshooting==<br />
<br />
* Some Versions of the Toolchain have corrupt .la files. If you compile an application using the Toolchain and you receive a '/space/fic/openmoko-daily/neo1973/work/armv4t-angstrom-linux-gnueabi/pango-1.18.3-r0/pango-1.18.3/pango/libpangoft2-1.0.la' error, you are affected. To fix that you should go to your "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib" directory and open the affected .la files and change "/space/fic..." to "/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib". You have to fix more than one .la file. For the pango error you have to change "libpangocairo-1.0.la", but there are more corrupt .la files.<br />
<br />
Attached is a beta fix for the .la problem. Untar the .tar.bz2 as root, and execute the following bash script as root:<br />
<br />
#!/bin/sh<br />
DIR=/usr/local/openmoko/arm<br />
for la in `find $DIR -iname \*.la`; do<br />
dependency_libs=<br />
. $la<br />
for lib in $dependency_libs ; do<br />
delib=`echo $lib | grep -E .la$`<br />
if [ -z $delib ] ; then<br />
echo -n<br />
elif [ -f $delib ]; then<br />
echo -n<br />
else<br />
basedelib=`basename $delib`<br />
replacedelibs=`find $DIR -iname $basedelib`<br />
found=0<br />
for replacedelib in $replacedelibs ; do<br />
if [ $replacedelib == $delib ]; then<br />
found=1<br />
fi<br />
done<br />
if [ $found -gt 0 ] ; then<br />
echo -n<br />
else<br />
sed_delib=`echo $delib | sed 's/\//\\\\\//g'`<br />
sed_replacedelib=`echo $replacedelib | sed 's/\//\\\\\//g'`<br />
# A bit slow, we could chain expressions for speed. :)<br />
cp $la $la.old<br />
cat $la | sed "s/$sed_delib/$sed_replacedelib/g" > $la.new<br />
mv $la.new $la<br />
rm $la.old<br />
fi<br />
fi<br />
done<br />
done<br />
<br />
* If you can't get the toolchain working in your distro (for example if you keep bumping into strange autotools issues), you can set up the toolchain inside a Debian chroot, which should provide reasonably standard environment. There's a guide for it: http://linux.fjfi.cvut.cz/~zub/debian-chroot-toolchain.txt<br />
* If you get something similar:<br />
../libtool: X--tag=CC: command not found<br />
<br />
under Ubuntu 8.10. Try do this:<br />
<br />
sudo apt-get remove libtool<br />
<br />
wget http://ftp.sjtu.edu.cn/ubuntu/pool/main/libt/libtool/libtool_1.5.26-1ubuntu1_i386.deb<br />
or<br />
wget http://ftp.sjtu.edu.cn/ubuntu/pool/main/libt/libtool/libtool_1.5.26-1ubuntu1_amd64.deb<br />
<br />
sudo dpkg -i libtool_1.5.26-1ubuntu1_i386.deb <br />
<br />
The original message [http://lists.openmoko.org/pipermail/devel/2008-December/003530.html here]<br />
<br />
* Please use the [http://lists.openmoko.org/mailman/listinfo/openmoko-devel Openmoko-Devel] mailing list.<br />
<br />
[[Category:Application Developer]]<br />
<br />
[[Category:Application Developer]]</div>Rainglaszhttp://openmoko.org/wiki/Openmoko:Community_PortalOpenmoko:Community Portal2009-01-29T22:18:39Z<p>Rainglasz: /* In English */ Link to Community Updates at top inserted</p>
<hr />
<div>{|align=right<br />
|__TOC__<br />
|}<br />
<br />
{{Todo| This page duplicates [[Development resources]]. It belongs to the main namespace, so naming it "Openmoko:***" is bad. And it's not a [http://en.wikipedia.org/wiki/Portal:Contents/Portals portal in Wiki sense]}}<br />
<br />
= In English =<br />
<br />
See also the [[Community Updates]] board <br />
<br />
== Mailing lists ==<br />
<br />
There are several [http://lists.openmoko.org/mailman/listinfo/ Mailing lists]. Archives of these lists can be searched with [http://openmoko.markmail.org/ Markmail]. There is a [http://lists.openmoko.org/nabble.html Nabble web interface] to read and post to the lists.<br />
<br />
You should ask for help on the [https://lists.openmoko.org/mailman/listinfo/support support mailing list].<br />
<br />
The [http://lists.openmoko.org/pipermail/community/ openmoko community mailing list] is perhaps the most active.<br />
As of July 2008, its volume amounts to dozens of messages per day. Openmoko people are there too. When posting about a specific distribution, please start the subject line with its name between bracket: [FSO], [2008.9]...<br />
<br />
Lots of Debian and FSO discussions among the pkg-fso team takes place on the [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland Smartphones-userland] list.<br />
<br />
== IRC ==<br />
<br />
There is always a good group in the IRC channel '''#openmoko on FreeNode'''. If you aren't an IRC-er, you might want to review the discussions anyways:<br />
<br />
* [http://logs.nslu2-linux.org/livelogs/openmoko.txt Current 24h live log]<br />
* [http://logs.nslu2-linux.org/livelogs/openmoko-prev.txt Previous 24h log]<br />
* [http://logs.nslu2-linux.org/livelogs/openmoko/ Archives back to 29 November 2006]<br />
<br />
(Courtesy of the NSLU2-Linux project)<br />
<br />
Within the time contstraints of middle Europe, the Freenode channel #neo1973-germany is also active and members switch to english on demand.<br />
<br />
You can also hang out in #openmoko-cdevel (the community developers channel) on chat.freenode.net if you have development questions.<br />
<br />
== Blogs aggregator ==<br />
<br />
The blogs of openmoko fans and developpers are aggregated at [http://planet.openmoko.org/ planet.openmoko.org]. Only posts tagged ''openmoko'' are syndicated. The planet is multilingual. To get your blog added, please open a ticket on the [http://admin-trac.openmoko.org/trac admin-trac] (you will need to open an account first).<br />
<br />
== Newsletters ==<br />
<br />
* [[Community Updates]] try to sum up what has been happening all over. Updates are also mailed to the openmoko-community mailing list, and major updates are also sent to the announce list.<br />
<br />
* Wolfgang Spraul tries to give a weekly summary of what's going on in Openmoko. You can follow it at the devel mailing list or follow the [[Weekly Engineering News]] page.<br />
<br />
== Forums and Jabber MUC==<br />
<br />
See [[Discussion Forums]]. There is very little activity at the [http://forums.makeopensource.com/ The Unofficial OpenMoko Forums], but others forums are more busy.<br />
<br />
== Wiki ==<br />
<br />
The old community wiki is at http://www.linuxtogo.org/gowiki/OpenMoko/, since the release of the official wiki at http://wiki.openmoko.org/, it should no longer be used for OpenMoko. Please help integrating the content of the old wiki into this wiki. Please note that you cannot just copy from the old wiki, as the old wiki is (unfortunately) not clearly licensed and the content on this wiki is licensed under GNU FDL. You will instead need to rewrite the articles.<br />
<br />
When you have integrated/rewritten an article, please update the old wiki with clear information that you have moved the information, so others do not update the old page.<br />
<br />
== Git server ==<br />
<br />
Bootloader(s), kernel(s), driver(s), phone stack(s), build tools: the Real Stuff is browsable via gitweb at http://git.openmoko.org/.<br />
<br />
== Projects forge ==<br />
<br />
OpenMoko maintains a GForge at http://projects.openmoko.org/ as a free hosting service for community-contributed applications.<br />
<br />
== Applications directory ==<br />
<br />
http://opkg.org<br />
<br />
= In other languages =<br />
<br />
In alphabetical order, there are many more other ressources. <br />
<br />
== French ==<br />
<br />
* [http://openmoko-fr.org/wiki/index.php/Bienvenue wiki]<br />
* [http://openmoko-fr.org/forum/index.php forums]<br />
* [http://openmoko-fr.org/blog/ blog]<br />
* [irc://chat.eu.freenode.net/openmoko-fr IRC channel]<br />
<br />
== German ==<br />
<br />
The German Neo1973 community created a Trac-based web site with SVN version control for their community projects: http://neo1973-germany.de/ The most notable project is Zad, which consists of a GUI and daemons for GSM/GPRS muxing, GSM, GPS and more, written using Enlightment for smooth, smooth, fast, alpha-blended graphics and glib and dbus for daemons, but the actual code of the project is all python. And yes, you can even make phone calls with it (even without "echo").<br />
<br />
<br />
FreeYourPhone - erstes deutsches Openmoko Forum: http://freeyourphone.de<br />
<br />
== Polish ==<br />
<br />
* [http://openmoko.opendevice.org wiki]<br />
* irc-room #openmoko.pl@freenode<br />
* [http://openmoko.opendevice.org/planeta planet]<br />
* [http://tytanick.net/openmoko forums]<br />
* Users [http://tinyurl.com/62ja5k map]<br />
<br />
== Spanish ==<br />
<br />
There is a spanish mailing list.<br />
<br />
= See also =<br />
<br />
* [[Development_resources]]<br />
* The large and growing list of [[Openmoko Local Groups| local users group]].<br />
<br />
[[Category:Community]]</div>Rainglaszhttp://openmoko.org/wiki/DistributionsDistributions2009-01-29T22:15:52Z<p>Rainglasz: /* See also */ Link to Community:Updates (hard to find, few links)</p>
<hr />
<div>{{Languages|Distributions}}<br />
<br />
{|align=right<br />
|__TOC__<br />
|}<br />
<br />
== About distributions ==<br />
Openmoko distributions are designed to run on various mobile devices, with the primary aim of supporting Openmoko Inc.'s [[GTA01:Neo 1973|Neo 1973]] and [[Neo FreeRunner]] phones. They are GNU/Linux distributions -- complete operating systems including user applications. You can install any of them on your phone or even have a dualboot system with two distributions installed. For downloads see [[Download]], for installation instructions see [[Flashing the Neo FreeRunner]].<br />
<br />
Besides, Openmoko distributions also run on [[Supported devices|other]] mobile devices and some other software distributions also run on the phones of Openmoko Inc.<br />
<br />
=== Choosing a distribution ===<br />
* Official/current. As of December 2008, the phones ship with [[Om 2007.2]]. It is not supported by Openmoko Inc. anymore. But community developers continue to work on its phone stack in the [[SHR]] project. The branch currently supported by Openmoko Inc. is [[Om 2008.12 Update]], which is the second minor upgrade of [[Om 2008.8]] (the version formerly named ''ASU'').<br />
* Official/future. The current trunk tip is a "base image" on which the next major release should be based. This next release can be previewed by installing milestones of the [[FSO]] - Free Smartphone.Org project. If you want to develop anything that last, your platform is [[FSO]] (and the choice between EFL, GTK+, Qt, Java, Python or whatever is open). The [[Debian]] packaging team also track that branch.<br />
* Openmoko community. Based on [[Om 2008.8]], the community made the [[FDOM]] distribution by adding lots of fixes and applications to it. Most new users find [[FDOM]] the most comprehensive and functional distribution.<br />
* Other community. The FreeRunner is also a reference platform for TrollTech's ''Qt Extended'' (formerly [[Qtopia]]) distribution. If you want "just a working phone", try [[Qtopia]].<br />
* Other communities. [[Android]] work is in progress; [[Debian]] and [[Gentoo]] are for people who do not need to ask which distribution they should use.<br />
<br />
<br />
{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"<br />
|<font color=white>Distributions</font><br />
|-<br />
! style='background-color:#333333;color:#FFFFFF'|<br />
<div align=left><br />
* <font color='#BBBBBB'>Openmoko (official)</font><br />
** [[Om 2008.12 Update]]<br />
** [[Om 2008.9 Update]]<br />
** [[Om 2008.8]]<br />
** [[Om 2007.2]]<br />
** [[OpenmokoFramework|FSO]]<br />
* <font color='#BBBBBB'>Om Community</font><br />
** [[SHR]]<br />
** [[FDOM]]<br />
* <font color='#BBBBBB'>Other</font><br />
** [[Qtopia]]<br />
** [[Debian]]<br />
** [[Gentoo]]<br />
** [[Android]]<br />
** [[Hackable:1]]<br />
</div><br />
|-<br />
|}<br />
<br />
=== Please note ===<br />
<br />
* Stable in the FreeRunner world does not mean the same thing as stable in the Debian world.<br />
* Most distributions use the same bootloader, kernel, drivers and hardware. Therefore, the same low level bugs are commonly found in all distributions. The latest and greatest software usually has most bug fixes, plus a whole set of new fresh bugs.<br />
* Most of these distributions also have package repositories. It is a BAD idea to feed from another distribution's repository.<br />
* Upgrade path between these distributions are mostly not tested, thus updating by changing the feeds will most likely end in broken packages or even an unbootable system. It is advisable to reflash the whole filesystem with [[dfu-util]] to switch between the different distributions, with the reminder that a dual-boot setup (e.g. via sdcard or NFS) can be used.<br />
<br />
== Official Openmoko releases ==<br />
<br />
'Release targets' offered by Openmoko Inc. are built out of different branches of the [[OpenEmbedded]] metadistribution source tree.<br />
<br />
=== Om series ===<br />
<br />
* '''[[Om 2008.12 Update]]''' is the second point release after the initial ''Om 2008.8'' release.<br />
<br />
{{Main|Om 2008.12 Update}}<br />
<br />
* '''[[Om 2008.9 Update]]''' is the first point release after the initial ''Om 2008.8'' release. Openmoko recommends that all existing installations of Om 2008.8 should be updated to that version. Quality-wise, we are still far from the goal, but this version includes general stability enhancing operating system improvements and a new splash screen. No applications were added or removed. Users with basic telephony needs will find it tolerable as an everyday phone.<br />
<br />
{{Main|Om 2008.9 Update}}<br />
<br />
* '''[[Om 2008.8]]''' was released on August 8, 2008, to replace 2007.2. Prior to that, its codename was ASU (April/August Software Update). This is still the name of the branch in the version control system. This distribution integrates the [http://trolltech.com/products/qtopia Qtopia] phone stack with a set of new Openmoko applications based on the Enlightenment Foundation Libraries ([[EFL_Documentation|EFL]]). Qtopia being a more mature product than the GNOME Mobile stack, the standard phone applications (dialer, contacts, calculator, calendar) work better than in 2007.2. The Qtopia used in 2008.8 was ported to run on X11, contrary to standard Qtopia which uses the framebuffer. This allows non-Qt applications to safely share the screen with Qt applications. This is a .0 release, many unresolved issues remain in the lower layers (kernel power management, sound, wifi drivers...).<br />
<br />
{{Main|Om2008.8}}<br />
<br />
* '''[[Om 2007.2]]''' is the base-system which is installed on FreeRunner when it leaves the factory. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand. There is a community effort (see [[SHR]]) to port the GTK based telephony applications to the future middleware from [[FSO]].<br />
<br />
{{Main|Om 2007.2}}<br />
<br />
=== FSO series ===<br />
<br />
'''FSO''' is an abbreviation for FreeSmartphone.Org. Openmoko is working on a stable system services back-end. Focus is on stable highlevel services that you can access from whatever language or UI that supports [http://dbus.freesmartphone.org/ dbus]. The framework will be used in forthcoming Openmoko distributions. FSO is all about middleware, but if one stacks a bootloader+kernel under it and telephony applications on top, one gets a functional distribution. These are made available as FSO-image milestones. <br />
<br />
* '''FSO Milestone IV''' was released on November 11th, 2008 and named 'Homework'. People report that despite its infancy, the phone server part in FSO is already more solid than anywhere else. The kernel under it is a Linux 2.6.24 with modules packaged separately. The telephony application on top of it is Zhone. This is a basic Python dialer/homescreen designed as scaffolding to test the FSO functionalities (even if Zhone is pretty, code path coverage is more critical to it than user-friendliness).<br />
<br />
{{Main|FSO}}<br />
<br />
== Openmoko community releases ==<br />
<br />
=== SHR - Stable Hybrid Release ===<br />
<br />
SHR is a community driven distribution. It contains some basic GTK+ based applications which make use of the FSO. There currently is an [[EFL_Documentation|EFL]] (with elementary) dialer, messages and contacts application programmed in C. As of November 9th, 2008, there is no stable release of this distribution yet, as the SHR team doesn't feel it to be good enough. You can find images though on the [http://shr.bearstech.com/shr-testing SHR buildhost].<br />
<br />
{{Main|Stable Hybrid Release}}<br />
<br />
=== FDOM (FAT and Dirty Openmoko) ===<br />
<br />
[[FDOM]] is a distribution based on Openmoko's currently supported image, updated with many ready-to-use applications and with fixes posted in the mailing lists. A combination of applications (everything goes) and fixes to demonstrate the capabilities of the Freerunner and to have a functional phone (sort of). This all while retaining the ability to update through the official feeds.<br />
<br />
{{Main|FDOM}}<br />
<br />
=== Non-Openmoko distributions ===<br />
<br />
These are not Openmoko (and OE) based distributions. These are alternatives you can run on your Openmoko phones.<br />
<br />
==== Qt Extended ====<br />
<br />
The Qt Extended distribution was formerly known as Qtopia up to version 4.3.x included. It comes from [http://www.trolltech.com Trolltech], a Nokia company, the makers of the Qt cross-platform application framework. This distribution aims to provide a ready-to-use image for Openmoko devices. It features a noticeably robust telephony stack. Recent release 4.4.2 also sports a webkit-based web browser and Gtalk support.<br />
<br />
{{Main|Qtopia / Qt Extended on FreeRunner}}<br />
<br />
==== Debian ====<br />
<br />
Debian is "the universal operating system". It comes with thousands and thousands of packages (most of them designed for desktops or servers so far). So in the words of Joachim "nomeata" Breitner from the [http://wiki.debian.org/Teams/DebianFSO pkg-fso] team, this is not really a distribution in the Openmoko sense of the word, but rather a different underlying system for Openmoko distributions. At the moment, we ship the software from the FSO stack, but hopefully we’ll also have, for example, the Stable Hybrid Release software in our archive. So for now, Debian is a different way of installing FSO, which takes more space and provides more programs :-)<br />
<br />
{{Main|Debian}}<br />
<br />
==== Gentoo ====<br />
<br />
Gentoo is all about choices. When installing Gentoo, this is made clear to you several times -- you can choose how much you want to compile yourself, how to install Gentoo, what system logger you want, etc. Gentoo is a fast, modern metadistribution with a clean and flexible design. Gentoo is built around free software and doesn't hide from its users what is beneath the hood. Portage, the package maintenance system which Gentoo uses, is written in Python, meaning you can easily view and modify the source code. Gentoo's packaging system uses source code (although support for precompiled packages is included too) and configuring Gentoo happens through regular textfiles. In other words, openness everywhere.<br />
<br />
{{Main|Gentoo}}<br />
<br />
==== Android ====<br />
<br />
Android is a mobile phone platform by Google, and later the Open Handset Alliance (OHA). Openmoko is fully supporting Android running on the Freerunner. Details along with images are being constructed at the moment. Visit the user web page for [http://wiki.openmoko.org/wiki/User:Seanmcneil3 Sean McNeil] for further details. And you can download kernel and image [http://people.openmoko.org/sean_mcneil/ here]. To boot the Kernel you have to adjust your [http://www.denx.de/wiki/U-Boot u-boot] environment to support a Kernel of more then 2 MB or your have to change to the [http://wiki.openmoko.org/wiki/Qi Qi] Bootloader.<br />
<br />
{{Main|Android}}<br />
<br />
==== Hackable:1====<br />
Hackable1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and implements the GNOME mobile platform. <br />
{{Main|Hackable:1}}<br />
<br />
==== Others / unreleased ====<br />
<br />
* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.<br />
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.<br />
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''<br />
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. Mickey Lauer used most of the technics & architecture, library & language choices of pyneo in fso. ''Status: still active, ask around on #neo1973-germany ''<br />
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: it does not have its own kernel so a Freerunner distribution waits for a solid basis and an arm-linux-gnueabi toolchain that runs natively on Mac OS X is currently lacking.''<br />
<br />
== Features by distribution/release target ==<br />
<br />
Generally, distributions can differ on one or more of the following components:<br />
* The bootsplash screen image. This is purely decorative.<br />
* The bootloader. Theoretically, any version of ''uboot'' could be used with any distribution. In the future ''Qi'' will replace ''uboot''.<br />
* The kernel. GNU/Linux kernels versions 2.6.24, 2.6.26 or 2.6.28 can be found. Some have modules compiled in, others have modules compiled separately. If compiled separately, modules can be distributed in the same package file as the kernel or separately.<br />
* Middleware: daemons to handle GSM calls or GPS, sound system, personal information storage and so on. Qt and Android have their own subsystems, FreeSmartphone.Org (FSO) is working towards a standard-based Free Software one.<br />
* Display driver. The original ''Qt Extended'' uses the framebuffer, most other distributions today use ''X11''.<br />
* Libraries and application framework (widget toolkit and and graphical environment) : EFL, Qt, Gtk+ or Java ?<br />
* Basic telephony applications: voice calls, SMS, alarm clock...<br />
* Smartphone applications: GPS, media player, simple games, web browser...<br />
* Open source applications: more games, scientific, you name it...<br />
<br />
=== Hardware Support ===<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%<br />
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|Om 2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android<br />
|-<br />
| GTA01 || ?? || ?? || ?? || {{Yes}} || ?? || {{Yes}} || {{Yes}} || ?? || ??<br />
|-<br />
| GTA02 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}<br />
|-<br />
|}<br />
<br />
=== Connectivity ===<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%<br />
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|Om 2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android<br />
|-<br />
| Telephony || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}<br />
|-<br />
| SMS || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}<br />
|-<br />
| [[GPRS]] || Not through UI || Not through UI|| Not through UI || Not through UI || {{Yes}} || {{Yes}} || {{Yes}} (1) || Not through UI || {{Yes}}<br />
|-<br />
| [[WiFi]] || {{Yes}} (*) || {{Yes}} || Not through UI || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Not through UI || {{Yes}}<br />
|-<br />
| VoIP || ?? || ?? || ?? || ?? || {{Yes}} || {{Yes}} (1) || {{Yes}} || ?? || {{no}}<br />
|-<br />
| Bluetooth || {{Yes}} || {{Yes}} || {{No}} || ?? || {{Yes}} || {{Yes}} || {{Yes}} || ?? || {{Yes}}<br />
|-<br />
| GPS (1) || {{Yes}} (1) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}} (1) || {{Yes}}<br />
|-<br />
|}<br />
<br />
=== Power ===<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%<br />
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|Om 2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android<br />
|-<br />
| Suspend || ?? || ?? || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ??<br />
|-<br />
| Resumes on Event || ?? || ?? || ?? || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || ??<br />
|-<br />
| Functions after Resume || ?? || ?? || ?? || {{Yes}} || {{No}} || {{No}} ||?? || {{Yes}} || ??<br />
|-<br />
|}<br />
<br />
=== User Interaction ===<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%<br />
! width=10%| !! width=8%|Om2008.8 !! width=8%|2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android<br />
|-<br />
| Stylus friendly || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}<br />
|-<br />
| Finger friendly || Partially || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || {{Yes}}<br />
|-<br />
| Accelerometer || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{No}} || {{yes}} (1) || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}<br />
|-<br />
|}<br />
<br />
=== Applications ===<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%<br />
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android<br />
|-<br />
| Terminal || {{Yes}} (1) || Basic (2) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}}<br />
|-<br />
| PIM || {{Yes}} || {{Yes}} || {{No}} || N/A || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || ??<br />
|-<br />
| Phonebook || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}<br />
|-<br />
| Dialer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}<br />
|-<br />
| Web Browser || {{Yes}} (1) || {{Yes}} (1) || ? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}<br />
|-<br />
| Mail Client || {{Yes}} || ? || ? || ? || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}<br />
|-<br />
| XMPP Client || {{Yes}} [[Instant Messaging|(1)]] || {{Yes}} (1) || ? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || || ??<br />
|-<br />
| Media Player || {{Yes}} (1) || {{Yes}} || ? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}<br />
|-<br />
|}<br />
<br />
=== Toolkits / Runtimes ===<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0"<br />
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android<br />
|-<br />
| GTK+ || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || ??<br />
|-<br />
| Qt/Qt Extended || {{Yes}} || {{No}} || {{Yes}} ? || {{Yes}}? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ??<br />
|-<br />
| Middleware || qtopia-x11 || gsmd/neod || FSO || FSO || qtopia-x11 || Qt Extended || FSO || FSO || ??<br />
|-<br />
| [[Java]] || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes}} || ?? || {{Yes|CacaoVM, JamVM}} || ?? || ??<br />
|-<br />
| [[Python]] || {{Yes}} || {{Yes}} || {{Yes}} || {{yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ??<br />
|-<br />
| [[Mono]] || {{Yes}} (1) || {{Yes}} (1) || ?? || {{no}} || ?? || ?? || {{Yes}} (1) || ?? || ??<br />
|-<br />
| [[Ruby]] || {{Yes}} || ?? || ?? || ?? || ?? || ?? || {{Yes}} (1) || {{Yes}} (1) || ??<br />
|}<br />
<br />
=== Images ===<br />
Latest and stable combinations for Neo FreeRunner gta02<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0"<br />
| || OM || FDOM || Qt Extended || Android<br />
|-<br />
| current bootloader || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/daily/ OM daily] version [http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin gta02v5_and_up] || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/daily/ OM daily] version [http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin gta02v5_and_up] || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/daily/ OM daily] version [http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin gta02v5_and_up] ||<br />
|-<br />
| future bootloader || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu ||<br />
|-<br />
| splash || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz ||<br />
|-<br />
| kernel || [[Linux]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest uImage.bin || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest uImage-gta02-mwester-stable.bin or from [http://downloads.tuxfamily.org/3v1deb/openmoko/ treviño] latest uImage-gta02-stable-3v1n0.bin || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest uImage-gta02-mwester-stable.bin or from [http://downloads.tuxfamily.org/3v1deb/openmoko/ treviño] latest uImage-gta02-stable-3v1n0.bin || [[Linux]] from [http://wiki.openmoko.org/wiki/User:Seanmcneil3 McNiel] version [http://people.openmoko.org/sean_mcneil/uImage-android 2.6.26-android]<br />
|-<br />
| modules || ? || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest modules-min-gta02-mwester-stable.tgz or modules-all-gta02-mwester-stable.tgz || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest modules-min-gta02-mwester-stable.tgz or modules-all-gta02-mwester-stable.tgz ||<br />
|-<br />
| rootfs || [[Main_Page|OM]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest rootfs.jffs2 || [[FDOM]] from [ftp://ftp.tuxbrain.com/openmoko/fdom/releases/ TuxBrain] version [ftp://ftp.tuxbrain.com/openmoko/fdom/releases/Fat_and_Dirty_OM.200809_20081023.rootfs.jff2 200809_20081023] || [[Qtopia_/_Qt_Extended_on_FreeRunner|QtExtended]] from [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 TrollTech] latest qtextended-gta02-flash.tgz or from [http://other.lastnetwork.net/OpenMoko/ Hypnotize] latest qtextended-gta02-rootfs-release-working.jffs2 || [[Android]] from [http://wiki.openmoko.org/wiki/User:Seanmcneil3 McNiel] version [http://people.openmoko.org/sean_mcneil/androidfs.jffs2 android]<br />
|}<br />
<br />
Footnotes:<br />
<br />
(1) works, but need additional software to be installed<br />
<br />
(2) unusable due to lack of certain keyboard characters. [[Switching_Keyboards#Matchbox_keyboard|Various fixes available.]]<br />
<br />
(*) unstable<br />
<br />
==Quick download page==<br />
<br />
[[Download]]<br />
<br />
== See also ==<br />
<br />
* Mickey Lauer's post "[http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!]" describes the differences between distributions 2007.2, ASU and FSO.<br />
<br />
* Latest news and tips are in [[Community Updates]]<br />
<br />
[[Category:Distributions| ]]</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-29T13:11:56Z<p>Rainglasz: /* SHR */</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS<br />
<br />
=== OM 2008.9 ===<br />
Works (booted from SD), more to follow<br />
<br />
=== OM 2008.12 ===<br />
Does not boot from SD: <i>Only GTA01 Hardware supported by ASoc driver</i><br />
Found finally the hint here: [[Community_Updates/January_12th,_2009#Tips_and_tricks]]. However, tricking with Uboot load is a hard requirement for a beginner, even with lots of system experience. I thought that testing from a SD card would be a wise thing!<br />
<br />
Nevertheless, this system booted then, but (except Sudoku and Dialer) no application works upto now. Maybe I have to reset the root fs..<br />
<br />
=== Qtopia ===<br />
Works fine (booted from SD), more to follow<br />
<br />
=== SHR ===<br />
Works fine (booted from SD)<br />
* Crashes WindowsXP-SP3 when connecting USB<br />
* Very slow (30% cpu time continuously in enlightenment)<br />
* WiFi access not yet working<br />
* Very quickly suspending<br />
* Phone calls working, even in suspend!<br />
* tangoGPS not yet working</div>Rainglaszhttp://openmoko.org/wiki/Openmoko_Local_Groups:_BielefeldOpenmoko Local Groups: Bielefeld2009-01-29T13:09:24Z<p>Rainglasz: /* Possible Participants */ Rainglasz added</p>
<hr />
<div>For anyone in Bielefeld or the Region (OWL, Lippe...).<br />
<br />
<br />
=== Possible Participants ===<br />
{|border=1<br />
!Name<br />
!Skills<br />
!Level of Interest<br />
!Location<br />
!Other<br />
!Has Device<br />
!Has Debug Board<br />
|-<br />
|[[User:Raven|Raven]]<br />
|Coding, Linux...<br />
|Finally starting to play with my FreeRunner.<br />
|Bielefeld<br />
|<br />
|Yes<br />
|No<br />
|-<br />
|[[User:Killerdackel|Killerdackel]]<br />
|Coding, Java, Human-Machine-Interaction<br />
|Waiting desperately for a new toy too<br />
|Bielefeld<br />
|<br />
|Yes<br />
|No<br />
|-<br />
|[[User:Seppi|Seppi]]<br />
|Coding, Linux, Human-Machine-Interaction, Robotics<br />
|Started coding, playing around with the device<br />
|Lage (near Bielefeld)<br />
|<br />
|Yes<br />
|No<br />
<!-- Copy from here... --><br />
|-<br />
|[[User:ernstabrams|ernstabrams]]<br />
|STuding in Bi. Using OM as a User...<br />
|From beginning a User.<br />
|Bielefeld<br />
|<br />
|Yes<br />
|No<br />
|-<br />
|[[User:Rainglasz|Rainglasz]]<br />
|Computer research; Design (Code & UI), occasional Coding<br />
|Exploring the device (in search for a open PDA that has a phone too)<br />
|Paderborn<br />
|<br />
|GTA02<br />
|No (not yet necessay)<br />
|}<br />
<br />
[[Category:Openmoko Local Groups]]</div>Rainglaszhttp://openmoko.org/wiki/Neo_FreeRunner_Hardware_IssuesNeo FreeRunner Hardware Issues2009-01-28T21:56:16Z<p>Rainglasz: /* Draws too much current from USB */ More info - is a software bug if present</p>
<hr />
<div>{{Neo FreeRunner Menu}}<br />
<br />
This is a community-written page that discusses '''hardware issues''' with the FreeRunner/[[GTA02]] device. Information here is unofficial (and possibly incorrect) unless otherwise stated. Corrections and clarifications from Openmoko employees would be greatly appreciated.<br />
<br />
Please '''DON'T PANIC''' when reading this page. Please give Openmoko employees time to investigate these issues and to develop a solution. Some of the items may turn out to be non-issues, or may have software workarounds. The FreeRunner's software is still under heavily development and can help fix most of this problems.<br />
<br />
=== Active Issues ===<br />
<br />
==== Poor Audio Quality ====<br />
<br />
Issue: The person on the other end of a GSM phone call may experience poor audio quality, to the point where he/she cannot carry on a normal conversation.<br />
<br />
There are three related aspects to this issue:<br />
* Call is too quiet (mixer settings for mic and/or earpiece are set too low)<br />
* Caller hears a loud echo of their own voice [http://docs.openmoko.org/trac/ticket/1267 #1267]<br />
* Buzzing noise caused by GSM radio interference [http://docs.openmoko.org/trac/ticket/883 #883] [http://docs.openmoko.org/trac/ticket/1352 #1352]<br />
<br />
<br />
Affects: all devices but only some users (depending on many factors)<br />
<br />
The source of the GSM buzz has been [http://lists.openmoko.org/pipermail/hardware/2008-August/000415.html identified]. It's a mere hw-issue, depending on the way you hold the device, and the local situation created by network settings made by the GSM-provider (mainly 1800/1900 seems to be affected), as well as your position relative to basestation. There is no way to fix GSM buzz by mixer-setting modifications. So all suggested settings here may improve a little the volume of buzz during you're *not* speaking only, while relative ratio of buzz/voice level while speaking can't be changed by mixer settings.<br />
<br />
Some [http://lists.openmoko.org/pipermail/hardware/2008-August/000451.html hidden Calypso commands] may help with the echo problem.<br />
<br />
Workarounds:<br />
<br />
# Using a bluetooth headset is a possibility.<br />
# Using external GSM-antenna will stop buzz.<br />
<br />
<br />
Due to the multiple factors influencing the result of a single test, it's nearly impossible to find a setup that lets you compare for a decent "before / after" result. If you ever took an old analog TV portable to a place where you had to fiddle around with the antenna to try and make the snow and shadows vanish off the picture, you might have gotten a slight idea of what it's like to reproduce the same situation for decent tests. So probably most of the suggested alsa-improvements are mere random results. Even if they worked for provider A evidently, this doesn't mean there's any improvement by using same settings for provider B.<br />
<br />
This being said, here they are:<br />
<br />
The...<br />
<br />
# Better mixer settings: One confirmed good settings are here: http://www.mail-archive.com/support@lists.openmoko.org/msg00564.html. Please change accordingly in /usr/share/openmoko/scenarios/gsmhandset.state. Should eliminate/lessen echo and buzz problems. [[Neo alsamixer]] is the main article for setting the mixer settings.<br />
<br />
===== Better set of mixer settings =====<br />
<br />
Regarding 2. in the previous paragraph, here are my further tweaked settings:<br />
<br />
[mic volume & buzz problem]<br />
* 'Mono Playback Volume' (95)<br />
* 'Mono Sidetone Playback Volume' (2)<br />
* 'Mic2 Capture Volume' (3)<br />
[speaker volume & echo problem]<br />
* 'Speaker Playback Volume' (112)<br />
* 'Bypass Playback Volume' (5)<br />
<br />
Lowering Mono Sidetone eliminated the buzz problem better. Please try out and report if you have good success... --[[User:TimoJyrinki|TimoJyrinki]] 08:19, 16 October 2008 (UTC)<br />
<br />
==== Can't boot with discharged or missing battery ====<br />
<br />
Issue: Neo FreeRunner requires battery power to boot, because Neo FreeRunner consumes too much current while booting to boot with only a charger. Since charging isn't enabled until the Neo FreeRunner has booted, this means that a discharged battery can not be charged. One manifestation of this problem is a kernel panic (red LED flashes constantly) when trying to boot using the power button.<br />
<br />
Affects: Unknown.<br />
<br />
Status: By properly sequencing module power sequence, a software solution to this problem should exist.<br />
<br />
Fixed(?) with [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003799.html Werner Almesberger patches] - [http://lists.openmoko.org/pipermail/commitlog/2008-July/005403.html more here] [http://lists.openmoko.org/pipermail/community/2008-July/023392.html additional information]<br />
<br />
I think this patch finally fixes the problem:<br />
[http://www.abanet.ch/~hug/moko/uboot-battery/ Philipp Hugs patches]<br />
<br />
Workarounds:<br />
<br />
# Make sure that the battery never discharges completely<br />
# Use [[:Image:Nokia-charging-stand.jpg|external stand-alone charger]] (compatible with the Nokia BL-5C battery)<br />
# Boot the FreeRunner with an [[Neo_FreeRunner_Battery#Compatible_Replacement_Batteries|alternative battery]], or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.<br />
# Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.<br />
## Oscilloscope digital clip probes fit perfectly on the Freerunner's battery connectors. Make sure polarity is correct!<br />
# Some users have reported that Neo FreeRunner '''is''' able to boot on USB power alone using the NOR u-boot, thus: press AUX, plug USB power, select boot. Reports of success would be appreciated.<br />
## Does work with sequence described. If after pressing boot it just turns off again (happened a few times), then: press AUX, plug in USB power, cycle through the menu a few times to keep it from turning off without booting, after a minute or so press boot. [[User:Imrehg|Imrehg]] 08:34, 10 September 2008 (UTC)<br />
## This does indeed work with sequence described. After pressing boot, the screen went blank for a few seconds, but then the beast came to life again. That saved the day! [[User:Edictor|Edictor]]<br />
## Trifirmed. Neither USB connection nor wall charger was able to wake my phone. But in NOR u-boot it worked (connected to the computer). I think this trick hasn't failed to anyone. --[[User:Flamma|Flamma]] 12:11, 17 September 2008 (UTC)<br />
## Unfortunately this is not working for me. My FreeRunner has been off for a few weeks and completely dead. I tried various combinations of holding aux and plugging in to both wall and computer, no luck. Tried with and without the battery in place, no luck. Aux and power button / just power / aux then power. No luck... --[[User:Safire|Safire]] 6 November 2008<br />
## This is working ! It has prevent me from buying an external power charger. My freerunner had its battery discharged for about 2 weeks now, and I was able to boot and charge it. --[[User:JRD|JRD]] 23:37, 12 November 2008 (UTC)<br />
## It has worked for me ! I have booted to 2008.9 Om with discharged battery (after connecting the FR to power supply and waiting a few minutes until AUX button red light stopped flashing) using the NOR boot menu. Tried the same with NAND boot menu and worked also !!! Then I could charge the battery. -- [[User:Emsyr|Emsyr]] 3:23, 20 November 2008 (UTC)<br />
## I can boot to 2008.9 without battery and with USB connection = plug USB power (FR <-> PC) + press power button. However I cannot shutdown correctly. --[[User:Cynan|Cynan]] 13:43, 9 December 2008 (UTC)<br />
## I can boot to 2008.9 without battery and with USB connection: press AUX button, then plug USB power, then press power button (keeping AUX pressed). NOTE that battery was fully charged. The problem wasn't battery but corrupted environment in NAND u-boot: with battery IN, no access to NOR u-boot<br />
## Both my friend's freerunner and mine was completely discharged. This trick failed. Finally booted the freerunner with a BL-5C battery from an old nokia n-gage. With the power connected I then switched the batteries. --[[User:Unlotto|Unlotto]] 14:27, 25 January 2009 (UTC)<br />
See also:<br />
:[[Neo_FreeRunner_Battery|Neo FreeRunner Battery]]<br />
<br />
==== Battery discharges when charging completes ====<br />
<br />
Issue: If the Neo FreeRunner has been charging, when charging completes, it seems to drain the battery and not turn on charging again. This seems to be bug of PMU-registers setup, that shows up when PMU has to handle bat autonomously (=suspend). There might be issues our current scheme relies on wake-interrupt at bat-full which doesn't succeed, or something like that.<br />
<br />
Affects: Unknown.<br />
<br />
Status:<br />
<br />
Workarounds:<br />
<br />
# When the battery is full, disconnect the charger<br />
<br />
See also:<br />
<br />
==== Suspend/resume corrupts SD card's partition table ====<br />
<br />
Issue: Suspend/resume corrupts the partition table of the SD card<br />
<br />
Affects: Unknown.<br />
<br />
Status:<br />
<br />
[[https://docs.openmoko.org/trac/ticket/1802#comment:6 Patched kernel]] might solve the problem<br />
<br />
Workarounds:<br />
<br />
# [[https://docs.openmoko.org/trac/ticket/1802#comment:5 Script]] as a temporary workaround<br />
<br />
See also:<br />
<br />
:[[https://docs.openmoko.org/trac/ticket/1802 trac ticket]]<br />
<br />
==== Some SIMs Don't Work ====<br />
<br />
Issue: There are reports that some users cannot register with their GSM network when using certain SIM cards. See for example http://lists.openmoko.org/pipermail/community/2008-July/020370.html<br />
<br />
It is possible that there is more than one issue involved here. The observed problems ''might'' (i.e. some items are only speculation at this point) be caused by:<br />
<br />
* User error, not inserting the SIM in the correct orientation or not sliding the holder to the 'locked' position<br />
<br />
* Software issues that result in a locked SIM (not properly prompting the user for a PIN and then passing this to the SIM)<br />
<br />
* Mechanical issues with the SIM holder that prevent the pins from making reliable contact with the pads on the SIM. Note that only 6 of the 8 pins are used, and the remaining two are not connected.<br />
<br />
* Electrical incompatibility (some tests show problems with 1.8V SIMs while 2.9V ones work OK)<br />
<br />
* Firmware bugs in the TI Calypso GSM chipset. Note that one issue in this category was found and fixed on the GTA01 devices (#666 in Trac), and that specific problem should not affect the FreeRunner.<br />
<br />
* Defective SIMs, i.e. ones that do not comply with the applicable standards and are acknowledged as being defective by the carrier (even if they happen to work in some phones).<br />
<br />
* You may have true 3G operating at 2100 and your sim doesn't fallback to GSM. The Phone works on 850/1800/1900 or 900/1800/1900.<br />
<br />
See also:<br />
* http://wiki.openmoko.org/wiki/Carriers/ATT<br />
* http://wiki.openmoko.org/wiki/Carriers/Rogers<br />
<br />
Affects: Only a subset of users (details unknown).<br />
<br />
Status: Fixed in GSM firmware moko10-beta2 or later. See [[GSM/Flashing]] for instructions. Please add your information to [[FreeRunner_unable_to_work_with_3G_SIM_cards]] or [[GSM network registration]]<br />
<br />
Workarounds:<br />
<br />
# Please document your existing SIM card and provider in the table [[FreeRunner_unable_to_work_with_3G_SIM_cards|here]].<br />
# If the table mentioned above shows any SIM cards known to work with your provider, make note of these numbers.<br />
# Contact your network provider and request a new SIM card. You may wish to print out the table mentioned above and bring it with you to the store.<br />
# Add your experience with the new SIM card to the table mentioned above.<br />
<br />
=== Known/Accepted Issues ===<br />
<br />
This section lists items that are acknowledged as being less than ideal, but are considered to be acceptable in the shipping product. They will not be discussed in detail on this page.<br />
<br />
* Poor performance + slow bus speed of the Glamo GPU - discussed to death on the mailing lists and IRC.<br />
** stable-2.6.26 branch of kernel has wait states lowered, core speed increased from 50MHz to 80MHz and memory speed from 80MHz to 90MHz (the latter is also in stable branch) - these lessen the problem a bit, though it's slow still<br />
* [http://lists.openmoko.org/pipermail/hardware/2008-April/000055.html GPS antenna switch] driven out-of-spec - does not appear to have a significant effect on device performance<br />
* Poor low-frequency audio response with low-impedance headphones, e.g. as discussed in this thread: http://lists.openmoko.org/pipermail/openmoko-kernel/2008-March/001999.html (NOTE - this thread refers to pre-mass-production devices)<br />
** Can be fixed to an semi-acceptable level (if not high fidelity most probably) by adjusting "Bass Volume" to full (15) and "Bass Filter" to "100Hz @ 8kHz" (bass will be boosted <= 600Hz when playing back at 48kHz) or "200Hz @ 8kHz" (<= 1200Hz @ 48kHz). The default is 130Hz @ 48kHz and does not help much with the more wider scope of low frequencies.<br />
** Ideally someone would record output and find out which setting produces best output, ie. compensating for the loss of low frequencies without boosting too high frequencies with this "bass" boost.<br />
<br />
Actually with 16 Ohm headphones the cutoff frequency is more than 2kHz, so even 1200Hz @ 48kHz seems to be not appropriate.<br />
If you have 30 Ohm, it might be just correct setting.<br />
<br />
=== Resolved Issues ===<br />
<br />
These are issues that have been discussed in the past, but have been fixed (or turned out not to be a problem) for the mass-produced devices.<br />
<br />
* Excessive LED current - Some early units lacked a current-limiting resistor for the LEDs. This has been fixed for the production units.<br />
* Battery life - At this time it appears that the FreeRunner battery life will be acceptable once suspend/resume support has been implemented in software.<br />
* slow GPS TTFF - see [[GPS Problems]]<br />
==== Empty NOR Flash ====<br />
<br />
Issue: NOR flash (backup copy of u-boot) is not programmed. [http://docs.openmoko.org/trac/ticket/1568 #1568]<br />
<br />
Affects: Unknown - maybe only 1 or 2 devices? Also need to confirm that the bug report was from a mass-production unit rather than an earlier prototype.<br />
<br />
Status: Solved. The new devices are tested better if they have the NOR flashed programmed and aren't shipped if the test fail.<br />
<br />
Workarounds: Use the NAND copy of u-boot and be careful not to brick the device unless a debug-board is available.<br />
<br />
<br />
==== Debug board has wrong vendor/product ID ====<br />
<br />
Issue: A debug board is not reporting the expected USB Vendor/Product ID.<br />
<br />
Affects: Only [http://lists.openmoko.org/pipermail/device-owners/2008-July/001775.html one report] has been seen so far.<br />
<br />
Status: Probably a single case scenario.<br />
<br />
Workarounds: Edit configuration files (e.g. openocd.conf) to use the IDs that the board is reporting.<br />
<br />
== List of "Current issues" Imported from the "Community update page" ==<br />
(to be sorted)<br />
<br />
The information below has been collected from various sources, feel free to add questions and comments here.<br />
<br />
===GPS Performance of the FreeRunner===<br />
The poor GPS performance on the FreeRunner has been traced to an<br />
interaction between the microSD card and the GPS unit. A software<br />
and a hardware fixes are available, see [[GPS Problems]].<br />
<br />
===GTA02 battery status===<br />
While writing a device driver for the new battery which provides an accurate counter of the charge state of the [[GTA02]], the driver developer discovered that the device driver does not get a reading of the charge state due to a very long response time with only one I/O signal when trying to read the charge state. To be able to read the battery status properly, it has been written that it will be necessary to re-design that part of the GTA02 for hardware version GTA02A5 to use two I/O signals to reduce the response time (one for transmitting commands, one for receiving data?). This was fixed two months ago (see [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=957#c1 Bug 957]).<br />
<br />
===Delivery of a GSM firmware update for the 3G SIM bug ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666 #666])===<br />
<br />
A bug in the GSM firwmare of Neo 1973 caused some 3G SIM cards to not work with Neo 1973. This Neo 1973 GSM firmware update can only be installed by an Openmoko employee due to licensing issues.<br />
<br />
This fix is already present in the Neo FreeRunner firwmare, and thus the Neo 1973 GSM firmware update is not required for the Neo FreeRunner. In fact since the firmware differs between the Neo 1973 and the Neo FreeRunner, it would very likely make the GSM module unusable.<br />
<br />
There seem to be other GSM issues on the Neo FreeRunner. See [[#Some_SIMs_Don.27t_Work|Some SIMs Don't Work]] above.<br />
<br />
=== SMedia 3362 Documentation & OpenGL ES Drivers ===<br />
There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and Openmoko developers will not be writing one in the near future (although they have not ruled it out in the long-term).<br />
<br />
Documentation for the SMedia 3362 has been promised ([http://lists.openmoko.org/pipermail/community/2007-September/010175.html see this post]). However, this refers to documentation Openmoko developers will be writing themselves, not the technical documentation SMedia have provided Openmoko with. The Openmoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See [http://lists.openmoko.org/pipermail/community/2007-November/011349.html this post] for details)<br />
<br />
=== Power Management on the Neo1973/FreeRunner===<br />
The current battery life of the Neo1973 and FreeRunner is not satisfactory. A lot of changes seem to be necessary to the kernel, drivers and related user-space applications. Hopefully the situation will improve over time.<br />
<br />
=== Draws too much current from USB ===<br />
Unless the battery is full, the device draws more than 500mA from the USB Device. Some devices then - correctly - switch off this presumably defect device, instead of limiting the current at the expense of too low voltage supplied. <br />
<br />
However, as learned from [[Specialized_USB_cables#How_to_make_a_USB_cable_for_powering_attached_USB_devices_and_charging_the_Neo_while_in_host_mode_.28aka_Y-Cable.29|Specialized USB cables]] <br />
, the power consumption can be switched by the host, and this simply seems to be a bug in many distributions not to honor the id-pin.<br />
<br />
<br />
[[Category:Neo FreeRunner Hardware]]</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-28T19:48:07Z<p>Rainglasz: /* OM 2008.12 */ found solution, but ...</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS<br />
<br />
=== OM 2008.9 ===<br />
Works (booted from SD), more to follow<br />
<br />
=== OM 2008.12 ===<br />
Does not boot from SD: <i>Only GTA01 Hardware supported by ASoc driver</i><br />
Found finally the hint here: [[Community_Updates/January_12th,_2009#Tips_and_tricks]]. However, tricking with Uboot load is a hard requirement for a beginner, even with lots of system experience. I thought that testing from a SD card would be a wise thing!<br />
<br />
Nevertheless, this system booted then, but (except Sudoku and Dialer) no application works upto now. Maybe I have to reset the root fs..<br />
<br />
=== Qtopia ===<br />
Works fine (booted from SD), more to follow<br />
<br />
=== SHR ===<br />
Works fine (booted from SD)<br />
* Crashes WindowsXP-SP3 when connecting USB<br />
* Very slow (30% cpu time continuously in enlightenment)<br />
* WiFi access not yet working<br />
* Very quickly suspending<br />
* Phone calls working<br />
* tangoGPS gets location</div>Rainglaszhttp://openmoko.org/wiki/Userspace_root_imageUserspace root image2009-01-28T17:40:09Z<p>Rainglasz: /* Mount on loopback device */ Link to jffs2 page</p>
<hr />
<div>{{Languages|Userspace_root_image}}<br />
<br />
== Creating a root filesystem from scratch ==<br />
<br />
To create a root file system image for storage in NAND flash, we use the mkfs.jffs2 program contained in the Debian package ''mtd-tools'' or ''sys-fs/mtd-utils'' in Gentoo portage.<br />
<br />
<pre><br />
mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x4000 -n -d/tmp/jffsroot/ # for GTA01?<br />
mkfs.jffs2 --pad=0x700000 -o rootfs.jffs2 -e 0x20000 -n -d/tmp/jffsroot/ # for GTA02<br />
</pre><br />
<br />
are typical commands. It creates a FS image for our erase block size of 16k (128k for GTA02), padded to 0x700000 bytes in length from the files contained in the ''/tmp/jffsroot'' directory and stores the FS image in ''rootfs.jffs2''.<br />
<br />
== Using pre-created rootfs image ==<br />
<br />
=== Prebuilt ===<br />
<br />
See [[Download]] and update the list if you have more information.<br />
<br />
=== OpenEmbedded ===<br />
<br />
OpenEmbedded will itself create a jffs2 image at the end of the build process.<br />
<br />
Once the build server is running, it will create root filesystem images for us.<br />
<br />
=== demo JFFS2 root image ===<br />
<br />
Check the [[Flashing the Neo FreeRunner]] page for pre-built root images. Please note that this image may take long to boot the first time, since this boot finishes the installation process.<br />
<br />
=== Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) ===<br />
==== Configure the kernel for support ====<br />
For a 2.6.25 kernel:<br />
*Device Drivers<br />
**Block Devices<br />
***Loopback device support<br />
**Memory Technology Device (MTD) support<br />
***Caching block device access to MTD device (mtdblock module, required for block2mtd)<br />
***Self-contained MTD device drivers<br />
****MTD using block device (block2mtd)<br />
*File systems<br />
**Miscellaneous filesystems<br />
***Journalling Flash File System v2 (JFFS2) support<br />
****Advanced compression for JFFS2<br />
*****JFFS2 ZLIB compression support<br />
*****JFFS2 RTIME compressoin support<br />
<br />
==== Mount on loopback device ====<br />
<br />
losetup is an application to manage loop devices, if you have the "losetup -f" option (for instance debian etch does not has such option) you can use the following commands:<br />
<br />
<pre><br />
export loop=$(losetup -f)<br />
losetup $loop <rootfs.jffs2><br />
modprobe block2mtd block2mtd=$loop,131072<br />
modprobe jffs2<br />
modprobe mtdblock<br />
mkdir <mountpoint><br />
mount -t jffs2 -o ro /dev/mtdblock0 <mountpoint><br />
</pre><br />
"losetup -f" just returns the first unused loop device, if your system do not comes with "losetup -f" just chose the first /dev/loop* device that is unused and change the first line with:<br />
<br />
export loop=/dev/loop0<br />
<br />
if loop0 is unused<br />
<br />
Here is a simple script to do the above automatically, complete with sanity checking: [[Media:Mntjffs.sh|JFFS2-Mount-Script]]<br />
<br />
Download it, make it executable and run it:<br />
<br />
# chmod +x Mntjffs.sh<br />
# ./Mntjffs.sh <image.jffs2> </mountpoint><br />
<br />
Make sure you run the script as root, because it needs to modprobe<br />
<br />
$ ./Mntjffs.sh -h | --help<br />
<br />
gives you a short summary of usage.<br />
<br />
<br />
Based on this [http://www.internettablettalk.com/forums/showthread.php?p=192475#post192475 script by fanoush].<br />
<br />
The following is an alternate way of doing the above; you can find a suitable script also under [[Jffs2]].<br />
<pre><br />
modprobe mtdcore<br />
modprobe jffs2<br />
modprobe mtdram total_size=59024 # default is 4 MByte - set to max. available size<br />
modprobe mtdchar<br />
modprobe mtdblock<br />
dd if=<rootfs.jffs2> of=/dev/mtd0<br />
mount -t jffs2 /dev/mtdblock0 <mountpoint><br />
</pre><br />
<br />
=== Mounting the JFFS2 image on a loopback device (Kernel Memory MTD Emulation) ===<br />
<br />
As mounting the JFFS2 image from /dev/loop0 device is not supported, use the mtdram device as described in http://www.handhelds.org/hypermail/familiar/62/6232.html and http://ubuntuforums.org/showthread.php?t=432481<br />
<br />
(On Fedora the first module to load is mtd, not mtdcore and you need to set e.g. vmalloc=256m as a kernel boot parameter for this to work.)<br />
<br />
modprobe mtdcore<br />
modprobe jffs2<br />
modprobe mtdram total_size=59024 # default is 4 MByte - set to max. available size<br />
modprobe mtdchar<br />
modprobe mtdblock<br />
<br />
Using ''total_size=59024'' will set the filesystem size to the available space on /dev/mtd4 of the GTA1 device. So when you copy the image back it will be about 58 MB. You can set this to smaller values though.<br />
<br />
<br />
Be careful to really use the mtd-ram-disk (maybe there is a real Flash-device somewhere in your development system)<br />
<br />
So check for that looking into /proc/mtd:<br />
cat /proc/mtd<br />
# dev: size erasesize name<br />
# mtd0: 039a4000 00020000 "mtdram test device"<br />
<br />
Then write the image to that device and mount it:<br />
<br />
dd if=<rootfs.jffs2> of=/dev/mtd0<br />
mount -t jffs2 /dev/mtdblock0 <mountpoint><br />
<br />
The image is an Little Endian jffs2 image. To mount it on Big Endian architectures (like PowerPC) it'll have to be converted:<br />
<br />
jffs2dump -l -c -e <rootfs.jffs2.be> <rootfs.jffs2> # only needed on non little endian archs<br />
<br />
==== create the new image ====<br />
To get the changed image back there are two ways. The obvious one is to unmount it and copy the data back from the MTD block device (the image will be 58 MB):<br />
<br />
umount /dev/mtdblock0<br />
dd if=/dev/mtdblock0 of=<rootfs.jffs2><br />
<br />
You can also create a new image using the mounted file system and the method described [[Userspace_root_image#Creating_a_root_filesystem_from_scratch | above]] (the image will have the size of its data):<br />
<br />
mkfs.jffs2 --pad=0x700000 -o new_rootfs.jffs2 -e 0x4000 -n -d <mountpoint><br />
<br />
== Flashing a root filesystem into NAND ==<br />
<br />
See [[U-boot#Writing_rootfs_to_NAND]]<br />
<br />
== Converting a GTA02 image for GTA01 ==<br />
<br />
The techniques on this page may be used to convert a GTA02 (FreeRunner) image for use on a GTA01, provided that it is small enough to fit into the GTA01's flash.<br />
<br />
The steps I used are shown below (corrections welcome). Please read all of this page before executing these commands, in particular the warning to make sure that /dev/mtd0 does not map to a real flash device on your system.<br />
<br />
<pre><br />
modprobe jffs2<br />
modprobe mtdchar<br />
modprobe mtdblock<br />
modprobe mtdram erase_size=128 total_size=262144<br />
dd if=gta02_image.jffs2 of=/dev/mtd0<br />
mount -t jffs2 -o ro /dev/mtdblock0 /mnt<br />
mkfs.jffs2 --little-endian -e 16 -x lzo --pad -n -r /mnt -o for_gta01.jffs2<br />
</pre><br />
<br />
To clean up when you're done:<br />
<pre><br />
umount /mnt<br />
rmmod mtdram<br />
</pre><br />
<br />
[[Category:System Developers]]</div>Rainglaszhttp://openmoko.org/wiki/Jffs2Jffs22009-01-28T17:33:44Z<p>Rainglasz: /* Mounting a JFFS2 image */ Skrip added</p>
<hr />
<div>== Mounting a JFFS2 image ==<br />
<br />
Make the MTD block device<br />
mknod /dev/mtdblock0 b 31 0 <br />
<br />
Associate the jffs2 file with a loopback device<br />
losetup /dev/loop0 /path/to/jffs2/file/eg/Om200Y.MM-gtaNN-YYYYMMDD.rootfs.jffs2<br />
<br />
Load the block2mtd module<br />
modprobe block2mtd <br />
<br />
Tell the module which loopback device to use<br />
echo /dev/loop0 >/sys/module/block2mtd/parameters/block2mtd<br />
<br />
Make a mount point for the file system<br />
mkdir /mnt/jffs2<br />
<br />
Mount the file system<br />
mount -t jffs2 /dev/mtdblock0 /mnt/jffs2/<br />
<br />
An alternative way is used in the following script:<br />
if test `id -u` != 0<br />
then echo "Must be root"; exit 2<br />
fi<br />
if test $# != 2 -o ! -d $2<br />
then echo Usage: $0 image.jffs2 directory; exit 2<br />
fi<br />
rmmod mtdram<br />
modprobe mtdcore<br />
modprobe mtdblock<br />
modprobe mtdchar<br />
modprobe jffs2<br />
s=$(ls -s $1)<br />
s=${s% *}<br />
echo modprobe mtdram total_size=$s<br />
modprobe mtdram total_size=$s<br />
dd if=$1 of=/dev/mtd0<br />
mount -t jffs2 /dev/mtdblock0 $2</div>Rainglaszhttp://openmoko.org/wiki/Neo_FreeRunner_Hardware_IssuesNeo FreeRunner Hardware Issues2009-01-28T17:20:34Z<p>Rainglasz: /* List of "Current issues" Imported from the "Community update page" */ USB draws too much current</p>
<hr />
<div>{{Neo FreeRunner Menu}}<br />
<br />
This is a community-written page that discusses '''hardware issues''' with the FreeRunner/[[GTA02]] device. Information here is unofficial (and possibly incorrect) unless otherwise stated. Corrections and clarifications from Openmoko employees would be greatly appreciated.<br />
<br />
Please '''DON'T PANIC''' when reading this page. Please give Openmoko employees time to investigate these issues and to develop a solution. Some of the items may turn out to be non-issues, or may have software workarounds. The FreeRunner's software is still under heavily development and can help fix most of this problems.<br />
<br />
=== Active Issues ===<br />
<br />
==== Poor Audio Quality ====<br />
<br />
Issue: The person on the other end of a GSM phone call may experience poor audio quality, to the point where he/she cannot carry on a normal conversation.<br />
<br />
There are three related aspects to this issue:<br />
* Call is too quiet (mixer settings for mic and/or earpiece are set too low)<br />
* Caller hears a loud echo of their own voice [http://docs.openmoko.org/trac/ticket/1267 #1267]<br />
* Buzzing noise caused by GSM radio interference [http://docs.openmoko.org/trac/ticket/883 #883] [http://docs.openmoko.org/trac/ticket/1352 #1352]<br />
<br />
<br />
Affects: all devices but only some users (depending on many factors)<br />
<br />
The source of the GSM buzz has been [http://lists.openmoko.org/pipermail/hardware/2008-August/000415.html identified]. It's a mere hw-issue, depending on the way you hold the device, and the local situation created by network settings made by the GSM-provider (mainly 1800/1900 seems to be affected), as well as your position relative to basestation. There is no way to fix GSM buzz by mixer-setting modifications. So all suggested settings here may improve a little the volume of buzz during you're *not* speaking only, while relative ratio of buzz/voice level while speaking can't be changed by mixer settings.<br />
<br />
Some [http://lists.openmoko.org/pipermail/hardware/2008-August/000451.html hidden Calypso commands] may help with the echo problem.<br />
<br />
Workarounds:<br />
<br />
# Using a bluetooth headset is a possibility.<br />
# Using external GSM-antenna will stop buzz.<br />
<br />
<br />
Due to the multiple factors influencing the result of a single test, it's nearly impossible to find a setup that lets you compare for a decent "before / after" result. If you ever took an old analog TV portable to a place where you had to fiddle around with the antenna to try and make the snow and shadows vanish off the picture, you might have gotten a slight idea of what it's like to reproduce the same situation for decent tests. So probably most of the suggested alsa-improvements are mere random results. Even if they worked for provider A evidently, this doesn't mean there's any improvement by using same settings for provider B.<br />
<br />
This being said, here they are:<br />
<br />
The...<br />
<br />
# Better mixer settings: One confirmed good settings are here: http://www.mail-archive.com/support@lists.openmoko.org/msg00564.html. Please change accordingly in /usr/share/openmoko/scenarios/gsmhandset.state. Should eliminate/lessen echo and buzz problems. [[Neo alsamixer]] is the main article for setting the mixer settings.<br />
<br />
===== Better set of mixer settings =====<br />
<br />
Regarding 2. in the previous paragraph, here are my further tweaked settings:<br />
<br />
[mic volume & buzz problem]<br />
* 'Mono Playback Volume' (95)<br />
* 'Mono Sidetone Playback Volume' (2)<br />
* 'Mic2 Capture Volume' (3)<br />
[speaker volume & echo problem]<br />
* 'Speaker Playback Volume' (112)<br />
* 'Bypass Playback Volume' (5)<br />
<br />
Lowering Mono Sidetone eliminated the buzz problem better. Please try out and report if you have good success... --[[User:TimoJyrinki|TimoJyrinki]] 08:19, 16 October 2008 (UTC)<br />
<br />
==== Can't boot with discharged or missing battery ====<br />
<br />
Issue: Neo FreeRunner requires battery power to boot, because Neo FreeRunner consumes too much current while booting to boot with only a charger. Since charging isn't enabled until the Neo FreeRunner has booted, this means that a discharged battery can not be charged. One manifestation of this problem is a kernel panic (red LED flashes constantly) when trying to boot using the power button.<br />
<br />
Affects: Unknown.<br />
<br />
Status: By properly sequencing module power sequence, a software solution to this problem should exist.<br />
<br />
Fixed(?) with [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003799.html Werner Almesberger patches] - [http://lists.openmoko.org/pipermail/commitlog/2008-July/005403.html more here] [http://lists.openmoko.org/pipermail/community/2008-July/023392.html additional information]<br />
<br />
I think this patch finally fixes the problem:<br />
[http://www.abanet.ch/~hug/moko/uboot-battery/ Philipp Hugs patches]<br />
<br />
Workarounds:<br />
<br />
# Make sure that the battery never discharges completely<br />
# Use [[:Image:Nokia-charging-stand.jpg|external stand-alone charger]] (compatible with the Nokia BL-5C battery)<br />
# Boot the FreeRunner with an [[Neo_FreeRunner_Battery#Compatible_Replacement_Batteries|alternative battery]], or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.<br />
# Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.<br />
## Oscilloscope digital clip probes fit perfectly on the Freerunner's battery connectors. Make sure polarity is correct!<br />
# Some users have reported that Neo FreeRunner '''is''' able to boot on USB power alone using the NOR u-boot, thus: press AUX, plug USB power, select boot. Reports of success would be appreciated.<br />
## Does work with sequence described. If after pressing boot it just turns off again (happened a few times), then: press AUX, plug in USB power, cycle through the menu a few times to keep it from turning off without booting, after a minute or so press boot. [[User:Imrehg|Imrehg]] 08:34, 10 September 2008 (UTC)<br />
## This does indeed work with sequence described. After pressing boot, the screen went blank for a few seconds, but then the beast came to life again. That saved the day! [[User:Edictor|Edictor]]<br />
## Trifirmed. Neither USB connection nor wall charger was able to wake my phone. But in NOR u-boot it worked (connected to the computer). I think this trick hasn't failed to anyone. --[[User:Flamma|Flamma]] 12:11, 17 September 2008 (UTC)<br />
## Unfortunately this is not working for me. My FreeRunner has been off for a few weeks and completely dead. I tried various combinations of holding aux and plugging in to both wall and computer, no luck. Tried with and without the battery in place, no luck. Aux and power button / just power / aux then power. No luck... --[[User:Safire|Safire]] 6 November 2008<br />
## This is working ! It has prevent me from buying an external power charger. My freerunner had its battery discharged for about 2 weeks now, and I was able to boot and charge it. --[[User:JRD|JRD]] 23:37, 12 November 2008 (UTC)<br />
## It has worked for me ! I have booted to 2008.9 Om with discharged battery (after connecting the FR to power supply and waiting a few minutes until AUX button red light stopped flashing) using the NOR boot menu. Tried the same with NAND boot menu and worked also !!! Then I could charge the battery. -- [[User:Emsyr|Emsyr]] 3:23, 20 November 2008 (UTC)<br />
## I can boot to 2008.9 without battery and with USB connection = plug USB power (FR <-> PC) + press power button. However I cannot shutdown correctly. --[[User:Cynan|Cynan]] 13:43, 9 December 2008 (UTC)<br />
## I can boot to 2008.9 without battery and with USB connection: press AUX button, then plug USB power, then press power button (keeping AUX pressed). NOTE that battery was fully charged. The problem wasn't battery but corrupted environment in NAND u-boot: with battery IN, no access to NOR u-boot<br />
## Both my friend's freerunner and mine was completely discharged. This trick failed. Finally booted the freerunner with a BL-5C battery from an old nokia n-gage. With the power connected I then switched the batteries. --[[User:Unlotto|Unlotto]] 14:27, 25 January 2009 (UTC)<br />
See also:<br />
:[[Neo_FreeRunner_Battery|Neo FreeRunner Battery]]<br />
<br />
==== Battery discharges when charging completes ====<br />
<br />
Issue: If the Neo FreeRunner has been charging, when charging completes, it seems to drain the battery and not turn on charging again. This seems to be bug of PMU-registers setup, that shows up when PMU has to handle bat autonomously (=suspend). There might be issues our current scheme relies on wake-interrupt at bat-full which doesn't succeed, or something like that.<br />
<br />
Affects: Unknown.<br />
<br />
Status:<br />
<br />
Workarounds:<br />
<br />
# When the battery is full, disconnect the charger<br />
<br />
See also:<br />
<br />
==== Suspend/resume corrupts SD card's partition table ====<br />
<br />
Issue: Suspend/resume corrupts the partition table of the SD card<br />
<br />
Affects: Unknown.<br />
<br />
Status:<br />
<br />
[[https://docs.openmoko.org/trac/ticket/1802#comment:6 Patched kernel]] might solve the problem<br />
<br />
Workarounds:<br />
<br />
# [[https://docs.openmoko.org/trac/ticket/1802#comment:5 Script]] as a temporary workaround<br />
<br />
See also:<br />
<br />
:[[https://docs.openmoko.org/trac/ticket/1802 trac ticket]]<br />
<br />
==== Some SIMs Don't Work ====<br />
<br />
Issue: There are reports that some users cannot register with their GSM network when using certain SIM cards. See for example http://lists.openmoko.org/pipermail/community/2008-July/020370.html<br />
<br />
It is possible that there is more than one issue involved here. The observed problems ''might'' (i.e. some items are only speculation at this point) be caused by:<br />
<br />
* User error, not inserting the SIM in the correct orientation or not sliding the holder to the 'locked' position<br />
<br />
* Software issues that result in a locked SIM (not properly prompting the user for a PIN and then passing this to the SIM)<br />
<br />
* Mechanical issues with the SIM holder that prevent the pins from making reliable contact with the pads on the SIM. Note that only 6 of the 8 pins are used, and the remaining two are not connected.<br />
<br />
* Electrical incompatibility (some tests show problems with 1.8V SIMs while 2.9V ones work OK)<br />
<br />
* Firmware bugs in the TI Calypso GSM chipset. Note that one issue in this category was found and fixed on the GTA01 devices (#666 in Trac), and that specific problem should not affect the FreeRunner.<br />
<br />
* Defective SIMs, i.e. ones that do not comply with the applicable standards and are acknowledged as being defective by the carrier (even if they happen to work in some phones).<br />
<br />
* You may have true 3G operating at 2100 and your sim doesn't fallback to GSM. The Phone works on 850/1800/1900 or 900/1800/1900.<br />
<br />
See also:<br />
* http://wiki.openmoko.org/wiki/Carriers/ATT<br />
* http://wiki.openmoko.org/wiki/Carriers/Rogers<br />
<br />
Affects: Only a subset of users (details unknown).<br />
<br />
Status: Fixed in GSM firmware moko10-beta2 or later. See [[GSM/Flashing]] for instructions. Please add your information to [[FreeRunner_unable_to_work_with_3G_SIM_cards]] or [[GSM network registration]]<br />
<br />
Workarounds:<br />
<br />
# Please document your existing SIM card and provider in the table [[FreeRunner_unable_to_work_with_3G_SIM_cards|here]].<br />
# If the table mentioned above shows any SIM cards known to work with your provider, make note of these numbers.<br />
# Contact your network provider and request a new SIM card. You may wish to print out the table mentioned above and bring it with you to the store.<br />
# Add your experience with the new SIM card to the table mentioned above.<br />
<br />
=== Known/Accepted Issues ===<br />
<br />
This section lists items that are acknowledged as being less than ideal, but are considered to be acceptable in the shipping product. They will not be discussed in detail on this page.<br />
<br />
* Poor performance + slow bus speed of the Glamo GPU - discussed to death on the mailing lists and IRC.<br />
** stable-2.6.26 branch of kernel has wait states lowered, core speed increased from 50MHz to 80MHz and memory speed from 80MHz to 90MHz (the latter is also in stable branch) - these lessen the problem a bit, though it's slow still<br />
* [http://lists.openmoko.org/pipermail/hardware/2008-April/000055.html GPS antenna switch] driven out-of-spec - does not appear to have a significant effect on device performance<br />
* Poor low-frequency audio response with low-impedance headphones, e.g. as discussed in this thread: http://lists.openmoko.org/pipermail/openmoko-kernel/2008-March/001999.html (NOTE - this thread refers to pre-mass-production devices)<br />
** Can be fixed to an semi-acceptable level (if not high fidelity most probably) by adjusting "Bass Volume" to full (15) and "Bass Filter" to "100Hz @ 8kHz" (bass will be boosted <= 600Hz when playing back at 48kHz) or "200Hz @ 8kHz" (<= 1200Hz @ 48kHz). The default is 130Hz @ 48kHz and does not help much with the more wider scope of low frequencies.<br />
** Ideally someone would record output and find out which setting produces best output, ie. compensating for the loss of low frequencies without boosting too high frequencies with this "bass" boost.<br />
<br />
Actually with 16 Ohm headphones the cutoff frequency is more than 2kHz, so even 1200Hz @ 48kHz seems to be not appropriate.<br />
If you have 30 Ohm, it might be just correct setting.<br />
<br />
=== Resolved Issues ===<br />
<br />
These are issues that have been discussed in the past, but have been fixed (or turned out not to be a problem) for the mass-produced devices.<br />
<br />
* Excessive LED current - Some early units lacked a current-limiting resistor for the LEDs. This has been fixed for the production units.<br />
* Battery life - At this time it appears that the FreeRunner battery life will be acceptable once suspend/resume support has been implemented in software.<br />
* slow GPS TTFF - see [[GPS Problems]]<br />
==== Empty NOR Flash ====<br />
<br />
Issue: NOR flash (backup copy of u-boot) is not programmed. [http://docs.openmoko.org/trac/ticket/1568 #1568]<br />
<br />
Affects: Unknown - maybe only 1 or 2 devices? Also need to confirm that the bug report was from a mass-production unit rather than an earlier prototype.<br />
<br />
Status: Solved. The new devices are tested better if they have the NOR flashed programmed and aren't shipped if the test fail.<br />
<br />
Workarounds: Use the NAND copy of u-boot and be careful not to brick the device unless a debug-board is available.<br />
<br />
<br />
==== Debug board has wrong vendor/product ID ====<br />
<br />
Issue: A debug board is not reporting the expected USB Vendor/Product ID.<br />
<br />
Affects: Only [http://lists.openmoko.org/pipermail/device-owners/2008-July/001775.html one report] has been seen so far.<br />
<br />
Status: Probably a single case scenario.<br />
<br />
Workarounds: Edit configuration files (e.g. openocd.conf) to use the IDs that the board is reporting.<br />
<br />
== List of "Current issues" Imported from the "Community update page" ==<br />
(to be sorted)<br />
<br />
The information below has been collected from various sources, feel free to add questions and comments here.<br />
<br />
===GPS Performance of the FreeRunner===<br />
The poor GPS performance on the FreeRunner has been traced to an<br />
interaction between the microSD card and the GPS unit. A software<br />
and a hardware fixes are available, see [[GPS Problems]].<br />
<br />
===GTA02 battery status===<br />
While writing a device driver for the new battery which provides an accurate counter of the charge state of the [[GTA02]], the driver developer discovered that the device driver does not get a reading of the charge state due to a very long response time with only one I/O signal when trying to read the charge state. To be able to read the battery status properly, it has been written that it will be necessary to re-design that part of the GTA02 for hardware version GTA02A5 to use two I/O signals to reduce the response time (one for transmitting commands, one for receiving data?). This was fixed two months ago (see [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=957#c1 Bug 957]).<br />
<br />
===Delivery of a GSM firmware update for the 3G SIM bug ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666 #666])===<br />
<br />
A bug in the GSM firwmare of Neo 1973 caused some 3G SIM cards to not work with Neo 1973. This Neo 1973 GSM firmware update can only be installed by an Openmoko employee due to licensing issues.<br />
<br />
This fix is already present in the Neo FreeRunner firwmare, and thus the Neo 1973 GSM firmware update is not required for the Neo FreeRunner. In fact since the firmware differs between the Neo 1973 and the Neo FreeRunner, it would very likely make the GSM module unusable.<br />
<br />
There seem to be other GSM issues on the Neo FreeRunner. See [[#Some_SIMs_Don.27t_Work|Some SIMs Don't Work]] above.<br />
<br />
=== SMedia 3362 Documentation & OpenGL ES Drivers ===<br />
There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and Openmoko developers will not be writing one in the near future (although they have not ruled it out in the long-term).<br />
<br />
Documentation for the SMedia 3362 has been promised ([http://lists.openmoko.org/pipermail/community/2007-September/010175.html see this post]). However, this refers to documentation Openmoko developers will be writing themselves, not the technical documentation SMedia have provided Openmoko with. The Openmoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See [http://lists.openmoko.org/pipermail/community/2007-November/011349.html this post] for details)<br />
<br />
=== Power Management on the Neo1973/FreeRunner===<br />
The current battery life of the Neo1973 and FreeRunner is not satisfactory. A lot of changes seem to be necessary to the kernel, drivers and related user-space applications. Hopefully the situation will improve over time.<br />
<br />
=== Draws too much current from USB ===<br />
Unless the battery is full, the device draws more than 500mA from the USB Device. Some devices then - correctly - switch off this presumably defect device, instead of limiting the current at the expense of too low voltage supplied. <br />
<br />
[[Category:Neo FreeRunner Hardware]]</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-28T15:06:24Z<p>Rainglasz: /* OM 2008.12 */ Boot fail message</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS<br />
<br />
=== OM 2008.9 ===<br />
Works (booted from SD), more to follow<br />
<br />
=== OM 2008.12 ===<br />
Does not boot from SD: <i>Only GTA01 Hardware supported by ASoc driver</i><br />
<br />
=== Qtopia ===<br />
Works fine (booted from SD), more to follow<br />
<br />
=== SHR ===<br />
Works fine (booted from SD)<br />
* Crashes WindowsXP-SP3 when connecting USB<br />
* Very slow (30% cpu time continuously in enlightenment)<br />
* WiFi access not yet working<br />
* Very quickly suspending<br />
* Phone calls working<br />
* tangoGPS gets location</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-27T22:08:18Z<p>Rainglasz: /* SHR */</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS<br />
<br />
=== OM 2008.9 ===<br />
Works (booted from SD), more to follow<br />
<br />
=== OM 2008.12 ===<br />
Crashes (booted from SD), more to follow<br />
<br />
=== Qtopia ===<br />
Works fine (booted from SD), more to follow<br />
<br />
=== SHR ===<br />
Works fine (booted from SD)<br />
* Crashes WindowsXP-SP3 when connecting USB<br />
* Very slow (30% cpu time continuously in enlightenment)<br />
* WiFi access not yet working<br />
* Very quickly suspending<br />
* Phone calls working<br />
* tangoGPS gets location</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-27T17:40:52Z<p>Rainglasz: /* SHR */</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS<br />
<br />
=== OM 2008.9 ===<br />
Works (booted from SD), more to follow<br />
<br />
=== OM 2008.12 ===<br />
Crashes (booted from SD), more to follow<br />
<br />
=== Qtopia ===<br />
Works fine (booted from SD), more to follow<br />
<br />
=== SHR ===<br />
Works fine (booted from SD)<br />
* Crashes WindowsXP-SP3 when connecting USB<br />
* Very slow (30% cpu time continuously in enlightenment)<br />
* WiFi access not yet working<br />
* Very quickly suspending<br />
* Outgoing Phone calls possible, incoming not<br />
* tangoGPS gets location</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-26T16:39:25Z<p>Rainglasz: Header lines for tested distributions; content to follow</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS<br />
<br />
=== OM 2008.9 ===<br />
Works (booted from SD), more to follow<br />
<br />
=== OM 2008.12 ===<br />
Crashes (booted from SD), more to follow<br />
<br />
=== Qtopia ===<br />
Works fine (booted from SD), more to follow<br />
<br />
=== SHR ===<br />
Works fine (booted from SD), more to follow</div>Rainglaszhttp://openmoko.org/wiki/User:RainglaszUser:Rainglasz2009-01-26T16:30:15Z<p>Rainglasz: New page: I am from Germany and working with computers nearly since the beginning; have a look at my [http://de.wikipedia.org/wiki/Benutzer:Rainglasz German Wikipedia page].</p>
<hr />
<div>I am from Germany and working with computers nearly since the beginning; have a look at my [http://de.wikipedia.org/wiki/Benutzer:Rainglasz German Wikipedia page].</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-26T16:29:05Z<p>Rainglasz: Moved about to right page</p>
<hr />
<div>== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-26T16:28:24Z<p>Rainglasz: /* About me */ Link to German Wikipedia</p>
<hr />
<div>== About me ==<br />
<br />
I am from Germany; please have a look to my [http://de.wikipedia.org/wiki/Benutzer:Rainglasz German Wikipedia page] to see some info until I extend this section here.<br />
<br />
== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-26T15:58:47Z<p>Rainglasz: /* My Log */</p>
<hr />
<div>== About me ==<br />
To be filled out soon<br />
<br />
<br />
== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02).<br />
<br />
Got it from [[http://www.pulster.de/openmoko.htm Pulster]] in Germany; <br />
extremely quick delivery, good prices and very nice people.<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking<br />
* No idea how to test GPS and WiFi; ''orrey'' did not read GPS</div>Rainglaszhttp://openmoko.org/wiki/NeoRndis.infNeoRndis.inf2009-01-26T15:44:31Z<p>Rainglasz: Warning Windows XP may crash</p>
<hr />
<div>To install the USB as Ethenet-over-USB under Microsoft Windows, you have to provide the following driver description (.inf) file. <br />
* First copy the file to your hard disk, then connect you device. <br />
* Point Windows to the .inf file when it asks for a driver. <br />
* Then edit the network configuration for the new network for fixed IP adress 192.168.0.200. <br />
* After this change, connect ssh (e.g. by putty) to 192.168.0.202<br />
<br />
'''Warning:''' WindowsXP may crash (Bluescreen: usb8023x.sys+0x1216 Datestamp 48025771), e.g. with SHR of December 22/23 [http://build.shr-project.org/shr-unstable/images/om-gta02/]<br />
<br />
<br />
Download [[Image:NeoRndis.inf.txt]] and drop .txt extension, or use this text:<br />
<br />
; Neo1973 USB Ethernet/RNDIS driver<br />
;<br />
; from the Template INF for a USB Remote NDIS Device<br />
; by Microsoft Corporation<br />
;<br />
; for Win2k you will need to download <br />
; http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx<br />
; and use "rndismpy.sys" and "usb8023y.sys"<br />
; from "RNDIS USB kit 2005\Drivers\x86fre\sys files"<br />
;<br />
; see http://wiki.openmoko.org/wiki/Neo1973_and_Windows<br />
; for further instructions<br />
<br />
[Version]<br />
Signature = "$Windows NT$"<br />
Class = Net<br />
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}<br />
Provider = %Linux%<br />
DriverVer = 08/03/2007,1.0.0.0<br />
; catalog file would be used by WHQL<br />
;CatalogFile = Linux.cat<br />
<br />
[Manufacturer]<br />
%Linux% = LinuxDevices,NT.5.1<br />
<br />
[LinuxDevices]<br />
%LinuxDevice% = RNDIS, USB\VID_1457&PID_5122<br />
<br />
[LinuxDevices.NT.5.1]<br />
%LinuxDevice% = RNDIS.NT.5.1, USB\VID_1457&PID_5122<br />
<br />
[ControlFlags]<br />
ExcludeFromSelect=*<br />
<br />
; Windows 2000 specific sections ---------------------------------<br />
<br />
[RNDIS.NT]<br />
Characteristics = 0x84 ; NCF_PHYSICAL + NCF_HAS_UI<br />
BusType = 15<br />
DriverVer = 08/03/2007,1.0.0.0<br />
AddReg = RNDIS_AddReg_NT, RNDIS_AddReg_WIN2K<br />
CopyFiles = RNDIS_CopyFiles_NT<br />
<br />
; DO NOT MODIFY THE SERVICE NAME<br />
[RNDIS.NT.Services]<br />
AddService = USB_RNDISY, 2, RNDIS_ServiceInst_NT, RNDIS_EventLog<br />
<br />
[RNDIS_CopyFiles_NT]<br />
; no rename of files on Windows 2000, use the 'y' names as is<br />
usb8023y.sys, , , 0 <br />
rndismpy.sys, , , 0 <br />
<br />
[RNDIS_ServiceInst_NT]<br />
DisplayName = %ServiceDisplayName%<br />
ServiceType = 1 <br />
StartType = 3 <br />
ErrorControl = 1 <br />
ServiceBinary = %12%\usb8023y.sys <br />
LoadOrderGroup = NDIS<br />
AddReg = RNDIS_WMI_AddReg_NT<br />
<br />
[RNDIS_WMI_AddReg_NT]<br />
HKR, , MofImagePath, 0x00020000, "System32\drivers\rndismpy.sys"<br />
<br />
; Windows XP specific sections -----------------------------------<br />
<br />
[RNDIS.NT.5.1]<br />
Characteristics = 0x84 ; NCF_PHYSICAL + NCF_HAS_UI<br />
BusType = 15<br />
DriverVer = 08/03/2007,1.0.0.0<br />
AddReg = RNDIS_AddReg_XP<br />
include = netrndis.inf<br />
needs = Usb_Rndis.ndi<br />
<br />
; no copyfiles - the files are already in place<br />
<br />
[RNDIS.NT.5.1.Services]<br />
include = netrndis.inf<br />
needs = Usb_Rndis.ndi.Services<br />
<br />
; Windows 2000 sections <br />
<br />
; DO NOT MODIFY ServiceName<br />
[RNDIS_AddReg_NT]<br />
HKR, Ndi, Service, 0, "USB_RNDISY"<br />
HKR, Ndi\Interfaces, UpperRange, 0, "ndis5" <br />
HKR, Ndi\Interfaces, LowerRange, 0, "ethernet"<br />
<br />
[RNDIS_AddReg_WIN2K]<br />
HKR, , ReclaimRecv, 0x00010001, 1<br />
HKR, NDI\params\NetworkAddress, ParamDesc, 0, %NetworkAddress%<br />
HKR, NDI\params\NetworkAddress, type, 0, "edit"<br />
HKR, NDI\params\NetworkAddress, LimitText, 0, "12"<br />
HKR, NDI\params\NetworkAddress, UpperCase, 0, "1"<br />
HKR, NDI\params\NetworkAddress, default, 0, " "<br />
HKR, NDI\params\NetworkAddress, optional, 0, "1"<br />
<br />
[RNDIS_EventLog]<br />
AddReg = RNDIS_EventLog_AddReg<br />
<br />
[RNDIS_EventLog_AddReg]<br />
HKR, , EventMessageFile, 0x00020000, "%%SystemRoot%%\System32\netevent.dll"<br />
HKR, , TypesSupported, 0x00010001, 7<br />
<br />
; An optional Property to demonstrate adding advanced properties on Windows XP <br />
[RNDIS_AddReg_XP]<br />
HKR, NDI\params\XPProperty, ParamDesc, 0, %NetworkAddress%<br />
HKR, NDI\params\XPProperty, type, 0, "edit"<br />
HKR, NDI\params\XPProperty, LimitText, 0, "12"<br />
HKR, NDI\params\XPProperty, UpperCase, 0, "1"<br />
HKR, NDI\params\XPProperty, default, 0, " "<br />
HKR, NDI\params\XPProperty, optional, 0, "1"<br />
<br />
<br />
[SourceDisksNames]<br />
1=%SourceDisk%,,1<br />
<br />
[SourceDisksFiles]<br />
usb8023y.sys=1<br />
rndismpy.sys=1<br />
<br />
[DestinationDirs]<br />
RNDIS_CopyFiles_NT = 12<br />
<br />
; DO NOT CHANGE ServiceDisplayName<br />
[Strings]<br />
ServiceDisplayName = "USB Remote NDIS Network Device Driver"<br />
NetworkAddress = "Network Address"<br />
Linux = "Linux Developer Community"<br />
LinuxDevice = "Neo1973 USB Ethernet/RNDIS"<br />
SourceDisk = "Ethernet/RNDIS Gadget Driver Install Disk"<br />
<br />
[[Category:Application Developer]]</div>Rainglaszhttp://openmoko.org/wiki/NeoRndis.infNeoRndis.inf2009-01-26T15:37:25Z<p>Rainglasz: Also downloadable</p>
<hr />
<div>To install the USB as Ethenet-over-USB under Microsoft Windows, you have to provide the following driver description (.inf) file. <br />
* First copy the file to your hard disk, then connect you device. <br />
* Point Windows to the .inf file when it asks for a driver. <br />
* Then edit the network configuration for the new network for fixed IP adress 192.168.0.200. <br />
* After this change, connect ssh (e.g. by putty) to 192.168.0.202<br />
<br />
Download [[Image:NeoRndis.inf.txt]] and drop .txt extension, or use this text:<br />
<br />
; Neo1973 USB Ethernet/RNDIS driver<br />
;<br />
; from the Template INF for a USB Remote NDIS Device<br />
; by Microsoft Corporation<br />
;<br />
; for Win2k you will need to download <br />
; http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx<br />
; and use "rndismpy.sys" and "usb8023y.sys"<br />
; from "RNDIS USB kit 2005\Drivers\x86fre\sys files"<br />
;<br />
; see http://wiki.openmoko.org/wiki/Neo1973_and_Windows<br />
; for further instructions<br />
<br />
[Version]<br />
Signature = "$Windows NT$"<br />
Class = Net<br />
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}<br />
Provider = %Linux%<br />
DriverVer = 08/03/2007,1.0.0.0<br />
; catalog file would be used by WHQL<br />
;CatalogFile = Linux.cat<br />
<br />
[Manufacturer]<br />
%Linux% = LinuxDevices,NT.5.1<br />
<br />
[LinuxDevices]<br />
%LinuxDevice% = RNDIS, USB\VID_1457&PID_5122<br />
<br />
[LinuxDevices.NT.5.1]<br />
%LinuxDevice% = RNDIS.NT.5.1, USB\VID_1457&PID_5122<br />
<br />
[ControlFlags]<br />
ExcludeFromSelect=*<br />
<br />
; Windows 2000 specific sections ---------------------------------<br />
<br />
[RNDIS.NT]<br />
Characteristics = 0x84 ; NCF_PHYSICAL + NCF_HAS_UI<br />
BusType = 15<br />
DriverVer = 08/03/2007,1.0.0.0<br />
AddReg = RNDIS_AddReg_NT, RNDIS_AddReg_WIN2K<br />
CopyFiles = RNDIS_CopyFiles_NT<br />
<br />
; DO NOT MODIFY THE SERVICE NAME<br />
[RNDIS.NT.Services]<br />
AddService = USB_RNDISY, 2, RNDIS_ServiceInst_NT, RNDIS_EventLog<br />
<br />
[RNDIS_CopyFiles_NT]<br />
; no rename of files on Windows 2000, use the 'y' names as is<br />
usb8023y.sys, , , 0 <br />
rndismpy.sys, , , 0 <br />
<br />
[RNDIS_ServiceInst_NT]<br />
DisplayName = %ServiceDisplayName%<br />
ServiceType = 1 <br />
StartType = 3 <br />
ErrorControl = 1 <br />
ServiceBinary = %12%\usb8023y.sys <br />
LoadOrderGroup = NDIS<br />
AddReg = RNDIS_WMI_AddReg_NT<br />
<br />
[RNDIS_WMI_AddReg_NT]<br />
HKR, , MofImagePath, 0x00020000, "System32\drivers\rndismpy.sys"<br />
<br />
; Windows XP specific sections -----------------------------------<br />
<br />
[RNDIS.NT.5.1]<br />
Characteristics = 0x84 ; NCF_PHYSICAL + NCF_HAS_UI<br />
BusType = 15<br />
DriverVer = 08/03/2007,1.0.0.0<br />
AddReg = RNDIS_AddReg_XP<br />
include = netrndis.inf<br />
needs = Usb_Rndis.ndi<br />
<br />
; no copyfiles - the files are already in place<br />
<br />
[RNDIS.NT.5.1.Services]<br />
include = netrndis.inf<br />
needs = Usb_Rndis.ndi.Services<br />
<br />
; Windows 2000 sections <br />
<br />
; DO NOT MODIFY ServiceName<br />
[RNDIS_AddReg_NT]<br />
HKR, Ndi, Service, 0, "USB_RNDISY"<br />
HKR, Ndi\Interfaces, UpperRange, 0, "ndis5" <br />
HKR, Ndi\Interfaces, LowerRange, 0, "ethernet"<br />
<br />
[RNDIS_AddReg_WIN2K]<br />
HKR, , ReclaimRecv, 0x00010001, 1<br />
HKR, NDI\params\NetworkAddress, ParamDesc, 0, %NetworkAddress%<br />
HKR, NDI\params\NetworkAddress, type, 0, "edit"<br />
HKR, NDI\params\NetworkAddress, LimitText, 0, "12"<br />
HKR, NDI\params\NetworkAddress, UpperCase, 0, "1"<br />
HKR, NDI\params\NetworkAddress, default, 0, " "<br />
HKR, NDI\params\NetworkAddress, optional, 0, "1"<br />
<br />
[RNDIS_EventLog]<br />
AddReg = RNDIS_EventLog_AddReg<br />
<br />
[RNDIS_EventLog_AddReg]<br />
HKR, , EventMessageFile, 0x00020000, "%%SystemRoot%%\System32\netevent.dll"<br />
HKR, , TypesSupported, 0x00010001, 7<br />
<br />
; An optional Property to demonstrate adding advanced properties on Windows XP <br />
[RNDIS_AddReg_XP]<br />
HKR, NDI\params\XPProperty, ParamDesc, 0, %NetworkAddress%<br />
HKR, NDI\params\XPProperty, type, 0, "edit"<br />
HKR, NDI\params\XPProperty, LimitText, 0, "12"<br />
HKR, NDI\params\XPProperty, UpperCase, 0, "1"<br />
HKR, NDI\params\XPProperty, default, 0, " "<br />
HKR, NDI\params\XPProperty, optional, 0, "1"<br />
<br />
<br />
[SourceDisksNames]<br />
1=%SourceDisk%,,1<br />
<br />
[SourceDisksFiles]<br />
usb8023y.sys=1<br />
rndismpy.sys=1<br />
<br />
[DestinationDirs]<br />
RNDIS_CopyFiles_NT = 12<br />
<br />
; DO NOT CHANGE ServiceDisplayName<br />
[Strings]<br />
ServiceDisplayName = "USB Remote NDIS Network Device Driver"<br />
NetworkAddress = "Network Address"<br />
Linux = "Linux Developer Community"<br />
LinuxDevice = "Neo1973 USB Ethernet/RNDIS"<br />
SourceDisk = "Ethernet/RNDIS Gadget Driver Install Disk"<br />
<br />
[[Category:Application Developer]]</div>Rainglaszhttp://openmoko.org/wiki/File:NeoRndis.inf.txtFile:NeoRndis.inf.txt2009-01-26T15:35:33Z<p>Rainglasz: Neo1973 USB Ethernet/RNDIS driver Installation script</p>
<hr />
<div>Neo1973 USB Ethernet/RNDIS driver Installation script</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-26T12:26:38Z<p>Rainglasz: Added OM 2007.2 remaks</p>
<hr />
<div>== About me ==<br />
To be filled out soon<br />
<br />
<br />
== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02)<br />
<br />
=== OM 2007.2 ===<br />
This was installed when shipped; remains until I find a stable later solution<br />
<br />
* Remarkebly stable and working version, useable for telephony and without pen.<br />
* Some problems with SMS messages reappeaing<br />
* phone-like data entry is boing, but woking</div>Rainglaszhttp://openmoko.org/wiki/User_talk:RainglaszUser talk:Rainglasz2009-01-25T22:15:20Z<p>Rainglasz: Intial template</p>
<hr />
<div>== About me ==<br />
To be filled out soon<br />
<br />
<br />
== My Log ==<br />
Here I write down what I experience with my FreeRunner (GTA02)</div>Rainglaszhttp://openmoko.org/wiki/U-BootU-Boot2009-01-24T20:26:14Z<p>Rainglasz: /* Using usbtty from Linux */ Minor additions</p>
<hr />
<div>{{Languages|Bootloader}}<br />
<br />
[[Image:GTA01-U-Boot.JPG|thumb|300px|u-boot menu on Neo1973]] [[Image:Neo1973 uboot splash closeup.jpg|thumb|300px|u-boot splash screen on Neo1973]]<br />
<br />
The bootloader used on the smartphones is called '''U-Boot'''. It takes care of device functionality until Openmoko is booted. This includes [[USB DFU]] for [[Flashing the Neo FreeRunner]], a splash screen, a boot menu, a console for [[bootloader commands]], configuration via [[bootloader environment]], and loading a [[kernel]].<br />
<br />
There are various [[bootloader versions]] available. Newer yet is [[Qi]].<br />
<br />
== Booting into U-boot ==<br />
<br />
* Make sure that your phone has had the battery and USB cable removed for at least 30 seconds.<br />
* Hold in the AUX button on power-up to access the boot menu.<br />
* Connect the Neo (ie not Debug Board) to a Linux host with the USB cable.<br />
* Set the console to USB.<br />
* Connect to /dev/ttyACM0 with a terminal program on the Linux host (you might need to chown uucp.uucp /dev/ttyACM0 )<br />
* Note that the cdc_acm /dev/ttyACM0 access disappears as soon as the Neo boots, and is replaced by the cdc_ether usb0 network access.<br />
* You're now at the bootloader prompt.<br />
* Set the bootdelay uboot environment variable to -1 if you want it to always halt at the bootloader on power-up.<br />
<br />
== General ==<br />
<br />
All versions of the OM smartphone use the [http://u-boot.sourceforge.net/ u-boot] bootloader.<br />
<br />
More information on u-boot can be found at<br />
* http://www.denx.de/wiki/DULG<br />
* http://www.gumstix.org/tikiwiki/tiki-index.php?page=U-Boot<br />
* http://linuxdevices.com/articles/AT5085702347.html<br />
<br />
Additions to the vanilla u-boot already implemented include:<br />
* Support for boot from NAND flash using [[S3C2410 Steppingstone]]<br />
* Support for S3C2410 NAND flash<br />
* Support for downloading programs via S3C2410 USB Device Controller<br />
* Support to display bootup logo / status on S3C2410 Framebuffer<br />
<br />
However, u-boot still doesn't support many of the features that GTA01 needs, such as<br />
* Support for reading kernel/initrd from SD/Transflash<br />
<br />
[[User:HaraldWelte|HaraldWelte]] is working on those issues, and in fact most of them have already been implemented.<br />
<br />
== Bootloader source code ==<br />
<br />
The current bootloader source can be found at http://git.openmoko.org/?p=u-boot.git;a=shortlog;h=stable .<br />
<br />
To get u-boot by git:<br />
<br />
git clone git://git.openmoko.org/git/u-boot.git openmoko/u-boot<br />
<br />
To build u-boot:<br />
* Clone the git tree and check out the stable branch<br />
* Set the CROSS_COMPILE environment variable to specify the prefix to your toolchain binaries<br />
* Run "make gta02v5_config" (or gta01bv4_config, or whatever hardware revision you have)<br />
* Run "make u-boot.udfu". This will give you an image which you can install with dfu-util, or which you can upload into memory via JTAG (with a debug board)<br />
<br />
== Bootloader binary ==<br />
<br />
The latest bootloader binary builds can be found under http://downloads.openmoko.org/daily/ .<br />
<br />
All versions of the GTA02 (Neo FreeRunner) that have been sold to the public are version 5 hardware, so look for a file with "gta02" and "v5" in the name, for example:<br />
uboot-gta02v5-latest.bin<br />
<br />
The file should be written to the NAND flash address 0x00000000 (size 0x30000) (the first [[Partitions|partition]]).<br />
<br />
== Bootloader development ==<br />
<br />
=== QT2410 ===<br />
If you want to do bootloader development on the QT2410, it's easier to work with a bootloader image that can be downloaded via USB into RAM instead of flashing.<br />
<br />
To do so, you need to edit the u-boot/include/configs/qt2410.h file, and change the "if 0" in Line 32 into a "if 1", then recompile with "make".<br />
<br />
The resulting "u-boot.bin" is _NOT SUITABLE_ for NAND flash, but only for direct execution from within ram, e.g. by using the [[s3c2410_boot_usb]] program.<br />
<br />
=== Neo 1973 ===<br />
<br />
Doing bootloader development on the [[Neo 1973]] is a bit more tricky. First, we don't have any NOR flash. Second, there is no other way to boot _but_ from NAND. Therefore, we also don't have a USB downloader like the QT2410.<br />
<br />
The main problem is: The [[S3C2410 Steppingstone]] unconditionally copies the first 4k of flash into its internal SRAM. That SRAM segment stays unconditionally mapped at physical address zero. How do we get around this<br />
<br />
=== Neo FreeRunner ===<br />
{{main|Neo_FreeRunner_Memory_Mapping}}<br />
<br />
==== Using JTAG to boot from RAM ====<br />
<br />
So how can we boot from RAM? We use JTAG / OpenOCD to:<br />
<br />
* Reset and halt the cpu at PC=0<br />
<pre><br />
> reset halt<br />
target halted in ARM state due to debug request, current mode: Supervisor<br />
cpsr: 0x400000d3 pc: 0x00000000<br />
MMU: disabled, D-Cache: disabled, I-Cache: disabled<br />
</pre><br />
<br />
* Download a small piece of code for low-level SDRAM timing initialization (overwrite 4k SRAM of steppingstone)<br />
<pre><br />
> load_binary /space/misc/gta01/u-boot.git/board/gta01/lowlevel_foo.bin 0<br />
downloaded 332 byte in 0s 21899us<br />
</pre><br />
<br />
* Assert a break point at address 0x33f80000 (which indicates that the low-level code has finished)<br />
<pre><br />
> bp 0x33f80000 4 hw<br />
breakpoint added at address 0x33f80000<br />
</pre><br />
<br />
* Run the code up to the break point<br />
<pre><br />
> resume<br />
Target 0 resumed<br />
> Target 0 halted<br />
target halted in ARM state due to breakpoint, current mode: Supervisor<br />
cpsr: 0x600000d3 pc: 0x33f80000<br />
MMU: disabled, D-Cache: disabled, I-Cache: enabled<br />
</pre><br />
<br />
* Download the u-boot RAM image to 0x33f80000<br />
<pre><br />
> load_binary /space/misc/gta01/u-boot.git/u-boot.bin 0x33f80000<br />
downloaded 135692 byte in 6s 567264us<br />
</pre><br />
<br />
* Resume processing<br />
<pre><br />
> resume<br />
Target 0 resumed<br />
</pre><br />
<br />
At this point, the display backlight gets bright and we see the following familiar prompt on the serial console:<br />
<pre><br />
U-Boot 1.1.6 (Jan 13 2007 - 23:44:23)<br />
<br />
DRAM: 128 MB<br />
NAND: 64 MiB<br />
*** Warning - bad CRC or NAND, using default environment<br />
<br />
In: serial<br />
Out: serial<br />
Err: serial<br />
Hit any key to stop autoboot: 0<br />
GTA01Bv2 #<br />
</pre><br />
<br />
== Creating bootable images ==<br />
<br />
U-boot needs bootable images (such as kernels, but also initrd and others) in form of a so-called ''uImage''. In order to create a ''uImage'' from e.g. a ''vmlinux'' kernel image, you can proceed as follows:<br />
<br />
<pre><br />
objcopy -O binary -R .note -R .comment -S vmlinux linux.bin<br />
gzip -9 linux.bin<br />
u-boot/tools/mkimage -A arm -O linux -T kernel -C gzip -a 30008000 -e 30008000 -n "Kernel Image QT2410" -d linux.bin.gz uImage<br />
</pre><br />
<br />
== Boot menu ==<br />
[[Image:Neo1973 uboot menu.jpg|thumb|400px|u-boot boot menu on Neo1973]]<br />
<br />
As of the Phase-0 release, our u-boot version now features an on-screen boot menu. The items are defined by [[bootloader environment#menu|menu entries in the environment]].<br />
<br />
=== Accessing the boot menu ===<br />
<br />
You can access the boot menu by pressing and holding the [[Neo1973 AUX Button]] together with the power button while switching the phone on.<br />
<br />
=== Using the boot menu ===<br />
<br />
By pressing the [[Neo1973 AUX Button]] you can cycle through the menu items. Use the ''POWER'' button to select one item.<br />
<br />
== Bootloader prompt ==<br />
<br />
=== Accessing the bootloader prompt ===<br />
The bootloader prompt is available either on the serial console (via [[Debug Board]]), or as virtual USB Serial device (USB CDC_ACM).<br />
Whether the serial port or usb is used depends on the u-boot environment variables '''stdin''', '''stdout''' and '''stderr'''.<br />
<br />
Whether or not you use usbtty, the first couple of messages will always be displayed on the serial console.<br />
<br />
The bootloader is currently configured to wait for three seconds. If a key press on the '''stdin''' is received within those three seconds, auto-boot is aborted.<br />
<br />
==== Using usbtty from Linux ====<br />
<br />
Just by connecting the phone in u-boot mode to your Linux pc should make it detect a [[CDC ACM]] device, and you should get a new tty device called /dev/ttyACM0. If not, check that module cdc_acm is loaded or CONFIG_USB_ACM=y (Device Drivers -> USB support -> USB Modem (CDC ACM) support). (Instructions for MacOS users are [[MacOS_X#USB_Serial|here]])<br />
<br />
Use your favourite terminal emulator (minicom, cu, zc, screen ...) to access it like any other serial port. Clear any modem intialisation strings (minicom).<br />
<br />
You can adapt the instructions for USB-serial from the [[MacOS_X#USB_Serial|Mac OS]] page.<br />
If you don't have a favorite, try just: (cu is in the taylor-uucp package, use "apt-get install cu" if it is not yet installed)<br />
cu -l /dev/ttyACM0<br />
<br />
You might need to<br />
chown uucp.uucp /dev/ttyACM0<br />
to get the necessary rights (even as root, must be done each time).<br />
<br />
A nice alternative for cu is Werner Almesberger's [[NeoCon|neocon]].<br />
<br />
First, you should try to check whether the USB device shows up in 'lsusb' while you're running in u-boot mode:<br />
<br />
<pre><br />
# lsusb -d 1457:5119<br />
Bus 005 Device 079: ID 1457:5119<br />
</pre><br />
'''Note''': The Neo Freerunner (GTA02) has the ID 1d50:5119<br />
<br />
Second, let's see some more details about the available endpoints and configurations:<br />
<br />
<pre><br />
# lsusb -v -d 1457:5119<br />
Bus 005 Device 079: ID 1457:5119<br />
Device Descriptor:<br />
bLength 18<br />
bDescriptorType 1<br />
bcdUSB 1.10<br />
bDeviceClass 2 Communications<br />
bDeviceSubClass 0<br />
bDeviceProtocol 0<br />
bMaxPacketSize0 16<br />
idVendor 0x1457<br />
idProduct 0x5119<br />
bcdDevice 0.00<br />
iManufacturer 1 Openmoko, Inc<br />
iProduct 2 Neo1973 Bootloader U-Boot 1.2.0-g6c7cac8c-dirty-moko3<br />
iSerial 3 0000000<br />
bNumConfigurations 1<br />
Configuration Descriptor:<br />
bLength 9<br />
bDescriptorType 2<br />
wTotalLength 85<br />
bNumInterfaces 3<br />
bConfigurationValue 1<br />
iConfiguration 4 TTY via USB<br />
bmAttributes 0xc0<br />
Self Powered<br />
MaxPower 0mA<br />
Interface Descriptor:<br />
bLength 9<br />
bDescriptorType 4<br />
bInterfaceNumber 0<br />
bAlternateSetting 0<br />
bNumEndpoints 1<br />
bInterfaceClass 2 Communications<br />
bInterfaceSubClass 2 Abstract (modem)<br />
bInterfaceProtocol 1 AT-commands (v.25ter)<br />
iInterface 6 Control Interface<br />
CDC Header:<br />
bcdCDC 0.6e<br />
CDC Call Management:<br />
bmCapabilities 0x00<br />
bDataInterface 1<br />
CDC ACM:<br />
bmCapabilities 0x00<br />
CDC Union:<br />
bMasterInterface 0<br />
bSlaveInterface 1<br />
Endpoint Descriptor:<br />
bLength 7<br />
bDescriptorType 5<br />
bEndpointAddress 0x81 EP 1 IN<br />
bmAttributes 3<br />
Transfer Type Interrupt<br />
Synch Type None<br />
Usage Type Data<br />
wMaxPacketSize 0x0010 1x 16 bytes<br />
bInterval 255<br />
Interface Descriptor:<br />
bLength 9<br />
bDescriptorType 4<br />
bInterfaceNumber 1<br />
bAlternateSetting 0<br />
bNumEndpoints 2<br />
bInterfaceClass 10 CDC Data<br />
bInterfaceSubClass 0 Unused<br />
bInterfaceProtocol 0<br />
iInterface 5 Bulk Data Interface<br />
Endpoint Descriptor:<br />
bLength 7<br />
bDescriptorType 5<br />
bEndpointAddress 0x02 EP 2 OUT<br />
bmAttributes 2<br />
Transfer Type Bulk<br />
Synch Type None<br />
Usage Type Data<br />
wMaxPacketSize 0x0010 1x 16 bytes<br />
bInterval 255<br />
Endpoint Descriptor:<br />
bLength 7<br />
bDescriptorType 5<br />
bEndpointAddress 0x83 EP 3 IN<br />
bmAttributes 2<br />
Transfer Type Bulk<br />
Synch Type None<br />
Usage Type Data<br />
wMaxPacketSize 0x0010 1x 16 bytes<br />
bInterval 255<br />
Interface Descriptor:<br />
bLength 9<br />
bDescriptorType 4<br />
bInterfaceNumber 2<br />
bAlternateSetting 0<br />
bNumEndpoints 0<br />
bInterfaceClass 254 Application Specific Interface<br />
bInterfaceSubClass 1 Device Firmware Update<br />
bInterfaceProtocol 1<br />
iInterface 7 USB Device Firmware Upgrade<br />
Device Status: 0x0001<br />
Self Powered<br />
</pre><br />
<br />
Next, you can access it using your favourite terminal program.<br />
<br />
Then, if the environment is not set correctly, you will need to use the current console (e.g. serial console) to change the [[bootloader environment#console|console entries in the environment]]:<br />
<pre><br />
GTA01Bv2 # setenv stderr usbtty<br />
GTA01Bv2 # setenv stdout usbtty<br />
GTA01Bv2 # setenv stdin usbtty<br />
</pre><br />
<br />
==== Typical u-boot prompt ====<br />
<br />
<pre><br />
U-Boot 1.2.0-moko1 (Feb 16 2007 - 00:36:13)<br />
<br />
DRAM: 128 MB<br />
NAND: 64 MiB<br />
Found Environment offset in OOB..<br />
Video: 640x480x8 31kHz 59Hz<br />
USB: S3C2410 USB Deviced<br />
In: serial<br />
Out: serial<br />
Err: serial<br />
Hit any key to stop autoboot: 0<br />
GTA01Bv3 #<br />
</pre><br />
<br />
=== Commands on the bootloader prompt ===<br />
<br />
:''See [[bootloader commands]].''<br />
<br />
=== What if I borked my bootloader environment and don't get a prompt anymore? ===<br />
{{Note|This solution applies to a changed u-boot environment which prevents NAND u-boot to successfully boot. The Debian u-boot configuration script may be a cause of this issue.}}<br />
Found a solution here:<br />
[[http://markmail.org/message/gqypwiohdet6x4am?q=almesberger+partition&page=1&refer=xbamkzwwsaobv7wa]]<br />
<br />
It works the following way:<br />
* Get the devirginator:<br />
svn co http://svn.openmoko.org/trunk/src/host/devirginator<br />
cd devirginator<br />
* Read the u-boot environment from the device:<br />
dfu-util -a u-boot_env -R -U env.in<br />
* Create a file that contains everything you want to change in your u-boot environment or get it by issuing the following command:<br />
wget http://svn.openmoko.org/trunk/src/host/devirginator/environment.in<br />
* Now let devirginator generate a new u-boot_env partition for us, - that contains the partition table from our u-boot_env, - and all changes we wanted to make; Note that the -D GTA02 is needed for the neo FreeRunner only, and has to come before the other options.<br />
./envedit.pl -D GTA02 -i env.in -f environment.in -o env.out<br />
* On my box the partition layout didn't seem to match the idea of envedit.pl, so it issued 2 warnings:<br />
warning: environment is 262144 bytes, expected 16384<br />
CRC error: expected 0xc33e35fc, got 0x93097bfb<br />
* In this case jut add an additional argument to the command line - that has to be the 1st argument, though, and that contains the size information we got from the warning:<br />
./envedit.pl -s 262144 -D GTA02 -i env.in -f environment.in -o env.out<br />
* Now the perl script should produce no more output anything but write a new u-boot_env partition that we can upload to the device by:<br />
dfu-util -a u-boot_env -R -D env.out<br />
<br />
== Device Firmware Upgrade ==<br />
<br />
Our version of u-boot also implements [[USB DFU]]. This can be useful to<br />
load files and kernel for quick testing.<br />
<br />
To find out whether your version of u-boot supports this, use the output of<br />
$ lsusb -v -d 1457:5119<br />
while the phone is in u-boot mode.<br />
<br />
If it supports DFU, you should see the following snippet towards the end of the output:<br />
<pre><br />
Interface Descriptor:<br />
bLength 9<br />
bDescriptorType 4<br />
bInterfaceNumber 2<br />
bAlternateSetting 0<br />
bNumEndpoints 0<br />
bInterfaceClass 254 Application Specific Interface<br />
bInterfaceSubClass 1 Device Firmware Update<br />
bInterfaceProtocol 1<br />
iInterface 0<br />
</pre><br />
<br />
For information on how to do firmware upgrades, please see [[dfu-util]]. For neo 1973 you may see [[Flashing the Neo 1973#Actually_flashing_things_into_the_device]], and for the FreeRunner : [[Flashing the Neo FreeRunner]].<br />
<br />
=== Booting files over DFU ===<br />
<br />
To load a file at memory address 0x32000000:<br />
<pre><br />
dfu-util -a 0 -D fileToLoad -R<br />
</pre><br />
<br />
After that, send 'bootm 0x32000000' to u-boot or 'bootelf 0x32000000' if<br />
its an elf file.<br />
<br />
Simple python script that can boot an ELF image - avoiding a ACM bug that breaks on large packets.<br />
<br />
<pre><br />
#!/usr/bin/python<br />
import sys<br />
import os<br />
import time<br />
<br />
cmd1 = "neo backlight off\n"<br />
cmd2 = "bootelf 0x32000000\n"<br />
<br />
def output(tty, str):<br />
for x in str:<br />
tty.write(x)<br />
tty.flush()<br />
<br />
if len(sys.argv) == 2:<br />
print "Loading %s..." % sys.argv[1]<br />
<br />
loadfile = "dfu-util -a 0 -D %s -R" % sys.argv[1]<br />
<br />
os.system(loadfile)<br />
<br />
time.sleep(3)<br />
<br />
tty = open("/dev/ttyACM0", "a")<br />
<br />
output(tty, cmd1)<br />
output(tty, cmd2)<br />
<br />
tty.close()<br />
else:<br />
print "Usage: %s elffile" % sys.argv[0]<br />
print ""<br />
sys.exit(2)<br />
</pre><br />
<br />
== Troubleshooting ==<br />
<br />
=== USB connectivity problems ===<br />
<br />
I once got errors like this (in dmesg or /var/log/messages) on the host side while connecting the neo in u-boot:<br />
<br />
usb 2-1: device descriptor read/64, error -110<br />
usb usb2: Controller not stopped yet!<br />
<br />
or<br />
<br />
hub 4-0:1.0: port 1 disabled by hub (EMI?), re-enabling...<br />
usb 4-1: USB disconnect, address 2<br />
<br />
A possible solution is given below. Please note that if you have a usb keyboard or mouse then the command might cause trouble.<br />
<br />
rmmod uhci_hcd ; modprobe uhci_hcd<br />
<br />
Another option is to plug the FR into a different USB port on the host, preferably one on the Motherboard not the hub.<br />
<br />
Disconnecting the Neo's USB while powering up may prevent this problem in the future.<br />
<br />
== Related pages ==<br />
<br />
See [[Flashing the Neo 1973]] and [[Flashing the Neo FreeRunner]] for instructions on using dfu-util to install a new bootloader in your phone.<br />
<br />
[[Category:System Developers]]<br />
[[Category:Flashing Openmoko]]</div>Rainglaszhttp://openmoko.org/wiki/NeoRndis.infNeoRndis.inf2009-01-23T22:01:52Z<p>Rainglasz: Intro what to do</p>
<hr />
<div>To install the USB as Ethenet-over-USB under Microsoft Windows, you have to provide the following driver description (.inf) file. <br />
* First copy the file to your hard disk, then connect you device. <br />
* Point Windows to the .inf file when it asks for a driver. <br />
* Then edit the network configuration for the new network for fixed IP adress 192.168.0.200. <br />
* After this change, connect ssh (e.g. by putty) to 192.168.0.202<br />
<br />
; Neo1973 USB Ethernet/RNDIS driver<br />
;<br />
; from the Template INF for a USB Remote NDIS Device<br />
; by Microsoft Corporation<br />
;<br />
; for Win2k you will need to download <br />
; http://www.microsoft.com/whdc/device/network/NDIS/rndis.mspx<br />
; and use "rndismpy.sys" and "usb8023y.sys"<br />
; from "RNDIS USB kit 2005\Drivers\x86fre\sys files"<br />
;<br />
; see http://wiki.openmoko.org/wiki/Neo1973_and_Windows<br />
; for further instructions<br />
<br />
[Version]<br />
Signature = "$Windows NT$"<br />
Class = Net<br />
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}<br />
Provider = %Linux%<br />
DriverVer = 08/03/2007,1.0.0.0<br />
; catalog file would be used by WHQL<br />
;CatalogFile = Linux.cat<br />
<br />
[Manufacturer]<br />
%Linux% = LinuxDevices,NT.5.1<br />
<br />
[LinuxDevices]<br />
%LinuxDevice% = RNDIS, USB\VID_1457&PID_5122<br />
<br />
[LinuxDevices.NT.5.1]<br />
%LinuxDevice% = RNDIS.NT.5.1, USB\VID_1457&PID_5122<br />
<br />
[ControlFlags]<br />
ExcludeFromSelect=*<br />
<br />
; Windows 2000 specific sections ---------------------------------<br />
<br />
[RNDIS.NT]<br />
Characteristics = 0x84 ; NCF_PHYSICAL + NCF_HAS_UI<br />
BusType = 15<br />
DriverVer = 08/03/2007,1.0.0.0<br />
AddReg = RNDIS_AddReg_NT, RNDIS_AddReg_WIN2K<br />
CopyFiles = RNDIS_CopyFiles_NT<br />
<br />
; DO NOT MODIFY THE SERVICE NAME<br />
[RNDIS.NT.Services]<br />
AddService = USB_RNDISY, 2, RNDIS_ServiceInst_NT, RNDIS_EventLog<br />
<br />
[RNDIS_CopyFiles_NT]<br />
; no rename of files on Windows 2000, use the 'y' names as is<br />
usb8023y.sys, , , 0 <br />
rndismpy.sys, , , 0 <br />
<br />
[RNDIS_ServiceInst_NT]<br />
DisplayName = %ServiceDisplayName%<br />
ServiceType = 1 <br />
StartType = 3 <br />
ErrorControl = 1 <br />
ServiceBinary = %12%\usb8023y.sys <br />
LoadOrderGroup = NDIS<br />
AddReg = RNDIS_WMI_AddReg_NT<br />
<br />
[RNDIS_WMI_AddReg_NT]<br />
HKR, , MofImagePath, 0x00020000, "System32\drivers\rndismpy.sys"<br />
<br />
; Windows XP specific sections -----------------------------------<br />
<br />
[RNDIS.NT.5.1]<br />
Characteristics = 0x84 ; NCF_PHYSICAL + NCF_HAS_UI<br />
BusType = 15<br />
DriverVer = 08/03/2007,1.0.0.0<br />
AddReg = RNDIS_AddReg_XP<br />
include = netrndis.inf<br />
needs = Usb_Rndis.ndi<br />
<br />
; no copyfiles - the files are already in place<br />
<br />
[RNDIS.NT.5.1.Services]<br />
include = netrndis.inf<br />
needs = Usb_Rndis.ndi.Services<br />
<br />
; Windows 2000 sections <br />
<br />
; DO NOT MODIFY ServiceName<br />
[RNDIS_AddReg_NT]<br />
HKR, Ndi, Service, 0, "USB_RNDISY"<br />
HKR, Ndi\Interfaces, UpperRange, 0, "ndis5" <br />
HKR, Ndi\Interfaces, LowerRange, 0, "ethernet"<br />
<br />
[RNDIS_AddReg_WIN2K]<br />
HKR, , ReclaimRecv, 0x00010001, 1<br />
HKR, NDI\params\NetworkAddress, ParamDesc, 0, %NetworkAddress%<br />
HKR, NDI\params\NetworkAddress, type, 0, "edit"<br />
HKR, NDI\params\NetworkAddress, LimitText, 0, "12"<br />
HKR, NDI\params\NetworkAddress, UpperCase, 0, "1"<br />
HKR, NDI\params\NetworkAddress, default, 0, " "<br />
HKR, NDI\params\NetworkAddress, optional, 0, "1"<br />
<br />
[RNDIS_EventLog]<br />
AddReg = RNDIS_EventLog_AddReg<br />
<br />
[RNDIS_EventLog_AddReg]<br />
HKR, , EventMessageFile, 0x00020000, "%%SystemRoot%%\System32\netevent.dll"<br />
HKR, , TypesSupported, 0x00010001, 7<br />
<br />
; An optional Property to demonstrate adding advanced properties on Windows XP <br />
[RNDIS_AddReg_XP]<br />
HKR, NDI\params\XPProperty, ParamDesc, 0, %NetworkAddress%<br />
HKR, NDI\params\XPProperty, type, 0, "edit"<br />
HKR, NDI\params\XPProperty, LimitText, 0, "12"<br />
HKR, NDI\params\XPProperty, UpperCase, 0, "1"<br />
HKR, NDI\params\XPProperty, default, 0, " "<br />
HKR, NDI\params\XPProperty, optional, 0, "1"<br />
<br />
<br />
[SourceDisksNames]<br />
1=%SourceDisk%,,1<br />
<br />
[SourceDisksFiles]<br />
usb8023y.sys=1<br />
rndismpy.sys=1<br />
<br />
[DestinationDirs]<br />
RNDIS_CopyFiles_NT = 12<br />
<br />
; DO NOT CHANGE ServiceDisplayName<br />
[Strings]<br />
ServiceDisplayName = "USB Remote NDIS Network Device Driver"<br />
NetworkAddress = "Network Address"<br />
Linux = "Linux Developer Community"<br />
LinuxDevice = "Neo1973 USB Ethernet/RNDIS"<br />
SourceDisk = "Ethernet/RNDIS Gadget Driver Install Disk"<br />
<br />
[[Category:Application Developer]]</div>Rainglasz