headers
Dr. H. Nikolaus Schaller | 1 Feb 08:08
Favicon

Re: [Gta04-owner] GTA04A4 starts shipping tomorrow


Am 31.01.2012 um 11:53 schrieb Dr. H. Nikolaus Schaller:

> 
> Am 31.01.2012 um 15:30 schrieb Gennady.Kupava:
>> As i were always wondering about SD reading issues in GTA02, which rises
>> voltage in driver with reduced clock at beginning, and is not working at
> 
> This is a patch in the GTA02 kernel to reduce noise *without* capacitor.
> Only GTA02A6 boards have it.
> 
>> 25MHz at all. I wonder can it be related to that capacitor? Are GTA04
>> users going to experience same speed issues with SD like in GTA02?
> 
> No. It works at full speed, even with capacitor.

Here:

Last login: Wed Feb  1 06:58:19 2012 from 192.168.0.200
gta04:~# hdparm -t /dev/mmcblk0

/dev/mmcblk0:
 Timing buffered disk reads:  56 MB in  3.09 seconds =  18.12 MB/sec
gta04:~# 

So it appears that the SD clock is even running at 50 MHz (SD is a 4 bit bus).
Permalink | Reply | 1 comment |
headers
Patryk Benderz | 1 Feb 09:24
Picon

Re: Installing v35

[cut]
> One is mine, and the buggy one my son's. They were bought at the same
> time. Neither has buzz-fix, they have the same date code on the
> internal sticker and the same date on the NOR boot screen.
[cut]
> Each would have had the NAND flashed between 10 and 20 times. I see
> the wiki suggests it should have lasted longer. 
So both these track gets us no where. However I have just reread through
your description of a problem and realised I had also some strange
problems (partial boot) which was resolved by flashing different qi
bootloader. Do both FR have the same bootloader?
--

-- 
Patryk "LeadMan" Benderz
Linux Registered User #377521
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments
Permalink | Reply | 9 comments |
headers
Gennady Kupava | 1 Feb 09:20

Re: [Gta04-owner] GTA04A4 starts shipping tomorrow

On Wed, 2012-02-01 at 08:08 +0100, Dr. H. Nikolaus Schaller wrote:

> Here:
> 
> Last login: Wed Feb  1 06:58:19 2012 from 192.168.0.200
> gta04:~# hdparm -t /dev/mmcblk0
> 
> /dev/mmcblk0:
>  Timing buffered disk reads:  56 MB in  3.09 seconds =  18.12 MB/sec
> gta04:~# 
> 
> So it appears that the SD clock is even running at 50 MHz (SD is a 4 bit bus).

Looks excellent, and may be even limited not by bus, but by sd card
itself. Sad that it's not possible to set clock to, say 51Mhz, to
eliminate GPS interference in it's roots.

Gena
Permalink | Reply | 0 comments |
headers
Liz | 1 Feb 10:40

Re: Installing v35

On Wed, 1 Feb 2012 08:15:11 +1000
Dave <dave.tv <at> gmail.com> wrote:

> Could it be that the AUX button is jammed closed. If powered on while
> AUX is pressed is how I get to a NOR boot.

Thanks for remembering, but already checked, and is OK.
Permalink | Reply | 0 comments |
headers
Liz | 1 Feb 10:55

Re: Installing v35

On Wed, 01 Feb 2012 09:24:29 +0100
Patryk Benderz <Patryk.Benderz <at> esp.pl> wrote:

>  However I have just reread through
> your description of a problem and realised I had also some strange
> problems (partial boot) which was resolved by flashing different qi
> bootloader. Do both FR have the same bootloader?

Currently yes, qi-v35.udfu
I have also tried the qi-31.udfu u-boot_g2x_2.udfu and even the ancient 
u-boot-gta02v5-1.3.1+gitr650149z53dbdd48bf6dfef90930c8ab182adb512-r1.bin
and just tried the qi-v36.udfu

======================================
root <at> mum-quad:/home/liz/downloads/qtmoko# dfu-util -a u-boot -R -D
qi-v36.udfu dfu-util 0.5

(C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.
(C) 2010-2011 Tormod Volden (DfuSe support)
This program is Free Software and has ABSOLUTELY NO WARRANTY

dfu-util does currently only support DFU version 1.0

Opening DFU USB device... ID 1d50:5119
Run-time device DFU version 0100
Found DFU: [1d50:5119] devnum=0, cfg=1, intf=0, alt=1, name="u-boot"
Claiming USB DFU Interface...
Setting Alternate Setting #1 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
(Continue reading)

Permalink | Reply | 8 comments |
headers
Gennady.Kupava | 1 Feb 16:09

Re: Installing v35

I see one more possibility here -

May be something with bad blocks in beginning of of NAND. You can try to
completely clear your NAND and recreate BBT and partitions.

Try this
http://wiki.openmoko.org/wiki/NAND_bad_blocks#Clearing_BadBlocks first.

Gena

В Срд, 01/02/2012 в 20:55 +1100, Liz пишет:
> On Wed, 01 Feb 2012 09:24:29 +0100
> Patryk Benderz <Patryk.Benderz <at> esp.pl> wrote:
> 
> >  However I have just reread through
> > your description of a problem and realised I had also some strange
> > problems (partial boot) which was resolved by flashing different qi
> > bootloader. Do both FR have the same bootloader?
> 
> Currently yes, qi-v35.udfu
> I have also tried the qi-31.udfu u-boot_g2x_2.udfu and even the ancient 
> u-boot-gta02v5-1.3.1+gitr650149z53dbdd48bf6dfef90930c8ab182adb512-r1.bin
> and just tried the qi-v36.udfu
> 
> 
> ======================================
> root <at> mum-quad:/home/liz/downloads/qtmoko# dfu-util -a u-boot -R -D
> qi-v36.udfu dfu-util 0.5
> 
> (C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.
(Continue reading)

Permalink | Reply | 7 comments |
headers
Gennady.Kupava | 1 Feb 16:13

Re: Installing v35

В Втр, 31/01/2012 в 10:58 +0100, Korbinian Rosenegger пишет:
> it may be possible that your AUX button got
> stuck somehow. A friend had the same problem with his brand new
> Freerunner. 

It should be easy to check stuck button, just press AUX in NOR u-boot
menu, it it doesn't react or meny items switching like crazy without
touching it - some problems with aux exist. It should be also possible
to just read some memory address from inside NOR u-boot i guess to find
out real state of AUX.

Gena

_______________________________________________
Openmoko community mailing list
community <at> lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Permalink | Reply | 0 comments |
headers
Liz | 1 Feb 12:28

Re: Installing v35

On Wed, 01 Feb 2012 19:09:50 +0400
"Gennady.Kupava" <gb <at> bsdmn.com> wrote:

> I see one more possibility here -
> 
> May be something with bad blocks in beginning of of NAND. You can try
> to completely clear your NAND and recreate BBT and partitions.
> 
> Try this
> http://wiki.openmoko.org/wiki/NAND_bad_blocks#Clearing_BadBlocks
> first.
> 
> Gena
> 
>
I saw that, and didn't know if it was appropriate to try it.
I've now dropped the microSD card and lost it so Ill that later.
Permalink | Reply | 3 comments |
headers
Gennady.Kupava | 1 Feb 16:35

Re: Installing v35

As your NAND is unusable at all, i guess it's appropriate to try
anything except hammer or trash bin.

> >
> I saw that, and didn't know if it was appropriate to try it.
> I've now dropped the microSD card and lost it so Ill that later.
> 
> _______________________________________________
> Openmoko community mailing list
> community <at> lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
Permalink | Reply | 2 comments |
headers
Dr. H. Nikolaus Schaller | 1 Feb 13:07
Favicon

Re: Installing v35


Am 01.02.2012 um 16:35 schrieb Gennady.Kupava:

> As your NAND is unusable at all, i guess it's appropriate to try
> anything except hammer or trash bin.

Before doing this, consider upgrading to a GTA04 board :)

Or getting a used GTA02 Motherboard:
http://www.handheld-linux.com/wiki.php?page=Neo%20Freerunner%3ASpare%20Parts
Permalink | Reply | 1 comment |

Gmane