Thanks, just got on line, and in interim I had a post in Out box with a copy of Bill's advice and referred to the original thread I started, which correlates with your advice. That's certainly how I ended up leaving my RS232 low level abstraction. I haven't seen any issues anymore (I think). This is on my LPC2000 Basic interpeter. -- Kris ----- Original Message ----- From: "embeddedjanitor" <manningc2@...> To: <lpc2000@yahoogroups.com> Sent: Tuesday, April 20, 2004 5:35 PM Subject: [lpc2000] Re: Disabling/enabling interrupt causing a data abort > In general, I'd say it is better to use global interrupt > enable/disable than doing this in the VIC. > > See http://www.arm.com/support/faqip/3677.html > > IMHO, getting defualt IRQs is a way to clean up/detect spiruous > activity rather than the normal way of doiing things. > > > --- In lpc2000@yahoogroups.com, "Curt Powell" <curt.powell@s...> > wrote: > > Kris, > > > > I added an assembler harness to accept the default irq, loaded up > > VICDefVectAddr with its address, and let it fly. The default > handler is > > being called periodically (it just prints a diagnostic and returns) > so > > it appears to be working- I can't give a definitive answer until it > runs > > for a couple of hours, but so far so good. Thanks so much for your > > insight. > > > > Curt
Message
Re: [lpc2000] Re: Disabling/enabling interrupt causing a data abort
2004-04-20 by microbit
Attachments
- No local attachments were found for this message.