Minimum DTS file for TI AM62

Technical Support
,
1

Dear all,

We designed a card based on Verdin TIAM62 (including Wifi + BLE module) with ethernet and LVDS , mainly based on Mallow board, I would like to know in the GIT repo “ti « dts « boot « arm64 « arch - linux-toradex.git - Linux kernel for Apalis, Colibri and Verdin modules” what is the minimum DTS file I shoud use ? I would add after the numerous SPI and I2C devices.

Thanks

2

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

Did you like my answer?

:+1: :-1:

Hello!

For the Verdin AM62, the appropriate base device tree to begin with is:

k3-am625-verdin-wifi-dev.dtb

This choice is due to the following reasons:

  1. You are utilizing the Verdin AM62 with a WiFi + BLE module.
  2. It is essential to start with a base device tree that aligns with your specific hardware platform.

To create your custom device tree, follow these steps:

  1. Clone the Linux Toradex repository and use the toradex_ti-linux-6.6.y branch.
  2. Create your custom .dts file by copying the base device tree.
  3. Add your SPI and I2C device configurations as needed.

For I2C devices, you can add them as child nodes under the appropriate I2C bus parent node. The Verdin standard provides one general-purpose I2C interface in the “Always Compatible” section and three additional I2C interfaces in the “Reserved” class.

If you need more specific details about customizing the device tree for your particular requirements, feel free to ask!

Best regards,
Toradex AI Assistant.

3

Dear @quatoria,

For your question to be answered we would first have to understand the structure of the device tree used, which can be seen on this developer page. As you can see there are the three major levels (SoC, SoM and carrier board). Generally speaking we can say that what is defined on SoC level can be overwritten by both the SoM and carrier board levels. Nodes defined on the SoM level can be overwritten on the carrier board level. In your specific case the minimal device tree thus essentially consists of the SoC and SoM levels. The carrier board level, consisting of k3-am625-verdin-wifi-mallow.dts, which includes k3-am62-verdin-mallow.dtsi and the SoC and SoM levels, defines all the hardware peripherals which are on our Mallow carrier board. Since your own board is based on it, I believe the best approach would be to start from the existing Mallow carrier board files and start excluding whatever you are not using on your own board. Keep in mind to constantly compile the device tree and test out the changes, since certain nodes might interfere with different device tree levels. Following that you can create your own nodes for hardware which is present on your custom carrier board but not on the mallow board.

Best regards,
Collin