This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-AM62B-P1: Issue with TPIC2810D Device Register Setting - Controller Timed Out

Part Number: SK-AM62B-P1
Other Parts Discussed in Thread: SK-AM62

Hi Team,

I am encountering an issue while testing the TPIC2810D device to light an LED using WKUP_I2C0. Whenever I try to set any value to the register, I receive a "Controller timed out" error. Below are the details of my configuration:

  mywkupi2c0_pins_default: mywkupi2c0-default-pins {
+               pinctrl-single,pins = <
+                       AM62X_MCU_IOPAD(0x004c, PIN_INPUT, 0) /* (B9) WKUP_I2C0_SCL */
+                       AM62X_MCU_IOPAD(0x0050, PIN_INPUT, 0) /* (A9) WKUP_I2C0_SDA */
+               >;
+               };
 
 
&wkup_i2c0 {
+       status = "okay";
+       pinctrl-names = "default";
+        pinctrl-0 = <&mywkupi2c0_pins_default>;
+        clock-frequency = <400000>;
+       tpic2810d: tpic2810d@60 {
+                       status = "okay";
+                       compatible = "ti,tpic2810d";
+                       reg = <0x60>;
+       };
+
+};

Please let me know if there are any additional steps or modifications required to resolve this issue.

Regards,

Vikash

  • Hello Vikash,

    What version of SDK are you using?

    What terminal output do you get during bootup around initializing the I2C interface? (e.g., dmesg | grep i2c)

    What do you see with i2cdetect? You want to make sure you are accessing the right I2C interface. More information at
    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1202980/tmds64gpevm-how-to-disable-i2c-bus-devices/4538179#4538179

    Regards,

    Nick

  • Hi Nick,

    SDK version: 09.02.01.09

    root@evm:# i2cdetect -y -r 0
         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
    00:                         -- [86030.683847] omap_i2c 2b200000.i2c: controller timed out
    -- [86031.707843] omap_i2c 2b200000.i2c: controller timed out
    -- [86032.731841] omap_i2c 2b200000.i2c: controller timed out
    -- [86033.755842] omap_i2c 2b200000.i2c: controller timed out
    -- [86034.779843] omap_i2c 2b200000.i2c: controller timed out
    -- [86035.803842] omap_i2c 2b200000.i2c: controller timed out
    

    root@evm:# dmesg | grep i2c
    [    0.838636] i2c_dev: i2c /dev entries driver
    [    0.924792] omap_i2c 2b200000.i2c: bus 0 rev0.12 at 400 kHz
    [    0.925777] omap_i2c 20000000.i2c: bus 1 rev0.12 at 400 kHz
    [    0.927273] omap_i2c 20010000.i2c: bus 2 rev0.12 at 100 kHz
    [    0.928349] omap_i2c 20020000.i2c: bus 3 rev0.12 at 400 kHz
    [    5.851191] i2c i2c-2: Added multiplexed i2c bus 4
    [  334.946700] omap_i2c 2b200000.i2c: controller timed out
    [  514.466819] omap_i2c 2b200000.i2c: controller timed out
    [ 1153.379245] omap_i2c 2b200000.i2c: controller timed out
    [ 1154.403245] omap_i2c 2b200000.i2c: controller timed out
    [ 1155.427242] omap_i2c 2b200000.i2c: controller timed out
    [ 1156.451244] omap_i2c 2b200000.i2c: controller timed out
    [ 1157.475244] omap_i2c 2b200000.i2c: controller timed out
    

    Regards,

    vikash

  • Hello Vikash,

    I assume from your devicetree file you are using the SK-AM62 EVM, and you are trying to use the onchip TPIC2810D. Please let me know if you are using a different setup.

    The TPIC2810D definition in your devicetree file does not look correct to me. Please reference how we define it in arch/arm64/boot/dts/ti/k3-am642-sk.dts.

    You should also refer to the driver's bindings documentation:
    Documentation/devicetree/bindings/gpio/gpio-tpic2810.yaml

    Regards,

    Nick

  • Hi,

    We are using the SK-AM62 EVM and attempting to utilize the on-chip TPIC2810D. I have defined it in the same way as in arch/arm64/boot/dts/ti/k3-am642-sk.dts, but I am still encountering issues. Can you assist me with this?

    &wkup_i2c0 {
           status = "okay";
           pinctrl-names = "default";
           pinctrl-0 = <&mywkupi2c0_pins_default>;
           clock-frequency = <400000>;
           tpic2810d: tpic2810d@60 {
                           status = "okay";
                           compatible = "ti,tpic2810d";
                           reg = <0x60>;
                          gpio-controller;
                          gpio-line-names = "LED1","LED2","LED3","LED4","LED5","LED6","LED7","LED8";
           };
    
    };
    

    Regards, Vikash.

  • Hello Vikash,

    What kinds of issues are you running into now? Do you see any new error outputs on boot? Is there any other debug information you can provide?

    I do not have power or internet in my part of the city, and it looks like I might not have power for a couple more days. So please expect delayed responses (I had to drive to another city to be able to write this response). If I have not responded by next week, feel free to ping the thread.

    Regards,

    Nick

  • Hi,

    I have implemented the changes as suggested in the arch/arm64/boot/dts/ti/k3-am642-sk.dts file. Unfortunately, I am still encountering the same issue.

    Could you please assist me further in resolving this matter?

    root@evm:# i2cdetect -y -r 0
         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
    00:                         -- [86030.683847] omap_i2c 2b200000.i2c: controller timed out
    -- [86031.707843] omap_i2c 2b200000.i2c: controller timed out
    -- [86032.731841] omap_i2c 2b200000.i2c: controller timed out
    -- [86033.755842] omap_i2c 2b200000.i2c: controller timed out
    -- [86034.779843] omap_i2c 2b200000.i2c: controller timed out
    -- [86035.803842] omap_i2c 2b200000.i2c: controller timed out

  • Hello Vikash,

    To confirm:

    1) Have there been any devicetree changes since your response here:
    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1364273/sk-am62b-p1-issue-with-tpic2810d-device-register-setting---controller-timed-out/5219420#5219420

    I am now out of the country for the rest of this week. If you are still running into issues next week, I can try to replicate your setup on my EVM.

    Regards,

    Nick

  • Hi Nick,

    No device tree changes have been made since the previous response; however, the same problem persists.

    Regards, Vikash