Grief with Cygwin-hosted GDB

[Nick.SIMON at syntegra.bt.co.uk]

I don't use wiggler either, but the 860 needs various registers setting up
so that chip selects are driven - an important requirement for memory
access!  The BRx and ORx need to be set for each chip select used, and for
your DRAM you'll probably need to set up a UPM, MxMR and MPTPR.  The good
news is that you can crib the values from the BSP.

As I don't use gdb I can't advise you about the init script.

Best wishes,


-- Nick Simon 

> -----Original Message-----
> From: Chris Johns [mailto:cjohns at cybertec.com.au]
> Sent: 10 October 2000 00:45
> To: Phil Torre
> Cc: rtems-users at oarcorp.com
> Subject: Re: Grief with Cygwin-hosted GDB
> 
> 
> Phil Torre wrote:
> > 
> > At this point, if I examine memory on the target, every DRAM
> > address seems to contain the same value as the address.  No
> > surprise, then, that GDB hangs if I do step or nexti.  Pressing
> > ctrl-c to unhang GDB makes it blow core.
> > 
> > Is anyone making GDB/Cygwin work with the Wiggler?  Any hints
> > would be welcome!
> > 
> 
> I do not use PowerPC's or the Wiggler pods, but with the Coldfire and
> 68360 you typically need to run a GDB init script (.gdbinit) to
> initialise the DRAM controller to enable access to the DRAM and insure
> refreshing happens.
> 
> -- 
>  Chris Johns, mailto:cjohns at cybertec.com.au mailto:ccj at acm.org
>