Until recently, I've been developing an application using the LaunchPad evaluation board, and with project_zero as my starting point. During that time I've not encountered this issue...
Now, I'm troubleshooting a new board with the CC2652R7, which has external oscillators for both 32kHz and 48MHz clocks. On one of four boards tested so far, I've run into a strange issue where the application crashes as soon as I try to do anything RTOS related. For instance, calling ProjectZero_createTask() in main, and even just calling sleep results in a hang. The only thing different I've been able to observe on this board is that during main, I can call OSCClockSourceGet(OSC_SRC_CLK_LF), and it returns OSC_RCOSC_LF instead of OSC_XOSC_LF (as expected, and like on the three working boards). What's even more strange is that I continued testing this board some more after a few days set aside, and it started working again. Any ideas why this issue might have happened, other things I could check in firmware to help troubleshoot if I encounter it again, or is there a proper way to override this LF clock back to XOSC if it initializes to the "wrong" one?