This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: gdb , warm reset and debugging
- From: "Paul D. DeRocco" <pderocco at ix dot netcom dot com>
- To: <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 5 Dec 2006 00:27:14 -0800
- Subject: RE: [ECOS] gdb , warm reset and debugging
> From: Sinan KAYA
>
> I wonder how other people have been performing their debugging process.
>
> With my current set up here:
> 1. arm946es
> 2. jtag
> 3. insight debugger
> 4. little endian
>
> i receive spurious interrupts when i stop a running a program
> load the software again and run again. However, it does not
> happen again if i do a reload again.
>
> So i receive one spurious interrupt problem per reloading of
> software. Once failed, i do a reload again and it works.
>
> Here is the message:
> ASSERT FAIL: <FFFF>hal_misc.c[213]hal_arch_default_isr() Spurious
> Interrupt!!!
> ASSERT FAIL: <FFFF>hal_misc.c [ 213] hal_arch_default_isr()
> Spurious Interrupt!!!
> ,
> I debugged the code and have seen that the source of spurious
> interrupt is the clock.
>
> To further trace the problem, i put a breakpoint to reset_vector
> function but it does not stop at this place when spurious
> interrupt happens.
>
> Is this a bug of insight or am i missing something ?
It sounds like interrupts are enabled when you restart, which they shouldn't
be. The spurious interrupt masks further interrupts, so when you restart a
second time, it works okay.
--
Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix.netcom.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss