SteveMarple has quit [Read error: Connection reset by peer]
SteveMarple has joined #beagle
SteveMarple has quit [Client Quit]
xet7 has quit [Ping timeout: 260 seconds]
buzzm has joined #beagle
buzzmarshall has quit [Read error: Connection reset by peer]
buzzm has quit [Quit: Konversation terminated!]
<set_>
my thingy came in today. Time to test the ServoCape at full functionality!
<set_>
So far, so good.
<set_>
No sparks, sort of, and no smoke!
<set_>
So, this DC-DC converter may just be the ticket out of "hello!"
<set_>
When updating kernel 4.19.x, would I have to purge other kernels from apt somehow?
<set_>
I see bbb.io-kernel is updating both 4.19.x and 5.10.x.
<set_>
Anyway, I saw on the forums from rcn-ee that one would use purge. Is it okay to keep the kernels both at the same time or is that a conflict?
<set_>
B/c now, apt controls the installs of the kernels.
<set_>
I just got chewed out by some salesman from Battery Tender.
<set_>
I think he hates me using his battery charger for 12v batteries for drones and bots.
<set_>
All CAPS is usually a sign of misunderstandings.
brook has joined #beagle
<set_>
ServoCape!
<set_>
@zmatt: I am learning about JSON notation in python3. It is totally neat for adding in specifics! I wonder when I will scare myself again!
starblue has quit [Ping timeout: 260 seconds]
starblue has joined #beagle
<set_>
I found pep-0008, @zmatt. Phew.
<set_>
Dang it. Sorry.
<set_>
I forget. No python3 jargon in here.
nick6 has joined #beagle
johanhenselmans has quit [Ping timeout: 248 seconds]
johanhenselmans has joined #beagle
<nick6>
I'm trying to use pru setup from a cloud9 example blinkExternalLed.pru0.c and am getting an error: 'writing "gpio" to "/sys/devices/platform/ocp/ocp:P9_14_pinmux/state"
<nick6>
How can I configure my board to make the P9_14_pinmux directory?
brook has quit [Remote host closed the connection]
nick46 has joined #beagle
nick46 has quit [Client Quit]
ikarso has joined #beagle
nick6 has quit [Quit: Client closed]
johanhenselmans_ has joined #beagle
johanhenselmans has quit [Ping timeout: 260 seconds]
johanhenselmans_ is now known as johanhenselmans
Shadyman has quit [Quit: Leaving.]
otisolsen70 has joined #beagle
otisolsen70 has quit [Remote host closed the connection]
otisolsen70 has joined #beagle
rob_w has joined #beagle
otisolsen70 has quit [Read error: Connection reset by peer]
otisolsen70 has joined #beagle
ft has quit [Quit: leaving]
jfsimon1981 has joined #beagle
starblue has quit [Ping timeout: 260 seconds]
starblue has joined #beagle
<set_>
BBBlue will fly! Trust it.
<set_>
It is driving me sensorless.
uart0_person has joined #beagle
<uart0_person>
Hello
<set_>
olay!
<uart0_person>
Is there a way I can access my beaglebone as a folder from windows?
<set_>
Yes.
<set_>
online.
<set_>
Do you have an Ethernet cable or USB shared network?
<uart0_person>
I use a usb to share internet from my pc to a pocket beagle
<set_>
Okay!
<set_>
We are in business.
<set_>
Can you install files and post files via git or however?
<uart0_person>
I did try to use samba to do this since I have done with a pi before, but I ended up not being able to do ssh. Since I don't much, I just reflashed the sd
<uart0_person>
Since I don't know much*
<uart0_person>
Yeah, I can download git
<set_>
You do not need it.
<set_>
I was just making sure you could in case I did not understand that you have Internet access on your Pocket beagle.
<uart0_person>
I have, I already download some repositories from git
<uart0_person>
downloaded*
<set_>
Okay. Good.
<set_>
That means, you can access files online. That is a start.
<set_>
I am turning on my beagle now.
<set_>
I will do it and brb. This way, I can make sense out of what I am saying.
<set_>
Go to 192.168.7.2
<set_>
That should do it!
Guest2 has joined #beagle
<Guest2>
hello
<uart0_person>
but doesn't that just opens the cloud9?
<set_>
That is odd. Mine does not even open Cloud9. What image do you use and what kernel?
<set_>
uart0_person: I have a book somewhere. I will have to research this idea more.
<uart0_person>
I used this one from the beaglebone website
<zmatt>
uart0_person: if you're looking for the latest testing images, rcn posts them on the forum together with notes: https://forum.beagleboard.org/tag/latest-images ... the ARM64 one is for the bbai64 obviously, the other two threads have the latest bullseye and buster images for am335x and am572x
<uart0_person>
oh thx
<zmatt>
uart0_person: btw to answer your earlier question, you can just transfer files via ssh/sftp... there are plenty of clients for that
<uart0_person82>
another question, which one of the images should I use for pocketbeagle?
<uart0_person82>
i don't know the difference between buster and bullseye
<zmatt>
same as for beaglebone black
<zmatt>
buster is an older version of debian, this is still used for the official released images (https://beagleboard.org/latest-images) except for the BBAI64
<zmatt>
the bullseye images are more modern and uptodate but will have a variety of backwards-incompatible changes which also means external documentation you may find on how to do things may not always apply anymore without changes
<zmatt>
of course any testing image will not (yet) be as well-tested and widely used as the officially released images
<uart0_person82>
so the last well tested image for pocket was from two years ago?
<zmatt>
yeah the latest images are getting a bit dated... I don't know what exactly is keeping the current testing images from becoming the official next release
<zmatt>
though the fact that the bbai64 uses bullseye images suggests to me the bullseye images might be nearing readiness
<zmatt>
(for other devices as well)
brook has quit [Remote host closed the connection]
brook has joined #beagle
florian has quit [Quit: Ex-Chat]
rob_w has quit [Remote host closed the connection]
uart0_person82 has quit [Quit: Client closed]
ikarso has quit [Quit: Connection closed for inactivity]
Guest62 has joined #beagle
<Guest62>
Is there any image for the BB AI-64 which includes the AI tools but no desktop environment (no graphical interface)?
brook has quit [Ping timeout: 252 seconds]
brook has joined #beagle
<zmatt>
Guest62: hmm, curiously it doesn't look like it... you could maybe take a minimal image and install the edgeai packages?
<zmatt>
rcn-ee: any reason there's no iot/iot-edgeai images for the ai64 ?
shoragan_ has joined #beagle
<Guest62>
Thank you very much zmatt. Do you know if the edgeai package are `ti-edgeai-8.2-base`, `ti-vision-apps-8.2`, and `ti-vision-apps-eaik-firmware-8.2`? I was trying to find documentation about how to install them in the https://docs.beagle.cc/latest/boards/beaglebone/ai-64/edge_ai_apps/index.html, but the only place such packages are mentioned is in
<Guest62>
the "Update software on BeagleBone AI-64" page...
<zmatt>
unfortunately I don't really know anything about the edgeai software, I've never done anything with ai and I don't own a bbai64
<Guest62>
Thank you anyway zmatt. It is good advice. I will try and see how it goes
<zmatt>
if I personally wanted to know what exactly the differences are between the edgeai and non-edgeai images, I'd probably just download both, extract a list of installed packages for both images, and compare those
<Guest62>
Oh well, my grep-foo is not very good then '=D
<Guest62>
Ok, so just installing the packages and enabling a systemctl package
<Guest62>
sounds good
Guest6212 has joined #beagle
<Guest62>
Thank you for the help zmatt
Guest6212 has quit [Client Quit]
akaWolf has quit [Ping timeout: 252 seconds]
vagrantc has joined #beagle
Guest62 has quit [Quit: Client closed]
brook has quit [Remote host closed the connection]
uart0_person has joined #beagle
<uart0_person>
Hello,
<uart0_person>
So I installed a newer image, but the steps I did before to pass internet from my pc to the board via usb don't work anymore
<zmatt>
uart0_person: networking is one of the things that changed significantly between buster and bullseye... is there a particular reason you're using a bullseye image anyway?
<uart0_person>
Just assumed it would be better to use the latest image
<zmatt>
"better" is a rather vague term.... better for what? better for who?
<zmatt>
*I* would rather use a bullseye system than a buster system, but then I'm quite familiar and comfortable with setting up a debian system in whatever way I want
akaWolf has joined #beagle
<zmatt>
what was the procedure you followed for buster images?
brook has joined #beagle
<zmatt>
uart0_person: it may suffice to add Gateway=192.168.7.1 to the [Network] section of /etc/systemd/network/usb0.network
<zmatt>
(or Gateway=192.168.6.1 to /etc/systemd/network/usb1.network if you're using the CDC-NCM interface rather than the RNDIS interface)
akaWolf has quit [Ping timeout: 260 seconds]
<zmatt>
and then sudo systemctl restart systemd-networkd
akaWolf has joined #beagle
<uart0_person>
In my windows machine, I would find my connection to wifi and set it to share with the name of the usb connection to the board. Then, I would configure the usb connection ip address since windows give a random one and not the right one. After this I create two files, one at root folder, another at /etc/init.d, give the permission and give a
<uart0_person>
symbolic link
<zmatt>
wait you mean configure the ip address on the beaglebone side? why not configure a fixed ip range on the windows side?
<zmatt>
or is that what you meant?
<zmatt>
I don't understand why you'd need a service on the beaglebone for this, networking is handled by a network manager - connman on buster images, systemd-networkd on bullseye images
uart0_person has quit [Quit: Client closed]
<zmatt>
you could also just configure the beaglebone to act as dhcp client, which is arguably the better solution that doesn't require any ip configuration anywhere
<zmatt>
the downside of that config is that you won't know the ip of the beaglebone since it'll be assigned by Windows
<zmatt>
but you can hopefully find it by hostname... at least that would work on mac or linux
<uart0_person>
So I add gateway to network
akaWolf has joined #beagle
<uart0_person>
or erase everyhting to the thing you sent me
<zmatt>
the "add gateway to network" solution is for when you want to use fixed IPs, 192.168.7.2 for the beaglebone and 192.168.7.1 for windows
<zmatt>
you'd need to configure that ip manually on the windows side if you use internet sharing
<zmatt>
I'm eating food right now but I'll look at your link after that
<zmatt>
the benefit of the "add gateway" solution is also that it at least doesn't break the normal networking setup, i.e. you can still just disable internet sharing and configure the interface automatically on the windows side and be able to reach the beaglebone
<zmatt>
with the solution of configuring the beaglebone to use dhcp, it _needs_ a dhcp server on the windows side (as provided by internet sharing) to have ipv4 connectivity to the beaglebone (though ipv6 should work regardless) ... of course you should be able to reach it via IPv6 regardless)
<zmatt>
ehh, that sentence failed near the end
<zmatt>
you can of course also use the usb serial interface exposed by the beaglebone to figure out what's going on with networking on its side
uart0_person has quit [Ping timeout: 260 seconds]
<zmatt>
and whenver I said "beaglebone" I meant "pocketbeagle" in your case of course, sorry
<zmatt>
uart0_person: adding the Gateway=192.168.7.1 line will make the network manager add a route similar to what "route add default gw 192.168.7.1" does
<uart0_person>
ok, let me add it and then reboot the board
akaWolf has quit [Ping timeout: 246 seconds]
<zmatt>
(note btw that the "route" command is old and deprecated, its modern replacement would be "ip route add default via 192.168.7.1", but either way you *generally* shouldn't mess with routes like that since they're the responsibility of your network manager)
<zmatt>
you don't really need to reboot, it suffices to "sudo systemctl restart systemd-networkd"
<uart0_person>
Yeah, didn't work
<zmatt>
did you do the configuration on the windows side? what your guide suggests probably still works
akaWolf has joined #beagle
<uart0_person>
yeah, I did all the steps
<zmatt>
"didn't work" in what sense? are you no longer able to reach the pocketbeagle?
<uart0_person>
I can reach the pocket, but it can't connect to internet
<uart0_person>
pinging 8.8.8.8 yields no results
<zmatt>
can you pastebin the output of "ip route" ?
<zmatt>
well it has a default gateway via usb networking, so any problems must be on the Windows side
<zmatt>
this routing table looks correct to me
<zmatt>
btw, just in case you've previously messed with /etc/resolv.conf ... that file shouldn't be touched, it should be a symlink to /run/systemd/resolve/resolv.conf (https://pastebin.com/2UY9g2Q4)
<uart0_person>
yeah, I did alter that file
<zmatt>
uart0_person: I'm honestly not sure why the guide you linked chose to change the interface back to "Obtain an IP address automatically" after enabling internet sharing, it probably makes more sense to just statically configure it to 192.168.7.1
<uart0_person>
ok, I will do that
<zmatt>
and just in case you can fix /etc/resolv.conf with: sudo ln -sfT /run/systemd/resolve/resolv.conf /etc/resolv.conf
<zmatt>
though that doesn't affect your ability to ping an IP
<uart0_person>
changed back the file, and set the static ip, but no internet yet
<uart0_person>
think will just reflash back to the old version
<uart0_person>
since the internet is not working
<zmatt>
I honestly don't see how the image version could be causing this, the routing table you have now should be the same as you would have had before
<zmatt>
if anything, it should work more reliably on bullseye since you don't have to worry about connman (which was used on buster) messing with your routes (which connman really likes to do)
<uart0_person>
strange
<uart0_person>
the only thing that is slightly different
<uart0_person>
when I had the other image version
<uart0_person>
the name of the ethernet connection was just like the guide
<uart0_person>
ethernet 2
<uart0_person>
but with new version is ethernet 3
<uart0_person>
but that shouldn't be causing this
<zmatt>
probably the mac address of the usb network interface changed, so windows doesn't know that it's the same device as before
<zmatt>
but yeah that is of no relevance, as long as you now share your internet with ethernet 3 instead of with ethernet 2
<uart0_person>
which I did
<uart0_person>
so it should be working
<zmatt>
it does feel more likely the problem is still on the Windows side rather than the pocketbeagle side, since the config on the pocketbeagle side looks correct to me
<uart0_person>
in the other version went to cloud9
<uart0_person>
now it says it can't connect
<zmatt>
cloud9 has been dropped since the project is dead and unmaintained
<uart0_person>
I will return the version and hope it works
<zmatt>
it is possible to run vscode on the beaglebone as a substitute, which (as the forum page of the testing images explains) is instaleld by default but not enabled by default
<uart0_person>
when I was coding with raspberry pi, I used samba and could open the rpi as a folder in windows, then I used my ide to code. I wanted to do something like this. Set said their version could do that so I updated
<uart0_person>
but now that internet is not working i think it's better to return the version and find another way
<zmatt>
you could use samba for file sharing yeah, or like I mentioned earlier you could use ssh to mount the filesystem
<zmatt>
both of these should work equally well regardless of whether you're using buster or bullseye
<zmatt>
samba is more hassle to setup, ssh requires no setup on the beaglebone side
<uart0_person>
I tried with samba
<uart0_person>
but I couldn't reach the pocket via usb anymore after I tried
<zmatt>
lol, how'd you manage that... samba shouldn't have any way of affecting your ability to ssh to the beaglebone
<uart0_person>
I don't know haha
<uart0_person>
I was surprised too
<uart0_person>
I was trying to repeat the steps I did for rpi but for beagle, and it ended up like that
<zmatt>
I still don't understand why internet sharing isn't working for you right now, but with Windows as a host I also have no clue how to diagnose it
akaWolf has quit [Ping timeout: 248 seconds]
akaWolf has joined #beagle
uart0_person has quit [Ping timeout: 260 seconds]
uart0_person has joined #beagle
akaWolf has quit [Ping timeout: 252 seconds]
akaWolf has joined #beagle
<uart0_person>
yeah, now the internet is not working even in the old image
<zmatt>
lol
uart0_person61 has joined #beagle
<zmatt>
like I said, the config looked fine on the pocketbeagle side
<uart0_person61>
I also did everything on windows side, like the other times, didn't change a step
uart0_person61 has quit [Ping timeout: 260 seconds]
uart0_person has joined #beagle
brook has quit [Ping timeout: 260 seconds]
<uart0_person>
whyyyy this pocketbeagle's internet doesn't work
uart0_person88 has quit [Ping timeout: 260 seconds]
<uart0_person>
now it works
uart0_person has quit [Quit: Client closed]
uart0_person has joined #beagle
akaWolf has quit [Ping timeout: 260 seconds]
samnob has joined #beagle
akaWolf has joined #beagle
<uart0_person>
I just disabled internet sharing then redid the process
<uart0_person>
and then it worked
akaWolf has quit [Ping timeout: 252 seconds]
ft has joined #beagle
akaWolf has joined #beagle
brook has joined #beagle
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #beagle
brook_ has quit [Ping timeout: 248 seconds]
brook has quit [Ping timeout: 252 seconds]
ft has quit [Remote host closed the connection]
ft has joined #beagle
uart0_person has quit [Ping timeout: 260 seconds]
otisolsen70 has quit [Quit: Leaving]
brook has joined #beagle
akaWolf has quit [Read error: Connection reset by peer]
akaWolf has joined #beagle
akaWolf has quit [Ping timeout: 246 seconds]
akaWolf has joined #beagle
brook_ has joined #beagle
brook has quit [Ping timeout: 260 seconds]
brook_ has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook_ has joined #beagle
nick38 has joined #beagle
nick38 has quit [Quit: Client closed]
nick12310 has joined #beagle
<nick12310>
Hi, how can I set up pins to function as bidirectional input/output? I want them to take in inputs on certain cycles, and then reconfigure it to output digital values on other cycles
<zmatt>
nick12310: uhh, that doesn't require any "set up", you can change the direction of a gpio as easily as you can read (as input) or change (as output) its value
<zmatt>
unless you're talking about PRU (in which case you should definitely have clarified that in your question)
<nick12310>
Yes, talking about the PRU. Right now i'm working with blinkExternalLED.pru0.c , one of the examples in the cloud 9. I see how it inits pins as output direction, but is there a way for input and output?
<zmatt>
unfortunately not for the pru's dedicated (low-latency) gpios
<nick12310>
can I use ocp for other gpios?
<zmatt>
if you need bidirectional GPIO from PRU, your options are to use regular GPIO (via the GPIO controllers) instead of PRU's direct GPIO, or use external logic (like a tristate buffer) to work around the limitation
<zmatt>
PRU can access everything
<zmatt>
there's a catch with changing GPIO direction from PRU though: you need to be sure that linux won't try to change the direction of any gpio on the same gpio controller, otherwise you'll end up with a race condition
samnob has quit [Quit: I'm not smart enuf to edit bouncer.conf]
samnob has joined #beagle
<zmatt>
since there's no way to atomically change the direction of a single gpio, gpio direction is controlled by reading/writing a register that controls the direction of all 32 gpios of that gpio controller (one bit per gpio)
<zmatt>
but on the bright side, I don't think linux has any reason to change the direction of a gpio on the beaglebone unless requested to by userspace, so you're in control of that
<nick12310>
That makes sense. I want the PRUs to be the only thing doing changes with the pin outputs
<nick12310>
But wait, you said PRU can't change the direction?
<zmatt>
PRU's dedicated low-latency gpio (wired into PRU registers) can't
samnob has quit [Quit: I'm not smart enuf to edit bouncer.conf]
<nick12310>
Oh ok, but if I use ocp I can change the direction
<zmatt>
normal GPIO, controlled via the four gpio controllers, can
samnob has joined #beagle
<nick12310>
Will that stop me from being able to use the physical pins that the pru is connected to, or can I use those pins in gpio mode the same?
<zmatt>
"use ocp" is a weird phrasing... ocp is just an abbreviation linux uses for the on-chip peripherals (collectively), either that or it refers to the Open Core Protocol used to interface peripherals to the interconnects, not sure
<zmatt>
nick12310: all of the digital I/O pins on the beaglebone support normal GPIO mode
nick1231026 has joined #beagle
<zmatt>
it's their default mode
nick12310 has quit [Ping timeout: 260 seconds]
<nick1231026>
Yea sorry for the ambiguity Open Core Protocol is what I mean. The example for PRU uses the Open Core Protocol (OCP) master port to toggle the GPIO pins
<zmatt>
it uses the OCP master port to interface to the L3 interconnect via which it can (directly or indirectly) reach all of the subsystems and peripherals on the AM335x
samnob has quit [Quit: I'm not smart enuf to edit bouncer.conf]
samnob has joined #beagle
<nick1231026>
So it uses that to move from pru subsystem to the GPIO pins? what exactly is the l3 interconnect
<zmatt>
(this doesn't include direction-changing since I didn't want to encourage people doing that without being aware of the dangers)
<zmatt>
nick1231026: the L3 interconnect is basically just a network that forwards read/write requests from initiators like PRU or the Cortex-A8 to various peripherals and other targets on the SoC, and their replies (write acknowledge / read data) back to the initiators
<zmatt>
(most peripherals are actually on one of several subsidiary interconnects known as the L4 interconnects)