Re: [ECOS] MPC860 (Debugging ISR)

Re: [ECOS] MPC860 (Debugging ISR)

[nprasad3]

Gary,

I am trying to build a tester (intr0.c) on the same lines as powerpc/arch/v2_0/test but interrupt chain does not get called. Halting with wiggler, control shows up in the default ISR but control never makes it to C land.

Ran into a seperate thread "Re: how does GDB set breakpoint to MPC860" which is helpful and I'll certainly give gdb a try. There probably is nothing wrong with the default ISR and the source of the problem most likely would be my platform initialization thats preventing the generic ISR to work the way it is supposed to.

Thanks in advance
Nirmal

----- Original Message -----
From: Gary Thomas <gary@mlbassoc.com>
Date: Tuesday, December 16, 2003 10:47 am
Subject: Re: [ECOS] MPC860 (Debugging ISR)

> On Tue, 2003-12-16 at 08:43, nprasad3@gmu.edu wrote:
> > Hi,
> > 
> > Can someone please tell me how I can debug the general 
> > interrupt service handler on the MPC860? I am using a 
> > wiggler and romstop doesn't work. I was thinking of putting 
> > in a tight loop at the begining of the ISR to allow the 
> > processor to stay put at that particular point till I release 
> > it from the debugger.
> > 
> > Is there a different way I can single step into the ISR and 
> > keep things under control while debugging the ISR?
> 
> What's wrong with running your code in RAM and using GDB?
> 
> BTW, what do you think is wrong with the "general interrupt
> service handler"?
> 
> -- 
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
> 
> 
> 


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

Re: [ECOS] MPC860 (Debugging ISR)

[Gary Thomas]

On Tue, 2003-12-16 at 08:43, nprasad3@gmu.edu wrote:
> Hi,
> 
> Can someone please tell me how I can debug the general 
> interrupt service handler on the MPC860? I am using a 
> wiggler and romstop doesn't work. I was thinking of putting 
> in a tight loop at the begining of the ISR to allow the 
> processor to stay put at that particular point till I release 
> it from the debugger.
> 
> Is there a different way I can single step into the ISR and 
> keep things under control while debugging the ISR?

What's wrong with running your code in RAM and using GDB?

BTW, what do you think is wrong with the "general interrupt
service handler"?

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


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

[ECOS] MPC860 (Debugging ISR)

[nprasad3]

Hi,

Can someone please tell me how I can debug the general interrupt service handler on the MPC860? I am using a wiggler and romstop doesn't work. I was thinking of putting in a tight loop at the begining of the ISR to allow the processor to stay put at that particular point till I release it from the debugger.

Is there a different way I can single step into the ISR and keep things under control while debugging the ISR?

Thanks in advance
Nirmal



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