I am working with an RTCC clock on my PIC. The data sheet says
The RTCSYNC bit indicates a time window during which the RTCC Clock Domain registers can be safely read and written without concern about a rollover. When RTCSYNC = 0, the registers can be safely
accessed by the CPU. Whether RTCSYNC = 1 or 0, the user should employ a
firmware solution to ensure that the data read did not fall on a rollover boundary, resulting in an invalid or partial read. This firmware solution would consist of reading each register twice and then comparing the two
values. If the two values matched, then, a rollover did not occur.
So first off what is rollover and why should I worry about it?
If I wait for RTCSYNC to be 0 like the datasheet says, it really slows down the reading of the register.
Do I really need to worry about it? Seems to work OK without waiting for RTCSYNC.
The RTCSYNC bit indicates a time window during which the RTCC Clock Domain registers can be safely read and written without concern about a rollover. When RTCSYNC = 0, the registers can be safely
accessed by the CPU. Whether RTCSYNC = 1 or 0, the user should employ a
firmware solution to ensure that the data read did not fall on a rollover boundary, resulting in an invalid or partial read. This firmware solution would consist of reading each register twice and then comparing the two
values. If the two values matched, then, a rollover did not occur.
So first off what is rollover and why should I worry about it?
If I wait for RTCSYNC to be 0 like the datasheet says, it really slows down the reading of the register.
Do I really need to worry about it? Seems to work OK without waiting for RTCSYNC.