• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 299 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM6442: TI AM6442 drivers are not deployed even if the lines are inserted into arch/arm64/configs/tisdk_am64xx-evm_defconfig file

Levent Karakaya
Prodigy 70 points
Part Number: AM6442

Hello,

I have a custom board. There are several custom components on i2c buses. All my changes on dts are obsersed under /sys/bus/i2c/devices. But, I don't see any entry in my dmesg output. I also didn't see it under /sys/class/hwmon. I think the changes in arch/arm64/configs/tisdk_am64xx-evm_defconfig file doesn't have any effect.

I use following command to compile and build the changes. I just make all modifications under kernel-sources directory. And I dont create patch files for the moment.

MACHINE=am64xx-evm bitbake -f tisdk-default-image -C compile virtual/kernel

For example, my temperature sensor is  PCT2075GVX. Its id is 0x48. It can be observed in the output of i2cdetect.

root@am64xx-evm:~# i2cdetect -y -r 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: 40 -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
50: UU UU -- -- -- -- 56 -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- 6b -- -- -- 6f
70: -- -- -- -- -- -- -- --

Below you can see my dts settings for temperature sensor;

tempsensor@48 {
compatible = "nxp,pct2075";
reg = <0x48>;
};

Can you please comment on the problem?

Best regards

  • 0
    TI__Guru 69582 points
    Levent Karakaya said:

    I think the changes in arch/arm64/configs/tisdk_am64xx-evm_defconfig file doesn't have any effect.

    I use following command to compile and build the changes. I just make all modifications under kernel-sources directory. And I dont create patch files for the moment.

    Just noticed this was still open so I wanted to add some comments here. Yes it can happen that Yocto doesn't pick up changes made directly to the source trees. One can clean a target and/or force a re-build of a particular recipe, but since you are modifying the sources directly that would also eliminate your changes. There's a couple of ways to do Kernel development in the context of Yocto, see for example the documentation here that applies to our Kirkstone-based SDKv9.x (same principles also apply to previous Dunfell-based SDKv8.x releases): https://docs.yoctoproject.org/4.0.11/kernel-dev/common.html

    If you don't want to dive too deeply into the related Yocto features you can just create/add patches to your Yocto Kernel recipe even during your development/testing.

    Regards, Andreas