Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

P9_28 not GPIO_123 #31

Open
loving2 opened this issue Aug 7, 2017 · 0 comments
Open

P9_28 not GPIO_123 #31

loving2 opened this issue Aug 7, 2017 · 0 comments

Comments

@loving2
Copy link

loving2 commented Aug 7, 2017

Hi,

I've been working with interfacing a beaglebone green with an LVDS transceiver chip where I needed to use a GPIO pin to select either READ_ENABLE or WRITE_ENABLE for half duplex communication. I had decided to use P9_28. It wouldn't function at all when I looked up the documentation for the beaglebone green regarding which GPIO pin P9_28 was. Your documentation claims it to be GPIO_123. To be clear, I'm referencing the wiki page found at http://wiki.seeed.cc/BeagleBone_Green/ under the section labelled "Pin Map". The beaglebone black documentation claims P9_28 is GPIO_113. I thought perhaps the pins were named differently from green to black, but when I tried setting it up as GPIO_113 it worked perfectly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant