• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 747 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.

DM3730 GPIO Pin configuration

Deepak L
Intellectual 270 points
Other Parts Discussed in Thread: DM3730

Dear all,

           We are working on DM3730 Panther board. We are analysing the GPIO pins on the board to use in some of our application.

We are trying to set and clear the gpio pins using Uboot commands as given below.

Path to the gpio pin access is "/sys/class/gpio"

#echo 114 > export

#echo out > gpio114/direction

#echo 1 > gpio114/value

#cat gpio114/value

# 1                                 value shown on the terminal.

As going through few documents. after the execution of the above commands, respective pin must be high(1.8V) on the board which is Pin no. 26 of  connector 1101 on the Panther Board. 

But the observed result is 0.2 V.

Kindly help us regarding this issue ASAP.

Thanks in advance.

  • 0
    TI__Guru 65405 points

    Hi Deepak,

    The sequence of commands which you are using in user space for setting the gpio 114 seems correct but probably there is some other reason for the issue.

    The easiest way to exclude hardware issue with connection to this pin is to configure other gpio and measure the voltage on it.

    You could try to add some code in kernel space to set gpio 114. See description at the link:

    http://processors.wiki.ti.com/index.php/GPIO_Driver_Guide#Kernel_Level

    BR

    Tsvetolin Shulev

  • 0 in reply to Cvetolin Shulev-XID
    Intellectual 270 points

    Thank you Tsvetolin Shulev, We tried with the other pins also like gpio 126, 127, 37,38, 114 and 115. But we could only see the change in voltage with Pins 37 and 38, other GPIOs are not responding for the commands. what would be the reason for this kindly help us.

    Rgds,

    Deepak

  • 0 in reply to Deepak L
    TI__Guru 65405 points

    Hi Deepak,

    Could you compare the pin mux configurations of gpios one which succeed manage the output level and failed one (gpio 37 and gpio 114 for example). The pin mux configuration could be found your board header file (../u-boot/board/ti/beagle/beagle.h for Beagleboard). There you would found something as:

    MUX_VAL(CP(GPIO_XXX),        (IEN  | PTU | EN  | M4))  /*GPIO_XXX*/\

    If the pin mux for both gpios are different change the settings of gpio 114 as gpio 37. Then re-build the u-boot and check gpio's behaviour.

    If the issue still exists it is possible to presents some hardware reason for the issue.

    BR

    Tsvetolin Shulev