On 22/03/17 16:24, David W. Schultz wrote:
> Calling another function from the ISR was what triggers this bad
> behaviour. Especially if the called function is in another file.
Hi David,
my code doesn't call a function in the interrupt, it merely decrements a 
count, tests it for zero and, if not, sets a port bit hi or low, then 
exits. This uses only R13 which is why I'm surprised that all the others 
are 'push-pulled'. Your description also depicts not the best behaviour.


The Sun is out, the sky is blue, it's time to drive the MR2.

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Mspgcc-users mailing list

Reply via email to