RE: [ECOS] RedBoot gets() problems

[Gary Thomas <gthomas at cambridge dot redhat dot com>]

On 02-Mar-2001 Grant Edwards wrote:
> 
> I'm having problems with RedBoot due to the way the main loop
> and gets() interact.  
> 
> If at some point a spurious byte comes in on one of the diag
> ports, RedBoot effectively "locks up" until it sees an
> end-of-line on that port: it ignores network packets, it
> ignores commands on the other diag port.
> 

What defines "spurious"?

> I think I'm going to have to re-design the input scheme so that
> Redboot still responds to the network and to all ports while
> in the "middle" of reading an input line.

I'm not convinced that this is the right thing to do.  Maybe
the check for network packets is OK (but I ruled out doing it all
the time because of overhead costs), but once data arrives on
one port, then RedBoot is designed to switch to that port
exclusively.

You can disable this using the CDL which may be what you want.