TMDX654IDKEVM: How to Develop Applications

Hi Akm,

if your goal is to develop and debug Linux userspace applications (as opposed to U-Boot or Kernel) using CCS, you can follow the instructions here: https://software-dl.ti.com/processor-sdk-linux/esd/AM65X/08_06_00_47/exports/docs/linux/Foundational_Components/Tools/Code_Composer_Studio.html While those instructions are somewhat outdated, the general principle and flow should still apply. These instructions also cover how to build (cross-compile) your application.

Another way you could go about this is using Visual Studio (or vanilla Eclipse, if you want), to connect to a gdbserver session running on your AM65x embedded platform. The debugging itself will usually happen through a network interface (Ethernet) between your host PC and the target platform in such cases. Doing such development and debugging is really generic (rather than TI-specific like in case of using Code Composer Studio), and doesn't even need JTAG. So I'd encourage you to do some Google search on this topic, there's a lot of resources online on this. For example this came up when I looked for Visual Studio Remote Debug, https://stackoverflow.com/questions/53519668/how-to-attach-to-remote-gdb-with-vscode, but there's probably a lot newer/better resources or tutorials you can find.

Regards, Andreas

Akm Islam said:

The SDK documentation does not list the AM65x family SOC with any SPI drivers. Does this mean it cannot be done for this specific board?

You can ignore that table, it is out of date. The AM65x supports multiple SPI interfaces without any issues. The same concepts in this chapter regarding the "McSPI" peripheral essentially apply to all TI processors no matter what.

Akm Islam said:

How can I adjust the pinmux configuration via the device tree?

The general flow is as follows:

1. Install the latest AM65x Linux SDK from https://www.ti.com/tool/PROCESSOR-SDK-AM65X
2. Use the TI SYSCONFIG tool to configure a suitable SPI interface that's accessible via the on-board headers on your EVM (check schematic and board user's guide to figure out which one to use). The SYSCONFIG tool is available in both online (cloud-based) and offline versions, see https://www.ti.com/tool/SYSCONFIG
3. From the SYSCONFIG tool then copy and paste the generated code section into the appropriate Linux device tree file for your board. In your case that would be <kernel_root_dir>/arch/arm64/boot/dts/ti/k3-am654-base-board.dts, see https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/arch/arm64/boot/dts/ti/k3-am654-base-board.dts?h=ti-linux-5.10.y
4. Make sure the SPI device node you've chosen isn't set to "disabled" somewhere in the DTS hierarchy. If so, set it to "enabled" in your top-level DTS file.
5. Use the AM65x Linux SDK to re-build the device tree files according to the SDK documentation, see https://software-dl.ti.com/processor-sdk-linux/esd/AM65X/latest/exports/docs/linux/Foundational_Components_Kernel_Users_Guide.html#compiling-the-device-tree-binaries

You can actually see an example how such a SPI device definition looks like including pinmux if you look at how main_spi0 is defined. So you can model after that, but using a different SPI module, available on the board.

Example pinmux definition for main_spi0:
https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/arch/arm64/boot/dts/ti/k3-am654-base-board.dts?h=ti-linux-5.10.y#n271

Example SPI device definition using main_spi0:
https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/arch/arm64/boot/dts/ti/k3-am654-base-board.dts?h=ti-linux-5.10.y#n436

Regards, Andreas