Talk:Neo FreeRunner Hardware Issues - Revision history

Jiri: /* Bad device ID in debug board */

2009-11-19T19:50:57Z

‎Bad device ID in debug board

2009-11-19T19:50:37Z

‎Bad device ID in debug board: new section

2009-04-25T20:51:58Z

‎battery no longer a problem?: new section

2008-12-04T02:55:58Z

2008-11-12T15:18:13Z

‎Battery discharges when charging completes

2008-11-11T05:28:13Z

‎Battery discharges when charging completes: new section

2008-09-04T18:32:48Z

‎Battery issue: new section

2008-09-03T18:09:19Z

2008-08-28T07:10:45Z

2008-07-16T09:15:21Z

← Older revision		Revision as of 19:50, 19 November 2009
Line 47:		Line 47:
	I've run to the same issue as documented in this thread [http://lists.openmoko.org/pipermail/device-owners/2008-July/001775.html]. My debug board v3 comes from Golden Delicious, shipped at 16 Oct 2009. The vendorID:productID was 0x0403:0x6010 (instead of :0x6001). I fixed this by editing the default ID in ftdi_eeprom's main.c.		I've run to the same issue as documented in this thread [http://lists.openmoko.org/pipermail/device-owners/2008-July/001775.html]. My debug board v3 comes from Golden Delicious, shipped at 16 Oct 2009. The vendorID:productID was 0x0403:0x6010 (instead of :0x6001). I fixed this by editing the default ID in ftdi_eeprom's main.c.

−	So this issue seems to affect more than one piece.	+	So this issue seems to affect more than one piece. [[User:Jiri\|Jiri]] 19:50, 19 November 2009 (UTC)

← Older revision		Revision as of 19:50, 19 November 2009
Line 42:		Line 42:

	I just received my Neo FreeRunner GTA2 in April of '09 and the first thing I did, before reading that it was impossible on this page, was boot it up without a battery in it. I simply plugged in the USB charger and held down the power button until it came on. Perhaps later revisions of the FreeRunner no longer have the discharged-battery can't boot problem? I'd edit the page, but I can only vouch for my one FreeRunner. [[User:Hackerb9\|Hackerb9]] 20:51, 25 April 2009 (UTC)		I just received my Neo FreeRunner GTA2 in April of '09 and the first thing I did, before reading that it was impossible on this page, was boot it up without a battery in it. I simply plugged in the USB charger and held down the power button until it came on. Perhaps later revisions of the FreeRunner no longer have the discharged-battery can't boot problem? I'd edit the page, but I can only vouch for my one FreeRunner. [[User:Hackerb9\|Hackerb9]] 20:51, 25 April 2009 (UTC)
		+
		+	== Bad device ID in debug board ==
		+
		+	I've run to the same issue as documented in this thread [http://lists.openmoko.org/pipermail/device-owners/2008-July/001775.html]. My debug board v3 comes from Golden Delicious, shipped at 16 Oct 2009. The vendorID:productID was 0x0403:0x6010 (instead of :0x6001). I fixed this by editing the default ID in ftdi_eeprom's main.c.
		+
		+	So this issue seems to affect more than one piece.

← Older revision		Revision as of 20:51, 25 April 2009
Line 38:		Line 38:
	done		done
	</pre>		</pre>
		+
		+	== battery no longer a problem? ==
		+
		+	I just received my Neo FreeRunner GTA2 in April of '09 and the first thing I did, before reading that it was impossible on this page, was boot it up without a battery in it. I simply plugged in the USB charger and held down the power button until it came on. Perhaps later revisions of the FreeRunner no longer have the discharged-battery can't boot problem? I'd edit the page, but I can only vouch for my one FreeRunner. [[User:Hackerb9\|Hackerb9]] 20:51, 25 April 2009 (UTC)

@@ Line 10: / Line 10: @@
 Low Battery Booting Issue:
 I can report that I was able to reanimate my FreeRunner having an almost empty battery by pressing the AUX button and then attaching the USB power. A normal boot using the power button was not possible in any battery/USB power configuration, a kernel panic (red blinking LED) always occured.
 == Battery issue ==

@@ Line 23: / Line 23: @@
 i2c_dir="/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073"
 force_usb="${i2c_dir}/force_usb_limit_dangerous"
 charger_type="${i2c_dir}/charger_type"
@@ Line 31: / Line 30: @@
 charger=$(cut -c 1-4 ${charger_type})
 if [ ${charger} != "none" ] ; then
-cat ${usb_curlim} > ${force_usb}
+echo -n 500 > ${force_usb}
 fi
 sleep 1800
 done
 </pre>

← Older revision		Revision as of 05:28, 11 November 2008
Line 14:		Line 14:

	For me it worked to connect the Neo to power source and then boot via aux button, too.		For me it worked to connect the Neo to power source and then boot via aux button, too.
		+
		+	== Battery discharges when charging completes ==
		+
		+	Workaround: I leave this script running in the background to start charging again every half hour if the device is plugged in.
		+
		+	<pre>
		+	#!/bin/bash
		+
		+	i2c_dir="/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073"
		+	usb_curlim="${i2c_dir}/usb_curlim"
		+	force_usb="${i2c_dir}/force_usb_limit_dangerous"
		+	charger_type="${i2c_dir}/charger_type"
		+
		+	while true;
		+	do
		+	charger=$(cut -c 1-4 ${charger_type})
		+	if [ ${charger} != "none" ] ; then
		+	cat ${usb_curlim} > ${force_usb}
		+	fi
		+	sleep 1800
		+	done
		+	</pre>

← Older revision		Revision as of 18:32, 4 September 2008
Line 10:		Line 10:
	Low Battery Booting Issue:		Low Battery Booting Issue:
	I can report that I was able to reanimate my FreeRunner having an almost empty battery by pressing the AUX button and then attaching the USB power. A normal boot using the power button was not possible in any battery/USB power configuration, a kernel panic (red blinking LED) always occured.		I can report that I was able to reanimate my FreeRunner having an almost empty battery by pressing the AUX button and then attaching the USB power. A normal boot using the power button was not possible in any battery/USB power configuration, a kernel panic (red blinking LED) always occured.
		+
		+	== Battery issue ==
		+
		+	For me it worked to connect the Neo to power source and then boot via aux button, too.

@@ Line 7: / Line 7: @@
 radio shack has a go phone for $14 bucks buy it and call att and swap to the new sim card that comes with the go phone. Dont let ratshack activate the go phone. The first store i went to would not let me. The second store asked me and I said no.
 ---
-----
+Low Battery Booting Issue:

← Older revision		Revision as of 09:15, 16 July 2008
Line 1:		Line 1:
		+	For me this is what has worked...
		+
		+	For GPS
	I can confirm removing sd card allowed my gps to work correct. With card in can not get a fix from interntal antenna, remove card and it works good.		I can confirm removing sd card allowed my gps to work correct. With card in can not get a fix from interntal antenna, remove card and it works good.
		+
		+	For ATT Sim card
		+	radio shack has a go phone for $14 bucks buy it and call att and swap to the new sim card that comes with the go phone. Dont let ratshack activate the go phone. The first store i went to would not let me. The second store asked me and I said no.
		+
		+
		+	----