Hello Leon,
The example code works fine on its own (both interrupt and RTC wake the mDot successfully), so the problem is not in the mDot itself. Calling the API directly from the main project acts the same as when calling it from mdotUtil (sleep not working, setWakePin not setting).
It seems to be some bug that occurs when my project interacts with the API, but I can’t seem to find why it’s acting the way it is… I guess I’ll just have to continue thoroughly inspecting my code until I find the problem. Is there any commands or settings I can use to get feedback from the library? For example – what error codes are risen before the controller hangs, or what happens when I call setWakePin? Is TRACE the lowest level of logging available?
Thanks,
Mark.