All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hawkins <dwh@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Increasing U-Boot partition size
Date: Mon, 04 Aug 2008 13:44:07 -0700	[thread overview]
Message-ID: <48976A17.9060005@ovro.caltech.edu> (raw)
In-Reply-To: <4897680C.1000309@ge.com>

> Arrr, my insanity.  Wolfgang is correct, of course.
> 

Gee, and I was just going to ask why on earth you liked
high-boot :)

I've seen one novel use of high-boot that could make it
useful if you're lazy and can't be bothered plugging in
your debugger ;)

Assuming your board has a toggle switch that sets the
state of BMS in the RCW (as most Freescale boards do),
you can put a 'good' version of U-Boot at say the
high-boot location, and the test version at the low-boot.
If the low-boot version doesn't boot, power-down, flip the
BMS toggle switch, power-up and boot-high, reflash to
the next low-boot test version, and continue.

I personally haven't tried the trick, but it sounded
like a nice idea.

Low-boot is the only sane method for booting, since
high-boot sticks the bootloader 8MB into your 32MB/64MB/etc
Flash ... I mean who uses 8MB Flash these days ... :)

Cheers,
Dave

  reply	other threads:[~2008-08-04 20:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 17:16 [U-Boot-Users] Increasing U-Boot partition size Jatin Sharma
2008-08-04 17:56 ` Scott Wood
2008-08-04 19:03   ` Jatin Sharma
2008-08-04 19:04     ` Scott Wood
2008-08-04 19:59       ` Jatin Sharma
2008-08-04 20:01         ` Scott Wood
2008-08-04 20:03           ` Scott Wood
2008-08-04 20:26           ` Jerry Van Baren
2008-08-04 20:33             ` Wolfgang Denk
2008-08-04 20:35               ` Jerry Van Baren
2008-08-04 20:44                 ` David Hawkins [this message]
2008-08-04 20:50                   ` Jerry Van Baren

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=48976A17.9060005@ovro.caltech.edu \
    --to=dwh@ovro.caltech.edu \
    --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.