On Nov 23, 2008 8:12pm, Andy Green <[EMAIL PROTECTED]> wrote:
Recent kernels have a workaround in that starts the card at slower clock
until the first bulk transfer completed successfully when it is cranked
up to 16MHz, that seemed to make the previous problems with some cards
pretty much go away
>>Yes, I know that, but I'm unable to connect to the phone through
>> DFU protocol because Neo don't offer itself as a device supporting
>> DFU.
>
> Have you tried to connect usb cable AFTER freerunner started NOR u-boot?
...
> My early problems with DFU disappeared after I took this approach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2008/11/24 Andy Green <[EMAIL PROTECTED]>:
|> My early problems with DFU disappeared after I took this approach in a
|> script, it seems it can announce under two different PIDs (this one is
|> for updating
2008/11/24 Paul Fertser <[EMAIL PROTECTED]>:
> It might be a silly suggestion but please double-check the usb cable
> used, try to connect directly to the motherboard (avoid front-panel
> connectors and usb hubs). May be you should try another PC.
>
> By no means (as you have no dboard) you could h
2008/11/24 Andy Green <[EMAIL PROTECTED]>:
> My early problems with DFU disappeared after I took this approach in a
> script, it seems it can announce under two different PIDs (this one is
> for updating U-Boot):
>
> #!/bin/bash
> dfu-util -a 1 -d 0x1d50:0x5119 -D u-boot.udfu
> if [ $? -eq 1 ] ; th
Hi,
"Evgeny Karyakin" <[EMAIL PROTECTED]> writes:
> 2008/11/24 Andy Green <[EMAIL PROTECTED]>:
>> I'm not sure what's happening to you, but your dmesg traffic would be
>> pretty normal if you were entering and then leaving U-Boot... the
>> connection would indeed timeout (-110) when we leave U-Boo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2008/11/24 Nikita V. Youshchenko <[EMAIL PROTECTED]>:
|>>Yes, I know that, but I'm unable to connect to the phone through
|>> DFU protocol because Neo don't offer itself as a device supporting
|>> DFU.
|
2008/11/24 Nikita V. Youshchenko <[EMAIL PROTECTED]>:
>>Yes, I know that, but I'm unable to connect to the phone through
>> DFU protocol because Neo don't offer itself as a device supporting
>> DFU.
>
> Have you tried to connect usb cable AFTER freerunner started NOR u-boot?
I haven't; will
> > If you hold down the AUX / corner key when you power up, you should
> > come up in NOR U-Boot with a menu on the LCM. If that's true, you
> > should have 30s to do the DFU you want to do before it times out.
>
>Yes, I know that, but I'm unable to connect to the phone through
> DFU protocol
2008/11/24 Andy Green <[EMAIL PROTECTED]>:
> |DFU is absent, dfu-util -l finds no suitable device to work with,
> | maybe because I damaged it when I changed environment in minicom
> | console or I uploaded wrong image onto that. AUX+POW on the phone,
> | menu appears, dfu-util -l on desktop, a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 2008/11/24 Andy Green <[EMAIL PROTECTED]>:
|> | dfu-util -a u-boot -R -D uImage-XX.bin
|>
|> Hum the -a "u-boot" or -a 1 tells it to put stuff in the U-Boot
|> partition, it's the wrong one: uImage-blah.
2008/11/24 Andy Green <[EMAIL PROTECTED]>:
> | dfu-util -a u-boot -R -D uImage-XX.bin
>
> Hum the -a "u-boot" or -a 1 tells it to put stuff in the U-Boot
> partition, it's the wrong one: uImage-blah.bin is a kernel image.
> To flash the kernel, you need to tell it -a "kernel" or -a 3.
Ah ye
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| From: "arne anka" <[EMAIL PROTECTED]>
|
|>> like writing past memory available, I guess it's because broken
|>> environment.
|> hardly. i'd rather think you try to flash the wrong partition.
|> what exactly
From: "arne anka" <[EMAIL PROTECTED]>
>>like writing past memory available, I guess it's because broken
>>environment.
> hardly. i'd rather think you try to flash the wrong partition.
> what exactly did you do and what exactly did dfu-util or the fr report?
I already flashed Freerunner several
2008/11/23 Andy Green <[EMAIL PROTECTED]>:
> Recent kernels have a workaround in that starts the card at slower clock
> until the first bulk transfer completed successfully when it is cranked
> up to 16MHz, that seemed to make the previous problems with some cards
> pretty much go away.
Presumably
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> seems you experience the well known sd card issue.
|> wiki and/or archives should offer a lot of postings on the issue.
|> it boils down to setting sd_max_clk -- in your case in the nand boot
environment si
> like writing past memory available, I guess it's because broken
> environment.
hardly. i'd rather think you try to flash the wrong partition.
what exactly did you do and what exactly did dfu-util or the fr report?
___
Openmoko community mailing list
c
> seems you experience the well known sd card issue.
> wiki and/or archives should offer a lot of postings on the issue.
> it boils down to setting sd_max_clk -- in your case in the nand boot
> environment since your fr seems
> unable to boot from sd at all.
> searching for "sd_max_clk +openmoko"
jewgeni,
seems you experience the well known sd card issue.
wiki and/or archives should offer a lot of postings on the issue.
it boils down to setting sd_max_clk -- in your case in the nand boot
environment since your fr seems unable to boot from sd at all.
searching for "sd_max_clk +openmoko" s
19 matches
Mail list logo
