Yahoo Groups archive

68300

Index last updated: 2026-04-29 00:01 UTC

Message

Re: [68300] IRQ7 acting odd

2003-07-15 by Scott Newell

>I have a Benchmarq bq4842y battery backed ram RTC chip with INT* tied to 
>IRQ7* directly (no pullup).

Have you examined the signal with a 'scope?


>I have programmed PFPAR with a value of 0x80. DDRF is irrelevant but has a 
>value of 0x13.
>
>VBR is 0x100000. Location 0x10007C has 0x10E0C8 (address of the interrupt 
>routine). Interrupt routine is declared as such and ends in RTE.

Are you autovectoring?  /AVEC tied low, or using a chip select?


>I have placed a breakpoint at the beginning of the interrupt routine (using 
>SDS debugger) and the breakpoint never fires. When the RTC interrupt 
>happens I can watch the INT* line go low and from that point on, when I try 
>to halt the processor, SDS complains that it had to use a double bus fault 
>to halt the processor. Prior to the interrupt the processor will halt
properly.

Hmm...can you separate the debugger from the ISR?  I'm thinking do
something in the ISR that you can see without using the debugger; toggle an
led, flip a pin, transmit out the serial port, etc.  At the very least,
increment a global variable and watch it from main line code and see if the
ISR is ever running.


newell

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.