From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot boot process is broken, how do i recover?
Date: Thu, 4 Apr 2013 10:18:15 +0200 [thread overview]
Message-ID: <20130404101815.705d805c@skate> (raw)
In-Reply-To: <kjgoaa$s5t$1@ger.gmane.org>
Dear JPT,
On Wed, 03 Apr 2013 10:13:02 +0200, JPT wrote:
> | \/ | __ _ _ ____ _____| | |
> | |\/| |/ _` | '__\ \ / / _ \ | |
> | | | | (_| | | \ V / __/ | |
> |_| |_|\__,_|_| \_/ \___|_|_|
> _ _ ____ _
> | | | | | __ ) ___ ___ | |_
> | | | |___| _ \ / _ \ / _ \| __|
> | |_| |___| |_) | (_) | (_) | |_
> \___/ |____/ \___/ \___/ \__|
> ** MARVELL BOARD: DB-88F6282A-BP LE
>
> U-Boot 1.1.4 (Feb 6 2012 - 14:40:46) Marvell version: 3.4.27
> Netgear version: Uboot-1_1_4-NetgearDUOV3-V1008
On Marvell hardware, you can send a different U-Boot using the serial
port, even if the on-flash U-Boot is broken. Have a look at
tools/kwboot.c in the mainline U-Boot sources. It uses the serial port
to send using the Xmodem protocol, a new U-Boot payload to the Kirkwood
SoC.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-04-04 8:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 8:13 [U-Boot] u-boot boot process is broken, how do i recover? JPT
2013-04-03 9:00 ` Albert ARIBAUD
2013-04-03 11:30 ` JPT
2013-04-03 11:55 ` Albert ARIBAUD
2013-04-04 8:18 ` Thomas Petazzoni [this message]
2013-04-04 9:17 ` Albert ARIBAUD
2013-04-04 10:21 ` JPT
2013-04-04 12:47 ` Albert ARIBAUD
2013-04-07 8:08 ` Thomas Petazzoni
2013-04-07 17:40 ` Albert ARIBAUD
-- strict thread matches above, loose matches on Subject: below --
2013-10-18 16:12 Philippe Noisette
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=20130404101815.705d805c@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox