**** BEGIN LOGGING AT Tue Jul 24 03:00:01 2018 Jul 24 03:30:46 jesus fucking christ, what is wrong with the people who run bitbucket... having the git server toss a 4-line message in yellow text with red background in your face when you push or pull Jul 24 04:06:16 e Jul 24 07:44:10 hi Jul 24 07:45:44 i am messing around with a beaglebone, and i am trying to remotely update a kernel. it is currently running a 3.13 kernel and i want to update it to a newer one. I haven't had success with simply compiling a new kernel and using it. because it would load the kernel and then nothing. So I am wondering if i update to say the latest kernel does that need say a filesystem update? Jul 24 07:46:06 3.13 ... o.o Jul 24 07:46:12 yes i know Jul 24 07:46:14 :D Jul 24 07:47:15 also, doing a major system update remotely definitely scores high on the hazard score Jul 24 07:47:59 with "it would load the kernel and then nothing" I'm assuming you're practicing on the local device? Jul 24 07:48:15 also, any specific reason to compile a custom kernel? Jul 24 07:48:53 do you have hardware connected to the expansion headers? do you use a custom dtb? overlays? Jul 24 07:49:24 are you booting from sd card or eMMC ? Jul 24 07:51:23 one issue that comes to mind is that iirc old u-boot versions passed something like root=/dev/mmcblk0p1 even when booting from eMMC, which with a new kernel will result in boot being stuck on attempting to mount the root filesystem Jul 24 08:09:17 zmatt: offcourse i am doing it local first :) Jul 24 08:09:43 good :) Jul 24 08:09:53 zmatt: good point it is an older u-boot Jul 24 08:10:03 it's a custom board really :D Jul 24 08:10:27 then say that instead of saying "beaglebone" Jul 24 08:10:37 oh sorry about that Jul 24 08:11:02 i got a little caught up :) Jul 24 08:11:21 do you use a custom dtb, or are you using a beaglebone dtb and patch it up with overlays? Jul 24 08:11:36 custom dtb Jul 24 08:12:27 not sure about overlays Jul 24 08:13:32 okay so you'll need to forward-port your dts with a bit of care, iirc there were some relevant differences between the am33xx.dtsi of prehistoric kernels and recent kernels Jul 24 08:13:41 well if you use a custom dtb then overlays sound unlikely Jul 24 08:18:31 alright i'll have a look into that then :) Jul 24 08:18:54 i see my uboot does this: root=/dev/mmcblk0p2 Jul 24 08:19:14 so how do newer kernels know where the filesystem is located ? Jul 24 08:19:17 ah right, such old systems still used a separate boot partition Jul 24 08:19:37 same way, but without broken numbering Jul 24 08:19:58 same partition but in a boot directory instead ? Jul 24 08:20:56 old kernels numbered mmc block devices sequentially, so whether mmcblk0 was SD or eMMC depended on whether an sd card was inserted. now mmcblk0 is always sd and mmcblk1 is always eMMC. also, if an initramfs is present, u-boot will pass root=UUID=... to the initramfs Jul 24 08:21:44 MLO and u-boot.img now live at fixed offsets in the space between the partition table and the root partition. but I *think* using a FAT boot partition should also still be supported Jul 24 08:22:10 pretty sure even Jul 24 08:24:06 cool :) Jul 24 08:24:26 you have given me so much to work with and insight! :D thanks Jul 24 08:24:27 (in case it's relevant: if MLO is present at fixed offset *and* in a FAT partition, the fixed offset one takes precedence) Jul 24 09:51:37 Hello, I have a problem with installing the drivers on my windows 10 can somebody help ? Jul 24 09:53:56 you don't need any Jul 24 09:55:12 "With the latest images, it should no longer be necessary to install drivers for your operating system to give you network-over-USB access to your Beagle." -- https://beagleboard.org/getting-started Jul 24 09:55:47 (where "latest" actually means anything that's not ancient) Jul 24 10:06:13 ... you're welcome Jul 24 10:33:18 I downloaded both drivers on my mac but i cant get access to the http://192.168.7.2 what do i have to do ? Jul 24 10:33:41 connect to http://192.168.6.2 (you didn't need to install any drivers) Jul 24 10:34:10 see table here: https://beagleboard.org/getting-started#step2 Jul 24 10:35:19 why do you say i dont need to install them ? its step 2 of getting started Jul 24 10:36:00 "With the latest images, it should no longer be necessary to install drivers for your operating system to give you network-over-USB access to your Beagle." -- step 2 of the getting started guide Jul 24 10:36:51 if you're looking at the getting started guide on the beaglebone itself, then if it has old info that suggests the beaglebone itself is flashed with an old image, in which case you probably want to reflash it with the latest image Jul 24 10:38:18 i tried to acces http://192.168.6.2 that doesnt work also .. i already tried it on windows but it isnt working anywhere for me Jul 24 10:39:00 then definitely just reflash to the latest image Jul 24 10:39:15 https://beagleboard.org/getting-started#update Jul 24 10:40:23 do i have to insert a sd card ? Jul 24 10:40:29 or willt it work without one ? Jul 24 10:42:46 once you've booted from the sd card you can uncomment a line in its /boot/uEnv.txt to turn it into an eMMC flasher card that will reflash the on-board eMMC storage, after which it will boot without sd card. alternatively you can download a pre-made flasher image here: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Stretch_Snapshot_iot Jul 24 10:42:47 okokok, you will need to download the image, flash the image onto your SD card, and go from there Jul 24 10:44:01 so i need to put a sd card into my beagle board ? Jul 24 10:44:03 once you've reflashed eMMC, you should probably erase the sd card to ensure you won't accidently boot the beaglebone from it again and end up unintentionally reflashing it again. (people accidently reflashing their bbb is why flasher images were removed from https://beagleboard.org/latest-images apparently) Jul 24 10:44:11 to reflash it yes Jul 24 10:44:19 once it's reflashed you no longer need the sd card Jul 24 10:45:09 this is also in the update instructions on the getting-started page Jul 24 10:46:35 okay and why is the getting started version from my beagle bone connection saying i have to install drivers an so on ? Jul 24 10:46:59 I already said that: that just means there's an old image flashed onto it Jul 24 10:47:23 okay Jul 24 10:47:29 when you buy a beaglebone you can't always assume it has a recent image flashed on it... who knows how long it'd been sitting on a shelf somewhere Jul 24 10:47:53 that's why the online getting-started recommend updating to the latest image if any step fails Jul 24 10:48:57 okay so i have to insert a new sd card into the beagle board and then i will download the latest debian image ? Jul 24 10:49:25 how about you just read and follow the steps? Jul 24 10:50:40 i do that but which image do i have to download for windows ? Jul 24 10:51:13 the instructions given are the same for mac, windows, or linux Jul 24 10:53:56 man im doing that, but when im going on the latest images site there are about 30 images to download but i dont know which i have to download #ß Jul 24 10:54:03 the first one Jul 24 10:54:29 okokok: I know what you mean, there are a gazillion links Jul 24 10:54:34 the one without graphical desktop ? i have the beagle bone black Jul 24 10:54:46 okokok: do you want a graphical desktop, or just command-line? Jul 24 10:54:56 do you plan on connecting a monitor? Jul 24 10:55:22 do you really want a graphical desktop on the beaglebone itself? I don't highly recommend it, and it leaves very very little free space on the beaglebone Jul 24 10:56:09 i dont wont to connect it with a monitor my project is to play a server on it and connect the server with an IoT thing and my PC Jul 24 10:56:29 so i need the Stretch IoT ? Jul 24 10:56:29 then use the stretch-iot image Jul 24 10:56:45 okay i will do that Jul 24 10:57:52 that will take some hours :D Jul 24 10:58:42 good thing you went with the iot version, the GUI ones are even bigger Jul 24 10:58:55 haha okay thanks Jul 24 10:59:32 i hope that it will work now because im trying for days to do that and i read every time the getting started from my beagle bone Jul 24 11:01:20 hmmm, all of this seems a bit strange to me. Shouldn't the instructions on the old image be accurate for that image? Jul 24 11:01:23 * dcmertens is just wondering aloud Jul 24 11:01:49 certainly the most up-to-date image, with the most up-to-date instructions, are the most likely to work Jul 24 11:02:19 well the older images only supported rndis, which mac doesn't support Jul 24 11:02:39 and the third party drivers also stopped working I think or something Jul 24 11:02:48 I dunno, I'm not that deeply into archeology :P Jul 24 11:03:02 on the old one the first step is to install drivers and then connect to the the given ip address Jul 24 11:03:18 l try it now on windows i download the image at the moment Jul 24 11:03:30 windows 10 ? Jul 24 11:03:54 yes Jul 24 11:04:24 okay yeah, recent images should work fine there (again without needing to install any drivers) Jul 24 11:04:50 so on windows 10 i only need to update the board ? Jul 24 11:05:11 with the new image ? Jul 24 11:05:12 if you update the board, it should work on linux, mac, and windows 10 Jul 24 11:05:22 okay thanks i will try Jul 24 11:05:52 zmatt, any thoughts on how to disable dnsmasq? I tried "sudo systemctl disable dnsmasq.service" but it came back up on reboot Jul 24 11:06:33 anything that my BBs will need to connect to will be in /etc/hosts, so I don't need DNS Jul 24 11:06:42 dcmertens: yeah, disable the service that runs the big ugly shell script at boot responsible for getting up the usb networking mess Jul 24 11:06:50 I think it also starts dnsmasq Jul 24 11:06:53 ah Jul 24 11:06:58 thanks Jul 24 11:07:04 generic-board-setup.service ? or something like that anyway Jul 24 11:07:20 just look around in /etc/systemd/system Jul 24 11:07:36 cool, thanks Jul 24 11:21:38 how to install net snmp on beaglebone black Jul 24 11:22:08 the same way as on any other debian system I'd presume? Jul 24 11:24:07 Swapnil_elcom: what is net snmp? Jul 24 11:24:23 ensure your bbb has internet access, sudo apt-get update and then follow instructions here https://wiki.debian.org/SNMP Jul 24 11:25:02 dcmertens: is wikipedia down? ;P Jul 24 11:25:18 no, I ask when I don't know for a reason Jul 24 11:25:49 I would like to know *their* context Jul 24 11:25:49 :-) Jul 24 11:25:59 strange way to ask it Jul 24 11:26:25 also, I sometimes found that chat rooms are treated by folks as support forums Jul 24 11:26:28 but they're really communities Jul 24 11:26:38 and asking simple questions like that tends to reinforce that notion Jul 24 11:28:19 I'll admit that's actually a neat trick, but it doesn't change that asking "what is ?" does kinda invite a lmgtfy link Jul 24 11:28:22 ;) Jul 24 11:30:30 I happen to believe that lgtfy is underutilized... Jul 24 11:30:50 I actually had an opportunity to use that on one of my students and was delighted Jul 24 11:30:54 first time in, like, five years! Jul 24 11:31:22 hehehe Jul 24 11:38:13 trying to figure out what is causing dnsmasq to load, I came across "systemctl --reverse list-dependencies" Jul 24 11:38:24 when queried against dnsmasq.service, I get nothing Jul 24 11:38:46 it's not a dependency, it's being manually started by an ugly shell script Jul 24 11:38:48 also, RCN's boot scripts make it easy to disable USB internet stuff Jul 24 11:39:06 edit /opt/scripts/boot/default/bb-boot Jul 24 11:39:20 which I did, to disable USB networking Jul 24 11:40:08 just disable the service I mentioned (after optionally checking what it does) Jul 24 11:40:25 hmm... Jul 24 11:40:29 * dcmertens hadn't thought of that Jul 24 11:40:51 it doesn't serve a particularly useful purpose, especially not if you don't care about the usb networking setup it does Jul 24 11:41:22 the service I saw kicks off /opt/scripts/boot/generic-startup.sh Jul 24 11:41:28 yeah that one Jul 24 11:41:33 among other things, that sets proper permissions on GPIO pins Jul 24 11:41:39 ?! Jul 24 11:41:40 what? Jul 24 11:41:41 so I guess I could move that code into rc.local Jul 24 11:41:47 why the hell doesn't he use an udev rule for that? Jul 24 11:42:04 that's what I do anyway Jul 24 11:42:11 hmm Jul 24 11:42:34 is there any particular reason not to do that, or any other pin setup, in rc.local? Jul 24 11:42:59 is rc.local guaranteed to run after udev is done? Jul 24 11:43:19 I guess for this it doesn't really matter Jul 24 11:43:19 I don't know, but rc.local runs *very* early Jul 24 11:43:57 udev is the right place in general: it ensures the rules get executed when the devices appear Jul 24 11:44:36 ah, yes, rc.local.service depends upon sysinit.target, which depends upon systemd-udevd.service Jul 24 11:44:37 for the gpios I guess it doesn't matter since they're platform devices whose drivers are compiled into the kernel, so I guess they're probably around even before userspace begins, but still Jul 24 11:45:03 depending on systemd-udevd.service doesn't guarantee all devices are available though Jul 24 11:45:59 ... so udev will be up and running, but not ... "done"? Jul 24 11:47:07 but anyway, although you can of course make a shell script run at a sufficiently late point using dependencies, using an udev rule is intrinsically correct without having to think since it's triggered by the device's appearance Jul 24 11:47:57 that makes sense. This sort of configuration all seems to have come about after I invested my time into learning about Linux configuration details Jul 24 11:48:11 hence my uncertainty Jul 24 11:49:24 this is what my udev rule for gpios looks like: https://pastebin.com/raw/6WCKzdgs Jul 24 11:49:55 * dcmertens looks up how to use udev Jul 24 11:50:08 (I declare my gpios in DT and create named symlinks in /dev/gpio so applications don't need to know or care about gpio numbers, they just use e.g. /dev/gpio/adc-reset/value ) Jul 24 11:50:27 create a file with ".rules" suffix in /etc/udev/rules.d/ Jul 24 11:51:17 cool Jul 24 11:51:46 actually, if my GPIO pin names can reflect their actual purpose, this will make my eventual goal a hell of a lot easier Jul 24 11:52:16 https://github.com/mvduin/overlay-utils/blob/master/gpio-demo.dtsi Jul 24 11:53:28 this is a simplified example of actual config I use: https://pastebin.com/CPiC2CnB Jul 24 11:53:37 and this yields: https://pastebin.com/GseLp62B Jul 24 11:54:36 it also prevents userspace from being able to change inputs to output (which could easily damage hardware) Jul 24 11:54:47 hmm, so all of this requires getting the right dtsi Jul 24 11:55:18 I use a fully custom dts, but it also works in an overlay of course Jul 24 11:55:54 it conflicts with cape-universal obviously, but that's true for pretty much any overlay Jul 24 12:03:35 ok, sticking with my original goal, I will try to disable generic-board-startup.service Jul 24 12:03:37 let's see what happens Jul 24 12:06:13 now dnsmasq is not started, and /sys/class/gpio are root:root Jul 24 12:06:48 now, while I'm at it, why the hell is wpa supplicant started??? Jul 24 12:06:58 or bluetooth? Jul 24 12:07:14 time for the power of... apt-get purge Jul 24 12:07:54 well first I have to find the package that installed the bluetooth stuff to begin with Jul 24 12:08:06 note that my udev rule only does chgrp/chmod on actual gpios (specifically those exported by DT, including by cape-universal if enabled), not the whole /sys/class/gpio directory Jul 24 12:08:23 try: dpkg --get-selections | grep wl18 Jul 24 12:08:44 zmatt++ Jul 24 12:08:44 that would be my first thought anyway Jul 24 12:10:01 Hello Jul 24 12:10:06 o/ Jul 24 12:11:03 How to make please an script executing at startup of beaglebone and always be executing while beaglebone run like cloud9 Jul 24 12:11:20 lol, that's been the whole conversation this morning Jul 24 12:11:49 how much do you know about systemd? Jul 24 12:12:26 http://mybeagleboneblackfindings.blogspot.com/2013/10/running-script-on-beaglebone-black-boot.html Jul 24 12:12:34 I used that Jul 24 12:12:40 and it is working Jul 24 12:12:53 but I want my script still executing Jul 24 12:13:06 while the Beaglebone work Jul 24 12:13:34 you want to start a daemon, then Jul 24 12:13:35 like cloud9 which URL : 192.168.7.2 : 3000 Jul 24 12:14:10 I Want when I click 192.168.7.2:port it's still working Jul 24 12:14:27 does this give you any inspiration: https://github.com/jirihnidek/daemon Jul 24 12:34:30 zmatt: i got a 4.4.13 kernel booted ! :D Jul 24 12:37:06 sweet, you've gone from prehistoric to merely old :D Jul 24 12:37:19 next up, 4.14 ? Jul 24 12:41:57 this is what was in the master branch Jul 24 12:42:06 i meen 4.4.113 Jul 24 12:42:59 actually nvm git says 4.4 :) Jul 24 12:50:52 master branch of what? Jul 24 12:53:11 all relevant repositories (both the main repositories, RobertCNelson/bb-kernel and RobertCNelson/ti-linux-kernel-dev which are used to build the -bone and -ti kernels respectively, and the beagleboard/linux and RobertCNelson/linux-stable-rcn-ee trees produced by them) have a branch per major kernel series, and no useful master branch Jul 24 13:01:37 hello Jul 24 13:01:55 o/ Jul 24 13:02:17 could you provide begalbone blue working images Jul 24 13:02:56 * dcmertens cues lmgtfy Jul 24 13:03:05 https://beagleboard.org/latest-images Jul 24 13:04:44 hello Jul 24 13:04:49 https://beagleboard.org/latest-images Jul 24 13:04:59 prasanth: ^^^ Jul 24 13:05:27 let me know begalbone black uboot images wil work to begalbone blue or not Jul 24 13:05:54 hmm, what does the website say about it? Jul 24 13:05:56 :-) Jul 24 13:08:06 hmm, I thought I might install the -bone kernel corresponding to my -ti kernel Jul 24 13:08:16 oddly, 4.14.54 only has a -ti version Jul 24 13:08:43 and 4.14.55 has -bone, but not -ti Jul 24 13:08:52 currently i was struck at bootloader stage only Jul 24 13:09:11 by currently you mean with the image downloaded from that page? Jul 24 13:09:23 could provide working MLO and u-boot.img for begalbone blue Jul 24 13:10:18 prasanth_: I do not understand your last statement. Are you asking for one of us to provide a working MLO...? Jul 24 13:10:21 i downloaded MLO only Jul 24 13:10:38 no, the image from beagleboard.org is the whole thing Jul 24 13:10:53 check the sha sums Jul 24 13:11:09 make sure your download matches what is posted on the website Jul 24 13:11:21 yes i m downloaded from beagleboard.org only Jul 24 13:14:35 prasanth_: does the sha sum agree with what is given on the web page? Jul 24 13:20:26 zmatt: yea i made a mistake that is why i checked with git :) Jul 24 13:20:37 sorry i am not getting what is sha sum Jul 24 13:22:38 prasanth_: an sha sum takes an arbitrarily long series of bits and gives you a number Jul 24 13:22:53 two bit sequences that differ by only one bit are supposed to have wildly different sha sums Jul 24 13:23:05 so it serves as an excellent check against mis-downloads Jul 24 13:23:22 the sha sum is a specific algorithm Jul 24 13:23:36 and your OS should have a program that runs this algorithm on any file you ask Jul 24 13:23:45 then it spits out the sha sum Jul 24 13:24:03 prasanth_: what is your OS? Jul 24 13:24:31 currently i am using ubuntu 14.04 Jul 24 13:25:08 check out man sha256sum Jul 24 13:25:45 It should be something like "sha256sum " Jul 24 13:29:51 when I run "lsmod" I gt *nothing* Jul 24 13:29:58 anybody have any idea why that might be? Jul 24 13:30:17 * dcmertens asks the google Jul 24 13:31:01 these folks think I might have a monolithic kernel: https://forums.gentoo.org/viewtopic-t-896498-start-0.html Jul 24 13:31:33 dcmertens _: before doing lsmod just give the insmod Jul 24 13:32:38 but isn't it odd that I have no drivers whatsoever? Jul 24 13:41:24 suppose I want a regular user to be allowed to load and run pru code. I think I need to change file permissions somewhere. Where? Jul 24 13:44:06 why oh why does "shutdown now" issue a reboot? Jul 24 13:44:08 grr Jul 24 13:50:28 hello, i want to download an image to my board, is the version with gui better or the one without ? Jul 24 13:50:45 only if you plan to plug a monitor into your BB Jul 24 13:50:52 the non-gui version is smaller, so it'll download faster Jul 24 13:51:04 hello: you probably want the iot (non-gui) one for most purposes Jul 24 13:51:45 a graphical desktop environment does not run particularly comfortably on a beaglebone, and the lxqt image leaves very little free space if flashed to eMMC Jul 24 13:52:18 the beaglebone is typically used as embedded system, not as a small desktop computer Jul 24 13:52:57 if i want to run an server which should i use Jul 24 13:53:01 and connect with iot Jul 24 13:53:15 iot or console Jul 24 13:53:23 what do you mean by "connect with iot" ? Jul 24 13:54:31 i am going to run a server on my beagle bone and connect it with an iot device to my pc Jul 24 13:56:21 I still have no idea what you mean by that, but you probably want the iot image Jul 24 13:56:25 Hello? Jul 24 13:56:33 o/ Jul 24 13:57:08 yes i want that one Jul 24 13:57:23 Does anyone know how we can build our own microcomputers? Jul 24 13:57:40 Cestdude: I let TI take care of that for me Jul 24 13:58:03 I do have a soldering iron, but that's a lot of pins! Jul 24 13:58:23 TI? Jul 24 13:58:28 Texas Instruments Jul 24 13:58:51 Apparently Beaglbone has their schematics available for public use Jul 24 13:59:05 that's what I've heard Jul 24 13:59:13 I've not looked at them myself Jul 24 13:59:31 Do you wish to build a computer using said schematics? Jul 24 13:59:36 Doing a project and want to build my own SCB Jul 24 14:00:34 I'm not sure what SCB means Jul 24 14:00:39 From the UK so using TI might not be feasible Jul 24 14:00:53 but i can use the gui version as i want to use the one without Jul 24 14:00:54 ? Jul 24 14:01:02 Small computer boards, like h BeagleBone Jul 24 14:01:28 hello: you can use both as ssh servers Jul 24 14:02:03 Cestdude: if you're debating between buying a small board, or producing one yourself Jul 24 14:02:24 and if you've come here for ideas... Jul 24 14:02:25 I suggest just buying one Jul 24 14:03:56 I need to build one Jul 24 14:04:18 Hence why I'm here Jul 24 14:27:58 lol Jul 24 14:29:57 hello! How to enable the serial ports TTY0 and 1? I saved a page telling how to change the uEnv.txt but it doesnt work anymore. Jul 24 14:30:27 (sorry: BBB with debian image Jul 24 14:30:51 on a recent image in its default config you don't need to do anything in uEnv.txt at all (and you should probably undo your changes) Jul 24 14:31:16 the /dev/ttyS* devices should exist by default and you just configure the pins using the config-pin utility Jul 24 14:32:13 if you want to use a port whose pins conflict with e.g. hdmi video then you can disable that in /boot/uEnv.txt Jul 24 14:32:45 ttyS0 is the serial console btw and always enabled Jul 24 14:33:35 ok, so my program complains about cannot open ttyS0 "maybe a permission problem" Jul 24 14:33:57 it's already in use by getty Jul 24 14:34:07 most likely Jul 24 14:34:35 Nope. I use the wi-fi connection Jul 24 14:34:48 and? Jul 24 14:35:03 that doesn't change the fact that a serial-getty is enabled on ttyS0 by default Jul 24 14:35:20 wait: Jul 24 14:35:27 i need 1 and 2 Jul 24 14:35:34 i don't touch the 0 Jul 24 14:36:03 my mistake in that message, sorry Jul 24 14:36:09 then, e.g. for uart1: config-pin P9.24 uart && config-pin P9.26 uart Jul 24 14:37:19 as for permissions, I don't know what the defaults are. just check with ls -l /dev/ttyS1 which group is allowed access by default (to see which groups you're member of, use the "id" command) Jul 24 14:39:15 trying to find what should i do to use that "pin-config utility" .... guess that asking this also to you will be faster Jul 24 14:39:28 I gave an exact command Jul 24 14:39:51 oh Jul 24 14:40:51 p9_24 pinmux file not found. Jul 24 14:41:21 did you undo whatever you did in /boot/uEnv.txt ? (and reboot) Jul 24 14:41:38 also, how old/recent is the image you're using? check with: cat /etc/dogtag Jul 24 14:42:00 ok, forgot to reboot. Jul 24 14:42:03 :\ Jul 24 14:47:39 no difference. pinmux file not found Jul 24 14:48:11 how do i check the actual assignement? Jul 24 14:48:59 version: BeagleBoard.org Debian Image 2018-01-28 Jul 24 14:49:22 are you booting from sd or eMMC ? Jul 24 14:49:26 sd Jul 24 14:49:37 do you care about the current contents of eMMC ? Jul 24 14:50:36 not really, but i'm compiling on the BBB and the whole libraries can't be in the eMMC Jul 24 14:50:37 otherwise erase it with: sudo blkdiscard /dev/mmcblk1 and then reboot. that will almost certainly fix the config-pin problem Jul 24 14:51:02 (known issue caused by an old u-boot on eMMC) Jul 24 14:51:29 oh.... ok, i'll try, Jul 24 14:51:42 the whole libraries can't be in eMMC ? what kind of library takes gigabytes of space? o.O Jul 24 14:52:01 boost and wxwidgets Jul 24 15:08:13 Hello Jul 24 15:08:36 I use this link http://mybeagleboneblackfindings.blogspot.com/2013/10/running-script-on-beaglebone-black-boot.html to make a script launch at startup but I want to make a script launch during the beaglebone works like cloud9, I want to access on 192.168.7.2:PORT at any time and it works. How to make it please ? Jul 24 15:16:30 nothing changed Jul 24 15:16:54 also pin21 (ttys2) does the same error Jul 24 15:17:15 parduz: okay that's odd, can you pastebin the contents of your /boot/uEnv.txt ? Jul 24 15:17:29 sure Jul 24 15:17:48 someone ping me? Jul 24 15:17:55 scrollback too long Jul 24 15:18:44 2018-07-21.log.bz2:00:12:19 < veremitz> jkridner: did you make any progress on the buildbot issue? Jul 24 15:18:55 https://pastebin.com/sEvgzyEk Jul 24 15:19:05 veremitz: still stuck on it. :-( Jul 24 15:20:00 parduz: cat /proc/cmdline Jul 24 15:20:22 I'm not really seeing anything wrong in the uEnv.txt ... Jul 24 15:21:22 console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait uboot_detected_capes=BB-BONE-LCD4-01, coherent_pool=1M net.ifnames=0 quiet Jul 24 15:21:47 ohh, you have a cape Jul 24 15:22:33 yep. Jul 24 15:22:53 when a cape is attached the pin config is determined by the cape's overlay Jul 24 15:23:32 theoretically it would be nice if pins unused by the cape would still be freely configurable, but that would probably be rather non-trivial to implement Jul 24 15:24:01 so you'll need to use an overlay instead Jul 24 15:24:50 was it not that lines to add to the uEnv.txt? Jul 24 15:25:34 yeah in *this* case you'll need to manually enable one or more overlays in /boot/uEnv.txt Jul 24 15:25:42 I didn't know you had a cape attached, that changes things Jul 24 15:26:50 also, your cape conflicts with uart1 Jul 24 15:26:53 not your fault: i didnt said that 'cause did'nt get that there's different ways Jul 24 15:27:02 i was following this page: Jul 24 15:27:03 http://tinkernow.com/2015/01/beaglebone-black-rs232-uart-setup/ Jul 24 15:27:17 anything from 2015 is almost certainly obsolete Jul 24 15:27:26 yup Jul 24 15:27:48 to enable uart2, set e.g. uboot_overlay_addr4=/lib/firmware/BB-UART2-00A0.dtbo Jul 24 15:28:18 uart1 is not possible since P9.24 is already in use by the cape Jul 24 15:28:49 I want to run my application developed on reactJS on frontend, nodejs on backend and MySQL about database, I want to make it works during I connect my Beaglebone with Pc, I try to write the bash script to make it running at startup and it works well, but after few minutes, I can't access to 192.168.è.2:MyPort to run it. Jul 24 15:28:55 so that's the line i have to write in the uEnv.txt? Jul 24 15:29:04 parduz: to check current pin configuration you can use my show-pins utility: https://github.com/mvduin/bbb-pin-utils/#show-pins Jul 24 15:29:18 parduz: yeah, there's already a commented-out example line for it (line 20 of the file) Jul 24 15:29:43 wanted to be sure. Jul 24 15:29:50 saving and rebooting Jul 24 15:29:54 parduz: uboot_overlay_addr0-3 can be used to override the overlays for autodetected capes, 4-7 and dtb_overlay are for custom overlays Jul 24 15:30:12 flikd: what do your log files say about your application? Jul 24 15:32:42 zmatt++ for show-pins Jul 24 15:32:46 that is *very* helpful! Jul 24 15:32:58 :) Jul 24 15:33:20 and it tells me that all sorts of stuff is *not* doing what I thought I told it to do Jul 24 15:33:28 lol Jul 24 15:33:29 (I too am working on /boot/uEnv.txt setup) Jul 24 15:36:19 speaking of which, I seem to be unable to load the universal cape. See https://pastebin.com/e513tpK0 Jul 24 15:37:15 geez! I have a ttyO2->ttyS2 :) Jul 24 15:37:23 thnx a lot Jul 24 15:37:54 yeah those ttyO* symlinks are still made for backwards-compatibility reasons Jul 24 15:38:41 dcmertens: read scrollback and follow the same suggestions? Jul 24 15:38:47 * dcmertens checks Jul 24 15:39:24 they are a good signal that ttyS* are working Jul 24 15:39:51 let see if my app is happy now Jul 24 15:39:59 oh right the ttyS devices exist even when they... don't. for reasons that completely elude me Jul 24 15:40:46 I honestly can't understand why they're treated in such a weird special way (with the number of instances determined by a kernel parameter, instead of them simply being made for the serial devices actually present) Jul 24 15:41:55 IT WORKS! Jul 24 15:42:01 \o/ Jul 24 15:42:19 (CAPS 'cause i'm so frustrated by linux and everything related :D ) Jul 24 15:44:04 may i ask another COMPLEX (and perhaps very long to do) question? Jul 24 15:44:54 you can always ask a question, you might just not get an answer Jul 24 15:45:41 Ok :) My Cape is a custom cape, derived from the LCD4 it "emulates" but it have a keyboard and a serial. Jul 24 15:46:07 then it shouldn't claim it's an LCD4 cape Jul 24 15:46:44 exactly. One step at time :) Jul 24 15:46:50 give it proper identification and make an overlay for it that correctly describes the hardware Jul 24 15:47:02 that the question. Jul 24 15:47:49 The minimum change from the LCD4 i need is to change the key it "fire" when a Input changes (the LCD4 had 5 buttons, one is the "Right arrow") Jul 24 15:48:33 there are of course lots of examples in https://github.com/RobertCNelson/bb.org-overlays/tree/master/src/arm ... although these overlays are typically not particularly easy to read. my https://github.com/mvduin/overlay-utils project aims to make overlays nicer to write by preprocessing the sources Jul 24 15:49:24 (but since you want to base it on an existing overlay you probably don't want to put in the effort of converting it to the format used by overlay-utils, even if the result is more readable and maintainable... or maybe you do, that's up to you) Jul 24 15:49:54 the best could be putting the TTYS2 configuration in the cape, and let "the system" do a i2C read at a specific address and then pass a keystroke event to the system hen that input change state. Jul 24 15:50:27 I don't understand what you mean by that last part Jul 24 15:50:37 ok Jul 24 15:51:11 if you're using an i2c gpio expander or something like that, and it has a kernel driver (there's a good chance of that), then you can declare it and then use its gpios just like the beaglebone's own gpios Jul 24 15:51:50 the last message is made by two parts: 1) the UART2 is necessary to my cape, so i guess my cape description should configure it Jul 24 15:52:13 the key fired by buttons is the "linux,code" property you find in the overlay Jul 24 15:52:14 yes it should Jul 24 15:53:51 the second part is the more complex one: right now i'm polling via i2c2 my cape, to get the keys status: Jul 24 15:54:40 but we made the keyboard rise that "right arrow" input when the keys changes Jul 24 15:55:12 so i want to read i2c2 only when i have that event, to get the key pressed. Jul 24 15:56:09 sounds like you're simply describing a gpio expander with irq line Jul 24 15:56:18 a simple "hack" would be to change that "right arrow" to some unusual key (F20, as example) and my app reading the keys via i2c only when that event is raised Jul 24 15:57:04 maybe. I dunno Jul 24 15:57:05 if you're using one of the many i2c gpio expanders supported by linux (or sufficiently behave like one of them), the kernel can handle all of this for you Jul 24 15:57:19 that would be grat Jul 24 15:57:22 great Jul 24 15:57:29 i just don't know how Jul 24 15:59:12 are you using an actual gpio expander or is this something weird and custom? Jul 24 15:59:34 (or keyboard scanner, or whatever) Jul 24 16:01:01 my best answer: the cape have an ATMEGA emulating the LCD4 EEPROM for cape identifying, and passing the keyboard status when you read at a specific address Jul 24 16:01:26 i.e. something weird and custom Jul 24 16:01:38 what i mean: i can read it as a EEPROM also from command line Jul 24 16:02:05 I understand, but that doesn't help for making it actually behave like a keyboard Jul 24 16:03:10 like I said: if it behaves like one of the numerous standard ICs that linux supports, things are easy Jul 24 16:03:31 what could be one of them? Jul 24 16:03:54 we can program the behaviour as we want. Jul 24 16:04:21 as long as he works also as a touch LCD Jul 24 16:04:36 how is that related to the keyboard? Jul 24 16:05:39 BBB searches for capes: the ATMEGA is seen as a LCD4 eeprom. There's no a real eepron on our cape Jul 24 16:06:13 eeprom is useful if you're going to sell the cape to users Jul 24 16:06:23 or otherwise have a use for autodetection Jul 24 16:07:19 but if it's just for a product you make, you can also just manually specify the overlay in /boot/uEnv.txt Jul 24 16:07:53 but, I'm afraid I'm going to be pretty distracted right now Jul 24 16:07:58 we're selling a closed system containg out own boards, and the BBB will be the optional touchscreen interface when the customer does'nt have a full PC to log in our device. Jul 24 16:08:30 ok, i will bore you another time :) Jul 24 16:08:38 thnx for all the help Jul 24 16:09:07 but like I said: the eeprom is just for autodetection, i.e. to allow your cape to work on a random bbb (after you submit your overlay to be included in the bb.org-overlays) Jul 24 16:09:16 if you don't care about that, you don't need an eeprom Jul 24 16:10:54 and maybe dig around in Documentation/devicetree/bindings/ to see if you can find an i2c gpio expander or keyboard scanner/controller that looks like it meets your requirements and whose protocol can be reasonably emulated Jul 24 16:11:37 EEPROM: I know. It is useful to attach our cape and have it working as a LCD4, and then use it to configure the full thing while already on the field. Jul 24 16:11:47 Ill dig in there Jul 24 16:39:50 zmatt++ Jul 24 16:39:58 I can now toggle all of the pins that I wanted to toggle Jul 24 16:40:13 turns out I was mis-reading the output of show-pins: everything *was* working properly Jul 24 16:40:18 :-D Jul 24 16:40:48 of course you read the readme that documents every column of the output Jul 24 16:40:59 readme? Jul 24 16:41:08 :-) Jul 24 16:45:50 I want to use the SPI1 device. I am using the universal cape and config-pins; do I need to load a cape, too? Jul 24 16:46:09 (or... is it perhaps in a location I haven't checked?) Jul 24 16:46:21 spi1 conflicts with hdmi-audio, so you need to disable that Jul 24 16:46:43 I believe I did that on line 31 here: https://pastebin.com/e513tpK0 Jul 24 16:46:45 (technically they could coexist if someone puts in the effort) Jul 24 16:47:05 oh you did Jul 24 16:47:18 but config-pin is not working? Jul 24 16:47:35 config-pin doesn't complain Jul 24 16:47:47 I just cannot locate the device under /dev/ Jul 24 16:47:54 which kernel version? Jul 24 16:48:05 4.14.55-bone16 Jul 24 16:48:15 and there's no /dev/spidev1.* ? Jul 24 16:48:24 nope Jul 24 16:48:31 no /dev/spi-nothin Jul 24 16:48:55 Now, show-pins says its set to GPIO output... Jul 24 16:48:57 hold on... Jul 24 16:49:22 are you sure u-boot overlays are working for you? Jul 24 16:49:25 wait, I may have made a stupid mistake Jul 24 16:49:35 afk Jul 24 16:49:52 (or, not really afk, but attention needed elsewhere) Jul 24 16:50:44 zmatt: no worries, drop in as able Jul 24 16:53:08 config-pin says the P9.29, P9.30, and P9.31 are configured for spi work, in agreement with show-pins Jul 24 16:53:30 but /dev/spidev1.* does no appear Jul 24 16:53:34 * dcmertens is asking google about it Jul 24 16:58:22 if anybody has permissions, please update this page to say "Out of date" at the top: https://elinux.org/BeagleBone_Black_Enable_SPIDEV Jul 24 16:59:19 or perhaps edit the giant red banner and remove the bit about "IT MUST BE ENABLED AT BOOT in uEnv.txt" Jul 24 17:02:26 fixed with "sudo insmod /lib/modules/4.14.55-bone16/kernel/drivers/spi/spidev.ko.xz" Jul 24 17:03:20 still, I would have expected something to load that for me Jul 24 17:13:44 dcmertens: sudo depmod Jul 24 17:13:48 and reboot Jul 24 17:16:40 * dcmertens tries Jul 24 17:19:44 zmatt++ Jul 24 17:19:56 also, now lsmod gives a bunch of modules Jul 24 17:20:02 including uio_pruss Jul 24 17:20:04 :-D Jul 24 17:31:04 I'm trying to follow the guide to setup dsp on my x15 here: https://elinux.org/BeagleBoard/DSP_Howto but almost all the links are dead/404/missing. Is there a more recent guide on how to do this? Jul 24 17:31:31 End goal is getting hardware accellerated video playback Jul 24 17:39:56 FR_Mike: that's about the old omap3 beagleboards Jul 24 17:40:41 on the x15, video acceleration is handled by IVA-HD, not by the DSPs Jul 24 17:41:22 oh Jul 24 17:41:44 how can I utilize the IVA-HD to render videos? is there a gstreamer plugin for it? Jul 24 17:41:58 pretty sure yes Jul 24 17:46:13 so I've tried poking around the processor sdk for these plugins but I'm not finding them. I'm probably missing something Jul 24 17:46:42 i.e. from here: http://processors.wiki.ti.com/index.php/Processor_Training:_Multimedia Jul 24 18:11:06 HOORAY GPIO AND SPI WORK AS EXPECTED!! Jul 24 18:11:09 :-D Jul 24 18:11:26 now on to pru stuff Jul 24 18:13:21 enhanced GPIO Just Works. :-D Jul 24 18:13:46 (or rather, using config-pin to set it up) Jul 24 19:55:08 How do I connect a bipolar stepper motor to my BB Blue? Do I simply connect to two different motor driver outputs? Jul 24 21:38:17 veremitz: followed https://www.vultr.com/docs/how-to-install-and-configure-buildbot-on-centos-7 and still https://builds.beagleboard.org doesn't work. **** ENDING LOGGING AT Wed Jul 25 03:00:02 2018