Other Parts Discussed in Thread: SYSCONFIG
Tool/software:
Dear TI Support Team,
root@am62xx-evm:/# cd libgpiod-2.0 root@am62xx-evm:/libgpiod-2.0# LS -sh: LS: command not found root@am62xx-evm:/libgpiod-2.0# ls COPYING LICENSES NEWS TODO autogen.sh autostuff config.log configure.ac include lib man tools Doxyfile.in Makefile.am README aclocal.m4 autom4te.cache bindings configure configure~ index_FDS.html m4 tests root@am62xx-evm:/libgpiod-2.0# sudo ./autogen.sh autoreconf: export WARNINGS= autoreconf: Entering directory '.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy --force libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'autostuff'. libtoolize: copying file 'autostuff/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' autoreconf: configure.ac: not using Intltool autoreconf: configure.ac: not using Gtkdoc autoreconf: running: aclocal --force -I m4 autoreconf: running: /usr/bin/autoconf --force configure.ac:75: warning: The macro 'AC_HEADER_STDC' is obsolete. configure.ac:75: You should run autoupdate. ../autoconf-2.72e/lib/autoconf/headers.m4:663: AC_HEADER_STDC is expanded from... configure.ac:75: the top level configure.ac:203: error: Unexpanded AX_ macro found. Please install GNU autoconf-archive. If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: error: /usr/bin/autoconf failed with exit status: 1 root@am62xx-evm:/libgpiod-2.0#
I am currently working on the AM62x E3 evaluation board and am encountering issues with the SPI driver. Specifically, the spidev device is not appearing in the /dev/ directory. We have enabled SPI in the Device Tree Source (DTS) file and compiled it, following the guide provided on the TI website. However, the spidev device node still does not show up.
To further diagnose this issue, I would like to rule out any potential hardware-related problems. My plan is to configure the SPI pins as GPIO output pins and toggle them to check the voltage levels. If the voltage levels change, it would suggest that the issue lies within the Device Tree Binary (DTB) configuration.
To achieve this, I used TI’s SysConfig tool to configure the SPI pins as output pins with pull-down settings. The tool generated the corresponding DTSI file, and I integrated the pin configuration into the DTS file. The file compiled successfully, but I now need assistance toggling the GPIO pins through application code or commands to verify the voltage levels on the SPI0 pins.
Here’s what I have tried so far:
Accessing GPIO through sysfs:
I attempted to access the /sys/class/gpio directory to toggle the GPIO pins, but the directory is missing. Upon further research, I found that the sysfs interface for GPIO control has been deprecated, and suggestions point towards using libgpiod.
Using libgpiod:
I downloaded the libgpiod library from GitHub and tried to compile and build it locally. However, I encountered errors when executing the ./autogen.sh script. I have attached the error details for reference.
Could you please guide me on how to properly toggle the GPIO pins using application code, particularly to check the voltage levels on the SPI0 pins? Earlier, we used sysfs to easily export and control GPIOs, but with the deprecation of sysfs, I am uncertain about the correct method to proceed.
Your assistance would be greatly appreciated.
Thank you!
Best regards,
Raj