> -----Original Message----- > From: lpc2000@yahoogroups.com > [mailto:lpc2000@yahoogroups.com] On Behalf Of y4krys > Sent: Thursday, 01 September, 2005 3:43 AM > To: lpc2000@yahoogroups.com > Subject: [lpc2000] Re: interrupt external > > --- In lpc2000@yahoogroups.com, Jean-Rene David <jrdavid@m...> wrote: > > * dasbento@a... <dasbento@a...>: > > > anyone knows if is possible change the mode of the external > > > interrupt when the arm is in operation, > > > > It seems the external interrupt registers are seriously broken. > > > > I have read the LPC2214's errata sheet, namely version 1.6. Three > > erratas concern the external interrupt registers: EXTINT.1, > EXTINT.2 > > and VPBDIV.1. > > > > However what I found was that the workarounds > > suggested: > > > > a. were not always necessary > > b. didn't always work > > > > Which is a bit unfortunate. > > > > In a bit more detail: > > > > I was able to configure EXTINT0 as rising edge sensitive *without* > > implementing any of the workarounds. > > > > I was *not* able to configure EXTINT0 as rising edge *with* all the > > workarounds. > > > > I was able to configure EXTINT3 as rising edge sensitive > only with all > > the workarounds *and* only if EXTINT0 had not been configured > > previously. > > > > If EXTINT0 had been configured as rising-edge sensitive > first, then I > > wasn't able to configure > > EXTINT3 as rising-edge at all, workaround or not. > > > > JR > > Does anybody know if the problem is common to all the LPC2xxx family? > I'm considering using an LPC2xxx processor in my next design. I also have had odd problems with getting combinations on an lpc2124. I couldn't seem to get edge triggered EINT0 working at the same time as edge triggered EINT2 and level+or triggered EINT3. As it turned out I was able to work around the problem for my application so I didn't pursue it furthur, but there does seem to be something broken there. Cheers, Bruce
Message
RE: [lpc2000] Re: interrupt external
2005-09-01 by Bruce Paterson
Attachments
- No local attachments were found for this message.