From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Stodden Date: Wed, 09 May 2012 01:00:30 -0700 Subject: [U-Boot] [PATCH v2] kwboot: boot Marvell Kirkwood SoCs over a serial link In-Reply-To: <4FA8E133.3070904@doukki.net> References: <20120502191643.GB14946@w500.lan> <1336434052.16515.85.camel@espiritosanto> <4FA8E133.3070904@doukki.net> Message-ID: <1336550430.3494.11.camel@ramone> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tue, 2012-05-08 at 11:02 +0200, DrEagle wrote: > 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 wrote: > >>> The kwboot program boots boards based on Marvell's Kirkwood platform > >>> via Xmodem over their integrated UART. > >>> > >>> Signed-off-by: Daniel Stodden > >>> Acked-by: Luka Perkov > >>> --- > >>> > >>> 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 ? I never played with it. But according to the documentation, it's rather orthogonal to image upload. You get a command line interface. However, I see no command references in the docs. Might support entering it in kwboot in the future, but I don't see how it's would help with the protocol issues. Daniel