Time() on IMP001 always zero


#1

On one of our test devices, using still an IMP001, the time() suddenly started to return 0 all the time.
It worked fine for several years, no change in code whatsoever.

Is this likely to be a hardware failure on the IMP001 (which is what I hope) or can there be something else ?

Dirk


#2

I guess it was a hardware failure on the IMP001. Swapping it with a new card solved the problem.

Have you guys seen this occuring anywhere else ?

Dirk


#3

Just out of curiosity, did you swap the “old one” back in and try it again? Perhaps it’s a firmware update issue and the imp didn’t get the updates?


#4

I believe that if the 32kHz xtal does not start, this is what you’d see on an 001. Could just be a hardware failure.