My recommendation is to go to "Data Sheet Finder" page on the Microchip web site, pull down the "Select a Device" menu, pick your processor, and download the data sheet PDF file.
<http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=2046> Even the wisest and most experienced developers have to make frequent reference to the data sheet. It spells out all the details. One detail about interrupts though: they WILL interrupt any and every place that they possibly can. If there are any multi-byte variables that are being accessed by both interrupts and foreground, you have to either disable interrupts before accessing them in the foreground, or come up with a scheme to control access. -Ken Jackson Matt Bauman writes: > Hello all, > > I recently started playing around with SDCC to program PIC16 > devices. I'm moving from a compiler that implemented interrupts in > software (by appending an if...then after every line of code!), so > hardware interrupts are new and marvelous enigmas to me. Forgive my > ignorance! :) > > I have a few general questions about their behavior in several > situations: > > 1. Firstly, how do the interrupt flags work? Do they immediately ... ------------------------------------------------------------------------- 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
