Sign in

username:

password:



Not a member?

Search motoroladsp



Search tips

Subscribe to motoroladsp



motoroladsp by Keywords

56303 | 563xx | 5680 | 56805 | 5680x | 56F80 | 56F800DEMO | 56F805 | 56f807 | 56F830 | ADC | Bootloader | Codec | CodeWarrior | CW5 | CW6 | Debugger | DSP56303 | DSP56303EVM | DSP563xx | DSP5680 | DSP56800 | DSP56807 | DSP56858 | DSP56858EVM | DSP56F803 | DSP56F805 | DSP56F807 | DSP56F80x | DSP56F826 | DSP56F827 | DSP56F8xx | EVM | FFT | Flash_over_jtag | GPIO | Interrupt | Interrupts | JTAG | LCD | Linker | MCF5307 | Metrowerks | Modulus | MSCAN | PCMaster | PWM | Quad | Rif | RTOS | SDK | SPI

Discussion Groups

Discussion Groups | Freescale DSPs | RE: DSP56F827 - Un-handled Interrupt: finding sour ce??

Technical discussions about Freescale (Motorola) DSPs (including the DSP56000, DSP56300, DSP56600, 56800 DSPs).

  

Post a new Thread

RE: DSP56F827 - Un-handled Interrupt: finding sour ce?? - Corey, Rick - Dec 30 16:45:00 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
_____________________________________
/groups.php3






(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )

RE: DSP56F827 - Un-handled Interrupt: finding sour ce?? - Corey, Rick - Dec 30 17:03:00 2003

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
_____________________________________
/groups.php3

_____________________________________
/groups.php3




(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )