We support different external RTC components. This is done using the following registry settings:
[HKEY_LOCAL_MACHINE\SOFTWARE\Toradex\RTCSync] "Protocol" = dword:0x00000001 default: 1 "SlaveAddr" = dword:0x00000068 default: 0x68 (7-bit address)
The following RTC protocols are supported:
|ST M41T0||1||0x68||Used on Evaluation Board, Iris, Orchid and Protea|
|Epson RX-8564LC||3||0x51||Used on the Limestone board|
|ST M41T81||4||0x68||Used on the MECS Tellurium Carrier Board|
|TI TPS658643||5||0x34||Internal RTC of PMU on Colibri T20|
Dates need to be 1.1.2010 or newer. Timer will overflow around 2044.
|TI TPS65911x||6||0x2D||Internal RTC of PMU on Colibri/Apalis T30|
The Default Protocol (if the registry entry is missing) is 1 (M41T0). The Default SlaveAddr (if the registry entry is missing) is 0x68 or 0x51, according to the table above.
Change the registry value "Protocol" to 3 to support the RTC chip on the Limestone.
If you are using the I2C interface in parallel to RTCSync, you can use a Mutex named "I2C" to synchronize your accesses with the RTCSync tool.
It is possible to purchase the source code of the RTCSync tool, in order to adjust it for a different RTC IC.
Following registry settings starts the RTCSync tool in the WinCE image:
You can change the value to set the key to your own sync tool or to disable the RTCSync tool.