From: DrEagle <dreagle@doukki.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] kwboot: boot Marvell Kirkwood SoCs over a serial link
Date: Tue, 08 May 2012 11:02:43 +0200 [thread overview]
Message-ID: <4FA8E133.3070904@doukki.net> (raw)
In-Reply-To: <1336434052.16515.85.camel@espiritosanto>
Hi,
Le 08/05/2012 01:40, Daniel Stodden a ?crit :
> On Sun, 2012-05-06 at 12:53 -0500, David Purdy wrote:
>> On Wed, May 2, 2012 at 2:16 PM, Luka Perkov <uboot@lukaperkov.net> wrote:
>>> The kwboot program boots boards based on Marvell's Kirkwood platform
>>> via Xmodem over their integrated UART.
>>>
>>> Signed-off-by: Daniel Stodden <daniel.stodden@googlemail.com>
>>> Acked-by: Luka Perkov <uboot@lukaperkov.net>
>>> ---
>>>
>>> Changes from version v1:
>>> * fix man page
>>> * minor cosmetic fixes in tools/kwboot.c
>>>
>>> I changed things pointed out on v1 of this patch which was originally
>>> made by Daniel.
>>>
>>
>> @ Daniel, Luka, Prafulla, etal :
>>
>> I've tried kwboot on two of my devices, and as I was expecting:
>>
>> - it worked perfectly with the v1.21 BootROM device (a Seagate GoFlex
>> Net) : Nicely done, well implemented, and the "timing" seems to be a
>> non-issue w/ kwboot. Other previous applications for UARTbooting have
>> seemed to me to be less reliable - only booting 50% or 75% of the
>> time. I tried it with kwboot a dozen times or more and it was
>> successful each time, The -p patch-for-UART-booting option is a nice
>> feature.
>>
>>
>> - it did not seem to work w/ v1.11 BootROM devices (a Pogoplug
>> V2/E02, Seagate Dockstar) {previous utilities/picocom-hacks showed the
>> same behavior - the bootROM version 1.11 apparently has some
>> difference/defect/shortcoming that does not allow this function to
>> work as the docs suggest it should. Too bad no one has pointed out
>> exactly what the issue is, or found a patch/workaround it make this
>> work on v1.11 BootROM devices.}. NOTE: It did _not_ adversely
>> affect the device otherwise. I'd seen a post on a thread at another
>> site that suggested that performing this procedure on a v1.11 device
>> could corrupt the NAND - this was __not__ the case w/ my attempts
>> (about a dozen trials, with UART uboot.kwb's and also using the -p
>> patch option w/ NAND files.
>
> Hey.
>
> Unfortunately I only have a couple Buffalo boards and a Qnap, all
> essentially the same chip.
>
> Say, if you find the time, could you run it through strace and post the
> full output? (strace -o /tmp/kwboot.log -s 256 -T ..).
>
> Just see where it bails. Maybe it's some issue worth trying to hack
> around.
Have you tried to put the bootrom in the debug mode ?
https://doukki.net/doku.php?id=wiki:tutoriels:u-boot.uart#boot_from_uart0
R?fs :
http://www.marvell.com/embedded-processors/kirkwood/assets/FS_88F6180_9x_6281_OpenSource.pdf
May be it can helps to understand the 1.11 and 1.21 differences ?
Amicalement,
---
Gk2
:-]
next prev parent reply other threads:[~2012-05-08 9:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 19:16 [U-Boot] [PATCH v2] kwboot: boot Marvell Kirkwood SoCs over a serial link Luka Perkov
2012-05-06 17:53 ` David Purdy
2012-05-06 23:33 ` Prafulla Wadaskar
2012-05-07 23:40 ` Daniel Stodden
2012-05-08 9:02 ` DrEagle [this message]
2012-05-09 8:00 ` Daniel Stodden
2012-05-09 13:25 ` David Purdy
2012-05-09 17:21 ` Daniel Stodden
2012-05-09 20:32 ` DrEagle
[not found] ` <CAPOFwxqDQKZ-3xu829uUtdFpA_308tGLY5qCpsyi2BSdyn00Xg@mail.gmail.com>
[not found] ` <1336444704.16515.115.camel@espiritosanto>
2012-05-08 21:23 ` David Purdy
2012-05-08 21:40 ` David Purdy
2012-05-09 7:49 ` Daniel Stodden
2012-05-07 8:19 ` Holger Brunck
2012-05-16 12:22 ` Simon Guinot
2012-05-21 21:33 ` [U-Boot] [PATCH v3] " Daniel Stodden
2012-05-21 21:33 ` Daniel Stodden
2012-05-21 21:59 ` Wolfgang Denk
2012-05-24 6:53 ` Prafulla Wadaskar
2012-05-21 21:58 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FA8E133.3070904@doukki.net \
--to=dreagle@doukki.net \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.