DSPRelated.com
Forums

RE: DSP56F827 - Un-handled Interrupt: finding sour ce??

Started by Corey, Rick December 30, 2003
Hi Boaz

I see on p.4-13 of the 56800 Family Manual (ITCN), a test register TCSR,
with bits 8..13 called "vector". That's just enough bits to encode the 64
interrupt vectors.

Text says that these bits "show the output of the current active vector".
Maybe it will reveal what tripped your unhandled IRQ. If it does, would you
let us know? If anyone with more of a clue has a clue, by all means correct
me.

It looks like TCSR is at ITCNBase+$1C, or 0x0E7C on the 56803. Your address
may vary, on the 56827.

Rick Corey

-----Original Message-----
From: bmbmz123 [mailto:]
Sent: Thursday, December 25, 2003 3:52 AM
To:
Subject: [motoroladsp] DSP56F827 - Un-handled Interrupt: finding
source?? Hello all,

It seems I'm getting Unhandled Interrupt from some source.

I get to archUnhandledInterrupt() in arch.c file.

How can I find the source of this interrupt when I reach this routine?

I am not THAT familiar with the ITCN registers and operation.

I am using CW ver 4.1 and SDK version 2.4.1. chip=DSP56F827.

thanks
boaz
_____________________________________
Note: If you do a simple "reply" with your email client, only the author of
this message will receive your answer. You need to do a "reply all" if you
want your answer to be distributed to the entire group.

_____________________________________
About this discussion group:

To Join:

To Post:

To Leave:

Archives: http://www.yahoogroups.com/group/motoroladsp

More Groups: http://www.dsprelated.com/groups.php3




Hi again

Well, trapping inside an ISR doesn't tell me much about TCSR. If I'm
looking at the right location, I just see "0000", no vector.

FWIW, the debugger lit that word (0x0E7C) up in red, as if it had just
changed value.

Corey

-----Original Message-----
From: Corey, Rick [mailto:]
Sent: Tuesday, December 30, 2003 11:45 AM
To: 'bmbmz123';
Subject: RE: [motoroladsp] DSP56F827 - Un-handled Interrupt: finding
sour ce?? Hi Boaz

I see on p.4-13 of the 56800 Family Manual (ITCN), a test register TCSR,
with bits 8..13 called "vector". That's just enough bits to encode the 64
interrupt vectors.

Text says that these bits "show the output of the current active vector".
Maybe it will reveal what tripped your unhandled IRQ. If it does, would you
let us know? If anyone with more of a clue has a clue, by all means correct
me.

It looks like TCSR is at ITCNBase+$1C, or 0x0E7C on the 56803. Your address
may vary, on the 56827.

Rick Corey

-----Original Message-----
From: bmbmz123 [mailto:]
Sent: Thursday, December 25, 2003 3:52 AM
To:
Subject: [motoroladsp] DSP56F827 - Un-handled Interrupt: finding
source?? Hello all,

It seems I'm getting Unhandled Interrupt from some source.

I get to archUnhandledInterrupt() in arch.c file.

How can I find the source of this interrupt when I reach this routine?

I am not THAT familiar with the ITCN registers and operation.

I am using CW ver 4.1 and SDK version 2.4.1. chip=DSP56F827.

thanks
boaz
_____________________________________
Note: If you do a simple "reply" with your email client, only the author of
this message will receive your answer. You need to do a "reply all" if you
want your answer to be distributed to the entire group.

_____________________________________
About this discussion group:

To Join:

To Post:

To Leave:

Archives: http://www.yahoogroups.com/group/motoroladsp

More Groups: http://www.dsprelated.com/groups.php3

_____________________________________
Note: If you do a simple "reply" with your email client, only the author of
this message will receive your answer. You need to do a "reply all" if you
want your answer to be distributed to the entire group.

_____________________________________
About this discussion group:

To Join:

To Post:

To Leave:

Archives: http://www.yahoogroups.com/group/motoroladsp

More Groups: http://www.dsprelated.com/groups.php3