Guest795 has joined #beagle
vagrantc has quit [Quit: leaving]
<Guest795> Hey, does anyone know the command to install an older version of robotics cape? "sudo apt-get install librobotcontrol='version'"? I've tried =V1.0.3, =1.0.3, but nothings showing up
Shadyman has joined #beagle
<rcn-ee> @Guest795, the repo doesn't support old versions..
<Guest795> @rcn-ee oof, ok ty : )
Guest93 has joined #beagle
Guest93 has quit [Client Quit]
GenTooMan has quit [Ping timeout: 250 seconds]
<set_> GenTooMan: !
<set_> I have sent my AI back to retrograde. no!
<set_> otay, reflashing did it. Phew.
<set_> Excitement in computing is hard on the brain and the machine.
<set_> I thought I was at the edge over here. The tensorflow libs. from TI have already been done and over a year back. Boo!
<set_> Anyway, I am going to try them out.
GenTooMan has joined #beagle
ikarso has joined #beagle
mattb0ne has quit [Ping timeout: 250 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
Guest795 has quit [Quit: Client closed]
LetoThe2nd has joined #beagle
florian has joined #beagle
giort has joined #beagle
giort has quit [Client Quit]
set_ has quit [Quit: I thought I saw a puddy-cat...]
Shadyman has quit [Remote host closed the connection]
set_ has joined #beagle
<set_> Updates...I am getting closer to making tensorflow a reality on the AI, old news or new news, that may be worth a write up.
<set_> 8% on the tf.lite build now!
<set_> I built it w/ bazel on the WSL2 Debian too but I am not sure about it so far.
<set_> WHy would the board, the BBAI, fault at a connection disconnected during compiling?
<set_> Why will you not allow me to build the tensorflow lib?
<set_> Argh.
ikarso has quit [Quit: Connection closed for inactivity]
<set_> brb
set_ has quit [Quit: I thought I saw a puddy-cat...]
set_ has joined #beagle
<set_> argh...stuck. Stuck at 8%.
<set_> Network Error: Software Caused the Abort <<< This is what happened.
<set_> bricked it. Hallo-hoola
<set_> bone kernels for the AI say, "I quit." But...I am going to reestablish a tensorflow lite before I die (maybe). There is another storm on the way.
set_ has quit [Ping timeout: 252 seconds]
<jduchniewicz> I am pretty sure people have been using TFlite on BBAI when searching around for my proposal
<jduchniewicz> as an alternative to TIDL
<jduchniewicz> and that is what jkridner also told me when I was preparing the proposal
ikarso has joined #beagle
kveremitz has quit [Ping timeout: 240 seconds]
akaWolf has quit [Ping timeout: 244 seconds]
calculus has quit [Ping timeout: 244 seconds]
mattb0ne has joined #beagle
calculus has joined #beagle
ds2 has quit [Ping timeout: 250 seconds]
ds2 has joined #beagle
akaWolf has joined #beagle
linkliu60 has joined #beagle
florian has quit [Quit: Ex-Chat]
<vd> zmatt hi -- in your spreadsheet, is there a way to figure out the global userspace gpio number? e.g. gpio23 is pin 9 (P8.13)
kveremitz has joined #beagle
<zmatt> my spreadsheet lists gpios are x.yy where x is the gpio controller (0-3) and yy is the gpio line of that controller (0-31)
SymbioticFemale has joined #beagle
<vd> zmatt yes indeed. A last thing that is hard to figure out and where your spreadsheet might actually help, is the mapping to the linux gpio number. e.g. gpio31 will be indeed 0.31, but gpio34 will be 1.02
<vd> It might be a nice addition to the document
<vd> otherwise in order to figure out this number, you must deduce it from the /sys/class/gpio/gpiochip*/{base,ngpio} attributes
LetoThe2nd has quit [Quit: Connection closed for inactivity]
<vd> zmatt I'm currently using this (because gpio0,1,2 have 32 GPIOs each): `gpio () { echo $(($1 / 32)).$(($1 % 32)); }` to figure out global gpio -> pin number
<vd> (well GPIO number then expansion pin number)
starblue has joined #beagle
<vd> zmatt for the rtc power cycle fix, a barebox guy is asking me why it has to go over the RTC, saying "you have an internal peripheral and an external chip. you can check the schematics, you likely have a signal running between them that the alarm would toggle". Do we need the RTC to toggle the alarm?
<vd> in order word, is this signal a pinmux that we could change in the bootloader to use it as a GPIO?
<vd> in other words*
tiger_xyz has joined #beagle
<vd> (so the bootloader use the signal as gpio (no rtc) but linux configures it for the rtc.)
lucascastro has quit [Ping timeout: 245 seconds]
<tiger_xyz> Hi Good Afternoon, We found some weird problems with Bluetooth. And I checked Bluetooth TI chip firmware loaded in the BBBw: 70311 Feb 27 2019 TIInit_11.8.32.bts, but from TI website, I downloaded ver11.8.32: 75166 Sep 1 2021 TIInit_11.8.32.bts
<rcn-ee> tiger_xyz, where is this firmware hosted?
<tiger_xyz> Don't know why the same version of firmware has different size
<tiger_xyz> The firmware is under /lib/firmware/ti-connectivity folder. I am not sure it is actually used in the BBBw.
<rcn-ee> oh i know which one is on the BBBw, we got it 5 years ago:
<rcn-ee> i'm wondering ti did something..
<tiger_xyz> But from TI web site, it seems to me that file is needed.
<rcn-ee> link?
<tiger_xyz> Here is the link:
<tiger_xyz> File sizes are 70311 bytes ( on BBBw ) and 75166 Bytes downloaded. Wondering why it uses the same version for two different firmware files (with different sizes)
Guest44 has joined #beagle
<Guest44> If I run fdisk against /dev/mmcblk1, it shows just one partition, which would be device mmcblk1p1. But under /dev/, I also see mmcblk1boot0, mmcblk1boot1, and mmcblk1rpmb. What are those? Why don't they show up under fdisk?
<rcn-ee> tiger_xyz, working on it: 11.8.32 = file name, nothing to do with version...
<rcn-ee> Guest44, eMMC's boot0 and boot1 , and Replay Protected Memory Block
<rcn-ee> tiger_xyz, turns out TI has been updating the firmware to fix bugs, in the last few years no one noticed..
<Guest44> rcn-ee, why don't they show up under fdisk?
<tiger_xyz> So we should use their latest firmware, right?
<rcn-ee> Guest44, fdisk ignore them, they are special memory blocks..
<rcn-ee> tiger_xyz, yeah working on it..
<tiger_xyz> just copy into /lib/firmware and overwrite the file?
<rcn-ee> yeah pretty much..
<Guest44> rcn-ee, so if I want to repartition mmcblk1, I can just ignore those other device files?
<tiger_xyz> Do we need .ili and .xml files?
<rcn-ee> no...
<tiger_xyz> Also there are two bin files, I guess the other one is for BT4.2 version, and don't need to copy into /lib/firmware folder, right?
<rcn-ee> Guest44, AM335x doesn't use that section to boot, your free to stick what ever you want into them.. think of them as a free 2x1Mb usb drive..
<rcn-ee> tiger_xyz, for normal usage, only the *.bts is needed, the PDF explains what the other are for..
kveremitz has quit [Ping timeout: 244 seconds]
<tiger_xyz> Ok, thank you
<tiger_xyz> In the PDF, the service pack is for wl18xx 2.2 2.1, I guess BBBw wl18xx is one of them?
<rcn-ee> tiger_xyz, "WL1835MOD"... that's us..
<tiger_xyz> thanks
<rcn-ee> no thank you for point out our firmware was 6 years out date. ;)
<rcn-ee> Some Enginner said to use "xyz" 6 years ago and we never looked at it again..
lucascastro has joined #beagle
lucascastro has quit [Remote host closed the connection]
<tiger_xyz> We found occasionally our ble scan program stops receiving data from ble driver, it cannot event be fixed with systemctl restart bluetooth. Currently it only fixes after a BBBw reboot. We hope this new firmware resolves our issue.
<rcn-ee> that was one of the bugs...
<rcn-ee> tiger_xyz, ; sudo apt update ; sudo apt upgrade ; sudo reboot ;)
<tiger_xyz> Ok, thank you again
kveremitz has joined #beagle
Guest44 has quit [Quit: Client closed]
mattb0ne has quit [Ping timeout: 252 seconds]
mattb0ne has joined #beagle
tiger_xyz has quit [Quit: Client closed]
SymbioticFemale has quit [Ping timeout: 276 seconds]
<vd> with gpio-hog, output-low or output-high is the equivalent of respectively writing 0 or 1 into /sys/class/gpio/gpioX/value?
<rcn-ee> vd, (and direction = out)... gpio-hog get's set before driver 'init'..
<vd> I was confused by the usage of output-low with GPIO_ACTIVE_LOW
<vd> but one should really read output-low as echo out ... echo 0
<rcn-ee> vd, well ouput-low means two things... Pin Direction = out.. and State = 0...
<vd> yes
<rcn-ee> yeah what you said.. (irc cross talk)
<vd> what's the purpose of a gpio-hog set with input property? will it still be accessible via /sys/class/gpio... ?
<rcn-ee> typically, gpio-hog = i screwed up my pcb design, and this pin needs to be set...
<vd> ha ha
<rcn-ee> You See this on the BeagleBone Green Wireless in two places.. One is a screw up, the other is the voltge shifter rail..
<vd> rcn-ee it actually looks like it, I'm trying to get rid of an old init script which set active_low, echo out / echo 1 on ACTIVE_LOW pins...
<rcn-ee> i've never used the 'input' option for gpio-hog, maybe useful for a weird state..
<rcn-ee> vd, if it's something a wire would fix externally on the board,use gpio-hog..
<rcn-ee> careful, thou... This is a small 'blib' between u-boot and kernel on that pin, but gpio-hog minimizes it's length..
<rcn-ee> We get away with that on the BBGW, as the Wireless enable isn't even on yet, so the gpio-hog blib doesn't matter..
<rcn-ee> vd, do you ever need to read or change the state later?
<rcn-ee> the 'gpio-led' has initial condition options..
lucascastro has joined #beagle
<rcn-ee> 1: gpio-hog quickest, 2: gpio-led has initial states and changeble, 3; then classic /syc/class/gpio...
russ has quit [Ping timeout: 252 seconds]
<vd> rcn-ee hum actually we might change the state later, it's mainly for USB_EN# pins
<vd> and an input for USB_OC#
<rcn-ee> Yeah, i'd then use gpio-led, for USB_EN..
<vd> the hogs seemed safe (to lock these non-generic gpios) but I'm trying without them, as you said it's define them only as fixup for bad design. But it the default state works, let's keep it as generic gpios.
<rcn-ee> i wish hog's where changeable..
<vd> rcn-ee so you'd hardware toggle the power on a usb interface via ... /sys/class/leds or something? This might irritates some people :D
russ has joined #beagle
<vd> GPIO_ACTIVE_HIGH/LOW is really only to tell the user what to expect when enabled, e.g. GPIO_ACTIVE_LOW means 0 is the active value, e.g. a push-button wired to the ground when pressed. Is that correct?
<rcn-ee> GPIO_ACTIVE_LOW = bodge wire to GND
Guest96 has joined #beagle
Guest96 has quit [Client Quit]
the_person48 has joined #beagle
<the_person48> hello, is it possible to put gcc/g++ 11 on the beaglebone? I am running debian 10 buster
<the_person48> it doesn't appear to be in the apt repos, although maybe I have just not added the right mirror, unsure
<the_person48> I have a beaglebone black rev C btw
<the_person48> I tried compiling it from source on the BBB but ran out of space
<the_person48> now I'm trying to figure out cross compiling but wonder if there is a simpler way/if this is possible at all
<rcn-ee> the_person48, "buster" only shipped with gcc-9... for gcc-10 or gcc-11 you need bullesye..
<rcn-ee> correction gcc-9 didn't even make buster..
<rcn-ee> the_person48, very basic bullseye images:
<the_person48> ok, so gcc-11 isn't compatible with buster?
<the_person48> I will intsall bullseye then
<rcn-ee> the_person48, no, gcc-11 didn't exist two years ago when buster was released..
<the_person48> great, ok, good to know
<the_person48> I was googling that but was having trouble finding a definitive answer
lucas_ has joined #beagle
<rcn-ee> debian can be a pain, when you have 30K packages. ;)
<the_person48> haha yeah
<the_person48> and I've also been running into space issues, do you know if the image you linked above is the bare-bones version?
<the_person48> or is it the default install?
<rcn-ee> it's pretty barebones... doesn't even flash the eMMC..
<rcn-ee> basicly i'm cleaning things up on bullseye for a fresh start..
<the_person48> cool
<the_person48> awesome
<the_person48> ok, so I'll write this to an SD card, then uncomment the eMMC flashing line
<rcn-ee> the_person48, no, that won't work..
<the_person48> then it should be a flashing SD card for bullseye?
<the_person48> how come?
lucascastro has quit [Ping timeout: 244 seconds]
<rcn-ee> "barebone's"...
<rcn-ee> i threw pretty much everything out and starting from scratch..
<the_person48> so it doesn't even have the capacity to flash the eMMC?
<rcn-ee> if you want to flash the eMMC, i'd say, boot with the microSD and then use dd on the image i linked to write directly to the eMMC...
<the_person48> ok, I can do that
<the_person48> It's been a while since I've used the dd command though
<the_person48> do I just find what the name of the SD card and the eMMC is, then use DD to copy from the former to the latter?
<rcn-ee> it'll mostly likely be /dev/mmcblk1, so sudo dd if=filename.img of=/dev/mmcblk1
<the_person48> ok I'll try that
<the_person48> thanks!
giort has joined #beagle
giort has quit [Client Quit]
buzzmarshall has joined #beagle
lucas_ has quit [Ping timeout: 240 seconds]
<the_person48> what IP address does this image have by default?
<the_person48> I booted from the SD card but am having trouble reaching it
<rcn-ee> oh, none... login over usb-serial or usb-serial-j1 header..
<the_person48> ah that would explain it
<the_person48> what does that look like?
<the_person48> sounds like it's different than ssh?
<rcn-ee> like i said, barebone's.. ;) eth0 is active, usb-serial is active.. and the J1 header on top is active..
<the_person48> haha, as promised
<the_person48> so do I use minicom to connect?
<rcn-ee> In linux, you should see a dev/ttyACM0
<the_person48> never connected over serial before
<the_person48> I do
<rcn-ee> tio /dev/ttyACM0
<the_person48> ttyACM0 and ttyACM1
<rcn-ee> <ctl - t> to get out..
<rcn-ee> i never have luck with minicom, too many options.. gtkterm or tio are simple..
<the_person48> ok trying that
<the_person48> ok I'm in
<the_person48> trying to figure out how to install ssh haha
<the_person48> having trouble finding an explanation of how to use tio, beyond initial connection
the_person48 has quit [Quit: Client closed]
<vd> rcn-ee so indeed without hogs or the init script setting a few gpios to out/low/1, I don't see the usb devices. So it looks like a good candidates for gpio-hogs :)
<rcn-ee> it's just a serial console.
the_person48 has joined #beagle
<the_person48> sorry, I lost connection there
<vd> rcn-ee also specifying only PIN_OUTPUT or PIN_INPUT in the pinmux (without _PULLUP or _PULLDOWN) works fine. Is this a better practice than trying to figure out PULLUP/PULLDOWN?
<the_person48> I am able to get into the new beaglebone image via tio -e ttyACM0, but am having trouble figuring out how to actually use this interface. I looked at the manpage of tio and googled it but all I find is how to get in, not how to actually use it
<the_person48> does anyone know how to install ssh from the tio serial interface on the beaglebone?
<rcn-ee> ssh is installed on the BeagleBone..
<rcn-ee> you just need to figure out the address.
<rcn-ee> vd, actually gpio-hog doesn't need a pinctrl setting..
<the_person48> ah, interesting
<vd> rcn-ee because most pinmux default to the GPIO mode I suppose
<the_person48> do you know how to find the IP address? still having trouble with tio. I don't see anything I type, even with local echo on, and am not sure where to find a list of commands I can use?
<rcn-ee> so when you enable gpio-hog, that 'pin' get's muxed out of "init"... so then if you set a pinmux... well it's muxed out..
<rcn-ee> the_person48, sudo ifconfig -a
<the_person48> ah, so maybe I'm not actually in after all then
<the_person48> I did:
<the_person48> tio -e ttyACM0
<the_person48> but the terminal doesn't respond to anything I type
<rcn-ee> tio /dev/ttyACM0
<the_person48> I thought I was maybe just entering the wrong commands but now I think I might not be connected
<rcn-ee> <ctrl -t > to quit and exit..
<the_person48> yeah I tried that as well
<the_person48> ctrl-t, q works to exit
<the_person48> but no other commands register as far as I can tell
<the_person48> maybe the image isn't working after all?
<rcn-ee> it works, i've been hacking on it daily for a few weeks..
<the_person48> for sure
<the_person48> any other ideas?
<the_person48> yeah, I think I am not connecting to it at all for some reason
<the_person48> dmesg | grep tty returns several ttyACM0 devices, but the list looks the same when the beaglebone is unplugged
<rcn-ee> it should disppear when you disconnect the usb cable..
<the_person48> yeah, it doesn't though
<the_person48> the steps I followed were:
<the_person48> 1) download the image you linked above:
russ has quit [Ping timeout: 252 seconds]
<the_person48> 2) unzip and install on SD card using reader and balena Etcher
<rcn-ee> and you used to write it? okay..
<the_person48> 3) boot from SD card by holding user boot button while turning beaglebone on
<the_person48> did I miss anything?
<the_person48> or should I try another image maybe?
<rcn-ee> Considering you don't have a USB-serial for J1 or using eth0, stick with the production images. ;)
<rcn-ee> and all the out of box ssh/etc works..
<the_person48> ok will do
<the_person48> thanks!
<the_person48> ah so these are all debian 10
<the_person48> I had that on there before but am trying to do 11 now so I can use g++ 11
<rcn-ee> Correct.. i'm not ready to provide a full out of box version of debian-11..
<rcn-ee> you just tried my latest..
<the_person48> ok, when I was on this forum last week I think that zmatt linked me to a debian-11 image for the beaglebone?
<the_person48> I can't find it currently
<rcn-ee> probally from the same server.. just a differnet day build..
<the_person48> at the time I didn't use it cause 10 is the latest stable one, but now I realize I need to use 11 for gcc 11
<rcn-ee> why do you need gcc-11?
<the_person48> ah, ok, I see one here
<the_person48> I'm not sure, but my team told me there are features in C++ 17 we need, that we can only get with gcc-11
<rcn-ee> that's the same one, just from yesterday..
<rcn-ee> okay...
<the_person48> oh oops
<the_person48> that's the same one
<the_person48> what's the difference between the versions that end in "gb"?
<rcn-ee> the "gb" is an image you can use with the other is a base rootfs to inspect..
<the_person48> ok got it
<the_person48> so I downloaded the right one then
<the_person48> ok, so it seems like the only option is to make this one work
<rcn-ee> 4gb = should fit on a 4gb eMMC...
<the_person48> got it, I do have 4gb eMMC
<rcn-ee> or 4GB microSD... these days it doesn't matter as much... but 10 years ago, 1GB/2GB microsd where common..
<the_person48> gotcha
<the_person48> ok, so any other ideas as to what I might be doing wrong with this one?
<the_person48> etched it to SD card, booted from SD card, but having trouble getting in
<the_person48> I'll check this out
<the_person48> also, I noticed that with this image, the beaglebone shows up as a device on my VM called "linux foundation bar gadget"
<the_person48> with the 10 image I had working earlier, it showed up as something named "...beaglebone black..."
<rcn-ee> VM... i'm out..
<the_person48> not sure if that's significant
<the_person48> I also tried connecting directly to a different ubuntu machine and experienced the same behavior
<the_person48> no VM there
<rcn-ee> So, no USB-Serial adapter to plug in J1, using usb0 for ethernet, and now vm.. talk about handcuff'ing your development..
<the_person48> ok, well this might be the problem
<the_person48> I'm currently trying to connect via a microUSB to USB cable
<the_person48> the article you linked has different cables
<the_person48> is that a problem?
<rcn-ee> that cable gives you serial console acccess..
<the_person48> ok, so if I'm using a micro-USB to USB cable, no serial possible?
<rcn-ee> over /dev/ttyACM0
<rcn-ee> but if your using a VM, good luck on that USB actually making it the linux machine..
<the_person48> I was using a VM, but then I switched to no VM to remove that factor
<the_person48> I don't understand your comment about usb0 and ethernet
<rcn-ee> i have a hate relationship with all VM's and anything uSB> ;)
<the_person48> and yeah, I don't have one of those cables, I wasn't aware they were needed
<the_person48> yeah fair
<the_person48> so is it not possible to connect over a regular microUSB to USB cable?
<the_person48> (without knowing the IP address and sshing?)
<rcn-ee> i haven't finished writing that for bullseye..
<the_person48> ok, maybe if I connect the beaglebone to a monitor and keyboard?
<rcn-ee> on the usb interface, there are two serial ports enabled and a USB0 for network, but the usb0 for networking isn nto setup yet..
<the_person48> I think I have an adapter for it's microHDMI
<the_person48> ah, so even if I have the IP, sounds like I won't be able to SSH over USB?
<rcn-ee> I'd just plug in an Ethernet cable and use J1 for serial acesss.
<the_person48> I can ethernet in, but this beaglebone doesn't have ethernet
<the_person48> *doesn't have wifi
<the_person48> so if I do then I can't install stuff cause no internet
<rcn-ee> so... how are you going to install gcc-11 then? that's not installed..
<rcn-ee> yeah, usb-ethernet bridge thru laptop...
<the_person48> yeah exactly, that's my concern
<the_person48> previously my plan was to install via ethernet
<the_person48> but I can't do that if I'm talking to it via ethernet
<rcn-ee> so can you install an Ethernet hub to get internet..
<the_person48> I also have a USB to ethernet converter, would that work?
<the_person48> or too much complication
<rcn-ee> What actual board are you using?
<the_person48> beaglebone black rev C
<rcn-ee> That has ethernet...
<the_person48> it does, but it does not have wifi
russ has joined #beagle
<the_person48> so I can install things via ethernet, but not if I'm connected to my host computer via ethernet
<the_person48> that was my concern
<rcn-ee> sure, you can setup a dnsmasq on your pc and share your network.. actually network-manager should allow you to tether it..
<the_person48> ok, I'll try that
vd has quit [Quit: Client closed]
vd has joined #beagle
lucascastro has joined #beagle
<the_person48> ok I managed to connect using a monitor and keyboard
<the_person48> confirmed that the image is 11, so that's good!
<the_person48> and I have it connected to ethernet so I can install stuff, in theory
<rcn-ee> so resing the rootfs is automatic but it needs a reboot..
<the_person48> and what does resetting the rootfs do?
<rcn-ee> resizing..
<rcn-ee> getting tired...
<the_person48> for sure, well I appreciate your continued help!
<the_person48> I still don't understand though, why do I want to resize the rootfs?
<rcn-ee> initially it's the size of the *.img, on first/2nd reboot it's the full size of the drive..
<the_person48> ok gotcha
<the_person48> I'll reboot
<the_person48> trying to get the ip address first though
<rcn-ee> more room for gcc-11
<the_person48> looks like ifconfig doesn't work on this version
<the_person48> perfect
<rcn-ee> sudo ifconfig -a eth0
<the_person48> but I did ip address
<the_person48> looks like that's the replacement?
<rcn-ee> failure as a replacment..
<the_person48> oh your command worked
<the_person48> didn't give me an address though
<the_person48> other than a mac address
<rcn-ee> is the other end of the Ethernet connected to something giving out ip addree's? dhcp/dnsmasq?
<the_person48> it was connected to the internet
<the_person48> then I tried connecting it to my laptop
<the_person48> no address in either case
<rcn-ee> sudo dhclient eth0
<the_person48> but yeah, the first hookup should be dhcp
set_ has joined #beagle
<the_person48> that returns nothing
<the_person48> and doesn't affect the output of sudo ifconfig -a eth0
<the_person48> both when connected to internet and to my laptop
<the_person48> I'm rebooting in case that is causing any issues
<the_person48> still not showing an ethernet address
<the_person48> even after dhclient eth0
<the_person48> do I need to manually configure one maybe?
<the_person48> it also appears to be unable to access the internet
<the_person48> can't ping --> temporary failure in name resolution
<the_person48> can't download packages
<rcn-ee> are you at home or the office?
<rcn-ee> if at the office, does IT block new devices?
<the_person48> I'm at home
<the_person48> we don't have any blocks as far as I'm aware of
<the_person48> the other images of ubuntu just worked with this same ethernet jack, as soon as I plugged them in
Shadyman has joined #beagle
<the_person48> is this image supposed to work with ethernet by default?
<the_person48> or does it require reconfiguration?
<rcn-ee> eth0 is enabled by default with network-manager in control
<the_person48> nmcli returns "unavailable" on eth0
<the_person48> and "unmanaged" on USB0
russ has quit [Ping timeout: 240 seconds]
<the_person48> have you installed the debian 11 version? does ethernet work for you?
<the_person48> interesting
<the_person48> I wonder what's different about my system
<the_person48> ifconfig isn't even recognized unless I use sudo
<the_person48> is that indicative of a problem already?
<rcn-ee> i logged in as root, less keystrokes..
<the_person48> gotcha
<the_person48> ok well your input looks like the same as mine
<the_person48> just your eth0 gives an address and mine doesn't
<the_person48> and pinging google still gives temporary failure in name resolution on mine
<rcn-ee> i blame your ethernet cable, or your Ethernet hardware beyond the wall..
<the_person48> the same cable and ethernet hardware works with this same beaglebone with image 10
<the_person48> maybe the interaction between the router and the OS is different here
<the_person48> but I doubt it's the cable at least
<the_person48> any other ideas?
<vd> does PIN_OUTPUT_PULLUP/DOWN has an action of the gpio direction/value or is it just to describe the default hardware value or something?
<vd> I'm asking because I change the PIN_OUTPUT_* for PIN_OUTPUT only and my device tree still works like a charm
<rcn-ee> internal pull-up or pull-down... weak...
<vd> but is it ok to not specify the _PULL* suffix or is it mandatory?
<rcn-ee> only use it if you need it..
<vd> great, I'll use only PIN_INPUT/PIN_OUTPUT as long as it works then.
the_person48 has quit [Quit: Client closed]
<vd> do you usually see the company name in the custom bb device tree name?
<vd> like am335x-<product>.dts or am335x-<company>-<product>.dts
russ has joined #beagle