[U-Boot] Problem with stand-alone apps

ANDY KENNEDY ANDY.KENNEDY at adtran.com
Thu Aug 29 22:25:38 CEST 2013


> From: Tom Rini [mailto:tom.rini at gmail.com] On Behalf Of Tom Rini
> 
> On Wed, Aug 28, 2013 at 03:07:47PM +0000, ANDY KENNEDY wrote:
> 
> > All,
> >
> > In an effort to play by the rules, we created a stand alone app that
> > handles breaking the boot process with bootdelay set to 0.  We require
> > a special key sequence to break into the boot process to ensure security,
> > and to ensure we do not interrupt the boot process with stray key strokes.
> > We are seeing strange behavior from our applet.  There are several API
> > calls that we make from within the app that seem to make our processor
> > go into a code violation error (even something as simple as a printf).
> 
> Unrelated, do CONFIG_AUTOBOOT_STOP_STR and similar not provide what you
> need here?  See doc/README.autoboot

Yeah, that would _almost_ work, but not.  I need to do something like:

If no boot, switch mux else boot.  I don't think that will work with
CONFIG_AUTOBOOT_STOP_STR.  It is close, but not exactly what we need.

Our configuration is multiple processor, one serial console.  Thus, there is
one processor that is fixed as a receiver, the rest only see/send traffic
when the multiplexor is set to that processor.  So, If the user is attempting
to break into one of the OTHER devices, and presses a stray
CONFIG_AUTOBOOT_STOP_STR then the system would stop unexpectedly.

Unfortunately, front panel space is a premium on our system :\.

Thanks for the info, though!

Andy


More information about the U-Boot mailing list