Post Reply 
When does the Y2K38 bug happen to the HP Prime?
02-25-2019, 06:17 AM
Post: #2
RE: When does the Y2K38 bug happen to the HP Prime?
Hello,

Because the emulator and physical calculator do NOT handle RTC in the same way.

The emulators ask the underlying OS for the current time/date and will store a delta in second to "convert" the "real" (as in OS reported time/Date) to the "calculator" time/date as set by the user using the calendar or the Time/Date functions.

This is a 32 bit signed number and should allow a +/-68 year compared with the "real" time/date.


The calculator itself (physical unit) uses the CPU RTC. The G1 RTC and G2 RTC do NOT work in the same way. The G1 RTC counts in hour, minutes, seconds, days, months and year (with 2 digits for the year). It should therefore be limited to the 2000/2099 range (this is if my memory serves me well).

The G2 RTC is a 47 bit counter with 32768 'ticks' per seconds. This means that there is 32 bits for the seconds, or ~130 years of clock. on the G2, I choose jan 1 2000 as "start of time". This should allow the RTC to work up to ~2130.

Normally, the user SetDate function should limit you to the 2000 to 2100 range.
Nice trick trying to use the calendar to change it!

Cyrille

Although I work for the HP calculator group, the views and opinions I post here are my own. I do not speak for HP.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: When does the Y2K38 bug happen to the HP Prime? - cyrille de brébisson - 02-25-2019 06:17 AM



User(s) browsing this thread: 1 Guest(s)