Hi all,
My modified peripheral program (based on the template) stops working after ~24 hours (upper limit - I didn't catch the exact moment). The program includes a 5-minutes timer that changes the advertising data (and also restarts the timer).
When I look at the module's current consumption with a scope, it looks like there's constant ~0.8mA consumption - i.e. the program doesn't go to sleep and does not broadcast.
I suspect one of two issues are happening:
1. An infinite loop due to a bug in my code - I don't see a reason why it would happen only after so many hours.
2. A memory leak - Not likely, the problem did not happen on the development kit, only on our burned module.
3. Clocks synchronization problem.
The third option looks most likely.
The only flag that I changed for the version that I burned on the OTP was the DEVELOPMENT_DEBUG (set to 0).
Is there another preprocessing flag that I should change, like a watchdog to synchronize the clocks?
Can you think of another reason for the problem?
Thanks,
Oren
----- Edit -----
有一个TODO-List-before-burning-OTPs regarding all the preprocessing parameters in da14580_config.h ?
Hello Oren, sorry i have missed your question. You mention module : Which module are you using ?
BR JE_Dialog
Hi Oren, I have sent you a mail on the subject.
Best regards, RvA(Dialog)
Hi I'm Having a similar problem with my module (PAN1740), can you please share if you found a solution for this issue.
Are you doing anything timer/timing-related? The internal 27-bit BLE-clock that can be retrieved by lld_evt_time_get() has 625us time unit which means it will wrap after 23.3 hours. If you leave Keil debugging on you can see what happens if you press the stop button when it gets stuck.