There are several reasons why we can’t move to sandboxed apps.
I can count the errors, but if there is a delay where no errors occur, the next errors might not trigger a reboot.
How is this handled?
Is there any code I can look up to understand the mechanism?
We really need to understand how it works, because we are also facing random reboots in the code that is not for unit testing.
Unfortunately there is nothing in uart2. The next message after the crash is the first line of the boot.
But how is this mechanism working?
Is it just counting the errors and after x errors it stops the app?
Or is it counting the errors over time and if x errors occur in x seconds it stops the app?
Its just a lot of LE_ERROR messages. The code itself doesn’t produce any fault which could be related to memory, etc.
If a function is not able to e.g. open a file, it will log it with LE_ERROR. This is where all the messages are comming from.
Also the reboot is absolutely random. It’s never at the same time or state of code.
But still all my question remain:
How does this feature work?
We are using the basic log API LE_ERROR(..), LE_INFO(..) and so on.
I’m not allowed to paste the code here and it would be way to much, because as I said, this is not happening in a particular case. It’s happening more on a random base.
I’ll figure it out how this mechanism works. Thanks