<mattb0ne>
zmatt: I read the logs how to I make sure I have the udev rules?
brook_ has quit [Ping timeout: 252 seconds]
<set_>
mattb0ne: Stick those udev rules where they belong!
vagrantc has quit [Quit: leaving]
<set_>
Then reboot! Or one could simply give the command to restart the udev rules...
<mattb0ne>
how?
<mattb0ne>
hmmm
<mattb0ne>
might of missed a step
<mattb0ne>
but could of sworn I did it
<mattb0ne>
let me try again
<mattb0ne>
how you doing set long time no chat
<set_>
Ha. Me too. I mean...long time no chat.
<set_>
Here : /etc/udev/rules.d/
<set_>
in /etc/udev/rules.d/* are a bunch of files. One could rearrange those files or make a brand new file...
<set_>
udev is not always so easy. I know. I keep trying to master it. Blah is all...but w/ specific entries in /boot/uEnv.txt, udev rules may not be so willing to help.
<mattb0ne>
I though I moved it to the right folder
<zmatt>
mattb0ne: the gpio-symlinks.rules (or whatever the file is called) should be in /etc/udev/rules.d/
<zmatt>
mattb0ne: also, what you just linked is completely unrelated, you're just missing symlinks
<set_>
Off to review symlinks!
<set_>
ln -s sometimes works depending on many factors... For instance, what uses what and when?
<set_>
Like, for me, using ln -s _MY_File.suffix may create issues if and when another file is using it at another time.
<set_>
Bundle it all in a type. Like, the bundling of static or dynamic linking can be useful too w/ an entire whole...
<set_>
Right?
<zmatt>
what the fuck are you talking about
mattb0ne has quit [Ping timeout: 264 seconds]
<set_>
@zmatt: Calm down. It is me!
<set_>
I am talking about linking.
<set_>
and now mattb0ne took off. Sheesh.
<set_>
You guys? man.
<set_>
@zmatt: Have you made a dOnkeyCar recently?
<set_>
I am going to try. It seems there are many pitfalls to it so far w/ building. They have particular versions that are "needed".
<set_>
Anyway, up, up, otay!
<set_>
oh and one last thing...
<set_>
Stop cussing at me...sheesh.
natlemat has joined #beagle
mattb0ne has joined #beagle
brook has joined #beagle
<mattb0ne>
ok I did the pruss values and I get the same error
<mattb0ne>
now I did use the uio-pruss overlay as oppose to the overlay specified on the github
<mattb0ne>
I have uio-pruss.dtbo in my uEnv.txt
<mattb0ne>
vs the AM335X....dtbo overlay file
<mattb0ne>
I do not remeber this happening before
<natlemat>
For a simple usage a BeagleBoard pretty much works like a Pi? No hat, nothing fancy. I install Debian and it "Just Works [TM]"? (I've got zero BeagleBoard so far but eight Pi, ranging from Model 1 to Model 3B, so not new to this "kind" of stuff, but new to the BeagleBoard)
<mattb0ne>
basicalyy
<mattb0ne>
zmatt any ideas
<mattb0ne>
I am booting off a sd card if that makes any difference
natlemat has left #beagle [#beagle]
starblue has quit [Ping timeout: 246 seconds]
starblue has joined #beagle
<zmatt>
mattb0ne: I'm not sure what you're talking about... are you still referring to the missing gpio symlinks? because that has absolutely nothing to do with pru or with uio
<mattb0ne>
yeah the sym links
<mattb0ne>
the additional instructions referenced moving a file
<zmatt>
if /dev/gpio/ doesn't exist at all then you're missing the udev rule, if you do have that directory and it contains symlinks but not the ones you're expecting then it's a DT issue
<zmatt>
?
<zmatt>
what instructions?
<mattb0ne>
uio-pruss.rules
<mattb0ne>
i thought that file would fix it
<mattb0ne>
the pru is fine
<mattb0ne>
ok so my overlay is bad your saying
<mattb0ne>
which is messing up my DT
<mattb0ne>
hmmmm
<zmatt>
since you do have /dev/gpio/ now?
<zmatt>
earlier you showed show-pins output that looked okay, in the sense that it appears to have declarations for your gpios that iirc used the custom names your code was relying on
<zmatt>
the name of each symlinks reflects the name given to the gpio in DT (using gpio-of-helper)
<zmatt>
uio-pruss.rules is needed for py-uio, it has absolutely nothing to do with gpio
<mattb0ne>
I do not have /dev/gpio
<zmatt>
"03:42 <@zmatt> if /dev/gpio/ doesn't exist at all then you're missing the udev rule, if you do have that directory and it contains symlinks but not the ones you're expecting then it's a DT issue"
<mattb0ne>
why would I not have a udev rule seems like that would be automated right ?
<zmatt>
no?
<zmatt>
it's a custom udev rule I wrote for convenience
<zmatt>
which you presumably installed on your previous system(s)
<mattb0ne>
ok I have a gpio-symlinks.rules file
<zmatt>
installed in /etc/udev/rules.d/ ?
<zmatt>
since if you do (and reboot) then you should also have symlinks in /dev/gpio/
<mattb0ne>
let me reboot
<mattb0ne>
i had the file but not in the correct directory
<mattb0ne>
just moved and rebooting now
<mattb0ne>
why would the designers make you use the overlays and then make a seprearte rules file to make pins work
<zmatt>
they don't
<zmatt>
you don't need to use an overlay, you don't need to use the udev rule
<zmatt>
but the overlay lets you name and configure the gpio in DT
<mattb0ne>
I have the gpio folder now
<mattb0ne>
getting the same error
<zmatt>
and the udev rule makes it really easy to find a particular gpio by name
<mattb0ne>
so like an alias file
<zmatt>
like, that's literally all the gpio-symlinks.rules does... it creates symlinks to make the gpios easy to find instead of having to know which expansion header pin is used and how that maps to gpio numbers and how to locate gpios by number
<mattb0ne>
so the error is complaining about a pin that I try and set with an overlay
<zmatt>
with the setup you used you setup your gpios in DT, and userspace doesn't need to know or care what pin or gpio number it maps to since it just accesses it by name via the symlink created by the udev rule
<zmatt>
mattb0ne: well yes it's looking for a gpio named "stepper_dir"
<mattb0ne>
so I have other things in there but not that one
<mattb0ne>
which I guess would come from my overlay
<mattb0ne>
but I see it in show-pins
<mattb0ne>
which is confusing
<zmatt>
it still shows as "stepper_dir" in show-pins, like line 11 of your earlier paste https://pastebin.com/M5fQQTSU ?
<mattb0ne>
no I lied
<mattb0ne>
i messed something up on uEnv.txt
<mattb0ne>
let me reboot
<mattb0ne>
no we are goo
<mattb0ne>
good
<mattb0ne>
I messed up my overlay after moving that rules file which was hanging me up
<mattb0ne>
now we are back on the road
<zmatt>
maybe put a comment in your code "if /dev/gpio/ doesn't exist, make sure you have /etc/udev/rules.d/gpio-symlinks.rules installed"
<zmatt>
for the next time :P
<zmatt>
or better yet have your program check whether /dev/gpio/ exists at startup and give a more useful error message if it doesn't
<mattb0ne>
good idea!
<mattb0ne>
I need to get more aquainted with try and catch
<zmatt>
or leave a README for future self on how to get your program working on a fresh beaglebone
<mattb0ne>
even better idea
<mattb0ne>
also I wanted to ask you about learning a system chip
<mattb0ne>
how much of your beagle knowledge transfer to another board
<mattb0ne>
I remember you saying the black and AI are totally different
<zmatt>
I mean, depends on what knowledge and depends on how closely related the SoC is
<zmatt>
some knowledge is generic to linux, some is specific to a specific SoC, some may be SoC-independent but specific to the way things are setup beagleboard.org images
<mattb0ne>
you use the beagle in your products you develop in your day job that is why you know it so well?
<mattb0ne>
or are you just fond of the porject
<zmatt>
we use the beaglebone yes
Shadyman has joined #beagle
ft has quit [Ping timeout: 248 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
brook has quit [Remote host closed the connection]
mattb0ne has quit [Ping timeout: 252 seconds]
mattb0ne has joined #beagle
brook has joined #beagle
brook has quit [Ping timeout: 268 seconds]
mattb0ne has quit [Remote host closed the connection]
mattb0ne has joined #beagle
mattb0ne has quit [Remote host closed the connection]
brook has joined #beagle
ikarso has joined #beagle
vagrantc has joined #beagle
vagrantc has quit [Quit: leaving]
rob_w has joined #beagle
Guest99 has joined #beagle
ft has joined #beagle
ft has quit [Quit: leaving]
florian has joined #beagle
Shadyman has quit [Remote host closed the connection]
Guest30 has joined #beagle
Guest30 has quit [Quit: Client closed]
starblue has quit [Ping timeout: 248 seconds]
starblue has joined #beagle
Stat_headcrabed has joined #beagle
Stat_headcrabed has quit [Client Quit]
zjason`` has joined #beagle
xet7 has joined #beagle
zjason` has quit [*.net *.split]
agraf has quit [*.net *.split]
danny has quit [*.net *.split]
zmatt has quit [*.net *.split]
kveremitz has quit [*.net *.split]
agraf has joined #beagle
zmatt has joined #beagle
danny has joined #beagle
kveremitz has joined #beagle
buckket has quit [Remote host closed the connection]
buckket has joined #beagle
Guest99 has quit [Quit: Client closed]
brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
rob_w has quit [Remote host closed the connection]
xet7 has quit [Quit: Leaving]
Stat_headcrabed has joined #beagle
Stat_headcrabed has quit [Client Quit]
brook has quit [Remote host closed the connection]
xet7 has joined #beagle
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Ping timeout: 268 seconds]
ikarso has quit [Quit: Connection closed for inactivity]
brook has joined #beagle
vagrantc has joined #beagle
florian has quit [Quit: Ex-Chat]
brook has quit [Remote host closed the connection]
brook has joined #beagle
ft has joined #beagle
vagrantc has quit [Quit: leaving]
djinni has quit [Quit: Leaving]
djinni has joined #beagle
otisolsen70 has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook_ has joined #beagle
brook_ has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook_ has joined #beagle
brook_ has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook_ has joined #beagle
brook_ has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook_ has joined #beagle
brook_ has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook_ has joined #beagle
brook_ has quit [Read error: Connection reset by peer]
brook has joined #beagle
ikarso has joined #beagle
otisolsen70 has quit [Quit: Leaving]
brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]