From: Ira W. Snyder <iws@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot] break command.
Date: Fri, 15 Feb 2013 11:28:38 -0800 [thread overview]
Message-ID: <20130215192838.GA24862@ovro.caltech.edu> (raw)
In-Reply-To: <2586B402-FB69-465C-82A4-62A065C74234@3gfp.com>
On Fri, Feb 15, 2013 at 02:00:10PM -0500, Harvey Chapman wrote:
> On Feb 15, 2013, at 7:38 AM, Albert ARIBAUD <albert.u.boot@aribaud.net> wrote:
> > On Thu, 14 Feb 2013 12:19:11 -0800
> > (PST), Sean Omalley <omalley_s@rocketmail.com> wrote:
> >
> >> Is there anyway to break back into u-boot after trying to boot from linux (arm)? Similar to Open Firmwares stop-a, ctrl-break? I didn't see anything in the documentation nor poking around online. I am really hoping I missed something, or there is support that just needs to be compiled in. :)
> >>
> > As soon as U-Boot gives control to the payload (Linux or whatever)
> > there is no possible assumption that U-Boot remains intact in RAM, so
> > your only chance is indeed some hardware reset... But then the question
> > is not related to U-Boot any more.
>
> On that note, does anyone know of a device that would do this? Perhaps a combination device like this:
>
> - USB interface to a pc
> - serial port for device
> - relay controllable A/C power plug (U.S.)
> - controllable gpio (for wiring to a power button, reset switch, etc)
>
I have a BayTech network-attached powerstrip that does something
similar. It has switchable AC outlets and network-accessible serial
ports, but it doesn't have controllable GPIOs or a USB interface.
Ira
next prev parent reply other threads:[~2013-02-15 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 20:19 [U-Boot] break command Sean Omalley
2013-02-15 12:38 ` Albert ARIBAUD
2013-02-15 19:00 ` Harvey Chapman
2013-02-15 19:03 ` Peter Barada
2013-02-15 19:28 ` Ira W. Snyder [this message]
2013-02-17 20:49 ` Wolfgang Denk
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=20130215192838.GA24862@ovro.caltech.edu \
--to=iws@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox