RE: [coldfire-gnu-discuss] Debugging from flash

["Corrin Meyer" <Corrin.Meyer@xxxxxxxxxxxxxxx>]

It actually is not a M52235EVB but the ColdFire is configured like a
M52235EVB.  I have been able to successfully run and debug applications
from RAM.  It is just once I go to Flash that I am getting this problem.

Corrin Meyer

> -----Original Message-----
> From: Daniel Jacobowitz [mailto:dan@xxxxxxxxxxxxxxxx]
> Sent: Monday, September 08, 2008 9:42 AM
> To: Corrin Meyer
> Cc: coldfire-gnu-discuss@xxxxxxxxxxxxxxxx
> Subject: Re: [coldfire-gnu-discuss] Debugging from flash
> 
> On Mon, Sep 08, 2008 at 09:21:09AM -0400, Corrin Meyer wrote:
> > (gdb) target remote | m68k-elf-sprite pe: m52235evb
> 
> Just checking, is your board actually an M52235EVB or is it something
> similar but slightly different?
> 
> > Program received signal SIGTRAP, Trace/breakpoint trap.
> > 0x00000e12 in __cs3_isr_illegal_instruction ()
> > (gdb)
> 
> At this point, I'd suggest you check the exception frame on the stack
> to see what instruction was illegal.
> 
> > I would expect that after issuing the continue command that the
program
> > should execute just as if the board had been booted.  Am I missing
> > something?
> 
> Almost the same.  The only difference is that the initialization
> sequence in the board file is executed first; this is to support
> programs run from RAM, which may require the memory controller
> to be initialized first.  But in general the initialization sequence
> does not cause a problem if executed twice.
> 
> --
> Daniel Jacobowitz
> CodeSourcery