[SOLVED] SES Year 2038 time_t Issue

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] SES Year 2038 time_t Issue

    I am using SES 5.60A with the Nordic nRF series and I have a project that requires epoch time in 64-bit. Currently the bundled SES libraries use a `long` for time_t which will overflow in 2038. Does Segger have any plans to update this to support signed long long for time_t?

    Thanks,

  • Hello,

    Thank you for your inquiry.
    There are no short term plans to change this as this is how it is still defined in the C standard.
    But we will take care of this when there is firmware with an expected lifetime beyond 2038.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.