public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] UBIFS fails on SheevaPlug
Date: Mon, 29 Oct 2012 10:11:05 +0100	[thread overview]
Message-ID: <508E4829.90004@gmail.com> (raw)
In-Reply-To: <CAF9kqNHeouPyxxjAMHnttN0mwjzLwzo173MMrMNxZ03Rm=RNyw@mail.gmail.com>

Dear Dimax,

please do not TOFU.

On 29.10.2012 09:50, Dimax wrote:
> Hi,
> What if I compile a new u-boot but to try it I will load and flash new
> created image after original u-boot and will run it from withing
> original reboot manually just pointing a new image address? Can it work?

well, you mean to run a u-boot out of a running u-boot?
U-Boot is not designed to do so. But some devices may allow you to just
run a newer u-boot from a running one (at91;). You need to know that
u-boot set up your SDRAM timings which destroys the content of the DRAM.
So if your new u-boot is located there it can not be executed.
I dunno if the kirkwood can do so, but I think they can not. You will need
a) a JTAG
b) another boot device, for example USB, MMC, whichever device the
kirwood SoC can read from its ROM code (I do not know)
to de-brick it.

Please ask some kirkwood specialist or google, there are a lot of
sheevaplug hackers out there, one of them may be able to help you here.

Best regards

Andreas Bie?mann

  reply	other threads:[~2012-10-29  9:11 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-28 14:48 [U-Boot] UBIFS fails on SheevaPlug Dimax
2012-10-28 22:54 ` Marek Vasut
2012-10-29  5:25   ` Dimax
2012-10-29  6:38     ` Dimax
2012-10-29  6:48       ` Andreas Bießmann
2012-10-29  6:55         ` Dimax
2012-10-29  8:38           ` Andreas Bießmann
2012-10-29  8:50             ` Dimax
2012-10-29  9:11               ` Andreas Bießmann [this message]
2012-10-29  9:27                 ` Dimax
2012-10-29  9:43                   ` Andreas Bießmann
2012-10-29 10:19                     ` Marek Vasut
2012-10-29 10:34                       ` Andreas Bießmann
2012-10-29 16:02                   ` Vikram Narayanan
2012-10-29 12:15                 ` Prafulla Wadaskar
2012-10-29 17:25                   ` Dimax
2012-10-29 18:53                     ` Vikram Narayanan
2012-10-29 19:05                       ` Dimax
2012-10-29 23:55                         ` Andreas Bießmann
2012-10-29 23:02                       ` Andreas Bießmann
2012-10-31 16:27                         ` Vikram Narayanan
2012-10-31 16:50                           ` Andreas Bießmann
2012-10-31 16:55                             ` Vikram Narayanan
2012-10-31 17:23                               ` Dimax
2012-10-31 17:56                                 ` Andreas Bießmann
2012-10-31 20:45                                   ` [U-Boot] How to enable debug information in u-boot Paulo Louro
2012-11-06  7:51                                   ` [U-Boot] UBIFS fails on SheevaPlug Dimax
2012-11-06  9:12                                     ` Andreas Bießmann
2012-11-12  5:33                                       ` Dimax
2012-11-12  8:33                                         ` Andreas Bießmann
2012-11-12 16:55                                           ` Dimax
2012-11-12 17:15                                             ` Vikram Narayanan
2012-10-29  6:01 ` Prafulla Wadaskar

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=508E4829.90004@gmail.com \
    --to=andreas.devel@googlemail.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