Thank you, Mark. I've been pouring over all the datasheets, and
couldn't quite seem to grasp these details.
On Mar 14, 2007, at 10:56 PM, Mark Rages wrote:
> ...
> So the code ends up looking like this:
>
> void isr_high interrupt 1 {
>
> if (PIR2bits.TMR3IF) {
> // deal with TMR3 expiring
> PIR2bits.TMR3IF=0;
> }
>
> if (INTCONbits.TMR0IF) {
> // deal with TMR0 expiring
> INTCONbits.TMR0IF=0;
> }
> }
>
Aha! That makes complete sense. Thanks. That's exactly the piece
of knowledge that I was missing. It clears up some other questions
that I had about execution order, too. And the DEF_INT* and
SIGHANDLER macros make a lot more sense now.
> Even if the ISR takes a long time, nothing bad happens. There will
> just be some little delay between two characters from the USART.
> RS-232 is fine with this. It would be a problem if you were using a
> software, bit-banged UART for obvious reasons.
Cool. That's good to know.
Thanks again!
Matt
–––––––––––––––––––––––––
Matt Bauman
Research Technician, Miller Lab
Physiology, Ward 5-150
Northwestern University
Ph: 312-503-7353
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sdcc-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sdcc-user
