External RTC Colibri IMX8X Torizon OS device driver support

[Deepak1]

Hi,

We are using torizon OS torizon-core-docker-colibri-imx8x-Tezi_5.7.2+build.20.tar
and we have below external RTC IC’s options to be used for our product, does torizon OS has device driver support for below, If yes can you please help to on how to configure the same from device tree.

1. microchip,mcp7940x
2. dallas,ds1340
3. pericom,pt7c4339

Thank you

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Hello,

Thank you for reaching out with your question about RTC IC support on Torizon OS for the Colibri iMX8X module. Torizon OS, being based on the Linux kernel, generally supports a wide range of hardware through existing drivers.

For the RTC ICs you mentioned:

1. microchip,mcp7940x: This RTC is supported by the Linux kernel. You can verify if the driver is available in your Torizon OS image by using the command lsmod to list loaded modules or modinfo mcp7940x to check for the module’s presence.

2. dallas,ds1340: Similarly, the DS1340 is supported by the Linux kernel. Use the same method as above to confirm its availability in your Torizon OS image.

3. pericom,pt7c4339: This RTC might not be as commonly supported. You should check the Linux kernel documentation or source to confirm driver availability.

To configure these RTCs in the device tree, you will need to add a node for the RTC in your device tree source file. Here is a general example of how you might configure an RTC in the device tree:

&i2c1 {
    status = "okay";
    rtc: rtc@68 {
        compatible = "microchip,mcp7940x"; // or "dallas,ds1340"
        reg = <0x68>;
    };
};

• compatible: This property should match the driver name in the kernel.
• reg: This is the I2C address of the RTC.

For applying these changes, you can use Device Tree Overlays, which allow you to modify the device tree without recompiling the entire kernel. The TorizonCore Builder tool can be used to apply these overlays to your Torizon OS image.

If the driver for a specific RTC is not included in your Torizon OS image, you may need to build it as an external module using the TorizonCore Builder tool. This involves downloading the kernel source, configuring the module, and integrating it into your system.

Ensure that your device tree modifications are correctly applied by checking the /proc/device-tree directory on your running system. This will confirm that your changes are active.

I hope this helps! If you have any more questions, feel free to ask.

Best regards,
Toradex AI Assistant.

Please, also check if these links can help you solve your problem:

Device tree or driver settings for alternate RTC on BSP 5.0

I have a carrier with an MCP7940N RTC chip in i2c bus 1 at address 6f. The device tree overlay includes: &i2c1 { #address-cells = <1>; #size-cells = <0>; status = "okay"; /* real time clock on carrier board */ rtc_i2c: rtc@6f { compatible = "microchip,mcp7940x"; reg = <0x6f>; status = "okay"; }; }; According to https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/rtc/rtc-ds1307.txt, this string looks like the correct “compatible” for the driver to use t…

Torizon RTC and RTC on SOM

I need to use internal RTC (SOM) IMX8d and a rechargeable battery. I tried to adjust time in different way date -s “2 June 2024 14:05:00” timedatectl set-time “2024-01-31 11:13:54” with set_clock in c++ program. all work fine also inside a docker, but when I switch off the board the date returns to the default value. I connected a rechargeable battery to PIN 40 of the SOM but maybe it is not using that rtc. dmesg | grep rtc print following [ 1.461967] imx-sc-rtc scu:rtc: registered as…

IOT RTC rv-3028 driver is written for 5.13 and Torizon is 5.5.