**** BEGIN LOGGING AT Mon Dec 14 03:00:00 2020 Dec 14 03:00:16 kubuntu is just ubuntu with KDE instead of Gnome or Unity or whatever Canonical is shipping this month. Dec 14 03:00:22 Oh. Wait. Dec 14 03:00:31 So, is there an Ethernet cable to your BBB? Dec 14 03:00:44 I haven't used ethernet over usb before, but I expected to see something like usb0. Dec 14 03:00:52 Yeah, I"m on wired right now. Dec 14 03:01:42 I could switch to wireless if the pocketbeagle wants to appear as eth0, though I thought I'd read somewhere that usb ethernet devices are usbN or something like that. Dec 14 03:01:42 Okay. You have a BeagleBone Black, usb to development desktop from the BBB, and an Ethernet cable in your BBB now? Dec 14 03:01:52 Oh. Dec 14 03:01:56 You have a pocketbeagle? Dec 14 03:02:11 Okay. Dec 14 03:02:14 No, I have a pocketbeagle connected by USB to a kubuntu machine connected to the net via ethernet. Dec 14 03:02:30 Okay. Dec 14 03:02:37 I misunderstood. Dec 14 03:03:06 So, you need USB networking that is shared from the Kubuntu machine. Dec 14 03:03:32 Yikes. Let me see if I can still find that shared internet connection via usb. Dec 14 03:03:47 Hmm. Here's an interesting thing. I see a couple of odd enx ethernet devices that I don't recognize,t hough I suspect there were there before I hooked up the beagle. Dec 14 03:04:46 What I understood the docs to say was that the beagle runs a DHCP server on 192.168.6.*, assinging itself to *.2 and handing out *.1. Dec 14 03:05:12 Yep. Dec 14 03:05:14 So I've been looking for an eithernet device on 192.168.6/24. Dec 14 03:06:04 Sharing via usb takes effort. https://gist.github.com/pdp7/d2711b5ff1fbb000240bd8337b859412 Dec 14 03:06:14 I found that a while back but i have not tested it. Dec 14 03:06:16 Again, I have never used usb ethernet, but I read enough to look for the usbnet driver and another one or two. Dec 14 03:07:59 Let me research the pocketbeagle again. It may have wifi. Dec 14 03:08:20 Hmm. Isn't that gist about letting the beagle access the rest of the world via the host's connection? Dec 14 03:08:41 I haven't gotten the host and the beagle connected yet so there is nothing to share. Dec 14 03:09:04 Oh. Dec 14 03:09:17 Wait, you cannot open a terminal via ssh? Dec 14 03:09:52 try ssh debian@192.168.6.2 Dec 14 03:10:18 There doesn't seem to be an ethernet device to connect to. I can try SSH, but if it can't see the web server at 192.168.6.2 I didn't think ssh could work either. Dec 14 03:10:31 Yep. Dec 14 03:10:33 It can! Dec 14 03:10:37 Neat, heh? Dec 14 03:10:41 USB networking! Dec 14 03:10:59 So far it's just hung. Dec 14 03:11:26 Hmm. So, you have usb pocketbeagle to usb dev. desktop? Dec 14 03:11:36 Yes. Dec 14 03:12:01 So far as I could tell, that's what the getting started docs said to do. Dec 14 03:12:26 ssh not going anywhere so far. Dec 14 03:12:45 I know someone must know how to diagnose this idea. Did you use etcher and find the image on beagleboard.org/latest-images? Dec 14 03:13:46 yes and yes. Dec 14 03:14:26 Okay. Man, it is usually just a simple ssh debian@192.168.7.2 or similar for their usb networking server. Dec 14 03:14:33 OK, ssh debian@192.168.6.2 finally timed out. Dec 14 03:14:55 Did you try @192.168.6.1 and @192.168.7.2? Dec 14 03:14:59 Right, but the device isn't being created. Dec 14 03:15:02 trurl314159: does the beaglebone seem to boot normally when you connect it to usb? (leds blinking and stuff) Dec 14 03:15:18 trurl314159: you're using linux on your host it seems, which distro? Dec 14 03:15:49 LEDs blink, though I don't know it's expected pattern. I think I get a blue one and another whole row of blue, which I assumed must indicate the initial boot. Dec 14 03:16:10 It's kubuntu, so identical to ubuntu except with KDE as the desktop. Dec 14 03:17:42 does the kernel log (monitor with "journalctl -k -f", control-C to exit) indicate a usb device connected? (this may take a bit after connecting, the beaglebone needs to start up first) Dec 14 03:18:09 Will check when the beagle's back up. Dec 14 03:19:07 you said you reflashed the beaglebone.. which image did you flash onto it? Dec 14 03:19:31 I just figured something out. When the board is up I have two strange ethernet devices named enx* where * is a long string of mostly digits. Dec 14 03:20:00 Those seem to be the board, but they do not have IPs so I can't simply connect to anything that way. Dec 14 03:20:01 those are the usb networking devices most likesly Dec 14 03:20:31 Right, I didn't recognize them before but I just took the board down and sure enough they're the beagle. Dec 14 03:20:42 They aren't terribly useful without IPs though. Dec 14 03:21:11 I didn't reflash it, I flashed an sd card. I don't think the pocketbeagle has any internal flash memory. Dec 14 03:21:13 sounds like maybe your network manager is failing to bring them up Dec 14 03:21:18 ah, pocketbeagle, my bad Dec 14 03:21:36 right, I misread, you said you flashed an sd card and booted it from that Dec 14 03:21:53 and correct, the pocketbeagle does not have eMMC Dec 14 03:22:31 OK, the downloaded file was bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz. Dec 14 03:22:37 yeah that's fine Dec 14 03:23:37 Yes, so now that I noticed those enx* devices, it *is* getting usb ethernet partly set up, but somehow they aren't actively connected. Or something. Dec 14 03:24:08 I'm sure that one was listed for the pocketbeagle, but I will double-check. Dec 14 03:24:17 so, most network managers should bring the interfaces up automatically.. the exceptions I know of are wicd and very old versions of gnome network manager, neither of which support having multiple interfaces up at the same time Dec 14 03:25:31 I know I can do that, as I"ve had both wired and wireless connections active simultaneously. Dec 14 03:26:20 do the network interfaces show in the gui for network connections? Dec 14 03:27:02 Mmm. Now that you ask, yes. Which suggests I could connect manually. Good observation. Dec 14 03:27:21 I see /var/log/syslog shows info. about the network manager on kubuntu! Dec 14 03:27:24 still strange it doesn't connect to them automatically Dec 14 03:27:52 Yes, I was blindly following the instructions. Dec 14 03:28:39 OK, I just connected to one, and two things are interesting. One is that the IP it received is *.7.1, even though the docs say it will be *.7.* only on Windows and 6 on Linux. Dec 14 03:29:01 Second, it took over eth0, so that would have conflicted with my wired connection before. Dec 14 03:29:01 one will be 192.168.7.1/24, the other will be 192.168.6.1/24 Dec 14 03:29:11 "took over" ? Dec 14 03:29:25 it should have nothing to do with your ethernet Dec 14 03:29:58 server for usb networking! Dec 14 03:30:06 Well, I guess I mean it's just named that. I thought that name was only used by the ethernet card, but I don't really know. Dec 14 03:30:54 And yeah, when I selected the other it disconnected eth0 from *.7.* and reconnected eth0 as *.6.* Dec 14 03:31:23 the reason there are two interfaces is because one uses one of the usb standard protocols for ethernet networking, while the other uses microsoft's proprietary RNDIS protocol because microsoft as usual doesn't give a fuck about implementing standards. linux supports both, hence both show up Dec 14 03:31:30 uhh, you're not making sense Dec 14 03:31:49 you said earlier that the interfaces are named "en" followed by a string of hexadecimal digits Dec 14 03:32:28 The good news is that connected that way I can hit the beagle webserver. Dec 14 03:32:35 what does "ip addr" on the terminal show? Dec 14 03:32:37 I agree, I don't understand it either. Dec 14 03:32:55 it sounds like your network manager or its gui is just confused somehow Dec 14 03:33:02 what kubuntu version are you using? Dec 14 03:34:03 Focal, whatever version striing that corresponds to (just looked in /etc/apt/sources.lst to be sure I had the right one). Dec 14 03:34:12 The latest, at least as of not too long ago. Dec 14 03:34:29 Yes, there seems to be some confusion. Dec 14 03:34:32 very odd Dec 14 03:34:36 I know now, Gorilla is the one used. Dec 14 03:34:58 focal should be fine, I just wanted to verify it wasn't a very old release Dec 14 03:35:38 So at the command line, ip addr says that eth0 is not connected, and one of the enx* devices is connected to 192.168.6.1. That makes sense. Dec 14 03:36:30 However, the desktop widget says that network connection is eth0(enx*). Dec 14 03:36:37 And that eth0(eth0) is not connected. Dec 14 03:37:03 I cannot see why it should be associating eth0 to the connected usb device, but it is. Dec 14 03:37:40 ifconfig agrees with ip addr and says nothing about eth0 being associated with enx* Dec 14 03:38:25 Linux graphical tool is mostly but not quite correct on something. Film at 11. :D Dec 14 03:38:44 Well, the most important thing here is that there is a way to talk ot the board. Dec 14 03:38:53 Even if it mysteriously isn't automatic. Dec 14 03:39:42 Sometimes people cancel their automatic usb device detection for source dev. Dec 14 03:39:49 I mean, you can try actually *talking* to the board... it won't reply, but it's a great listener ;) Dec 14 03:39:58 set_: ??? Dec 14 03:40:00 i have seen that happen. Dec 14 03:40:09 Wha? Dec 14 03:40:12 I have! Dec 14 03:40:42 I had to cancel my auto. usb detection to get into uboot before. Dec 14 03:41:10 set_: I have no idea what you're talking about Dec 14 03:41:25 No issue. I can explain if it is necessary? Dec 14 03:41:49 Hmm. This is fun. I think they did not adapt the web interface for the pocketbeagle. Dec 14 03:41:56 See, automatic usb detection on computers is an option. Dec 14 03:42:04 trurl314159: what does "nmcli d" show? Dec 14 03:42:16 It wants to upgrade debian, and offers advice on how to get connected to wifi. The pocketbeagle doesn't have wifi. Dec 14 03:42:44 trurl314159: yeah there's just one set of documentation Dec 14 03:43:07 Hey, that's a very nice tool I didn't know about. Dec 14 03:43:20 Same as the other command line tools, but with much prettier output. :D Dec 14 03:44:06 nmcli is specific to network-manager, while "ip addr" just shows what's configured in your kernel and is agnostic to how networking is being managed Dec 14 03:44:21 (i.e. "ip addr" will also work on a beaglebone, "nmcli" won't) Dec 14 03:44:40 As is ifconfig. I probably use that because it was around in the 90s when I started using LInux. Dec 14 03:44:56 yeah, ifconfig is the old (and long deprecated) tool Dec 14 03:45:18 I do agree that the output of "ip addr" is.. not great Dec 14 03:45:37 like, maybe some of that stuff should have been hidden under a --verbose option or something Dec 14 03:45:39 Oh, wait, I didn't read carefully. nmcli does show the oddness, because it shows the connected enx device as "eth0" in the far right CONNECTION column. My bad. Dec 14 03:46:02 well that's just silly Dec 14 03:46:33 I tend not to care if things are deprecated if I like them better (the output is definitely better than ip) and I don't think they're likely to get away with removing the tool I'm used to. Dec 14 03:47:01 And tools that people used in thousands of admin scripts tend to live forever. Dec 14 03:47:28 @zmat Dec 14 03:47:36 the problem is that ifconfig can't handle the full flexibility of networking configuration and in some cases may give misleading or confusing output Dec 14 03:47:48 Er, that was odd. But then, I'm using IRC on my phone through a web interface, so why wouldn't it be odd. Dec 14 03:48:16 I know. They've been saying that for a long time. :D Dec 14 03:48:44 the problem with "ip addr" is that it's a disorganized info dump :P Dec 14 03:49:01 And even harder to read than that description suggests. Dec 14 03:49:16 Yes, that's why I don't care if ifconfig is deprecated until it actually becomes a problem for me. Dec 14 03:50:08 there is a history of new unix tools being harder to use for simple jobs than the old ones. Dec 14 03:50:42 So I guess mainly I just connect to the board manually. Dec 14 03:51:17 So I guess mainly I just connect to the board manually. Dec 14 03:52:23 you could set the interfaces up in /etc/network/interfaces (which will cause them to become "unmanaged" by network-manager) Dec 14 03:52:40 I suspect we're not going to fix the auto connection, and really it doesn't matter. Dec 14 03:52:57 The main thing is that my son can use it. This is really for him. Dec 14 03:54:00 He got the pocketbeagle as swag as the local Linux convention quite a while ago, and I kept putting off figuring it out for him. That and he was having a lot of trouble focusing on getting his homework done, and he didn't need another more fun thing to do. Dec 14 03:54:19 He's got time tonight and tomorrow, so I wanted to get it working for him. Dec 14 03:54:52 I"m going to give it to him so he can play tonight. Dec 14 03:55:11 putting a configuration block like this (with NAME replaced by the interface name) in /etc/network/interfaces should bring it up automatically: https://pastebin.com/raw/4zBXBaUm Dec 14 03:55:13 So no more experiments unless someone can think of one I need to do iright now. Dec 14 03:55:27 Ah, interesting. Dec 14 03:55:51 Make a Cape? Dec 14 03:56:01 assuming ubuntu still has debian's old ifupdown installed in addition to network-manager Dec 14 03:56:16 (if not then that file will not exist) Dec 14 03:56:27 Yeah, ifup/down are still there. Dec 14 03:57:19 okay. ifupdown generally sucks but I don't know enough about network-manager to be able to figure out why it's refusing to bring the interfaces up automatically for you :P Dec 14 03:57:25 (I use systemd-networkd myself) Dec 14 03:57:58 I could do that. I do have a slight aversion to changing defaults though. When I started using Linux (when Slackware was the most popular of all distros, I must have just missed using SLS LInux), I did what everyone else does and configured everything to my likeing. Dec 14 03:58:57 this shouldn't cause any problems, especially since those long interface names are MAC-derived hence souldn't conflict with anything else you might hook up to the computer in the future Dec 14 03:58:58 After a few decades (apparently I'm a slow learned) I realized that I had more trouble figuring out what I'd done later and how it interacted with other stuff, like upgrades, tthan I did with defaults. Dec 14 03:59:10 Even keeping extensive logs of what I did. Dec 14 03:59:33 I use etckeeper which turns /etc into a git repository Dec 14 03:59:51 (with automatic commits before and after installing packages) Dec 14 03:59:53 So now I'm falling off the other side of the horse, as Ambrose Bierce said, and minimzing it. That change, though, is pretty safe. I doubt that subsystem will ever change. Dec 14 04:00:23 I agree, that one isn't a problem. Dec 14 04:02:40 heh, I just remembered I once wrote a small utility that produces this as output: https://pastebin.com/raw/NLKBv2Kn (I partially masked the IPv6 addresses for privacy) Dec 14 04:03:19 ah it looks like it's unfinished.. missing "dev INTERFACE" Dec 14 04:03:54 which is probably why I named it "test" Dec 14 04:06:26 it really shouldn't be hard to polish that into something that produces info in a format that's easily readable... like, I've gotten used to the output of "ip addr" but really there's no excuse for it Dec 14 04:09:53 Darn it. Using it on my phone sucks. I stepped away for a minute, so it went to sleep and disconnected me. Dec 14 04:10:02 And of course that flushes the history. :( Dec 14 04:10:21 why are you using irc on your phone instead of on your computer? Dec 14 04:12:01 Arg. Clearly I shouldn't. Dec 14 04:12:33 The reason is I was away from the computer and researching this problem on my phone when I stumbled across the IRC channel. Dec 14 04:12:49 And apparently I"ve been punished properly for it. Dec 14 04:13:01 lol Dec 14 04:13:35 transcript of what you may have missed: https://pastebin.com/F5FatuhR Dec 14 04:13:36 I used to use xchat, but it looks like I don't even have it installed. I use IRC pretty rarely. Dec 14 04:14:15 I realize no one will believe both that and the fact that I''ve been using unix since the 80s. I should be a lifelong IRC addict. Dec 14 04:19:08 That other Trurl is me on a real computer. Dec 14 04:19:47 I have joins/quits hidden to keep chat from scrolling off the screen by (sometimes spammy amounts of) joins/quits Dec 14 04:20:14 I regret missing the opportunity to do a little improv theatre with my two alter-egos arguing deep existential issues about who is the real Trurl. :D Dec 14 04:20:40 don't worry, noone would have questioned it :P Dec 14 04:20:54 I' Dec 14 04:21:01 I'm just having fun. Dec 14 04:21:09 No you aren't. Dec 14 04:21:15 Yes I am. Dec 14 04:21:18 :D Dec 14 04:21:19 -.- Dec 14 04:23:05 So strangely, the board didn't immediately work on my Son's machine. It could be because I didn't install the recommended udev rules, or because I did a stupid thing when I installed it to save disk space and started with a minimal install. I bought a brace of inexpensive laptops for school work, but the minimal install often behaves in ways I just don't have time to debug. Dec 14 04:23:18 bi ydev rykes are beeded Dec 14 04:23:42 okay I didn't watch what I typed and my hands were misaligned, lol Dec 14 04:23:50 no udev rules are needed Dec 14 04:24:05 I wondered. They did look like they were for something different. Dec 14 04:24:27 I heartiy regret doing a minimal install, though the disk space is pretty modest. Dec 14 04:25:16 still, network-manager is installed evidently, I don't see why it would behave differently than normal Dec 14 04:25:21 Me neither. Dec 14 04:25:33 there's probably a logical explanation, but like I said I don't really know NM all that well since I don't use it myself Dec 14 04:25:57 I occasionally have the temptation to just go back to Slackware, where nothing ever changes ever. Dec 14 04:26:21 But then I remember how inconvenient it can be. Dec 14 04:27:36 But yeah, I don't take full advantage of the graphical tools. I often treat KDE as a glitzy, super heavyweight GNU screen: more terminal and editor windows. Dec 14 04:30:48 So he did get it to work. Dec 14 04:30:52 looking to see if I have a screenshot of what my graphical desktop looks like... Dec 14 04:31:56 Now that I'm not likely to lose the history, would you all mind re-posting the links for the iptables rules for sharing the connection and for doing the auto-connect? Dec 14 04:32:19 Might as well make hacking the board work more nicely for him. Dec 14 04:32:32 <@zmatt> putting a configuration block like this (with NAME replaced by the interface name) in /etc/network/interfaces should bring it up automatically: https://pastebin.com/raw/4zBXBaUm Dec 14 04:33:15 Ah, yes, that was it. Dec 14 05:34:36 Was off doing daddy things. Thanks for the help, guys. Eric is all set with the board. Dec 14 05:35:23 I think it's just dawning on him that you have to do hardware to do anything with the pocketbeagle. It will be interesting to see how that goes. Dec 14 05:56:27 trurl2718: I mean, you don't *have* to, but otherwise it's just a really crappy linux computer :P Dec 14 13:33:03 hello can anyone help me in getting how to set the clock for i2c communication in beagle bone Dec 14 13:54:38 hi Dec 14 13:55:13 hi Dec 14 13:56:16 suddenly someone has worked integrating the at1ilc1000 module with the beaglebone Dec 14 15:15:38 zmatt: "I mean, you don't *have* to, but otherwise it's just a really crappy linux computer :P" -- That's why I said "Interesting." :D Well, if he's interested enough, he can learn some basic electronics, which is always good. Dec 14 15:21:10 do be careful with actually connecting stuff though... the AM335x on the beaglebone/pocketbeagle does not have the electrical robustness of arduinos and such Dec 14 15:21:39 Uh, oh, good to know. Dec 14 15:22:12 I didn't pick it as a first embedded board. It was convention swag, and he wants to use it for that reason. Dec 14 15:22:42 Hmm. Well, I have good EEs at work who would answer questions if I don't pester them too much. Dec 14 15:24:17 I haven't enirely figured out the beagle's niche, what it's specialized for and how it differentiates itself. The realtime coprocessors are very interesting, but he doesn't know enough to take advantage of that. Dec 14 15:26:15 most important bit is to not expose any I/O to voltages that (relative to GND) are below 0V or above the I/O supply (3.3V while powered on, 0V while powered off) .. and definitely never more than 0.5V outside that range Dec 14 15:28:03 the AM335x (the SoC in the beaglebone (except AI) and pocketbeagle) is primarily targeted at industrial markets Dec 14 15:29:54 PRUSS is indeed its single best feature, though it has a lot of other nice I/O capabilities (e.g. a bunch of PWM outputs, things that can perform pulse width/distance measurements with 10ns precision, quadrature decoders, and the usuals like i2c, spi, uart, yada yada) Dec 14 15:35:04 and the beaglebone/pocketbeagle is great if you want to prototype a design but eventually move to a custom pcb... the bbb and pocketbeagle designs are open, and the AM335x is easily available in small quantities (down to single units) Dec 14 15:36:27 (which can be contrasted with e.g. the broadcom SoC used on the RPi, which has no product page, no real documentation from broadcom (just a tiny bit of info written by someone from the rpi foundation), and which is not available at all - broadcom is not interested in dealing with small fish) Dec 14 15:43:30 also octavo. Dec 14 15:43:48 expensive but it has a kitchen sink Dec 14 15:46:03 yeah, octavo make AM335x-based modules that makes them even easier to use by integrating the most difficult parts (DDR3 ram and PMIC).. they recently even made one with integrated eMMC, shown off by being able to run like this: https://twitter.com/pdp7/status/1100349116515827712 Dec 14 15:46:13 but indeed they're kinda expensive Dec 14 15:46:55 and you can do a 2 layer board. maybe even 1.. Dec 14 15:47:51 (if you don't need to comply with EMC regulations anyway :P ) Dec 14 15:49:54 an initial prototype of the pocketbeagle (then "pocketbone") was 2-layer, but the final pocketbeagle is 4-layer Dec 14 15:50:29 (the BBB is 6-layer) Dec 14 15:58:51 I discovered the /sys/kernel/debug folder, and it is immensly helpfull. Dec 14 15:59:36 that's debugfs, and indeed it is Dec 14 16:00:21 are those only things with a debug option checked in the kernel though? Dec 14 16:00:28 no Dec 14 16:00:57 though I'm sure the amount of info available via debugfs may vary dependent on kernel config Dec 14 16:01:41 excellent. Dec 14 16:26:35 Hello, anyone here? Having problems with the PocketBeagle and interfacing a 2.4in TFT LCD Display, from how to install the drivers required to run the display, to modifying or writing existing code to display images Dec 14 16:37:30 what's the issue? Dec 14 16:38:59 do make sure you follow the device tree binding terminology matching your kernel version. I ran into a problem where the terminology changed between the kernel i was on and the examples provided expected kernel. Dec 14 17:32:55 Hi Guys, I am trying to run Precosion Time Protocol (PTP) on beaglebone black. I have downloaded the LinuxPTP package. However, I am getting while using PTP4l as it shows command not found. Dec 14 17:34:24 Do I need to connect internet in beaglebone black via USB or via Ethernet cable for PTP function? Dec 14 17:41:43 hardware timestamping is only available via Ethernet, not usb networking Dec 14 17:42:58 (ptp can be used on any network interface when using software timestamping, but this will result in high jitter / poor accuracy) Dec 14 17:55:12 So if I am using ethernet for time sync then do I need to use USB for internet connection? Dec 14 17:56:13 I am using Putty to ssh my beaglebone black using USB cable to power them and Ethernet cable for internet. I have cloned the LinuxPTP source file from Github and Ethtool -T eth0 is working fine. The only problem is when I am writing the command "ptp4l -i eth0 -H -2 -m", the output is bash:ptp4l: command not found. Can you let me know why this Dec 14 17:56:13 error is occurring? Dec 14 17:56:49 because "command not found" Dec 14 17:57:09 Can you tell me how to solve this problem? Dec 14 17:57:26 arrange for it to be found Dec 14 17:57:38 I ma so sorry I am a power Engineer PhD STUDENT and using Linux and beaglebone for the first time for a small connectivity in my designed device Dec 14 17:57:38 if you're trying to run an executable you compiled but didn't install (i.e. that's sitting in the current directory) you need to invoke it like ./ptp4l Dec 14 17:57:51 this isn't a beaglebone thing, this is basic linux Dec 14 17:58:20 So how to invoke it? As I can see that the PTP4l is in the LinuxPTP package. Dec 14 17:58:58 So should I just type $ ./ptp4l and it will get sorted? Dec 14 17:59:46 if that's where it is located Dec 14 18:00:08 Its located in the LinuxPTP package. Dec 14 18:00:20 what do you mean by "package" here Dec 14 18:00:52 I mean the LinuxPTP folder which I cloned from github Dec 14 18:00:53 you didn't install a package, you said you cloned the source code from github Dec 14 18:01:02 Yes. Correct. Dec 14 18:03:07 in general to run a program that's not installed, you need to invoke it by providing a path to the executable, not merely its name Dec 14 18:03:35 . refers to the current directory, hence if it is located in the current directory then it would be ./ptp4l Dec 14 18:30:36 Hi I am trying to run LinuxPTP in beaglebone black. I want to know I have connected Beaglebone in putty using USB ip address i.e 192.168.7.2, my query is that do we need to ssh multiple beaglebone (Master and slaves beaglebone blacks) at the same time for running LinuxPTP in putty? If yes, then how can we ssh multiple beaglebone at the same time Dec 14 18:30:36 since the ip address of all the USB cables for all beaglebone are same? Dec 14 18:31:13 aren't you going to connect them to an ethernet network anyway? why bother with usb networking at all? Dec 14 18:31:54 To give the power to BBB? Dec 14 18:32:04 what does that have to do with networking? Dec 14 18:32:40 My point is if I am using Ethernet for the internet then how to have the ip address to log in to putty? Dec 14 18:33:24 give them different hostnames, e.g. "sudo hostnamectl set-hostname beaglebone2" (replace "beaglebone2" by desired hostname) Dec 14 18:34:02 then connect to them by hostname (depending on network details usually either just the bare hostname ("beaglebone2") or the hostname with .local added ("beaglebone2.local") should work) Dec 14 18:34:31 So do these hostname need ip address details to log in for the first time in putty? Dec 14 18:34:39 ? Dec 14 18:35:05 if your ethernet network has a home router or something like that, it will assign IP addresses and (usually) ensure you can find them by hostname Dec 14 18:36:03 Yes so If I am connecting more than 1 BBB in putty all the BBB will have same ip address as they are assign to the same home router ip address. will this be a problem? Dec 14 18:36:13 uhh what? Dec 14 18:36:20 no, they will get different ip addresses Dec 14 18:36:52 a home router isn't going to assign the same ip address to two different devices Dec 14 18:38:06 OK. Got it. My other problem is can i switch on 2 BBB at the same time in putty? Dec 14 18:38:46 how exactly do you imagine you could switch a device on in putty, that doesn't even make sense Dec 14 18:39:31 I have to use PTP precision time protocol in which one BBB is Master and others are slave Dec 14 18:39:43 I want to transfer time packets between these BBB Dec 14 18:39:49 ptp sorts all that out automatically Dec 14 18:40:23 So you mean first I log in master in putty and then slave BBB one at a time. and it will work? Dec 14 18:40:44 it doesn't matter in which order you start them or with which timing Dec 14 18:41:31 ptp automatically detects new devices and the devices collective chooose a master among them Dec 14 18:41:38 *collectively Dec 14 18:41:59 ok got it. My last problem is the one which I just asked 10 minutes back. How to solve that PTP4l:command not found when I cloned LinuxPTP in my BBB Dec 14 18:42:40 I fully explained that. if you need more help with basic linux usage, this is not really the place for that. maybe look for some online resources for learning to use linux for beginners Dec 14 18:43:16 Should I download the LinuxPTP package in place of making a clone of it? Dec 14 18:43:24 Is their any difference in that? Dec 14 18:44:14 you can also just install the package with "sudo apt install linuxptp" instead of compiling it from source code Dec 14 18:44:26 Yes I did the same Dec 14 18:44:51 bu that PTP4l error is coming. You said invoke the ptp4l command Dec 14 18:45:00 I will go and search about it. Dec 14 18:45:48 Thanks a million Dec 14 18:45:59 you installed the package? why did you say something completely different earlier? Dec 14 18:46:27 I am sorry. I got confused as I cloned something which I mixed with this Dec 14 18:46:36 Yes I installed the package Dec 14 18:46:43 with sudo-apt command Dec 14 18:47:16 then you should be able to invoke it with "ptp4l" ... or, well, "sudo ptp4l" since it probably needs root privileges Dec 14 18:48:15 ptp4l -i eth0 -H -2 -m i AM WRITING THIS COMMAND Dec 14 18:48:33 though with or without sudo it should find the command, so if it doesn't then either you failed to install the linuxptp package or something is very messed up about your system Dec 14 18:48:34 and its saying bash: ptp4l: command not found Dec 14 18:48:55 I can see the linuxPTP package in my system Dec 14 18:49:23 I am login in to putty via 192.168.7.2 USB ip address Dec 14 18:49:53 you can't "see" an installed package Dec 14 18:50:01 forget the stuff you cloned, that is not useful Dec 14 18:50:11 ok. Dec 14 18:50:18 what does "dpkg-query --show linuxptp" say? Dec 14 18:50:33 I have to check that. Give me a minute please. Dec 14 19:25:08 hi Dec 14 19:26:27 Someone has integrated the atwilc1000 module with the beaglebone Dec 14 19:28:24 Hi I am trying to run LinuxPTP in my beaglebone black Dec 14 19:28:40 I got an error saying selected /dev/ptp0 as PTP clock Dec 14 19:29:03 Can you guide me whats the problem? Dec 14 19:30:31 This error occurred when I typed ptp4l -i eth0 -H -2 -m Dec 14 19:46:38 I do the cross compilation to be able to add the drivers, also create the device tree for the beaglebone but when I try to start the device I have the following error Dec 14 19:48:31 [ 20.007826] WILC_SPI spi1.0: Failed cmd response, cmd (cf), resp (00) Dec 14 19:48:31 20.205702] WILC_SPI spi1.0 wlan0: ERR [wilc_mac_open:1029] Failed to initialize wilc Dec 14 20:17:05 Hi has anybody interact with ina219 (I2C)? Can't run it with any example on pocketbeagle board. I took this C++ library, but the garbage (exept voltage) is shown : https://github.com/regisin/ina219 Dec 14 20:17:37 tried also https://pypi.org/project/pi-ina219/ Dec 14 20:56:28 https://github.com/geeekpi/upsv3 that's work. Thanks to all) **** ENDING LOGGING AT Tue Dec 15 02:59:57 2020