vigneshr has quit [Quit: Connection closed for inactivity]
<thinkfat_>
opengl es2 is not so bad if you don't have legacy apps that need OpenGL and GLX
akaWolf has joined #beagle
argonautx has quit [Ping timeout: 240 seconds]
mattb0ne has quit [Ping timeout: 268 seconds]
lucascastro has joined #beagle
starblue3 has joined #beagle
starblue2 has quit [Ping timeout: 272 seconds]
Phanos has joined #beagle
<Phanos>
Hi I have beagle bone black and I notice that on some GPIOs (already exported as such) the default value is 1 (input) and the voltage is arround 3.0v. Does anybody knows why is that and how can I change it to input and to 0 by default?
<tbr>
sounds like a pull-up/pull-down thing
<zmatt>
Phanos: all gpios default to input
<Phanos>
I have tried to disable the pull up resisitor but still is reported as high
<zmatt>
which pin?
<zmatt>
also, you should _not_ disable internal pull-up/down unless the pin is always externally driven or has external pull-up/down
<Phanos>
P9.11 28 fast rx 7 gpio 0.30 << hi P9_11 (pinmux_P9_11_gpio_pin)
<zmatt>
the voltage on a floating pin is undefined, do not leave pins floating
<Phanos>
I have disable internal pull-up or pull down but still is high
<zmatt>
also, the internal pull is fairly weak and really mostly just intended to keep the pins from floating
<Phanos>
you mean I need to have external resistor on with ground connected on the other end of the resistor?
<zmatt>
at the very least enable internal pull-down
<Phanos>
in order to get it to low (0)?
<Phanos>
ok I have just down this
<Phanos>
P9.11 28 fast rx up 7 gpio 0.30 << hi P9_11 (pinmux_P9_11_gpio_pu_pin)
<zmatt>
but more generally, why are you expecting pins to have a specific value if you don't have anything connected?
<Phanos>
but still is high
<zmatt>
that has pull-up enabled, not pull-down
<zmatt>
that's why it says "up"
<Phanos>
P9.11 28 fast rx down 7 gpio 0.30 hi >> P9_11 (pinmux_P9_11_gpio_pd_pin)
<Phanos>
now is down enable but still is high
<Phanos>
:(
<zmatt>
you changed the pin to output
<Phanos>
yes you are right
<Phanos>
one momment
<Phanos>
P9.11 28 fast rx down 7 gpio 0.30 << hi P9_11 (pinmux_P9_11_gpio_pd_pin)
<Phanos>
now?
<Phanos>
still high
<zmatt>
what's connected to the pin?
<Phanos>
Basically I want to connect mcp23017 interrupt pin to P9.11
<Phanos>
according to specification of mcp chip by default you do not need an external resistor on the input pin of the microcontroller
<Phanos>
the interrupt of mcp is 3.3v
<zmatt>
looks like its INT like is a push-pull output, so it will completely override whatever internal pull you configure
<Phanos>
what is the recommended way to connect it say to pin P9.11?
<zmatt>
a wire
<Phanos>
right now nothing is connected
<Phanos>
the P9.11 shows high like that
<zmatt>
uhh
<Phanos>
any ideas?
<Phanos>
what am I doing wrong here?
<zmatt>
if there's nothing connected to the pin and it's configured as shown above then it should most definitely read low
<zmatt>
have you previously done tests/experiments on this pin with something (e.g. the mcp23017) connected?
<Phanos>
no I have not
<Phanos>
and the BBB pins are not connected to anything
<Phanos>
right now
<Phanos>
the voltage on the pin reads arround 3.0v
<Phanos>
not even 3.3v
<Phanos>
in the past few days yes I tried to connect the interrupt on that pin.
<Phanos>
and the interrupt was driven low when a change on the mcp chip occured
<Phanos>
then the pin was reading 0
<Phanos>
but then immediatly I stated havving issues on the I2C bus and I had to reboot the BBB to get it back online
<zmatt>
any chance you accidently configured the pin as output like you did earlier? (and potentially damaged it using a drive conflict)
<Phanos>
do not think so
<Phanos>
the default is input and I did not change anything on that
<Phanos>
during testing
<zmatt>
also, just to double-check, you're powering the mcp23017 at 3.3V ? (not at 5V)
<Phanos>
I only started experiment when I notice that It was already high by default
<Phanos>
yes I am
<Phanos>
3.3v
<Phanos>
on I2C bus 1
<zmatt>
being high by default is normal for that pin
<Phanos>
so high is the default value
<zmatt>
being high when configured to pull-down and nothing attached however is _not_ normal
<Phanos>
ok I see
<Phanos>
so maybe is damaged you mean somehow?
<zmatt>
if I change it between gpio_pd and gpio_pu I can see it change between << lo and << hi
<zmatt>
in the end the internal pull doesn't matter if the pin will be driven by the mcp23017
<zmatt>
but my concern would be that this is an indication of a damaged I/O being internally shorted to the 3.3v supply
<Phanos>
ok I get the same behavior on the P9.15
<Phanos>
P9.15 16 fast rx down 7 gpio 1.16 << hi P9_15 (pinmux_P9_15_gpio_pd_pin)
<Phanos>
so this is not restricted to P9.11
<zmatt>
P9.15 is a weird one because it's connected to two processor pins
<zmatt>
I assume this means you intend to reuse the eMMC pins for other purposes... beware that the eMMC itself isn't (and can't be) disabled so it's a good idea to leave P8.20 (eMMC cmd) and/or P8.21 (eMMC clk) unused to ensure the eMMC won't think you're trying to send it a command
<zmatt>
this is really weird
<Phanos>
actually I did tried to disable to re-use the pins but then I notice that there are issues with some of the P8 pins so I abandome the idea. Then I tried to use the mcp chips to exte nd input functionality
<zmatt>
is this a newly purchased BBB ? what your paste is showing really makes no sense
<Phanos>
yes it new
<Phanos>
only a few weeks old
<zmatt>
Phanos: on my BBB in its default state, every gpio that has pull-down is "<< lo" and every gpio that has pull-up is "<< hi"
<zmatt>
the output you're getting is really abnormal
<zmatt>
and I'm honestly not sure what's going on here
<zmatt>
uhh, I've absolutely never heard of these people
<Phanos>
so you mean it might be damaged?
<Phanos>
I order it online because I could not find it anywhere local
<Phanos>
did not hear them before either
<zmatt>
can you make photos of your beaglebone, just to be sure?
<zmatt>
(top and bottom)
<Phanos>
could this be a damage or even worse a counterfeit bad copy?
<Phanos>
not right now
<zmatt>
ok
<zmatt>
I don't know
<Phanos>
I am at work and the begle is how
<Phanos>
I can sent you later
<zmatt>
I don't understand what's going on, I'm just trying to come up with theories
<Phanos>
do you have an address that I can sent you and should I open again the chat and sent it there?
<zmatt>
my irc client is always connected here... if you send it here I'll see it sooner or later
<Phanos>
ok great
<zmatt>
actually maybe I have heard of waveshare before... now I'm not sure
<Phanos>
I will do that zmatt
<zmatt>
they just seem to be a reseller anyway
<zmatt>
or not
<zmatt>
hmm
<zmatt>
I don't know
<Phanos>
maybe you can understand better when you see the photos
<Phanos>
I paid normal money for this board so if it is coutnerfeit then I got scammed
<zmatt>
let's not jump to conclusions
<Phanos>
just a note where can I buy BBB online and sent it to europe address?
<Phanos>
do you have online store or something?
<zmatt>
uhh, lots of places? I'm not even sure where we buy them
<zmatt>
note I'm not with beagleboard.org, I'm just a beaglebone user
<Phanos>
ok no problem
<Phanos>
I see thanks :)
<Phanos>
also another question please
<Phanos>
how do I set the correct internal pull-down resistor on boot? Should I create a script that runs on boot time or is there a better way?
<zmatt>
normally there's no need to, why do you think there is?
<zmatt>
like I said earlier, the internal pull is pretty weak and mostly just intended to keep unconnected pins from floating
<zmatt>
if something is connected to the pin that drives it then that will override the weak internal pull
<Phanos>
ok I see. so if I connect the interrupt of mcp chip on a pin should not matter correct?
<zmatt>
correct
<Phanos>
yes that is what I believed as well but then I got the issues with the I2C bus and I thought maybe something else what happening here
<Phanos>
thanks a lot smatt
<Phanos>
zmatt
<Phanos>
will sent you the photos later here
<zmatt>
note that if the interrupt pin is configured as open-drain you should use external pull-up
<Phanos>
yes I know
<Phanos>
do you believe that I should enable it as such and then use external resistors?
<Phanos>
maybe this will be better?
<zmatt>
I see no reason to do that
<Phanos>
ok maybe is better to keep things simple them
<Phanos>
you are right
<zmatt>
also, why are you using an I/O expander in the first place?
<zmatt>
while most of the BBB I/O is unused
<Phanos>
because I am trying to connect and lot of inputs and outputs
<Phanos>
I have a extenral system that requires arroun 30 inputs and 30 outputs
<Phanos>
it is a small project I am trying to do :)
<zmatt>
that's a lot of i/o
<Phanos>
for home automation
<Phanos>
yes it is and interrups will come in handy
<zmatt>
the BBB supports interrupts on all gpio
<Phanos>
so I do not poll and date all the time
<zmatt>
polling is not required
<Phanos>
yes this the idea is to connect 8 interrupt pins on the BBB from the mcp chips so I know when a pin on a side of an mcp ship is change so then I read that side
<Phanos>
most of the time there is no change on the input pins on the mcp chips so a constant polling on the mcp chips it will be an overkill
<Phanos>
:)
<zmatt>
wtf, I just noticed your show-pins output is showing some of the unused eMMC pins as being low
<Phanos>
what do you mean?
<zmatt>
those have external pull-ups
<Phanos>
that there is some issues on the those pins?
<Phanos>
externally
<Phanos>
?
<zmatt>
also, it's pretty bad that they have pull-down configured in the default cape-universal config when eMMC is disabled, I'll file a bug report for that
<Phanos>
wait I forgot to mention
<Phanos>
I do have some pins connected on the p8 side on the BBB
<Phanos>
7 pin input and 7 output
<Phanos>
sorry :(
<zmatt>
I explicitly asked you whether you had anything connected to the expansion headers
<Phanos>
yes you are right
<Phanos>
I apologized
<Phanos>
I totally forgot that since I made that change a few weeks back
<Phanos>
when I got bbb
<Phanos>
I am not sure what pins are connected though
<Phanos>
there are on the P8
<Phanos>
I will sent a picture of that as well
<zmatt>
how sure are you that nothing is connected on the P9 side? :P
<Phanos>
other than the I2C nothing
<Phanos>
even the 1-wire has nothing connected
<Phanos>
2-wires only
<Phanos>
I am sorry I only mention nothing since I know that nothing connected on the P9 side since during the testing of the interrupts and after noticing the issues on the I2c bus I disconnected the interrupts
<Phanos>
and nothing else was connected there.
<Phanos>
But I will double check this when I get home
<Phanos>
now sure I missed anything
<Phanos>
make sure I did ot missed anythig
<zmatt>
anyway, I'm afk for now
<Phanos>
ok thanks a lot for the help
xet7 has quit [Ping timeout: 265 seconds]
Phanos has quit [Quit: Client closed]
xet7 has joined #beagle
Guest36 has joined #beagle
Guest36 has quit [Client Quit]
rob_w has quit [Remote host closed the connection]
buzzmarshall has joined #beagle
m-atoms has joined #beagle
M-blaise has joined #beagle
vagrantc has joined #beagle
florian has quit [Quit: Ex-Chat]
zjason has quit [Ping timeout: 265 seconds]
Shadyman has joined #beagle
mattb0ne has joined #beagle
set_ has quit [Ping timeout: 272 seconds]
mattb0ne has quit [Ping timeout: 252 seconds]
mattb0ne has joined #beagle
tbr has quit [Ping timeout: 256 seconds]
tbr has joined #beagle
akaWolf has quit [Ping timeout: 252 seconds]
akaWolf has joined #beagle
<mattb0ne>
can a try and catch block work with asyncio
<mattb0ne>
I am having a problem of my program hanging but never throwing an error