Implementing time_t as 64 bit to solve Y2038 problem.

[Arie_tondo]

Hi,

We use SDK nRF5_sdk15.2 and ARM GCC cross compiler to develop application that runs on nRF52840.

We use new lib, as it was done in examples.

I noted recently that time_t is implemented as signed 32 bit what means that it can cause problem in 2038.

We use time_t to save epoch as we need to use c library functions (like mktime, ...)

Is there a way to change the definition of time_t to 64 bit or otherwise prevent the Y38 problem? 

[Arie_tondo]

Hi,

thank you for the reply.

We have units in the field that can be updated only by FOTA(above cellular network), Is it possible to update in DFOTA units that runs SDK and soft device to units that run sdk connect and zephyr?

[AHaug]

Hi,

Unfortunally we do not support  DFU/FOTA upgrades from nRF5 SDK to nRF Connect SDK. This thread from a few months ago is a good read as to why we don't support it, some reasons to migrate from nRF5 SDK to nRF Connect SDK, as well as the challenges that may come with trying to create a custom DFU method.

I believe the discussion in that thread answers this questions, and feel free to join in on that thread if you have any follow up questions to what is asked there. Additionally, please feel free to ask more questions here as well if your question is still unanswered! 

Kind regards,
Andreas