With the word 'failed' it makes the message seem like something is messed up.
Thanks for the quick reply Chris.
Hello Chris,
Sorry for bringing back this thread, but I am also experiencing something similar when making some fast input readings using
interrupts.
My scenario is similar to this thread:
http://forums.netdui...goodbye-net-mf/
After upgrading to firmware 4.2 I started to get these "Failed allocation for X blocks". To verify if my app was still running I put some LED blinking, but it seems the app is crashing.
I would like to confirm if my thinking is correct:
As my test app does not allocate much objects but it does use
interrupts, I suspect the
memory is missing due to the "nested
interrupts". In other words, during the
interrupt handling my application receives a new
interrupt request that is also handled before the first
interrupt is completely treated. So after some time there will be no RAM enough for saving such a huge stack, correct?
I tried to change the
InterruptMode to
InterruptLevelHigh instead and the error messages were gone. This way I would "avoid" having nested
interrupts as I reactivate it only at the end of the handler. Obviously I will loose input pulses this way...
Igor.