CC1310: CC1310 Clock loss interrupt not triggering in standby mode

I don't think it exist an easy work around on this.

- Is it an option to use the internal 32 kHz RCOSC? 

- What sort of environment have you placed the DUT in to get clock loss? It would be useful to look into if it exists options to prevent the clock loss in the first place. 

yes there is the possibility to switch to the internal one but in the errata notes it says dont use it (RCOSC_LF (32.768 kHz) may occasionally produce glitches)

all i know is that a customer has thousend of devices with this mcu and it looks like some where stored in a warehouse (sleeping) and they wanted to activate it, 4-5 weren't waking up anymore. With a esd gun we could get this behavior too but we are not sure if its esd related.

just wanted to know if there is something we could try to prevent it, but i guess we can only tell them turn it off and on again. seem to be a rare case.

Meaning that it's not know why the device has stopped? Has it been verified that what they seeing is actually clock loss? 

that's what i have been told, and with a reset it was oscillating again.

How often does this seems to happen? The reason I ask is that it would be interesting to know if placing a Launchpad running close to the same software at the same location will experience the issue. In other words, could it be that the layout is not optimal? 

first time i hear about it in 5 years of selling this device, so not that common.

I was thinking for this customer and in this environment: " it looks like some where stored in a warehouse (sleeping) and they wanted to activate it, 4-5 weren't waking up anymore"

i meant that customer.

OK, so basically very hard to reproduce and debug

yes, i think we can close this topic.

thanks anyway

Ok. Let me know if it's possible to reproduce in some way. 

If you want to test it with the eval board you can touch the quartz or shortcut it. Maybe you find a way to get the clock loss reset in standby mode.

That is unfortunately not possible since in standby everything is off except for the clock. The clock is needed to wake up the chip and if the clock dies, no possibility to detect that the clock has died.

I was more thinking about finding out why the clock dies in the first place. I forgot to ask: The devices that "died", were they placed close to a potential noise source?