8 years, 10 months ago.

nrf51_rtc and BLE_API

Hi,

I am trying to build a sort of Smartwatch using a BLE Nano (contains an nRF51). I am using both the BLE_API and nrf51_rtc.

At startup, the phone sends its timestamp to the BLE Nano for initializing the RTC. This works fine and I see the correct time displayed on the external SPI LCD.

After that, I am sending a message via BLE from my phone to the device. A bluetooth callback is made, displaying the message on the LCD display, and then I go back to my "watch" mode where I call rtc.time().

At that point, the rtc seems to "jump" for about 10 to 15 minutes in the future.

Have you tried using both BLE_API and your lib in the same program ?

Do you have any idea why this is happening and if I can try something to fix it ?

Question relating to:

An attempt to provide a Real Time Clock for the nRF51-DK. This code provides rtc.time and rtc.set_time replacements for the similarly named C standard methods (unimplemented for nRF51-DK last I … nRF51-DK, RTC, time
Be the first to answer this question.