This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
Re: '+' on reset
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: Jonathan Larmour <jifl at eCosCentric dot com>
- Cc: eCos developers <ecos-devel at sources dot redhat dot com>
- Date: 31 Mar 2003 09:06:44 +0000
- Subject: Re: '+' on reset
- References: <3E87DCCA.8090709@eCosCentric.com>
Jonathan Larmour <jifl at eCosCentric dot com> writes:
> When using serial, the viper always corrupts the first char when the
> serial is reset. Unfortunately this mostly means the '+' from the stub
> in RedBoot. This is sort of benign and sort of not because if you've
> got a GDB there waiting (say after using maintenance packet r) it will
> prod RedBoot again for an ack, which it will get, but then RedBoot is
> stuck listening to the serial in GDB mode.
>
> I think it may be sensible to output *two* plusses in generic-stub.c
> since this isn't the first time this has happened - it certainly isn't
> surprising for asynchronous ports.
>
> Anyone think this is a bad idea? FAOD I'm not proposing this for 2.0
> since it isn't _that_ important.
>
I seem to recall that some platforms used to output two plusses anyway
at one time because initialize_stub() got called twice -- it may have
been stub ROMs that did this rather than RedBoot. It never did any
harm then, so it should be OK now.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts