Pin Acting Odd

21 views
Skip to first unread message

jmsch...@gmail.com

unread,
Jul 8, 2015, 10:09:07 PM7/8/15
to beagl...@googlegroups.com

Hey all,

I am pretty new to the BBB and I came across something pretty odd that I have been trying to figure out for a few hours now as I was creating a push button circuit:

P9_25 is a GPIO pin.  I set it to input but noticed that it would not respond to my button.  After some digging I realized that the pin itself was acting funky, so I isolated it to run some tests with BB's Bonescript tutorial on GPIO digitalWrite().  I ran this code below (apologies for the sloppy picture) with the adjacent circuit configuration shown as well.  Obviously, the LED should turn off, but it doesn't:


 


I then tried the same tests on other pins, such as P9_26, and it worked perfectly, so that's where I'm startled.


I have two theories:


1)  I messed with P9_25 in the past, and it is reconfigured in a weird way; if someone has this hunch, could you please perhaps inform me how to reset the pin to its original glory?


2) The pin is busted.  Fingers crossed for #1.


If anybody has run into something similar, or has any idea what I should do, please let me know!


Thank you for you time.


-Joe

Gerald Coley

unread,
Jul 8, 2015, 10:14:00 PM7/8/15
to beagl...@googlegroups.com
Take a look at the schematic. GPIO3_21 is connected to the output of a clock generator. To use it you must disable the Oscillator.

Oscillator can be disabled via SW
for power down modes or if
GPIO3_21 needs to be used

My suggestion is to pick another pin to work with. Less headaches.

Gerald


--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

jmsch...@gmail.com

unread,
Jul 9, 2015, 8:32:13 AM7/9/15
to beagl...@googlegroups.com
Okay I think I see what you are saying.  The MODE0 for GPIO3_21 is "mcasp0_ahclkx",  so with that beaglescript code, when I say "b.pinmode("P9_25",b.output)" it is outputting the results of the MODE0 (clock generator output) and not the MODE7(GPIO output) as I had expected?

But if this were the case, in my Python ADAfruit code, I explicitly set that pin to GPIO, so shouldn't behave like that?

Thanks for your help, really trying to get a solid grasp on these concepts!

-Joe

Gerald Coley

unread,
Jul 9, 2015, 8:33:14 AM7/9/15
to beagl...@googlegroups.com
I can't speak for the SW implementations. I just know how the board was designed.

Gerald

jmschmitz12

unread,
Jul 9, 2015, 11:20:57 AM7/9/15
to beagl...@googlegroups.com
Okay gotcha. Would you agree with my logic in the first part then (about the beaglescript)?



Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/UpeUMNBIkKU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.

Gerald Coley

unread,
Jul 9, 2015, 1:40:05 PM7/9/15
to beagl...@googlegroups.com
I defer to the creator of BoneScript to answer that. I assume that if the HDMi port were disabled, it frees this pin as well. But maybe not.

Gerald

Reply all
Reply to author
Forward
0 new messages