**** BEGIN LOGGING AT Wed Jun 03 02:59:57 2020 Jun 03 03:00:47 are old bootloaders still a thing w/ the AI? Jun 03 03:04:30 that would be a zmatt type question Jun 03 03:04:37 Okay. No issue. Jun 03 03:08:12 GenTooMan: Do you deal w/ a lot of I/O? Jun 03 03:11:13 Okay. is the pwmchip0 interface on the AI supposed to be able to be altered from sysfs? Jun 03 03:15:31 I went into /dev/pwm too. NO go. Jun 03 03:27:06 set_ good question I wouldn't know. what was it on the BBB? Jun 03 03:45:26 BBAI. Jun 03 03:45:51 I am listening to a Element14 post on the AI and coming across issues. Jun 03 03:46:15 Anyway...I guess I can rehash the issue tomorrow or at a later date. Jun 03 06:57:44 set_: the BBAI has tons of pwm, not just two Jun 03 06:58:04 and the interface to userspace hasn't changed, that's a linux thing not a BBB/BBAI thing Jun 03 06:59:24 all potential pwm outputs on BBB vs BBAI: https://docs.google.com/spreadsheets/d/e/2PACX-1vR_yw3T67jWc4I7mjxl3NAyeFClZ_k27cvOWEuryKeA_5LTABJ54xelpHAtf8zXO3iLmN7K55Se5tHV/pubhtml?gid=150833013&single=true Jun 03 16:18:22 what is the 'best' way to read a text file on the beaglebone from a windows machine? I've got a statemachine running on my BB that relies on the data found in the text file on a windows machine on the same LAN Jun 03 16:39:41 m Jun 03 17:34:10 biggi: uhh, that's a really vague problem statement with an enormous solution space Jun 03 17:34:32 run a webserver on the windows? Jun 03 17:34:40 *windows machine Jun 03 17:34:43 or smb/cifs Jun 03 17:34:45 or ftp Jun 03 17:37:06 or do it the IdiOT way, some heath robinson contraption involving nodejs, cloud services, a few databases, and unintentional information disclosure Jun 03 17:40:08 https://xkcd.com/763/ Jun 03 17:42:37 lol Jun 03 19:12:19 Good ol' xkcd. Jun 03 19:57:21 I'm trying to send a binary file through UART with sx.. the BBB is sending "CCCC.." but I get Retry 0: NAK on sector Jun 03 20:16:14 what's on the receiving side? Jun 03 20:21:01 oh, the BBB is the receiving side Jun 03 20:21:11 ? Jun 03 20:24:44 it's the output of the sx command Jun 03 20:25:40 what is? Jun 03 20:26:13 "CCC" sounds like the xmodem receiver to me, not the transmitter Jun 03 20:26:55 I guess the "NAK on sector" message is printed by sx Jun 03 20:27:29 yes.. the BBB only prints CCC Jun 03 20:27:48 you're trying to uart-boot the BBB ? Jun 03 20:28:24 that's what it looks like to me Jun 03 20:28:47 yes Jun 03 20:29:10 loading a bare metal app Jun 03 20:29:22 why via xmodem? that sounds terrible Jun 03 20:29:31 why not put it on an sd card? Jun 03 20:29:36 or use tftp boot Jun 03 20:29:55 maybe that's not bare enough Jun 03 20:30:00 or metal enough Jun 03 20:30:21 tftp boot is extremely convenient for baremetal dev: after recompiling your program just hit the reset button and bootrom will download your executable straight from your computer Jun 03 20:30:24 are there heavy metal apps? Jun 03 20:31:12 I will try tftp..is there any guide? Jun 03 20:31:36 example config file for dnsmasq (which is both the bootp and tftp server): https://github.com/mvduin/bbb-asm-demo/blob/master/extra/dnsmasq.conf Jun 03 20:33:04 the file sent should be a raw binary (no MLO header), same as for UART boot Jun 03 20:34:31 to get the BBB to netboot via ethernet, pull sysboot2 (P8.43) down and sysboot0 (P8.45) up Jun 03 20:34:49 that makes the boot order { spi, sd, ethernet, uart } Jun 03 20:37:13 or instead of ethernet you can also use usb (bbb appears as rndis interface and then netboots the same as via ethernet). this option is in the default boot order (eMMC, sd, uart, usb) if you prefer wiping eMMC's boot sector over connecting wires, or you can pull down sysboot2 (or equivalently hold down the S2 button during power-up) to change the boot order to { spi, sd, usb. uart } Jun 03 20:39:55 I had a pulldown on 8.43, no SD card.. so it was on UART. But I will try tftp Jun 03 20:40:34 I can recommend it, it's easier than xmodem, faster than xmodem, and way more convenient than xmodem Jun 03 20:44:35 It blows my mind xmodem is still a thing. Jun 03 20:46:06 it's out there.. I don't know if as a thing Jun 03 21:02:33 Hello! I recently started using the PocketBeagle for the first time and I have been struggling with routing my internet connection to it via usb. I'm able to ssh into the beagle as well as access Cloud9 and ping back and forth without issue. However the moment I enable "Internet Connection Sharing" on my host Windows 10 PC, I lose and do not regain the ability to communicate with the Beagle (Until "Internet Jun 03 21:02:34 Connection Sharing" from my wifi adapter is disabled again). Any ideas on what to try? I have tried as many of the online guides as I could find and am happy to go into more detail on those efforts if needed. Any help is greatly appreciated. Jun 03 21:09:37 I know there exist people who have managed to get that scenario to work :) Jun 03 21:11:54 (I also know how I'd get it working, but not with Windows as host and not with networking on the BBB being handled by a magic blend of connman and bash scripts) Jun 03 21:14:50 generally speaking if your computer uses internet sharing (or bridging / proxy arp) to provide the bbb with networking then it should be a dhcp client instead of a dhcp server (which is what it is by default) Jun 03 21:20:18 and then locate the bbb by hostname instead of by ip (which may or may not work. I'd just use "beaglebone.local" to reach it, which works on Linux (usually), Mac, and it apparently should work on Windows 10) Jun 03 21:34:13 Yes, it looks like the PB is set up as a dhcp server and is properly assigning my Windows 10 PC to 192.168.7.1. I am able to ping beaglebone.local successfully when not sharing the internet connection but it takes about 13 seconds for it to start responding. Doesn't work when I enable internet sharing :( Jun 03 21:35:30 13 seconds after powering up you mean? I can imagine that, the default image doesn't boot very fast Jun 03 21:35:46 but yeah it's not going to work as long as the basic networking setup isn't working Jun 03 21:36:12 No, 13 seconds after starting the ping for it to respond. It responds immediately with SSH though. The delay is probably something else but I thought I'd mention it Jun 03 21:36:28 it's probably windows sucking Jun 03 21:37:07 Let me clarify: pinging with "beaglebone.local" : 13 sec VS pinging with "192.168.7.2" : instantaneous. Not sure if that's usual as I don't have lots of experience in the networking realm Jun 03 21:37:22 microsoft doesn't care much about standards and didn't support mdns (what's used to resolve .local addresses) at all until windows 10 Jun 03 21:37:42 I'm not surprised if it doesn't work well Jun 03 21:37:43 Hahaha I can definitely see it just being Microsoft Jun 03 21:39:09 You mentioned you're familiar with doing this sort of thing over Linux, right? Have you done internet via USB on linux with a pocket beagle? Jun 03 21:39:40 not with a pocketbeagle specifically but I have on the beaglebone, which should work identically in that regard Jun 03 21:40:04 the main difference is that if you screw it up on the pocketbeagle you potentially lose all ways to communicate with it Jun 03 21:40:55 I know that experience :) I've reflashed the microSD roughly 10 times now Jun 03 21:41:14 anyway, I don't know how to reconfigure usb networking to be a dhcp client rather than dhcp server, at least not without just getting rid of the setup scripts entirely and replacing connman by systemd-networkd, which I know how to configure appropriately Jun 03 21:42:28 I can probably write down some plausible steps but since I can't test them right now it'd still be a bit of a gamble Jun 03 21:44:24 Oh you're saying on Linux you'd need to reconfigure the beagle to be a dhcp client in order to connect to the host's internet connection? Jun 03 21:45:25 no I mean in general you should Jun 03 21:45:50 if you're sharing internet from your computer to the bbb then your computer will be the dhcp server (on the connection to the bbb) Jun 03 21:46:32 Interesting. In all the guides it maintains that the PB stays as the dhcp server but the host computer is specified as a gateway Jun 03 21:46:46 in all the guides I have read* Jun 03 21:47:22 that sounds like a bizarre configuration, dunno if windows can be convinced to accept that Jun 03 21:47:46 I'm guessing not, or at least you haven't had success in doing so since otherwise you wouldn't lose the ability to reach the bbb Jun 03 21:48:43 I do have a MacMini formatted unto Ubuntu. I tried to get internet via USB on it to no avail but I'll try again Jun 03 21:48:59 but maybe you can, if guides are saying they got it to work... I don't know anything about windows Jun 03 21:50:28 it would be nice if the bbb could auto-select between being a dhcp client or dhcp server based on whether an existing dhcp server is detected on the network Jun 03 21:53:28 a 3.3v usb-serial cable to access the pocketbeagle serial console would probably help being able to investigate and fix things on the pocketbeagle side when networking isn't working Jun 03 21:53:42 if you happen to have one Jun 03 21:53:50 Do you know what the reason behind windows hosts connecting via 192.168.7.2 and Linux/OSX connecting via 192.168.6.2 is? Jun 03 21:54:01 Not a bad idea. I'll have to search around for one of mine Jun 03 21:54:11 Microsoft is the reason Jun 03 21:56:30 the standard for Ethernet over USB is CDC-ECM, specified by the USB consortium all the way back in 2007. Microsoft however can't be bothered to implement the USB standard, they instead have their similar but proprietary "RNDIS" protocol Jun 03 21:57:07 so the bbb/pocketbeagle declares two usb networking interfaces, one for operating systems that implement the USB standard and one for microsoft windows Jun 03 21:58:03 (and even then it's frequently a struggle to convince Windows to actually load their own fucking driver for their own fucking protocol) Jun 03 21:58:34 192.168.7.2 is the RNDIS interface, 192.168.6.2 is the CDC-ECM interface Jun 03 21:58:39 (linux actually supports both) Jun 03 21:58:52 Yeah I noticed that on Linux which made me wonder Jun 03 21:58:58 Makes sense! Thank you for the info :) Jun 03 22:23:00 Still no dice with the Linux host :( However, the situation is different from the Windows 10 attempt. I am still able to ping between devices fine. The PB just cannot ping google or even 8.8.8.8 Jun 03 22:23:34 then it probably doesn't have a default gateway (check with "ip route") Jun 03 22:23:55 (or internet sharing isn't working) Jun 03 22:26:17 It's reporting "default via 192.168.6.1 dev usb1" where usb1 is set to "inet 192.168.6.2" and the corresponding device on the Linux host reports "inet 192.168.6.1" Jun 03 22:26:40 So the gateway seems to be set up (I added it earlier) Jun 03 22:27:35 And I used sysctl net.ipv4.ip_forward=1 and adjusted iptables to forward to the device on the host Jun 03 22:28:09 that's not how internet sharing works Jun 03 22:28:26 oh wait Jun 03 22:28:26 How would you go about doing it on Linux? Jun 03 22:28:31 you did it entirely manually, okay Jun 03 22:28:36 that can work, if you did it right Jun 03 22:29:36 I mean, I've generally only used bridging from ethernet to usb since I wanted the bbb to be reachable from the network Jun 03 22:29:48 If you're curious, I was looking through both of these guides and of course changing the devices to ones found on my system (and ip to 192.168.6.2) Jun 03 22:29:50 http://jpdelacroix.com/tutorials/sharing-internet-beaglebone-black.html Jun 03 22:30:17 Jesus incoming link Jun 03 22:30:18 https://www.elementzonline.com/blog/Sharing-Internet-using-Network-Over-USB-in-PocketBeagle#:~:text=Sharing%20internet%20using%20Network%2DOver%2DUSB%20in%20PocketBeagle,-Posted%20by%20dhanishvijayan&text=PocketBeagle%20features%20an%20incredible%20low,Ethernet%2C%20by%20default%20has%20192.168. Jun 03 22:30:36 I should note that trying to use three different network configuration mechanisms at once (the setup scripts that normally configure usb networking, connman, and ifupdown) sounds like a great recipe for a hot mess Jun 03 22:31:01 Yeah, I completely agree which is why I reflash it every time Jun 03 22:31:05 why did you copy all that? :P Jun 03 22:31:15 everythign after the # is fluff Jun 03 22:31:23 I realize that now, good point Jun 03 22:31:39 seeing "sudo su" is never a great start -.- Jun 03 22:31:57 and the use of the old and deprecated ifconfig utility Jun 03 22:33:15 oh what should I be using instead of ifconfig? I don't work too often on Linux networking stuff so I never knew there was a more updated version Jun 03 22:33:53 it looks like it could work, although it'll apply NAT to all traffic from your computer (so your computer won't be reachable from the LAN anymore) Jun 03 22:34:03 and of course this isn't persistent Jun 03 22:34:16 the "ip" utility is the replacement for "ifconfig" and "route" Jun 03 22:36:12 can you share (e.g. via pastebin.com or some other paste service) the output of "ip addr" and "ip route" on both your computer and the BBB, and the output of "sudo iptables -L" and "sudo iptables -t nat -L" on your computer? Jun 03 22:44:07 PB : https://pastebin.com/VZHKP4V5 Jun 03 22:44:36 Host : https://pastebin.com/mpqCWNiz (user and host renamed) Jun 03 22:46:30 and iptables? Jun 03 22:46:42 -L flag : https://pastebin.com/5q5Jh0T1 Jun 03 22:46:59 yeahhhh looks like your iptables is already being managed ;) Jun 03 22:47:20 oh it looks like -L needs some additoinal flag to actually show the info that matters Jun 03 22:47:37 -v probably Jun 03 22:49:15 https://pastebin.com/AM1m5bXz Last one Jun 03 22:49:22 Sorry had a few things that needed doing Jun 03 22:49:42 Ah let me get that Jun 03 22:49:46 sorry, add the -v option to both iptables commands Jun 03 22:50:28 Man I forgot how mangled this little guy is with Docker stuff. I probably don't need those anymore Jun 03 22:54:27 Nat -V : https://pastebin.com/eQAqDmrt Jun 03 22:55:35 -L -v : https://pastebin.com/1Pzi39G7 Jun 03 22:57:12 I feel like the FORWARD chain almost certainly also to ACCEPT packets from wifi to the bbb Jun 03 22:57:38 (or just set the policy of the FORWARD chain to ACCEPT) Jun 03 22:59:38 and I'd personaly limit the MASQUERADE rules to packets coming from the BBB IP ranges Jun 03 22:59:53 to avoid applying it to all traffic from your computer Jun 03 23:03:28 I had made the policy of the forward chain to ACCEPT in iptables but how would I do so in ip? Jun 03 23:06:10 ip has nothing to do with iptables Jun 03 23:07:09 Would "iptables --append FORWARD --in-interface devhere -j ACCEPT" Not do something similar to what you said? Sorry if I am being a little dense. I'm not familiar with this stuff Jun 03 23:07:38 Oh or are you saying you cannot configure with the "ip" command Jun 03 23:11:43 ip replaces ifconfig and route, it doesn't replace iptables Jun 03 23:12:28 Oh my bad, poor assumption Jun 03 23:12:47 and you can change the policy with iptables --policy FORWARD ACCEPT Jun 03 23:13:18 (there is a more modern replacement for iptables called nftables but let's ignore that) Jun 03 23:20:55 Just changed the policy to ACCEPT on FORWARD with still no success. Do I need to restart any services or anything? Jun 03 23:22:03 no Jun 03 23:22:16 sorry, I don't really have time to try to debug your network set up :) Jun 03 23:22:30 I haven't used iptables to setup nat in quite a while Jun 03 23:23:14 btw you seem to have multiple identical MASQUERADE rules... I doubt that's a good idea Jun 03 23:24:08 speaking of iptables, what is the port used for tftp? Jun 03 23:24:38 grep tftp /etc/services Jun 03 23:25:09 great Jun 03 23:28:11 Thanks zmatt for all your help. I really appreciate you spending your time to help and I understand the time issue. I'll use this knowledge to continue debugging on my own. Jun 03 23:47:55 zmatt: what is this line for? dhcp-host=c8:a0:30:c2:d8:04,192.168.1.167,barebone Jun 04 00:00:29 that's the static lease for your bbb Jun 04 00:00:39 macaddress,ip,hostname Jun 04 00:01:06 i.e. the ip given to it by the bootp server Jun 04 00:03:05 I need to find the macaddress, then the ip,hostname is what I choose? Jun 04 00:03:56 yep Jun 04 00:04:12 you can probably get the mac address simply by enabling dhcp logging Jun 04 00:46:55 sigh...even python can't sort its own dependencies out... what a POS **** ENDING LOGGING AT Thu Jun 04 03:06:17 2020