Hello Raphael Neider schrieb: > Dear Néstor, > >> your answer is very appreciated. I have refactored the code as you >> told, I put all the global variables in a header file, called >> "defs.h". I have also taken out all the calls to functions from the >> interrupt. Now, interrupt handler routine is a lot simpler. Just one >> thing: I haven't been able to disable the interrupt and save the stack >> with the code you gave me. Apparently, it should work, since I'm using >> a PIC 16F877, which seems to have 16 stack bytes. Am I missing >> something from your explanation?
One sidenote. IIRC you cannot access the stack on the pic16f devices. This is only possible on pic18f devices. There is a wonderfull appnote about that on microhcip website. I managed to have a small scheduler which saves the context (stack, sdcc-stack via FSR1,FSR2, and some regs) of up to 4 tasks running on a pic18f. If you like i can send you the code. Regards, Jan ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
