**** BEGIN LOGGING AT Tue Dec 29 02:59:57 2020 Dec 29 03:21:20 Hello, what is the size of elf-test.py that can be loaded from source to pru mem? Dec 29 03:21:37 Is it just the 16Kb? Dec 29 03:23:42 Okay. So. core0. Got it. Off to look. Dec 29 04:35:16 set unleashed on the pru Dec 29 04:35:46 zmatt I am trying to find a way to communicate with a beagle if I am using a hub on the usb Dec 29 13:14:30 m Dec 29 13:44:56 mattb0000ne: I don't see why a hub would make any difference? wait, are we talking about a BBAI here instead of a beaglebone? Dec 29 13:45:08 yes Dec 29 13:47:25 please say "bbai" instead of "beagle" or whatever when you're talking about a bbai, since it is completely different from every other beaglebone Dec 29 13:48:54 the usb-c can take on either role (host or device), but not at the same time Dec 29 13:49:51 I don't know if the bbai's host port can be reconfigured into device mode, I'd need to check. even if it can be, almost certainly the overlay I gave earlier won't be right for the bbai Dec 29 13:49:58 why not just use ethernet or wifi ? Dec 29 13:51:59 to ssh in? Dec 29 14:02:33 yes? Dec 29 14:02:54 I can do that and still use it for internet? Dec 29 14:03:08 ehm yes, why would those uses conflict? Dec 29 14:03:54 i guess I was confused since I always have ethernet and the usb connected and i would lose my ssh when I switched the usb-c to host Dec 29 14:04:49 if you're connected via both usb and ethernet then you can ssh in via both routes, and if you ssh in via usb then obviously that will drop when you reconfigure the usb-c into host mode Dec 29 14:06:50 to ssh via ethernet you can often use the hostname, either as-is or with a ".local" suffix (e.g. "beaglebone.local") .. which of these work depend a bit on the network router and on the OS you're using (.local addresses work fine on mac and linux, and I think in _theory_ windows 2000 should support them but it's really vague) Dec 29 14:07:37 I am on debian Dec 29 14:07:53 I will give that a shot seems much easier. I guess the default is usb Dec 29 14:07:54 if neither works you'll need to use its IP address (on the ethernet/wifi interface, i.e. not 192.168.7.2 or 192.168.6.2 since those are its IPs on the two USB interfaces) Dec 29 14:08:29 if you're on debian then you can probably just ssh to hostname.local, but if it's connected via both usb and ethernet it'll be random which one it will use Dec 29 14:09:14 (so just disconnect the usb and then try to ssh to .local) ... what's the default hostname of the bbai anyway? is it just "beaglebone" like the others? Dec 29 14:09:35 I followed your instruction and I just say bbai Dec 29 14:09:44 with the adjustments to that file Dec 29 14:09:58 i forgot which one you had me edit Dec 29 14:10:07 I will give it a go Dec 29 14:10:24 I actually need to find a plug Dec 29 14:11:20 hmm? oh, to change the hostname? either edit /etc/hostname or use the command "hostnamectl set-hostname" (followed by the desired hostname) Dec 29 14:12:14 since I got you here one more question. So I got the bbai to boot with the 7" panel and I can see the tux and logon info on the screen. That is what I had before on the black. I ran a simple qt demo and it loads but I cannot see anything else. Do you think the fact that it could display the tux and text correctly allows me to rule out the panel driver? Dec 29 14:33:50 yes Dec 29 14:34:52 my guess would be the qt app used the wrong display - on the bbai the video output via cape headers does not conflict with hdmi, so you'll now have two displays Dec 29 14:35:28 but that's just a guess Dec 29 15:40:13 ok that is good to know **** ENDING LOGGING AT Wed Dec 30 02:59:57 2020