[ECOS] Cannot communicate with RedBoot on Viper board

Erik Reikes ereikes@hotmail.com
Wed Mar 6 14:20:00 GMT 2002


I am using the same board with the same settings and mine is working.  Make 
sure you are using a null modem between your host and target and not just a 
F-F DB9 cable.

Also, ensure that flow control is turned off in your hyperterm as the SMC 
ports do not support flow contol.  Additionally press only one of the reset 
buttons.  I believe it is the one labelled <something>2.  It will take a 
while to get started after you see the "+" because it is initially set up 
for bootp ethernet which has to timeout.  You can fix this by setting it to 
fixed ip address using fconfig at the redboot prompt (if/when you get 
there).

When you get there fire up powerpc-gdb with an application and type target 
remote com1 (or whatever)
load
continue

and you should be running.  I started out with the Hello Ecos World 
Application in the examples directory.

If you ever figure out what it takes to make the ethernet debugging work let 
me know.  I tried a couple of redboot images and they all crap out during 
download after gdb connects.

Good luck!

-Erik Reikes


>On Tue, 2002-03-05 at 09:43, Paul Randall wrote:
> > Hi All,
> >
> > I just purchased a A&M Viper board and I am having trouble communicating
> > with RedBoot.
> >
> > I am connected to Serial Port 2 (SMC1) on the Viper and I'm using
> > Windows 98 HyperTerminal to communicate with the board.  I'm running
> > with the data rate set to 38400 bits per second, 8 data bits, no parity,
> > and one stop bit as instructed by the RedBoot documentation.  I have
> > flow control turned off.  A&M tech support told me I should see a '+'
> > when RedBoot starts up, but I don't get any response at all.  A&M has
> > assured me that RedBoot was installed on my board.
> >
> > When I plug in the Viper, green LEDs D3 and D4 both light up as does LED
> > D7.  A&M support suggested I press the reset switches and look for the
> > '+' but all that happens is LED D8 turns on for a fraction of a second
> > before LED D7 turns back on.
> >
> > Has anyone seen similar problems with the Viper?  Any suggestions?
>
>Are you sure you are using the correct port (serial port 2)?  The settings
>are indeed 38400/8N1, no handshake.  Perhaps you have a problem with Tx/Rx
>wiring?
>
>When the LED changes from D8 to D7, the basic initialization is complete 
>and
>RedBoot starts to use the on-board DRAM.  It should [almost] immediately
>print '+' on the serial port.
>
>
>--
>Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
>and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss



More information about the Ecos-discuss mailing list