From mboxrd@z Thu Jan  1 00:00:00 1970
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
Date: Sun, 7 Apr 2013 19:40:03 +0200
Subject: [U-Boot] u-boot boot process is broken, how do i recover?
In-Reply-To: <20130407100822.4f45750f@skate>
References: <kjgoaa$s5t$1@ger.gmane.org> <20130404101815.705d805c@skate>
	<20130404111734.14bf0fd0@lilith> <kjjk7j$502$1@ger.gmane.org>
	<20130404144718.1b758045@lilith> <20130407100822.4f45750f@skate>
Message-ID: <20130407194003.5577f81b@lilith>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Thomas,

On Sun, 7 Apr 2013 10:08:22 +0200, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:

> Dear Albert ARIBAUD,
> 
> On Thu, 4 Apr 2013 14:47:18 +0200, Albert ARIBAUD wrote:
> 
> > Since you seem to have a binary meant for UART booting, yes, you might
> > try sending it to the board; with any luck that'll allow you to inspect
> > and possibly revert your U-Boot environment into what it was before the
> > bricking. As to how... any serial app with Xmodem should work, I
> > presume. If the transfer starts, chances are the image will run
> > automatically.
> 
> No, any app doing Xmodem will not work. In order to turn the Marvell
> Kirkwood romcode into UART boot mode, you have to send a series of
> magic bytes to the UART. This is what kwboot does before sending the
> binary using the Xmodem protocol.

Thanks for the correction -- however, it was done already in a private
e-mail exchange with JPT, where indeed the requirement became "any app
which can send files in raw as well as xmodem modes".

> Best regards,
> 
> Thomas

Amicalement,
-- 
Albert.