Re: crossgcc: code wont run from ROM.

[Peter Popov <ppopov at redcreek dot com>]

Brendan J Simon wrote:
> 
> Peter Popov wrote:
> 
> > > I just had a thought.  Maybe I need to copy the initialised data section from
> > > ROM to RAM ?
> > > I know that the DiabData startup files do this and I'm pretty sure I haven't done
> > > this in my gcc startup files.
> > > Does this sound plausable ?
> >
> > Sure, if you are not doing that, you'll have all sorts of problems.
> >
> > Also, you mentioned that SDS does not support gcc's -g feature, so you
> > are debugging assembly code.  I'm using gcc-2.95.2, binutils-2.91, and
> > newlib-1.8.2 with the SDS 7.5 debugger, and it works fine (MPC8xx
> > processor).  The debugger understands the elf output file and I can
> > debug c source code (haven't tried c++).
> 
> I'm using SDS-7.3.  Do you use -g or -gdwarf for your debug switch ?
> My debugger understands the elf.  I do get the symbols in the source window but no
> function or filenames in the pop windows.

I use the -g switch, and the debugger seems to be happy.  It generates
its
own files from the elf output file, and then I can single step through
my c code.  I'm having other bdm related problems with the debugger
and/or
the wiggler, but that's a separate issue.  I've given up on SDS, at
least
for now. 

Pete

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com