starblue has quit [Ping timeout: 252 seconds]
starblue has joined #beagle
thinkfat_ has quit [Ping timeout: 260 seconds]
thinkfat_ has joined #beagle
brook has joined #beagle
akaWolf has quit [Ping timeout: 252 seconds]
GenTooMan has quit [Remote host closed the connection]
GenTooMan has joined #beagle
akaWolf has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Ping timeout: 268 seconds]
Shadyman has quit [Remote host closed the connection]
<set_> eBay!
<set_> That is where all good things go to be replaced.
<set_> Outside of that idea...
<set_> BBAI-64 and ROS!
ikarso has joined #beagle
otisolsen70 has joined #beagle
otisolsen70 has quit [Remote host closed the connection]
otisolsen70 has joined #beagle
demirok has quit [Ping timeout: 255 seconds]
<set_> Nope.
demirok has joined #beagle
<zmatt> wouldn't be surprised if the "beaglebone black" they purchased for cheap isn't even actually a beaglebone
otisolsen70 has quit [Quit: Leaving]
otisolsen70 has joined #beagle
otisolsen70 has quit [Remote host closed the connection]
otisolsen70 has joined #beagle
florian has joined #beagle
otisolsen70 has quit [Quit: Leaving]
static_rocket1 has quit [Quit: You have been kicked for being idle]
Guest99 has joined #beagle
Guest99 has quit [Client Quit]
set_ has quit [Read error: Connection reset by peer]
set_ has joined #beagle
mag has quit [Remote host closed the connection]
mag has joined #beagle
akaWolf has quit [Ping timeout: 268 seconds]
Guest6317 has joined #beagle
akaWolf has joined #beagle
<Guest6317> Hi everyone, I am working on a project that uses a beaglebone black wireless but mine seems to have broken. Ignoring the wireless features, how interchangable are the beaglebone black and beaglebone black wireless?
<zmatt> Guest6317: fully
<zmatt> Guest6317: well, that and the bbb has a mini-usb connector while the bbb-wireless has a micro-usb connector ... but the correct cable is included in both cases anyway
<Guest6317> Thanks!
starblue has quit [Ping timeout: 255 seconds]
starblue has joined #beagle
Guest6317 has quit [Quit: Client closed]
Guest87 has joined #beagle
<Guest87> how to install software on beaglebone green
<Guest87> i want to install minicom
<zmatt> using apt, like any other debian system
<Guest87> I did sudo apt-get install minicom
<Guest87> but get sudo: apt‐get: command not found
<zmatt> uhh, the "‐" in "apt‐get" is not a "-", it's some unicode character
<zmatt> it should be "apt-get" instead (with a normal -)
<Guest87> that is
<zmatt> I'm guessing you copy-pasted apt-get from something that helpfully used unicode characters to make things look nicer :P
<Guest87> I'm sorry but I didn't understand. write without -
<zmatt> "sudo apt-get install minicom"
<Guest87> yes i wrote that
<Guest87> I can't even do anything with apt-get
<mayab> try just 'apt' without the '-get' they should be the same
<mayab> ie "sudo apt update"
<Guest87> I did it right away but he does not allow it to be done - it gives errors
<Guest87> Err:1 http://deb.debian.org/debian stretch InRelease
<Guest87>   Temporary failure resolving 'deb.debian.org'
<Guest87> Err:2 http://repos.rcn-ee.com/debian stretch InRelease
<Guest87>   Temporary failure resolving 'repos.rcn-ee.com'
<Guest87> Err:3 http://deb.debian.org/debian stretch-updates InRelease
<Guest87>   Temporary failure resolving 'deb.debian.org'
<Guest87> Err:4 http://deb.debian.org/debian-security stretch/updates InRelease
<Guest87>   Temporary failure resolving 'deb.debian.org'
<Guest87>                      so I don’t know if it’s possible to install at least something on BBG
<zmatt> Guest87: 1. stretch is obsolete, please reflash to at least debian buster first
<zmatt> 2. your beaglebone doesn't have an internet connection so it can't download any packages, easiest way to provide internet to it is by plugging it in via ethernet
<Guest87> I have debian
<Guest87> ok, I connected it to both the computer and the Internet
<zmatt> "stretch" and "buster" are debian releases... debian 9 is called stretch, debian 10 is buster, debian 11 is bullseye
<zmatt> debian 9 (stretch) is obsolete
<Guest87> how to check what version of debian
<Guest87> lsb_release -a
<Guest87> bash: lsb_release: command not found
<jfsimon1981> I think éuname -aé
<jfsimon1981> sorry "uname -a"
<zmatt> and you were getting a "command not found" error because the "-" in "apt-get" was some weird character, look closely: https://imgur.com/a/xxZvPJ0
<Guest87> Linux beaglebone 4.9.82-ti-r102 #1 SMP PREEMPT Thu Feb 22 01:16:12 UTC 2018 armv7l GNU/Linux
<zmatt> jfsimon1981: uname only shows the kernel version
<zmatt> Guest87: cat /etc/debian_version
<jfsimon1981> ok
<zmatt> Guest87: it also showed "stretch" when you were trying to do apt update
<Guest87> 9.3
<zmatt> which, as I said, is stretch
<Guest87> and how can i change it?
otisolsen70 has joined #beagle
<zmatt> download the latest official flasher: https://debian.beagleboard.org/images/bone-eMMC-flasher-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz .. write it to a microSD card (4GB or larger) using https://www.balena.io/etcher/
<zmatt> when you boot the beaglebone from that sd card, it will automatically wipe and reflash it
otisolsen70 has quit [Remote host closed the connection]
<zmatt> (if you have any important files on it, make a backup of those first)
<Guest87> yes thank you very much. I've been doing this several times already with only version 9
otisolsen70 has joined #beagle
<zmatt> why with version 9 ?
<Guest87> and after that apt -get should work?
<zmatt> this is unrelated to that, apt-get (or apt) should work if your beaglebone has internet access (and you type it correctly, and do "sudo apt-get update" once before attempting to "sudo apt-get install")
<Guest87> I don’t know why - I’m just learning and I saw a lesson that they do this .... I didn’t know that it was very important
<zmatt> like, running debian stretch on a beaglebone is kinda like running Windows XP on a PC :P
<zmatt> like, sure, you can do it, and people still do, but it's getting really old and it's not getting any updates
<Guest87> Is it compatible with all versions of Linux?
<zmatt> ??
<Guest87> I have linux beaglebone 4.9.82-ti-r102
<zmatt> "Linux" is just the name of the kernel, the heart of the operating system
<zmatt> 4.9 is also a very ancient version of that
<Guest87> oops, I messed up - sorry (I'm still a beginner)
<Guest87> I installed linux on my bbg and not debian
<zmatt> linux is at the heart of a debian system
<zmatt> like, "debian" describes the overall system, which includes the kernel (linux) and many other programs and files needed to make an actual usable system
<zmatt> (there are also other linux-based systems, like Ubuntu and Android)
<Guest87> when i insert a microSD card linux will not be erased? because i formatted it like that
<zmatt> ????
<zmatt> you're very confused, and I no longer have any idea what you're trying to ask
<Guest87> that is, will I still have the same version of Linux or not? I'm just interested in how it works, it doesn't matter to me which version
<zmatt> the debian 10.3 image I linked above includes linux kernel 4.19.something
<zmatt> the kernel can be updated like any other package on the system
<Guest87> that is, when I install another version of debian, it also changes the version of Linux ????
<zmatt> 4.19.94-ti-r42
<zmatt> the linux kernel is part of the debian system, it's just one of many software packages (albeit a quite important one)
<Guest87> in conclusion: inside debian there are packages from a certain version of linux
<zmatt> linux is a kernel, a core component that's at the heart of an operating system, like the engine of a car. people often also use the term "linux" to describe operating systems that are built around the linux kernel, debian is one of such operating systems
<zmatt> operating systems built around the linux kernel are also called "linux distributions" or "linux distros" for short... debian is such a linux distro, but there are many others
<Guest87> super thanks you helped me a lot. if not with a problem then with understanding
<Guest87> I hope after updating debian I can finally install minicom :)))
<zmatt> it looked like your main issues with attempting to install packages (besides the weird char in "apt-get") was the beaglebone not having working internet access
<Guest87> in the new version of debian it should be?
<zmatt> I already told you, updating to debian 10 is unrelated to your problem, it's just something you should do because debian 9 is severely outdated
<zmatt> the error you showed indicates that your beaglebone does not have internet access
<zmatt> without internet access, it can't download anything to install
<Guest87> Would connecting to the internet help? i need to install minicom
<Guest87> ethernet (not internet)
<zmatt> easiest way to provide internet access to a beaglebone black is by connecting its ethernet to your internet router/modem. if you're connecting it via ethernet to your computer instead, and your computer has internet via wifi, then you'd need to enable something called internet sharing to share your PC's internet connection to the beaglebone
<zmatt> anyway, I've got other things to do, maybe someone else can help if you have further questions
<Guest87> I have BeagleBone GREEN!!!
<zmatt> beaglebone green, black, same thing pretty much
<Guest87> thank you so much and have a great day!!!
<zmatt> what I just said applies to all debian systems running on some computer that only has ethernet and no wifi
<zmatt> (e.g. most beaglebones)
<zmatt> (hmmm, actually now that I think of it "most beaglebones" these days actually have wifi... well never mind that :P )
<zmatt> afk
<Guest87> please tell me what exactly should I do to connect to the Internet via an ethernet cable. I have never connected like this.
<Guest87> I connected my beagle to 1-computer 2-to ethernet cable
<Guest87> right
RachelM has joined #beagle
YB has joined #beagle
RachelM84 has joined #beagle
RachelM84 has quit [Client Quit]
YB has quit [Client Quit]
<Guest87> please tell me what exactly should I do to connect to the Internet via an ethernet cable. I have never connected like this.
<Guest87> I connected my beagle to 1-computer 2-to ethernet cable
<Guest87> right?
<RachelM> I'm trying to send data to driver on BeagleBone Green via USB Serial Adapter.
<RachelM> I'm connecting  adapter  to the GPIO pins of uart2 (I added all port data to the device tree)
<RachelM> 1. im openning configured minicom on pc,
<RachelM> 2.im connecting to bbg via ssh
<RachelM> but when im writing in minicom symbols
<RachelM> cat utilite on bbg side ,that wait to get data, dont get nothing
<RachelM> where is i have problem?
<RachelM> I'm new at this and I really hope for help
RachelM has quit [Quit: Client closed]
RachelM has joined #beagle
<RachelM> I'm trying to send data to driver on BeagleBone Green via USB Serial Adapter.
<RachelM> I'm connecting  adapter  to the  pins of uart2 (I added all port data to the device tree) on bbg and to pc
<RachelM> 1. im openning configured minicom on pc,
<RachelM> 2.im connecting to bbg via ssh
<RachelM> but when im writing in minicom symbols
<RachelM> cat utilite on bbg side ,that wait to get data, dont get nothing
<RachelM> where is i have problem?
<RachelM> I'm new at this and I really hope for help
<zmatt> RachelM: is the baudrate configured the same on both sides?
<RachelM> yes
<zmatt> Guest87: don't send unsolicited private messages
<zmatt> RachelM: is it a 3.3V TTL usb serial adapter?
<RachelM> 115200
<zmatt> Guest87: and I already answered the question you're asking, having to keep repeating things to you is getting rather tiresome
<zmatt> RachelM: also, I'm not sure if catting a serial port works correctly, I think some terminal settings need to be configured after opening the port but before trying to read... not 100% sure about that though, it's been a while since I've worked with serial ports
<RachelM> I think so i have cp2102 adapter
<zmatt> RachelM: have a part numbe or a link to the product page or something?
<zmatt> try: stty -F /dev/ttyS2 raw 115200 clocal -crtscts -ixon
<zmatt> RachelM: also double-check that the pins are configured correctly using my show-pins utility: https://github.com/mvduin/bbb-pin-utils/#show-pins
<RachelM> on beaglebone side?
<zmatt> yeah
<zmatt> show-pins should show "uart 2 rxd" for the receive pin in show-pins
<RachelM> im configure pins in driver via data sheet
<zmatt> not sure what you mean by that, but regardless of how you've configured the pins, it's good to verify that the pins are indeed setup correctly, and my show-pins utility is a convenient way to check this
<RachelM> I used the program from the site https://alexrhodes.io/blog/post/22/
<zmatt> uhh. this is a tutorial on how to write a kernel driver?
<RachelM> i do step by step how written on the site but not succesful
<zmatt> you trying to learn how to write a kernel driver, or are you just trying to get a serial port working?
<zmatt> because this is the former, not the latter
<RachelM> my task to write uart driver on bbg and my code is based on the code of site
<RachelM> and i want to check if it work well
<zmatt> task? is this a homework project or something?
<RachelM> final project
<zmatt> if this is a final project, it sounds like perhaps you should be able to debug your own software? :P
<RachelM> on the end of
<RachelM> ...
<zmatt> and you should certainly be better at asking questions... instead of coming in here asking for help with serial communication, when you were actually asking for help with getting a custom kernel driver working
<zmatt> :P
<zmatt> anyway, I've got things to do too... but good luck with your driver project
<RachelM> i compiled and installed driver with device tree
<RachelM> but i want to check if it work
Guest87 has quit [Quit: Client closed]
brook has joined #beagle
TuoDrable has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
nslu2-log has quit [Remote host closed the connection]
nslu2-log has joined #beagle
RachelM has quit [Quit: Client closed]
brook has quit [Ping timeout: 255 seconds]
brook has joined #beagle
TuoDrable has quit [Quit: Leaving]
brook has quit [Remote host closed the connection]
brook has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
buckket has quit [Read error: Connection reset by peer]
buckket has joined #beagle
florian has quit [Quit: Ex-Chat]
brook has quit [Remote host closed the connection]
demirok has quit [Remote host closed the connection]
brook has joined #beagle
Guest42 has joined #beagle
<Guest42> hi good day
<Guest42> I just want to know if the BEAGLEBOARD-X15 is compatible with Android 12
<zmatt> looks like TI's AM572x processor sdk for android is for android 9
<zmatt> though I don't know if that means android 12 isn't compatible.... I don't really know anything about android myself, nor have I ever heard of someone running it on a beagleboard-x15 (which is pretty much identical to the processor board of the AM572x EVM)
<zmatt> looking at TI's git repo, I'm getting the impression they stopped maintaining android for the am57x: https://git.ti.com/cgit/android/hardware-ti-am57x/refs/
<zmatt> oh there's even a bbx15-specific repo... it's equally dead though: https://git.ti.com/cgit/android/device-ti-beagle-x15/refs/
brook has quit [Remote host closed the connection]
brook has joined #beagle
<Guest42> Helo
<Guest42> Im sorry for the dely
<Guest42> *delay
Guest19 has joined #beagle
Guest42 has quit [Quit: Client closed]
Shadyman has joined #beagle
<Guest19> hello all. I may have done a boo-boo and wiped the /dev/mmcblk1 on a beaglebone AI (I did this because that's the standard way of SD booting on a BBB). Now the beagle doesn't turn on.
<Guest19> Is it bricked?
<zmatt> no
<zmatt> not sure if mmcblk1 is eMMC or SD card on the bbai
<zmatt> I think you probably just wiped your sd card
<zmatt> hmm maybe not
<zmatt> mmcblk1 seems to be the eMMC here
<zmatt> it appears the bbai boot order for bootrom prefers to load u-boot from SD card over loading it from eMMC, so there was no point in wiping eMMC anyway
<zmatt> though if wiping eMMC caused it to no longer boot the sd card, that would seem to imply to me that your sd card doesn't actually have a (functioning) u-boot installed
<rcn-ee> zmatt: Sept 1st snapshots are now posted... https://forum.beagleboard.org/tag/latest-images
<rcn-ee> bbai: eMMC = mmcblk1, microSD = mmcblk0
<zmatt> Guest19: wiping eMMC is recommended for AM335x-based beaglebones if you want to use an SD card as primary boot device, because the AM335x bootrom can't be configured to prefer loading u-boot from SD card over loading it from eMMC... either eMMC is preferred over SD (default on all beaglebones that have eMMC) or eMMC is not consulted at all (which happens when you power up while holding down the S2 ...
<zmatt> ...button)
<zmatt> Guest19: this simply doesn't apply to the bbai
<zmatt> Guest19: regardless, if the bbai doesn't boot your sd card, the logical conclusion is that your sd card isn't bootable
<zmatt> and if it used to boot but no longer does after wiping eMMC, then the specific reason the sd card isn't bootable will be because u-boot is missing or damaged on the SD card
<zmatt> (and you were unknowingly just relying on the u-boot installed on eMMC)
<zmatt> actually, not "missing or damaged", just missing
<zmatt> rcn-ee: in the readme, you may want to use e.g. "sudo systemctl disable --now nodered" ... the ".service" is redundant and the "--now" will also imediately stop the service (in addition to preventing it from booting at next startup)
<rcn-ee> cool, didn't know about --now... updating..
<zmatt> and you probably also want to disable the associated .socket unit in that case, although that's also something you could arrange for in the .service unit itself
<rcn-ee> we no longer do socket activation in nodered...
<zmatt> ah ok
<rcn-ee> it was something upstream didn't care about, and teh patch got more difficult, so it was dropped...
<rcn-ee> (and it was slow...)
<zmatt> yeah socket activation is more useful for sockets used by local services, since it means you may be able to avoid a strict dependency between services
<rcn-ee> and for applications that dont take 30seconds to start.. looking at you code-server..
<zmatt> running the cloud version of vscode as a server on a beaglebone still seems insanity to be, compared to running vscode locally and using https://vscode-eastus.azurewebsites.net/docs/remote/ssh
<zmatt> though lol wtf, "1 GB RAM is required for remote hosts, but at least 2 GB RAM and a 2-core CPU is recommended" ... WHY
<zmatt> also why does google keep giving me that weird link as top result instead of the normal url https://code.visualstudio.com/docs/remote/ssh
<rcn-ee> While being slow at startup, it does actually work 'decently'... it's not how fast cloud9 was.. but it actually loads..
<rcn-ee> also on am335x, we have to enable a swap file, to make it even load.. yeah for am335x it fills a checkbox, more a gimic.. on am57xx or bbai64 it runs pretty good..
<zmatt> please don't enable swap by default /o\
<rcn-ee> `2.965s dphys-swapfile.service`
<zmatt> I feel like this void should be fillable by a tutorial on getting started with vscode (desktop version) + remote development via ssh
<rcn-ee> dphys-swapfile is directly tied to the bb-code-server package...
<Guest19> thanks @zmatt. I will take a look at a known good SD card.
<rcn-ee> Guest19: what image did you flash to your SD card? wondering why the bootrom didn't pick it up...
<rcn-ee> Guest19: and how did you flash it? etcher.io ? or something else..
<zmatt> rcn-ee: good to know that disabling bb-code-server will thus also disable swap, but still I question whether you really want this "gimmick" as you described it to be enabled by default, particularly on AM335x images
<rcn-ee> it's actually 'disabled' by default... user has to enable it..i think i worded the wiki wrong..
<rcn-ee> `#rfs_enable_vscode="enable"` it's disabled in the build script..
<rcn-ee> yeah, looking at the config files, arm64 is the only one with it enabled out of the box... `rfs_enable_vscode="enable"`
<rcn-ee> There it is... back on Dec 29, 2021 https://github.com/RobertCNelson/omap-image-builder/commit/fef9dab055016411cf14be521b7bb6b8536e7c41 defaulting to enabled on arm32 was stupid.. forgot to update the wiki to 'opt-in/enable it'...
<Guest19> @rcn-ee: used dd, and used bbai64-debian-11.3-xfce-arm64-2022-06-14-10gb.img.xz - I was able to mount it and confirm that the SD card is mounting.
<Guest19> one note I would have is that the first partition isn't the boot partition, but I'm assuming that's just the way it is.
<rcn-ee> Guest19: which board do you have "BBAI" or "BBAI64".... based on your previous post, it's a "BBAI"..
<Guest19> ahh. that would explain this actually.
<rcn-ee> that image you mentioned, is for the 64 Bit, BBAI64.. it won't do anything on a BBAI..
<Guest19> aahh. did not notice that.
<zmatt> rcn-ee: btw, not sure how common knowledge this is, but in case it's useful; a short tutorial on how to do remote debugging of nodejs -> https://pastebin.com/skVvPRSC
<zmatt> (using Google Chrome)
<rcn-ee> Guest19: as your looking at 11.x, grab today's snapshot... https://forum.beagleboard.org/t/debian-11-x-bullseye-monthly-snapshots/31280 these last few weeks i've been cleaning up on teh BBAI again...
<rcn-ee> zmatt: that's cool! i normally stay out of nodejs, but it's cool to know..
<rcn-ee> Guest19: is there a specific feature of the bbai that you are trying to utilize?
<rcn-ee> zmatt: does `sudo systemctl enable --now bb-code-server` work just like disable does?
<zmatt> yep
<zmatt> enable --now = enable + start, disable --now = disable + stop
<Guest19> rcn-ee: no particular features. I just want a headless server.
<Guest19> thanks for the heads up. I wasn't aware of that page.
<rcn-ee> Guest19: ah then, just grab the minimal/iot, no reason to waste the cpu cylces on xorg loading!
<zmatt> that use-case sounds like you'd want minimal indeed
<zmatt> and a fan to cool it ;)
<Guest19> yes, the reason I ended up with that image was because I noticed on the download page that it was the only 11.x installer. I was going to get IOT but that one's still at 10.3
<Guest19> (I was going to do that and then uninstall the xfce libs)
<Guest19> currently downloading the minimal snapshot
<zmatt> it's easier to start with a minimal image and install just the things you need then to start with a bloated image and try to carefully remove superfluous crap
<rcn-ee> i think @jkridner is going to update those pretty soon, now that everything is stablized again..
<Guest19> zmatt: much prefer to do it that way too
<Guest19> rcn-ee: thanks for the update. I appreciate very much that you guys are maintaining this
Guest19 has quit [Quit: Client closed]
Guest19 has joined #beagle
Guest19 has quit [Quit: Client closed]
Guest19 has joined #beagle
<Guest19> not sure why I keep getting disconnected, but thanks zmatt and rcn-ee: was saying I apprecaite the fact that this is all being maintained.
<zmatt> Guest19: yep, that message came through!
PhotoJim_ is now known as PhotoJim
CrazyEddy has quit [Ping timeout: 255 seconds]
GenTooMan has quit [Ping timeout: 255 seconds]
otisolsen70 has quit [Quit: Leaving]
GenTooMan has joined #beagle
<Guest19> I do have another question: I'm not sure if my hardware is flaking out, but when I power on my BBAI, the LEDs don't 'always' come on. Prior to wiping my mmc, the beagle would power on (green LED next to USB-C) but I would have to hit reset then power to get the USR LEDs to come on. Now that I've wiped my MMC, I can't get USR LEDs to ever come on. I
<Guest19> have the impression I must either be missing something obvious, or this is a hardware issue
<zmatt> the USR leds not coming on just means it's not booting, it doesn't say anything about why it's not booting
<zmatt> so "Now that I've wiped my MMC, I can't get USR LEDs to ever come on" is equivalent to "I haven't managed to boot from SD card yet"
<Guest19> roger that.
<zmatt> that could of course be due to a hardware issue (e.g. a defective card slot), but in that case the slot would just not work whatsoever (and not merely fail to boot from it)... it sounded to me like that isn't the case in your situation
<zmatt> not sure what to make of the other issue you just mentioned, about previously having needed to reset to get it to boot.... while I think I've had sporadic issues with booting at some point in the past, it normally has no problem booting immediately when I apply power
<zmatt> but my bbai is probably my least-used board, in no small part because of its tendency to overheat
<Guest19> it might be a card reader issue, honestly.
<Guest19> I have no positive confirmation that I ever read the SD card. only that I was able to boot to mmc.
<Guest19> Is there anything I should know about the flashing process? I'm just dd'ing the uncompressed image to the sd card. I'm not setting it as a bootable partition used parted or anything like that.
<zmatt> dd'ing the decompressed image to the sd card *should* work, be sure to overwrite the entire card and not a (typically the only) partition
<zmatt> we generally recommend using https://www.balena.io/etcher/ since it's less error-prone, and additionally performs on-the-fly decompression (no need to unxz the image) and more importantly verifies the sd card contents after flashing to ensure the card isn't flaky
<zmatt> (I have a microsd card whose contents is different each time you read it)
<Guest19> ok, I will give that a try. I've been making sure the image is mountable every time I flash it.
<Guest19> I'm actually going to try another SD cazrd
<Guest19> this is unfortunate. I think I may have bricked my bb after all by virtue of having a bum sd card reader and no longer having a viable emmc os. I just tried a known good SD card and it won't boot
<Guest19> oh, as if Murphy were watching over my shoulder. it just came up
<Guest19> ok, matter is settled. Thank you again for taking the time.
<zmatt> a bum sd card is unlikely since I think the board gets flashed in the factory *using* the sd card slot
<zmatt> (though even with bum sd card it wouldn't be bricked technically, it would just be harder to recover)
<zmatt> also, yay, my RNG microsd card still works! :D https://pastebin.com/raw/zYtDPZrD
<zmatt> *a bum card slot I mean
<Guest19> I think the card slot would have gotten bum from mistreatement post factory
<Guest19> I'm very closed to convinced that's the issue now. I just swapped out the SD card to check something and it won't come back now.
<Guest19> I believe there's a connection issue. I'll have to be gentle with it once I boot back in
<Guest19> (mistreatement from me, that is)
<zmatt> at work we ran into a bbb with bum sd card slot, which got discarded so I gave it to a friend... he discovered a slightly bent contact in the sd card slot and fixed it by bending it into proper position
<Guest19> I'll give that a looksy. my eyes ain't what they used to be though  :|
<zmatt> I wonder if cpu prcm on the am57x got fixed in newer kernels... on my bbx15 running 4.19.94-ti-r72, using my utility to enable cpu power management causes the cpu temp (while idle) to drop very substantially... https://pastebin.com/Ms2CVnDU
vvn has quit [Quit: WeeChat 3.6]
vvn has joined #beagle
Whisky` has joined #beagle
bryanb_ has joined #beagle
renrelkha_ has joined #beagle
NishanthMenon_ has joined #beagle
bryanb has quit [Ping timeout: 244 seconds]
NishanthMenon has quit [Ping timeout: 244 seconds]
PhotoJim has quit [Ping timeout: 244 seconds]
renrelkha has quit [Ping timeout: 244 seconds]
GenTooMan has quit [Ping timeout: 244 seconds]
Whiskey` has quit [Ping timeout: 244 seconds]
ketas has quit [Ping timeout: 244 seconds]
PhotoJim has joined #beagle
bryanb_ is now known as bryanb
NishanthMenon_ is now known as NishanthMenon
GenTooMan has joined #beagle
ketas has joined #beagle
jfsimon1981 has quit [Remote host closed the connection]
jfsimon1981 has joined #beagle
dinuxbg_ has quit [Ping timeout: 268 seconds]
vagrantc has joined #beagle
ft has joined #beagle
behanw has joined #beagle
brook has quit [Remote host closed the connection]
nparafe has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
nparafe has joined #beagle