Other Parts Discussed in Thread: SEGGER, SYSCONFIG, LAUNCHXL-CC1352R1
Good afternoon everyone, I'm experiencing some strange new problems on the LPSTK-CC1352R board I have.
Until yesterday, it worked just fine, but then, inexplically, it started having some issues regarding the timer and uart2.
It's actually quite difficult to describe, but it looks like that the debug reset and shutdown do not work properly anymore. What I mean is that, they do reset and shutdow the debugger, but then the code won't work properly anymore, with some unpredictable behaviour, ranging from being stuck in the function "HwiP_dispatch" or not calling the interrupts anymore. Even stranger than this, sometimes it will work as expected and some other times it will behave like this. I also noticed that turning off the board helps most of the times and that it will surely have problems if the debugger is resetted of shutdown while the timer or uart2 are still operating (not stopped).
The code I'm testing these problems on was already tested and it worked just fine. These problems surface even when using TI own examples.
For example, let's take a no-rtos example with the time interrupt, having it have a led blink each second. This is a standard TI example and it worked no problem before, but now, most of the times, these problems will pop up.
I'm having a hunch that it has to do with the battery alimentation, however, even after changing them with fresh new ones the problems did not go away.
Did somebody have a similar experience before? It is driving me crazy.