Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] Interrupt Handling

2004-11-07 by microbit

Apart from the VIC handler, you shouldn't have a pressing need to
change the vector table, they're all weak symbols, so you just need to
define
a handler with the same name to override, doesn't affect your table.

Eg : An swi_handler :

# ifdef    EXCEPTIONS
void swi_handler (void )
{
// do your own thing
}
#endif


the address of your swi_handler function will override
in the linker, so you don't need to change the vector table for that.

-- Kris




----- Original Message -----
From: "Robert Wood" <robert.wood@...>
To: <lpc2000@yahoogroups.com>
Sent: Sunday, November 07, 2004 11:51 PM
Subject: Re: [lpc2000] Interrupt Handling


> >> What toolchain are you using ? <<
>
> Crossworks.
>
> >> Depending on toolchain, I could send you the modfied startup file
> directly.. <<
>
> The datasheet says:
>
> "The reserved ARM interrupt vector location (0x0000 0014) should contain
the 2
> s complement of the check-sum of the remaining interrupt vectors. This
causes
> the checksum of all of the vectors together to be 0."
>
> So, I'm thinking it shouldn't be that difficult to actually work out, but
I'm
> don't understand whether it's just talking about the first few memory
> locations, all the interrupt vectors, both, or something else again.
>
> I should work out how to calculate it really, as there's every chance I'll
> want to mod it again!
>
>       Yahoo! Groups Sponsor
>             ADVERTISEMENT
>
>
>
>
>
> --------------------------------------------------------------------------
------
> Yahoo! Groups Links
>
>   a.. To visit your group on the web, go to:
>   http://groups.yahoo.com/group/lpc2000/
>
>   b.. To unsubscribe from this group, send an email to:
>   lpc2000-unsubscribe@yahoogroups.com
>
>   c.. Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>
>

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.