**** BEGIN LOGGING AT Fri Dec 13 02:59:58 2019 Dec 13 08:46:40 anybody have any ideas how to get gpio access on the beagleboard x15 Dec 13 08:46:53 without getting a printed pcb board Dec 13 08:47:21 yeah the expansion headers on the bbx15 are not very experimentation-friendly Dec 13 08:51:19 :( Other question, I was looking into the beaglebone AI because it has the 2 c66x DSP chips.. From the diagrams, I only see it supports a maximum of 6 video inputs. unlike the beaglebone x15 that was 3 Video input ports (VIP), which you can mux and make 8 channels work. Dec 13 08:52:09 I need 8 video input channels for what I am doing, you think it is possible for the beagleboard AI? Dec 13 09:42:27 vin1a_d0 Video Input 1 Port A Data input Dec 13 09:42:32 vin1a_d7 Video Input 1 Port A Data input Dec 13 09:43:07 still learning this... does vin1a_d0-vina1_d7 mean I can use any pin? Dec 13 09:45:33 nevermind Dec 13 12:09:29 whoops, got distracted Dec 13 12:27:55 zmatt you get distracted? Dec 13 12:28:03 it happens Dec 13 13:17:29 hello Beagles! Dec 13 13:19:12 https://www.youtube.com/watch?v=ZjYjjLJtGpo Dec 13 13:20:02 AC/DC - Givin the dog a bone. Dec 13 13:23:02 Well, anyway I'm tryin to get OpenBSD to boot from SD card, which works if I press the boot button Dec 13 13:23:42 but I don't want to press that button everytime I start a network of SBC Dec 13 13:24:31 I need to change uenv.txt in /boot Dec 13 13:24:34 build a robot to press it for you ? Dec 13 13:24:58 my skills are not 1337 for that Dec 13 13:25:19 great idea though Dec 13 13:25:46 I managed to start the boot prompt Dec 13 13:26:14 where i can enter commands like save, setenv ... Dec 13 13:26:25 fatload Dec 13 13:27:00 I managed to setenv mmc 1, but it is not saved Dec 13 13:27:13 tick: there is no editor in the uboot shell. why not just modify the file through your host machine? Dec 13 13:28:50 that is what I tried first, but I didn't find the file there Dec 13 13:29:25 well, I can try now... Dec 13 13:29:58 i didn't find uenv.txt Dec 13 13:30:30 which is supposed to be in /boot Dec 13 13:32:08 acutally, if i'm not super completely mistaken, a sufficiently recent u-boot should try to boot from the sdcard frist. Dec 13 13:33:10 afaik and experienced, it never boots from SD card first, except I press that button Dec 13 13:33:56 maybe I missed the docs on some place Dec 13 13:34:38 well i usually force sdcard booting usually wither through just wiping the emmc or setting the sysboot pins. but thats just me Dec 13 13:35:38 my emmc doesn't boot correctly anymore, since I tried to install OpenBSD Dec 13 13:35:53 only if I press the button it boots to openbsd Dec 13 13:36:24 I will write down my erros Dec 13 13:37:36 load address: 0x82000000 Loading: T T T T T T T Dec 13 13:37:45 after that nothing happens Dec 13 13:38:05 can you just wipe the emmc? Dec 13 13:38:35 How am I supposed to do that? Dec 13 13:38:40 when having booted from sdcard, something like flasherase.. sorry don't completely remember it myself, don't need it often Dec 13 13:41:05 so if I wipe the emmc, it will boot from sd card after that? Dec 13 13:43:16 well anyway, thank you for the hints/advice Dec 13 13:47:04 yeah, it should work like that. Dec 13 13:49:29 right now, I have the sd card in debian, open the Boot directory Dec 13 13:50:29 and there are files like am335x-bone.dtb am335x-boneblack.dtb etc Dec 13 13:50:56 if i open those files, they are not readable to usual editors Dec 13 13:51:33 .dtb -> device tree binary Dec 13 13:51:34 according to manuals, there should be uEnv.txt and I should remove a comment like this Dec 13 13:52:27 # cmdline = init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh Dec 13 13:52:40 but I canot find that file in boot Dec 13 13:53:20 * /boot Dec 13 13:54:15 I#ve got an EFI directory, there is boot and bootarm.efi Dec 13 13:58:08 that's were i'm stuck right now Dec 13 13:59:03 then there was a manual that said to go to boot prompt and execute 2 commands Dec 13 13:59:23 fatload mmc 0 0x82000000 MLO Dec 13 13:59:32 setenv mmc 1 Dec 13 13:59:35 and save that Dec 13 14:07:49 lol Dec 13 14:08:17 mixing instructions from openbsd and debian, yeah that's going to yield excellent results Dec 13 14:16:45 Back again Dec 13 14:17:16 My debian shut down Dec 13 14:17:35 Par: you're "tick" ? Dec 13 14:17:36 if someone answered my question, I couldn't read it Dec 13 14:17:39 yes Dec 13 14:17:51 so, some stuff you said is specific to debian, not openbsd Dec 13 14:18:04 interesting, but makes sense Dec 13 14:18:06 basically, the only instructions relevant for openbsd will be those specific to openbsd :P Dec 13 14:18:30 but, as far as your original question goes: if you wipe eMMC then you won't have to hold down the S2 button, it'll boot from sd card by default if eMMC isn't bootable Dec 13 14:18:43 great Dec 13 14:18:43 (wiping sector 256 of eMMC suffices) Dec 13 14:19:31 when do i need to use the boot prompt? Dec 13 14:20:01 kernel recompile? Dec 13 14:22:16 Now i need to find a way to wipe the eMMC Dec 13 14:22:35 what? Dec 13 14:22:59 wiping the sectotr 256 of eMMC Dec 13 14:23:01 boot prompt? kernel recompile? what are you talking about? Dec 13 14:23:36 when it boots, i can stop the process and there is a > Dec 13 14:23:53 I don't know anything about openbsd, on linux I'd do sudo blkdiscard /dev/mmcblk1 to wipe eMMC entirely or sudo dd if=/dev/zero of=/dev/mmcblk1 seek=256 count=1 to wipe only sector 256 Dec 13 14:24:16 maybe the dd command works on openbsd too, but you'd need to check which device is eMMC Dec 13 14:24:30 maybe it could be done in u-boot but I have no idea Dec 13 14:24:54 eMMC is the memory on the beagle. Dec 13 14:25:02 Par: any particular reason why you bruden yourself with the way less documented an popular openbsd instead of just linux if you're already struggling with the basics? (e.g. what the u-boot console is and does, etc.) Dec 13 14:25:22 if you choose to use an extremely uncommon OS on an embedded system, I feel like you should be very familiar already with both the OS and the embedded system in question Dec 13 14:26:59 I try to learn. my way may not be the best way, but that's what I'm stuck with. Dec 13 14:27:31 why exactly? Dec 13 14:27:38 why not just use debian? Dec 13 14:27:59 "i have no clue of walking, but hey, i'm gonna learn competition dancing right now!" Dec 13 14:28:09 * LetoThe2nd shrugs Dec 13 14:28:36 Par: feel free to, but please don't be surpised if you're having a hard time in getting support. Dec 13 14:28:57 I'm thankful for the support I'm getting right now. Dec 13 14:35:59 I have used debian, both on my laptop and on beaglebone. It worked like a charm. without any need for boot console. Dec 13 14:36:46 so because's masochistic and hate it when stuff just works, you've decided to try openbsd instead? Dec 13 14:37:00 to study something new? Dec 13 14:37:08 like BSD? Dec 13 14:38:29 :) Dec 13 14:39:08 flame war or simple trolling? Dec 13 14:39:31 I wasn't being very serious... I have nothing against openbsd Dec 13 14:39:47 but against noobs? Dec 13 14:39:58 lol Dec 13 14:40:08 but it is a simple fact that if very few people use a particular OS on a particular device, you'll probably need to be good at solving problems yourself Dec 13 14:41:21 since almost nobody here (except kremlin) will know anything about running openbsd on a beaglebone, and if you'd ask in #openbsd then almost nobody there will know anything about running openbsd on a beaglebone Dec 13 14:43:22 just asking, that's what the guide says: don't ask to ask Dec 13 14:43:39 and you got some answers :) Dec 13 14:43:53 but the details (e.g. on how to wipe eMMC) are openbsd-specific Dec 13 14:44:25 unless you boot a debian sd card, then you can just use sudo blkdiscard /dev/mmcblk1 Dec 13 14:49:16 why is it openbsd specific to wipe the memory on BBB? Dec 13 14:49:47 that's only to get the bootloader to be loaded off of microsd Dec 13 14:50:07 because I don't know 1. the tools available on openbsd 2. what device path is used for eMMC on openbsd 3. what privilege is required to be able to wipe it, or how to obtain it Dec 13 14:50:31 vagrantc: well that or holding down the S2 button at power-on Dec 13 14:50:51 * vagrantc wore out the S2 button at some point on one board Dec 13 14:51:03 but i guess that's what i get for testing the bootloader all the time :) Dec 13 14:51:43 vagrantc: then you can just connect P8.43 to ground (preferably via a resistor) Dec 13 14:52:32 eventually i think i just stopped installing to the eMMC :) Dec 13 14:53:43 Is it possible to merge two network connections at same time like (Ethernet & PPP0) in beagleboneblack. Dec 13 14:53:56 what do you mean by "merge" ? Dec 13 14:54:58 actually it doesn't matter much: it's a linux system, hence it supports all the routing/bridging features that linux does on any other system Dec 13 14:55:01 mean Can we access the both networks PPP0 and Ethernet at same time Dec 13 14:55:09 of course you can Dec 13 14:55:26 Stupd question: Did anybody use IP over USB? Dec 13 14:55:40 Par: most bbb users do Dec 13 14:55:44 probably Dec 13 14:55:53 it's the most common way to connect to the BBB for new users Dec 13 14:56:05 (using RNDIS specifically) Dec 13 14:56:16 we have tried to do routing in priority based but it's not working Dec 13 14:56:56 I tried because of some tutorial, but failed so... I went back to ethernet Dec 13 14:57:37 Nagarjuna: that's a bit too vague to give any comment on, other than that it's not really a beaglebone-specific question, it's just about linux networking Dec 13 14:57:56 Par: do you mean on debian or on openbsd? on debian it should just work plug&play, on openbsd I have no idea if it's supported Dec 13 14:58:04 on debian Dec 13 14:58:14 yes on debian Dec 13 14:58:33 on debian I have connected it per USB and couldn't connect per ssh Dec 13 14:58:37 Nagarjuna: I was asking Par, not you Dec 13 14:59:02 on debain ethernet ssh worked Dec 13 14:59:23 Par: assuming you're using a not-ancient debian image, it should work plug&play on most systems (mac, windows, and linux). it should work on any host that supports CDC-ECM or RNDIS (either suffices since the BBB exposes both) Dec 13 14:59:38 Hi, I am running 5.4.2-bone10 on a beaglebone enhanced. It is working except for Ethernet which is detecting a link but it does not appear to send/receive data. Dec 13 15:00:10 Has someone else observed similar behaviour? Dec 13 15:00:22 I doubt anyone uses a 5.4-bone kernel Dec 13 15:00:47 it sounds odd though Dec 13 15:01:05 @zmatt What is the latest one that is commonly used? Dec 13 15:01:13 4.19-ti Dec 13 15:01:50 don't get me wrong, it should definitely work on 5.x-bone as well, if it doesn't then that's a serious regression Dec 13 15:02:11 I can't easily test that right now though, it would have to wait until I get home Dec 13 15:02:31 That would be grat Dec 13 15:22:05 @zmatt can you please help to me how to access ppp0 and eth0 at same time. Dec 13 15:22:23 what is ppp0? Dec 13 15:23:07 Nagarjuna: you can access them at the same time by default, although the details will depend a bit on your networking situation Dec 13 15:23:22 regardless, it's kind of a generic linux networking question, not a beaglebone-related question Dec 13 15:23:31 ok Dec 13 15:25:02 point to point protocol giyf Dec 13 15:27:20 Nagarjuna: even if ppp0 has a default route, it should still use ethernet for local IP addresses Dec 13 15:28:09 well there you have your answer: I started to go BSD because my TCP/IP book mentions SLIP and PPP and BSD and I was stuck with limited linux knowledge. Dec 13 15:28:25 if you want something more complicated than that you'll need to elaborate what you mean by "access at the same time" Dec 13 15:30:08 you talking to me? Dec 13 15:30:13 no, to Nagarjuna Dec 13 15:34:51 Nagarjuna: again, it's hard to give more useful feedback with the very limited information you've provided Dec 13 15:35:55 richard stevens TCP/IP. p.40 4.2BSD, 4.3BSD 4.4BSD SVR4 AIX SunOS Dec 13 15:36:14 Par: what are you talking about? Dec 13 15:36:54 why I went BSD on BBB Dec 13 15:37:07 I don't see any mention of OpenBSD in that list Dec 13 15:37:08 I wanted to understand TCP/IP and UDP Dec 13 15:37:18 okay, what does that have to do with BSD? Dec 13 15:37:26 sockets work the same on pretty much every OS Dec 13 15:38:08 I don't know why my introductionary book on TCP/IP decided to fill me up with BSD. Most likely because TCP/IP was first implemented in BSD Dec 13 15:38:39 in 1983 4.2BSD Dec 13 15:39:50 "In 1975, a two-network TCP/IP communications test was performed between Stanford and University College London. In November 1977, a three-network TCP/IP test was conducted between sites in the US, the UK, and Norway. Several other TCP/IP prototypes were developed at multiple research centers between 1978 and 1983." Dec 13 15:40:35 anyway, that hardly seems relevant today Dec 13 15:41:09 and if that's your reason for trying to use openbsd, I suggest you just go back to debian Dec 13 15:41:10 anyway I suck at TCP/IP and BSD seems to be closely related according to the book I bought at a local store. Dec 13 15:42:16 any code that uses TCP or UDP that runs on BSD that doesn't use very obscure features should work just as fine on Linux and vice versa Dec 13 15:43:08 and if your book only talks about archaic operating systems then maybe the book itself is a bit outdated? :P Dec 13 15:43:15 seems Mr. Richard Stevens prefers to look at BSD instead. maybe to fool people likeme Dec 13 15:43:20 (note that OpenBSD isn't in your list either) Dec 13 15:44:35 well that list you gave sounds like it's straight from the 80s or something :P Dec 13 15:44:49 printed in 2010 Dec 13 15:45:02 lol Dec 13 15:47:14 which books do you recommend on TCP/IP instead? (*no books only internet yada-yada*) Dec 13 15:49:02 I don't have any recommendations on that Dec 13 15:49:02 I guess this is a strictly debian zone Dec 13 15:49:34 not at all, but if you want to Bring Your Own OS then you should also bring your own knowledge about it... you can't expect us to be able to help you with whatever random OS you decide to use Dec 13 15:50:09 and if you're not familiar with BSD, and your reason to use it was because you want to use TCP/IP... well then that's a pretty bad reason Dec 13 15:50:25 since TCP sockets work the same on linux as they do on bsd Dec 13 15:50:54 don't blame me, blame richard stevens Dec 13 15:51:32 I'm just curious and ready to learn Dec 13 15:51:45 I haven't read the book so I'm not in any hurry to place blame there Dec 13 15:52:09 so far you haven't quoted anything that suggests to me he's suggesting you should use BSD to follow along Dec 13 15:52:21 (let alone OpenBSD) Dec 13 15:53:58 if the list you quoted appeared in a recent book, my guess would be it was in a context that was talking about the history of TCP/IP Dec 13 15:54:14 not should use, but the example servers in the book are SunOS, SystemV R4, and so on Dec 13 15:54:22 AIX Dec 13 15:54:58 ... and? Dec 13 15:55:41 I mean, yes those implement TCP/IP do, just as linux, mac, and windows do Dec 13 15:56:27 BSD/386, UNIX System V SunOS 4.1.3 Solaris 2.2 AIX3.2.2 4.4BSD that are the systems written in this book, so I kind of got curious Dec 13 15:56:56 Instead I got myself FreeBSD, next OpenBSD and hopefully soon NetBSD Dec 13 15:57:53 but OpenBSD never boots by itself right now Dec 13 15:58:04 it always needs a push Dec 13 16:01:58 Par: are you still talking about the button? since you've already been given the workaround for that: wipe eMMC Dec 13 16:02:58 yes that button Dec 13 16:05:39 thank you so far. I think I'm gonna get off for the evening. Dec 13 16:07:28 bb Dec 13 16:37:19 4m Dec 13 16:37:47 zmatt: Par: hi yes, i am the openbsd beagleman **** BEGIN LOGGING AT Fri Dec 13 17:32:50 2019 **** ENDING LOGGING AT Sat Dec 14 02:59:57 2019