00:06 <Guest37100> my beagle bone green is having issues

00:07 <Guest37100> the blue power light stays on but its not functioning

00:08 <Guest37100> can anyone here help me

00:17 <Guest33> can someone help me

01:19 <GenTooMan> well they didn't stick around ...

01:36 <zmatt> "not functioning" is also very descriptive

01:37 <GenTooMan> you do have a fair point on that as well.

04:19 <set_> I am back to colors on here. No more b & w. Nice!

04:29 <set_> Oh and rcn-ee_: The new image for the BBAI w/ ' sudo beaglecfg ` works just fine!

07:49 <Guest15> @zmatt if you have a moment could you take a look at an strace. It was too big for pastbin so I threw it on filebin: https://filebin.net/brxbjlg7tkrv5x3a

08:29 <Guest85> Why is the BBB Wireless price almost double what it was a year ago?

10:33 <set_> BBBlue! Aw!

10:33 <set_> Sorry. I take that back.

10:34 <set_> It is the multitudes of source being counter intuitive for now. Flying...blah. I need a real hobby. Like playing hookie. Ha.

10:53 <zmatt> Guest15: QT_QPA_EGLFS_INTEGRATION=egl_kms that's not a valid name, it's eglfs_kms

10:56 <zmatt> not sure why you sent an strace log if you got it working

11:00 <zmatt> interesting, so qt5 seems to think the currently configured mode is acceptable for its configuration, but then the pageflip somehow fails. so something about the mode must be not quite right for what qt5 is doing, though I'm not sure what that could be

11:34 <set_> Okay...things are building slowly. So, the materials in my bom are being gotten and soon. Also, arducopter is whooping my tailwinds. Just a heads up here.

11:34 <set_> Oh!

11:35 <set_> Is anyone using the BBAI w/ the PVR SDK from imgtec on the newer-testing images w/ bullseye?

11:35 <set_> I know a lot of the issues pertaining to the compilation of the SDK had to do w/ Python not being v3.9.x.

11:36 <set_> and! W/ bullseye, python3.9 is a given! yea boy!

13:42 <set_> bbl!

15:04 <Guest15> @zmatt From what I saw in the strace, Qt picks the wrong renderer. It chooses renderD129 instead of renderD128. I'll check again fixing that typo, thanks for catching that.

15:07 <zmatt> 129 seems correct to me

15:07 <zmatt> for the gpu

15:10 <zmatt> yeah it looks like the sgx library scans for the correct gpu render device by iterating over them and checking the driver of each (using DRM_IOCTL_VERSION)

15:11 <Guest15> what is platform-omapdrm.0-render -> ../renderD128 then? I was under the impression it belonged to the right card.

15:11 <zmatt> omapdrm is the display controller

15:13 <zmatt> I don't know if there's any use for its render device, I think every drm device gets both a primary device (card*) and a render device regardless of whether it is useful

15:14 <Guest15> setting export QT_QPA_EGLFS_INTEGRATION=eglfs_kms properly still doesn't make Qt work without supplying QT_QPA_EGLFS_KMS_CONFIG.

15:15 <zmatt> no I was just saying it to make the warning about inability to load eglfs_kms go away

15:15 <zmatt> presumably it loads it anyway as a default fallback?

15:16 <zmatt> inability to load egl_kms I mean, since it doesn't exist

15:16 <Guest15> Ah, but why do I need to specify QT_QPA_EGLFS_KMS_CONFIG to get everything working?

15:16 <zmatt> dunno, presumably something is going wrong with qt5's autodetection/autoconfiguration logic

15:16 <zmatt> which is also shown by the need to force modesetting

15:17 <Guest15> Right, but with the 1.14 drivers, there's no issue.

15:17 <zmatt> figuring out why would require investigating qt5's logic and how this interacts with the drivers and the kernel

15:17 <zmatt> since it's definitely odd

15:18 <zmatt> like, the configuration you showed in that .cfg file is all stuff that's related to the display controller (omapdrm), not the pgu

15:18 <zmatt> *gpu

15:18 <zmatt> so I don't know why the gpu driver version would be of any relevance whatsoever

15:29 <Guest15> Okay you said "sgx library scans for the correct gpu render", would it be worthwhile testing the other 1.17 branches?

15:53 <zmatt> I very much doubt it would have any impact. there's a slightly newer branch, ti-img-sgx/thud/1.17.494857, which appears to be a typo for ti-img-sgx/thud/1.17.4948957, but the only difference between them is commit bcca77e fix texture corruption

15:54 <zmatt> the only branch that's newer than that is ti-img-sgx/dunfell/1.17.4948957 (aka 1.17.4948957-next), which requires glibc 2.29

15:57 <zmatt> graph of most recent commits in 1.17 branches (down to ti-img-sgx/thud/1.17.4948957), ordered by commit date: https://pastebin.com/raw/VbYqezuZ

16:04 <zmatt> so there's two major branches right now: the thud branch (glibc 2.28) and the zeus/dunfell branch (glibc 2.29), there's a major update between thud and zeus (completely new build), while between zeus and dunfell there's just a tiny header-file change, and parallel to this the thud branch also received this "fix texture corruption" commit but the result was pushed to the erroneously named ...

16:04 <zmatt> ...ti-img-sgx/thud/1.17.494857 instead of ti-img-sgx/thud/1.17.4948957

16:11 <set_> How is it I updated everything earlier and now nothing updates on the BBAI w/ Linux BeagleBone 5.10.59-ti-r22 && BeagleBoard.org Debian Bullseye IoT Image 2021-10-02 ?

16:12 <set_> I know you all are busy.

16:12 <set_> If someone could point me to a special place, that would be nice if time provides.

16:14 <set_> https://pastebin.com/DgDsviNU is my error exactly.

16:16 <set_> I know it is a wip, i.e. no issue.

16:16 <zmatt> that looks like the bbai has no internet access

16:17 <set_> Hmm. I just updated like today. Earlier today.

16:17 <zmatt> then maybe it's just a temporary error, like it said :P

16:17 <set_> Maybe I need to configure Ethernet?

16:17 <set_> Ha.

16:17 <set_> Maybe.

16:18 <zmatt> I can currently resolve repos.rcn-ee.com without any problem

16:18 <set_> Hmm.

16:18 <set_> Okay.

16:20 <set_> Now. It works!

16:20 <set_> ' mr. impatient over here! '

16:21 <set_> I guess I have been unloading some installs too rapidly for the AI for now.

16:21 <set_> slow 'mo...

16:22 <set_> That sucker is fast, bro.

16:22 <set_> Man.

17:09 <set_> Finally!

17:10 <set_> opencv4.5.x is up and runnin' w/ ease. I have been working on making this work since the last time it worked.

17:10 <set_> It has been so long, I cannot remember...minds. Sheesh.

17:11 <set_> Now, time to hook up a fancy cam. One w/ LEDs and other things.

17:11 <set_> yes!

17:12 <set_> The only issue is that the USB cam takes so much cpu effort. It is too costly for a USB cam.

17:13 <set_> I mean...usb cams are a dime a dozen. The BBAI chip is, well, almost unheard of...

17:18 <set_> GenTooMan: I know you do not mess w/ webcams much but look at this footage. Wait...

17:24 <set_> Look here, https://imgur.com/a/dwKloWS , b/c you are number one!

17:25 <set_> It is manipulating photos and video and before my very eyes. Nice.

17:27 <set_> I can find squares! All jokes aside, I am ecstatic and really childlike now!

17:28 <set_> Psychadelic Gabor! Ha.

18:34 <set_> There...I know the BBAI is not Desktop Ready. But here: https://imgur.com/a/8XuQ7SR . Some histogram after drawing on the video while recording live. Odd stuff...

22:57 <set_> I got it all! The video, altering of photo(s), and saving of each of those two things. Neat-O!

22:57 <set_> Did anyone look at the Gabor(n)?

23:13 <set_> That is just the ARM, i.e. nothing but pure power. I wonder how to start investigating the EVE or DSP onboard. Is it possible to offload to those chips still?

23:14 <set_> Think of me in the land of ill refute. I am smart but w/out education. So, it will be trying...trying.

23:14 <Guest29> Hello

23:15 <Guest29> anybody here has experience with enabling can bus with pocketbeagle?

23:18 <set_> So, when the EVE program cache states 32 KB, is that amount of installed memory I can use?

23:18 <set_> Guest29: Hello! I am slowly starting to jump into the deep end to quickly!

23:20 <set_> I might have to use TIDL, right?

23:26 <set_> I am starting to learn more. So, my puny (not a server) 'puter may not be able to conduct a training. Blah.

23:26 <set_> Luckily, there are more training sites available.

23:26 <set_> MNIST for one.

23:35 <set_> Guest29: Here... https://www.beyondlogic.org/adding-can-to-the-beaglebone-black/

23:36 <set_> It is not the PocketBeagle but it may provide some info. that is sort of current.

23:37 <set_> I have a CAN tranceiver over here if you want to get dirty!

23:38 <set_> Sorry for being disgusting. Dirty could be something smarter like, "working," or "teaming up to conquer the world!"

23:45 <Guest29> right now I don't have acess to pocket beagle or a transceiver, the place I would go to test currently has limitations for use of the installations due to covid-19

23:45 <set_> Oh.

23:45 <set_> Hmm.

23:46 <Guest29> so right now I am researching and collecting every information about can and pocketbeagle

23:46 <set_> That takes the fun out of it for me. Maybe someone can help you w/ notes.

23:46 <set_> Right. Okay.

23:46 <Guest29> it seems there is not much

23:46 <set_> Do you have access to a computer?

23:46 <Guest29> yep

23:46 <set_> W/ interwebs?

23:47 <set_> Try the beyondlogic.org site I listed. It may prove valuable.

23:47 <Guest29> ok

23:47 <Guest29> thanks

23:47 <set_> For starters and notes. Serious.

23:47 <set_> Every bit helps in the long run!

23:48 <set_> It is like a gatherer that never stopped moving to gather things. Sooner or later, that gatherer will build something 'nice.' Hopefully.

23:49 <set_> No mutant cyborgs yet but something in 8-bit Car logic!

23:49 <set_> I think...I may have been wrong. Let me double check that link.

23:52 <set_> Yep. That will help. So, the available pinout is here from what I gather: https://maker.pro/beagleboard/projects/how-to-get-started-with-pocketbeagle

23:52 <Guest29> I think I found something here, I was digging in beagleboard group google and seems like some people used a pocketbeagle as the processor for a device to tinker with cars

23:52 <Guest29> https://groups.google.com/g/beagleboard/c/zmg4A7S3NJY/m/dtJKUwtlAgAJ

23:53 <Guest29> thanks again for the links

23:53 <set_> You can see the CAN interface.

23:53 <set_> No issue. I thought I caught someone who wanted to work w/ me. Sorry.

23:54 <set_> bbl!