maxruben
Are you sure that the CAN controller actually is sending the wrong data since this didn't happen when you where running without interrupts?
Perhaps you are only fixing some of the effects from the real, so far unidentified, error.
But now you should be able to trace exactly what is going on in the processor and what interrupts, if any, are triggered around the time where you get the wrong data.
/Ruben
Hi Ruben, you're so right about that. I actually mend that the bug is closed about the undefined resets. I've now found it's cause. We continue however our investigation how and why sometimes we get wrong data from the external CANbus controller. It's weird that when not using interrupts, there wasn't a single problem reported.
Thank you all for you'r mindsets :)
