**** BEGIN LOGGING AT Wed Mar 20 02:59:57 2019 Mar 20 07:12:18 what's the right way to keep a bluetooth device always connected , whenever it is powered on or back into controller range ??? I'm ending in unreliable stupid script.... any info please ? Mar 20 07:33:08 it must be powered on to be back within controller range. Mar 20 07:34:02 so maybe detect controller. Mar 20 07:34:15 fred__tv: use systemd-bluetoothd, should be able to do this automatically Mar 20 07:35:14 fred__tv: https://wiki.archlinux.org/index.php/Bluetooth has a lot of inspiration for proper setup Mar 20 07:45:59 nice ! Mar 20 07:46:21 I was using rfcomm ... Mar 20 08:22:34 Hi, looking for information on how to program the C66 DSPs, where can I find a tutorial or similar? Mar 20 08:29:17 For the beagleboard x15 that is Mar 20 09:29:44 Hi, do I need to modify the device tree (am57xx-beagle-x15-revc.dts) to be able to use a Ti WL1801MOD WiLink Wi-Fi and Bluetooth module? The drivers seem to be enabled in the linux kernel I am using. Mar 20 09:30:49 connecting anything to the expansion headers of the beagleboard-x15 generally requires both a custom device tree and a custom u-boot (since that's where pin configuration is done) Mar 20 11:06:05 I've got the custom u-boot, however, I don't know how to modify the device tree, is there any example I could follow to add WiFi support for am57xx-beagle-x15-revc? Mar 20 11:18:12 there should be plenty of examples for the device tree declarations for a wilink8 Mar 20 11:18:47 e.g. those of one of the beaglebone black wireless or beaglebone blue (minus the pinmux declarations of course) Mar 20 11:27:54 you can probably find more examples by doing grep -rlI 'ti,wl18' in arch/arm/boot/dts in the linux kernel tree (or src/arm in the dtb-rebuilder tree) Mar 20 11:28:57 oh that actually yields results that should be directly applicable: am57xx-evm-common.dtsi Mar 20 11:55:35 I will have a look, thank you very much!! Mar 20 13:04:58 <__ikki__> Is there any major problem if I disable `enable_uboot_cape_universal=1` ? Mar 20 13:05:21 <__ikki__> Have a similar problem: https://groups.google.com/d/msg/beagleboard/HpR7FkkrVK4/cAis3JlVBAAJ Mar 20 13:05:58 I'm assuming with the virtual ethernet interface my Beagle's 192.168.6.2 address cannot be accessed by anything but my laptop? Mar 20 13:09:41 <__ikki__> zmatt: This is what I get: https://pastebin.com/FSJu4Sa2 Mar 20 13:40:43 Hi, where can I find CE certificate for BB Blue? Mar 20 13:41:32 Bone_: google :P Mar 20 13:42:09 "ask your distributor" Mar 20 13:42:31 galaxie: the usb-ethernet interface just connects the beaglebone to your laptop yes. in theory you can set up your laptop to be a bridge, but it's typically easier to just plug the beaglebone into an ethernet network Mar 20 13:43:38 __ikki__: uhh, context? are you using a custom overlay? if so, can you pastebin its source code? Mar 20 13:44:10 __ikki__: if you enable cape-universal, you won't have cape-universal. that's the totality of consequences Mar 20 13:44:14 *if you disable Mar 20 13:45:38 zmatt: I can't seem to get Internet sharing working on Debian, unfortunately. The BBB is up and running, and i can SSH and stuff, but sharing doesn't seem to work. Mar 20 13:46:38 galaxie: that's why I said "it's typically easier to just plug the beaglebone into an ethernet network" Mar 20 13:47:00 people often have trouble sharing internet from your laptop to the beaglebone Mar 20 13:47:32 zmatt: Huh, I'm seeing dropped packets logged when I try pinging my laptop from BBB. Let me look into that.. Mar 20 13:47:38 in part because it also requires changing network settings on the beaglebone side, which risks cutting off your access to it (although you should still be able to use the serial console it exposes via usb) Mar 20 13:48:00 I also don't exclude the possibility that windows firewall gets in the way Mar 20 13:48:06 zmatt: If I connect to Ethernet, though, that would allow others access to the machine? Mar 20 13:49:39 if you connect it to an ethernet network then anyone on that network can access the beaglebone. if you stick it into the ethernet port of your laptop (while your laptop is connected to a wifi network), you will still need to enable internet sharing, but at least it won't require messing with settings on the beaglebone side Mar 20 13:50:47 zmatt: Oh, no messing with settings on laptop then? Mar 20 13:54:16 uhh, like I just literally said: if you connect the beaglebone directly to an existing network then no settings have to be changed anyone, but if you connect it directly to your laptop as an indirect way to connect it to a wifi network, then you'd still need to enable internet sharing on your laptop (but no messing with settings other than that) Mar 20 13:55:32 zmatt: The Ethernet interface is wanting to send out DHCP broadcasts, why would it need to do that? My laptop already has an assigned IP. Mar 20 13:56:37 zmatt: And the reason I asked the last quesiton was because I'm trying the Ethernet from BBB to laptop, not through USB. Mar 20 13:57:18 that should actually work, but by default you'll probably only have working link-local IPv6 Mar 20 13:57:39 you should still be able to find the beaglebone using mdns though, i.e. "beaglebone.local" Mar 20 13:58:19 zmatt: Pinging beaglebone.local doesn't work, probably because mDNS works on different port that's blocked. Mar 20 13:58:46 both your laptop and the beaglebone will try to acquire an IPv4 address using DHCP (already an IP on another interface is not relevant), but there's no DHCP server Mar 20 13:58:51 mDNS normally works on all interfaces Mar 20 13:59:02 what OS are you using on your laptop? Mar 20 14:00:07 Debian 9. Mar 20 14:00:24 then it should definitely Just Work I think Mar 20 14:00:45 can you pastebin 'ip addr show eth0' Mar 20 14:00:56 also, try ping6 instead of ping Mar 20 14:03:25 I don't have a eth0, but an equivalent: https://pastebin.com/KiPKnurA Mar 20 14:06:59 avahi-resolve-host-name beaglebone.local (if you have avahi-utils installed) Mar 20 14:07:40 I don't have it installed; is there an equivalent? Mar 20 14:08:26 it's installed on teh beagle by default.. Mar 20 14:08:29 you should really get a usb serial console going so you can diagnose these issues Mar 20 14:08:42 I don't think there's any issue on the beaglebone side Mar 20 14:09:14 Wait, am I supposed to run that on my laptop or BBB? Mar 20 14:09:34 laptop Mar 20 14:11:16 I'm trying to figure out which interface actually is my BBB. I used the second one to run that dhclient command, but now I'm not sure if it would work for forwarding: https://pastebin.com/zd2VjLqT Mar 20 14:11:19 i have a recently installed debian 9.5 image and it shows up here as beaglebon.local Mar 20 14:12:00 Maybe either interface would work, so long as I'm consistent? Mar 20 14:12:57 Also, what determines whether the IP would be 192.168.6.2 or 7.2 or 8.2? It seemed to change from last night. Mar 20 14:13:16 both should show up on linux Mar 20 14:13:28 OK, beaglebone.local works now. Mar 20 14:13:32 yeah but via usb Mar 20 14:13:54 can you disconnect it from usb (power it otherwise) and just connect ethernet? Mar 20 14:13:59 They both are... but the '05 Mar 20 14:14:20 they both are.. but hte '05' mac address is misconfigured: Mar 20 14:14:21 * rcn-ee[m] sent a long message: < https://matrix.org/_matrix/media/v1/download/matrix.org/FWrqFovupxtwOburiEzxvQcR > Mar 20 14:14:30 I can't seem to find a cable that would power it. Mar 20 14:15:18 rcn-ee: How's it misconfigured and how do I fix it? It was like that the first time I plugged it in. Mar 20 14:15:36 journalctl | grep cpsw Mar 20 14:15:38 busctl call org.freedesktop.Avahi / org.freedesktop.Avahi.Server ResolveHostName iisiu -- 2 -1 beaglebone.local -1 0 Mar 20 14:15:46 simplest fix is just burn a new image on the sdcard Mar 20 14:16:11 I just burnt it yesterday! Mar 20 14:16:20 which one are you using? Mar 20 14:16:37 The very latest stretch-iot image. Mar 20 14:16:57 wait why is anyone thinking there's an issue on the beaglebone side? Mar 20 14:17:00 k can't help there i just used the desktop debian 9.5 .. everything just worked out of the box Mar 20 14:17:26 galaxie: just to confirm, what exactly are you trying to achieve? Mar 20 14:17:43 Hmm, I might have ran route add default gw 192.176.7.1 with different IPs more than once.. Mar 20 14:17:51 since I seem to recall the ultimate goal was to grant other hosts on the network access to your beaglebone Mar 20 14:17:55 so the '05' address should be 192.168.7.1, and giving your laptop 192.168.7.2 Mar 20 14:17:55 heh .. "i might have" Mar 20 14:18:24 I'm trying to share my Internet either through the USB interface or the Ethernet port, both connected to my laptop at the moment. I do NOT want it accessed by anyone except my laptop on the local network. Mar 20 14:18:33 did you try to manually update teh ip address on '05'.. (aka what does it look like on a clean bootup..) Mar 20 14:18:59 so the bbb is going to be the gw for your laptop? Mar 20 14:19:04 rcn-ee: Not yet, should I do sudo shutdown -r ? Mar 20 14:19:07 or the laptop is going to be the gw for the bbb Mar 20 14:19:10 galaxie: ok, then easiest is to enable internet sharing to your laptop's ethernet, and connect the beaglebone via that, and do not mess with any settings on the beaglebone Mar 20 14:19:35 Rickta59: gw = gateway? Laptop would be the one sharing the Internet. Mar 20 14:20:04 galaxie: when you share internet access to the beaglebone, your computer will act as dhcp server Mar 20 14:20:40 since you'd use ethernet for that, your ability to access the beaglebone via usb won't be affected hence you'll be able to verify things are working as desired on the beaglebone side Mar 20 14:21:01 sharing internet via usb it also possible, but more involved and error-prone Mar 20 14:21:06 *is also Mar 20 14:21:15 And slower? Mar 20 14:21:20 no idea Mar 20 14:22:07 theoretically it could be faster, but reality may very well be otherwise Mar 20 14:25:25 So, assuming I am trying to use my Ethernet connection (i.e. I connected an Ethernet cable from my BBB to my laptop), would this tutorial, plus renaming, be sufficient? http://robotic-controls.com/learn/beaglebone/beaglebone-internet-over-usb-only Mar 20 14:26:09 galaxie: I would suggest none of that Mar 20 14:26:21 you can probably just enable internet sharing in the network settings gui Mar 20 14:26:25 and be done Mar 20 14:28:14 My machine uses wicd-daemon, and I see a wired connection, but it looks like it wants to connect to the BBB versus share the network?? Mar 20 14:28:16 you may need to apt-get install dnsmasq-base for the option to show up Mar 20 14:28:18 so is this all because you don't have an ethernet cable? Mar 20 14:28:23 Rickta59: no Mar 20 14:28:57 Oh, no, I have an Ethernet cable, and it works fine. Mar 20 14:29:32 zmatt: Already installed. I typically use my local DNS server for DNS here. Mar 20 14:31:17 galaxie: oh, then I'm not sure since it might conflict with network-manager's use of it Mar 20 14:32:04 Huh, I might not be using the right cable. How can I easily tell if it's a cross-over? I need that, right? Mar 20 14:32:13 doesn't matter Mar 20 14:32:17 also, you had link up already Mar 20 14:32:22 Figures. Mar 20 14:32:54 Do I need a DHCP server installed on my laptop? Mar 20 14:33:08 yes, which is what dnsmasq is used for Mar 20 14:33:38 either that or both sides need manual configuration (but the benefit of doing it via ethernet was that no manual configuration is required) Mar 20 14:34:29 Oh, I just saw that. Two in one I guess. Mar 20 14:35:00 if you don't use the simple internet sharing provided by the network-manager gui, then it's probably not really easier to share internet via ethernet than via usb Mar 20 14:35:47 I'm using Wicd Network Manager, are we referring to a different one? Mar 20 14:35:47 (in fact probably the opposite) Mar 20 14:36:10 uhh, I was assuming the default for debian, which I'd assume is still gnome network manager Mar 20 14:36:13 I don't know anything about wicd Mar 20 14:36:18 I mean, if I get it to work over USB that'd make it easier and less cluttered. Mar 20 14:36:21 I use LXDE. Mar 20 14:36:36 So yeah, not gnome. Mar 20 14:37:03 in that case, good luck! :D I kinda need to go back to focus on work stuff anyway Mar 20 14:37:34 Alright. I'll mess around further and see what I do. Mar 20 14:37:55 via usb, in theory all you need to do is setup iptables on your laptop and add a default route to the beaglebone Mar 20 14:38:02 *on the beaglebone Mar 20 14:38:40 I rebooted the Beagle and the default route table is smaller than last I checked.. Mar 20 14:38:55 What's the default route? The first one on netstat -nrv? Mar 20 14:38:59 adding a default route won't be persistent Mar 20 14:39:23 default route(s) are those starting with "default via" in the output of "ip route" Mar 20 14:39:45 (I don't know anything about the archaic output of legacy tools like netstat or ifconfig) Mar 20 14:40:16 Grr, there's two usb interfaces, usb0 and usb1 on BBB. Use the 7.2 or 6.2 one? Mar 20 14:40:26 doesn't matter Mar 20 14:41:14 so the usb gadget on the bbb is creating two usb devices? 192.168.6.1 and 192.168.7.1 ? Mar 20 14:41:22 * years ago I remember only one Mar 20 14:41:27 one is CDC-ECM, one is RNDIS Mar 20 14:41:31 ic Mar 20 14:41:45 sp the 6.1 is the CDC? Mar 20 14:41:48 usb0 = Windows RNDIS, usb1 = CDC (Mac). Mar 20 14:41:53 Linux get's both ;) Mar 20 14:41:54 Apple only supports the standard CDC-ECM and not microsoft's proprietary RNDIS Mar 20 14:42:11 Microsoft never bothers implementing standards and just uses their own proprietary crap Mar 20 14:42:23 True. Mar 20 14:42:28 in theory, this makes both Apple and Windows work "WithOut" a driver install.. Mar 20 14:42:36 until microsoft broke there own RNDIS driver again.. Mar 20 14:42:39 beaglebone.local is 192.168.6.1 for me .. Mar 20 14:42:46 rcn-ee[m]: I thought that had been fied again? Mar 20 14:42:48 * connecting host is linux Mar 20 14:42:49 Rickta59: it'll be both Mar 20 14:43:33 rcn-ee[m]: *fixed Mar 20 14:43:36 it should be fixed again, but we have another month, till the next Windows 10 update, and i bet they break it again.. Mar 20 14:43:38 '05 somehow is different now, it's now shown as an Ethernet interface? I guess I'll use that one for http://robotic-controls.com/learn/beaglebone/beaglebone-internet-over-usb-only Mar 20 14:44:08 galaxie: I'd look for more recent instructions Mar 20 14:44:26 for one, step 1 of those instructions already looks bad Mar 20 14:45:03 https://github.com/RobertCNelson/boot-scripts/tree/master/network scripts were meant to try to address this. Mar 20 14:45:19 it also looks like it'll do ip masquerading for all traffic from your laptop and not just forwarded traffic, but I'm not 100% sure Mar 20 14:45:32 howdy rcn-ee! Mar 20 14:45:33 so it seems i can connect to both although beaglebone.local only seems to be 6.1 based on a ping Mar 20 14:45:37 yeah, there is a script under: /opt/scripts/network/usb* Mar 20 14:46:00 Rickta59: beaglebone.local just resolves to one of them Mar 20 14:46:17 if you manually take down that interface, it should resolve to the other one Mar 20 14:46:54 rcn-ee: There's two of them, one for 7.1 the other for 6.1.. Mar 20 14:47:01 so does it default to cdc because that is better when connecting from linux? Mar 20 14:47:17 rcn-ee: Also, it's the same as that tutorial above, except without that ifconfig thing. What DOES that do anyways? Mar 20 14:47:39 Rickta59: nah probably just whichever it finds first Mar 20 14:47:46 Rickta59: linux really doesn't care Mar 20 14:47:58 galaxie, use "either" in linux, it doesn't matter.. Mar 20 14:48:12 ifconfig -a just shows you the interfaces in the console window.. Mar 20 14:48:27 Well, good news, I can ping 8.8.8.8.. let me setup DNS.. Mar 20 14:49:04 (note: "ifconfig" and "route" are deprecated legacy tools, their replacement is the "ip" tool) Mar 20 14:49:08 seems avahi is the picker .. i pull usb1 down and then avahi didn't acknowledge that until i stopped and started it Mar 20 14:49:25 Rickta59: that's odd, it should react immediately Mar 20 14:50:02 to be honest i had disabled it .. and just use # Mar 20 14:50:02 DNS working, everything working, however I did that. Thanks everyone! Mar 20 14:50:07 ifconfig -a is easy to remember, no idea on "ip.." ;) Mar 20 14:50:13 "ip addr" Mar 20 14:50:34 (or "ip address") Mar 20 14:51:13 see that's hard.. it should be 'ip -a'. Mar 20 14:51:56 except ip can display way more information than just ip addresses... a true "ip -a" would vomit pages and pages of output across your screen :P Mar 20 14:51:57 Now, any sort of quick check-up list of securing my BBB? Like do I need to regenerate SSH keys, change root password, etc.. Mar 20 14:53:03 root should not have a password configured Mar 20 14:53:14 ssh keys are generated at first boot after flashing Mar 20 14:53:17 galaxie, ssh key's get re-generated on first bootup... root is locked out of ssh, but it's password is root.. you should change teh default user password thou... as it's been the default over 10 years and available over ssh.. Mar 20 14:53:29 it has a password by default? Mar 20 14:53:32 didn't know that Mar 20 14:53:49 rcn-ee: temppwd? I'm logging in through debian account.. that the default user account? Mar 20 14:54:03 yeap it's 'root'... angstrom had a blank.. we 'faked' a blank in debian 7.x days.. Mar 20 14:54:03 rcn-ee[m]: not too relevant though since noone can access his beaglebone Mar 20 14:54:17 galaxy correct.. Mar 20 14:55:01 rcn-ee[m]: why does it have a password configured at all? Mar 20 14:56:07 it's the debian way, root is always "available" and "enabled" so some tools expect it to be available.. whereas ubuntu disables it outright.. Mar 20 14:56:13 instead of just root:*:16502:0:99999:7::: Mar 20 14:56:22 hm Mar 20 14:56:51 what tools? Mar 20 14:57:23 initramfs, when it dumps you to the console on a failed fsck on bootup.. Mar 20 14:57:40 (that one has hit me the most) Mar 20 14:57:51 oh lol, can't that be disabled? Mar 20 14:58:43 Should someone gain user access, though, with the default root password, they'll elevate, right? So I should change the root password if so? Mar 20 14:59:02 galaxie: should someone gain user access, they have sudo rights anyway Mar 20 14:59:29 galaxie, the default user 'debian' has wheel privileges, so if they get that user, they have root.. Mar 20 14:59:42 the difference between the debian account and root is just to prevent accidently wrecking your system with a typo, it does not offer any security in the default configuration Mar 20 15:03:25 zmatt: So change default passwords on root and debian, and remove debian from wheel, requiring a different password for root access? Mar 20 15:03:42 <__ikki__> zmatt: I was using your dt-overlay utils spi0.dtsi Mar 20 15:03:51 galaxie: how about just prevent people from gaining access to any account in the first place Mar 20 15:03:54 galaxie: that's a lot simpler Mar 20 15:04:07 __ikki__: the latest version? Mar 20 15:04:47 preventing malicious actors to become 'local' is *always* a good idea Mar 20 15:04:48 <__ikki__> yes! Mar 20 15:05:21 galaxie: the debian account has far-reaching rights on the beaglebone, since you typically need those on an embedded system and it is intended that the debian account is usable for most purposes Mar 20 15:05:32 <__ikki__> 8a37404 (HEAD -> master, origin/master, origin/HEAD) cape-universal compatibility and other cleanups Mar 20 15:06:23 __ikki__: odd, I wonder if status="disabled"; doesn't work for spi devices... which I'd consider to be a kernel bug, but I don't exclude the possibility Mar 20 15:06:27 zmatt: Then maybe change root and debian passwords and use a normal user account for most things? Mar 20 15:06:47 I would rather have used /delete-node/ but that isn't supported by overlays Mar 20 15:07:23 galaxie: if by "most things" you don't mean "most things for which people would typically use a beaglebone" Mar 20 15:08:30 galaxie: why are you worried about people gaining local access to your beaglebone? you're behind NAT (and probably two layers of it) Mar 20 15:09:05 zmatt: My use case is a bit different, but my RPi wouldn't boot so I'm using BBB. I'm more worried of malware actually. I'd rather not run stuff on an account like that. Mar 20 15:09:34 <__ikki__> zmatt: Uh, what other method should I try to enumerate a spi sensor ? Mar 20 15:09:46 galaxie: malware? you're browsing the internet on your bbb? poor you Mar 20 15:11:17 zmatt: More like running a server. Mar 20 15:11:53 __ikki__: if disabling spi devices doesn't work (like I attempted to do with lines 11-14 of spi0.dtsi), then your options are disabling cape-universal or giving your own spi device node(s) the same name as those used by cape-universal Mar 20 15:12:04 (to overwrite their settings) Mar 20 15:12:26 or fixing the kernel to make disabling spi devices work :P Mar 20 15:12:49 (which is probably a two-line patch in the right place) Mar 20 15:13:00 https://libreboot.org/docs/install/bbb_setup.html Debian 9.5 2018-10-07 4GB SD LXQT I installed debian on beaglebone black revision c. On the libreboot website it says you have to set up spidev. Does that also apply for debian 9.5? Are there some instructions which are easier to read? Mar 20 15:13:54 flj, spidev is enabled out of the box, just use config-pin to set the spi pinmux, or use the spidev overlay in /boot/uEnv.txt Mar 20 15:15:04 thank you. So all what is written on libreboot's website about spidev I do not have to consider? Mar 20 15:15:16 <__ikki__> zmatt: disabling cape-universal was what rcn-ee[m] recommended: https://groups.google.com/d/msg/beagleboard/HpR7FkkrVK4/cAis3JlVBAAJ Mar 20 15:15:38 <__ikki__> I will give it a try.. Mar 20 15:16:17 __ikki__: in that case you may also need to remove (or comment out) lines 11-14 of my overlay Mar 20 15:19:28 "use config-pin to set the spi pinmux" Can you elaborate? Mar 20 15:20:02 zmatt: df -h shows /dev/mmcblk0p1 3.3G 2.1G 976M 69% / ... did I run from eMMC this whole time? Mar 20 15:20:25 galaxie: no, mmcblk0 is sd card Mar 20 15:20:39 <__ikki__> rcn-ee[m]: I used https://github.com/mvduin/overlay-utils/blob/master/spi0.dtsi to enumerate a spi sensor but it fails:https://pastebin.com/FSJu4Sa2 Mar 20 15:20:48 <__ikki__> What do you recommend ? Mar 20 15:21:18 m Mar 20 15:22:34 Hmm, what's a quick way to make sure my BBB first checks if there's a valid microSD installation and boots from that before checking eMMC? Mar 20 15:23:04 m Mar 20 15:23:06 whoops Mar 20 15:23:16 hold S2 iirc Mar 20 15:23:18 on boot Mar 20 15:23:45 And if I want it to boot up to SD by default? Mar 20 15:24:17 destroy emmc image so that it defaults to SD Mar 20 15:24:45 I assume I can later flash eMMC if I choose? How would I wipe the image? Mar 20 15:25:41 the quickest way .. make the password on the emmc different from the sdcard Mar 20 15:27:54 galaxie: it does this by default Mar 20 15:28:05 (try to boot from sd before trying to boot from eMMC) Mar 20 15:28:22 zmatt: But you have to hold the S2 button down?? Mar 20 15:28:25 however the bootloader is loaded from eMMC by default, and SD only as fallback Mar 20 15:28:30 that's what the S2 button overrides Mar 20 15:28:48 if the image on eMMC and the image on SD are of similar age there isn't a problem Mar 20 15:29:20 however if they aren't, then using the bootloader on eMMC to load linux from sd card can result in problems (ranging from not being able to boot to merely having subtle issues) Mar 20 15:29:35 that's why I usually recommend wiping eMMC when booting from sd card Mar 20 15:30:53 note that instead of pressing the button, you can achieve the same by connecting a resistor (1K-10K or so) from P8.43 to ground Mar 20 15:31:08 zmatt: OK. How do I tell if I loaded from SD or eMMC? That df command makes me think I'm running from eMMC.. Mar 20 15:31:20 mmcblk0 = sd, mmcblk1 = eMMC Mar 20 15:32:02 So why's the size so small? My SD card is 32 GB... do I need to resize partitions or something? Mar 20 15:32:04 note that the size df shows is of the filesystem (which is bounded by the partition size), not the entire card Mar 20 15:32:08 yeah Mar 20 15:32:35 Hi, I have modified u-boot and device tree to enable a WL18xx WiLink on beagleboard x15, how can I know that the module has been correctly configured when I run Linux? The wlan interface doesn't appear yet, and I would like to find out if I have a software or hardware problem in my system. Mar 20 15:32:38 There a nice way to do that while I'm still running from SD? Mar 20 15:32:39 galaxie: iirc there's a script for that somewhere in /opt, although doing it manually is also quite easy: https://pastebin.com/ThmLM0pX Mar 20 15:33:16 I think you can also use partprobe instead of rebooting, not sure Mar 20 15:36:54 zmatt: So run first command, sudo shutdown -r now, then third command? Mar 20 15:37:38 zmatt: that lirc thing (IR) is a trash.... Mar 20 15:37:54 something you know more reliable ? Mar 20 15:38:55 galaxie: 'sudo reboot' is less typing :P Mar 20 15:39:03 zmatt: Says Re-reading the partition table failed.: Device or resource busy. I guess that's why you reboot? Mar 20 15:39:22 fred__tv: I'm sure lirc is fine. if you mean gpio-ir-receiver is unreliable then that doesn't surprise me Mar 20 15:40:56 galaxie: yes Mar 20 15:41:27 yep, probably that gpio way.... Mar 20 15:43:41 fred__tv: like I said last time, the beaglebone has fine facilities for it, but it seems nobody has bothered to write drivers for them Mar 20 15:44:05 .....so ...peace and love Mar 20 15:44:09 zmatt: I still have to run sudo dhclient -v enx84eb18e20b08 everytime I reboot. There a way to do that automagically? Mar 20 15:44:41 <__ikki__> rcn-ee[m]: ping! Are you there ? Mar 20 15:45:08 galaxie: get a network manager that isn't broken? Mar 20 15:45:42 running the dhcp client is exactly the job for a network manager Mar 20 15:45:48 zmatt: Fair enough. I'll research. About how long does partition resizing take? Mar 20 15:45:56 basically zero time Mar 20 15:47:11 Ah, took about 1 minute. Mar 20 15:47:35 df -h looks much more reasonable now. Thanks! Mar 20 15:47:39 ah you mean the filesystem resize? I guess that might take a bit longer yeah Mar 20 16:04:47 zmatt: it's a tsop1738 , as the schematic is this https://imagebin.ca/v/4ar5Z7yvH6Lu , I've connected Vs directly to VDD3V3 and output directly to gpio, with a 4u7 cap across supply pins, am I wrong ? Mar 20 16:12:36 fred__tv: seems fine. be sure to put ACTIVE_LOW in the device tree, not ACTIVE_HIGH (I can't remember what the example used) Mar 20 16:13:59 How gentle on the sd card is stretch-iot? I know a lot of live systems and such try to minimize writing to flash storage as much as possible.. Mar 20 16:14:33 ok, debugging with irw it displays the right button pressed but sometimes pressing buttons nothing is displayed (received/decoded) Mar 20 16:15:46 galaxie, we only set noatime in /etc/fstab, otherwise it's just the defaults, systemd does detect it is an ssd and we have trim enabled too.. Mar 20 16:25:49 rcn-ee: So not particularly gentle? Mar 20 16:25:51 galaxie: I'd personally consider at least apt-get purge rsyslog and rm -rf /var/log/journal to keep only runtime journal Mar 20 16:27:28 galaxie, if you want it to be more gentile, open up /boot/uEnv.txt and enable the overlayroot option... Mar 20 16:27:52 the file system will be ro, and use half the memory as the overlay fs.. Mar 20 16:27:56 zmatt: So it doesn't log more than that session? Mar 20 16:28:10 galaxie: it wouldn't preserve logs across reboots Mar 20 16:28:23 if that's not acceptable, then mkdir /var/log/journal Mar 20 16:28:37 I'd still recommend removing rsyslog since its logging is redundant Mar 20 16:28:57 rcn-ee: Read-only? So I could perhaps switch back and forth, to allow write access whenever I need to upgrade software? Mar 20 16:29:37 making the whole root ro+overlay is a more extreme version of keeping stuff only in ram, but it also sounds like a great way to quickly exhaust ram Mar 20 16:30:11 in case it's useful, here's a script to monitor the amount of data written: https://pastebin.com/SCYTWNez (this is for eMMC, but you can just replace mmcblk1 by mmcblk0 to monitor sd card instead) Mar 20 16:30:29 galaxie, overlayroot is actually pretty nice.. by default the drive is ro, but with one command "sudo overlayroot-chroot" and then update your packages, and exit. and your drive has been updated.. Mar 20 16:30:42 that's nifty Mar 20 16:30:54 but it still sounds like a hack Mar 20 16:31:08 rcn-ee: So that command spawns some shell? Mar 20 16:31:44 bash, or what ever you send to it.. Mar 20 16:31:48 http://manpages.ubuntu.com/manpages/cosmic/man8/overlayroot-chroot.8.html Mar 20 16:32:34 but unlike the classic, just mount the drive as 'ro' overlayroot, works well with systemd, and more advanced applications (xorg, etc..) Mar 20 16:32:38 fred__tv: if it works sometimes when probably your configuration is fine, and the trouble is simply because using a gpio and software timestamping sucks Mar 20 16:33:42 galaxie: systemd can also enable accounting of how much data is written by which services to which block device(s) Mar 20 16:33:55 which can be helpful to track down who's pointlessly writing data Mar 20 16:34:01 Debian has a bigger list of all the issues seen with a pure "ro" https://wiki.debian.org/ReadonlyRoot Where as overlayroot just works.. Mar 20 16:34:10 zmatt: Any services and servers I might want to disable? I won't be needing the Apache server. Mar 20 16:34:43 that's up to you :) Mar 20 16:35:06 this is what boot looks like on one of my beaglebones: https://liktaanjeneus.nl/boot.svg Mar 20 16:35:22 most things are socket based, so even if they are enabled, they don't take much.. Mar 20 16:50:29 galaxie: in case you want to track how much data is written by which service: https://pastebin.com/s3HwHpyp Mar 20 16:50:38 as before, replace mmcblk1 by mmcblk0 to track sd card writes instead of eMMC writes Mar 20 16:50:54 (and yes this script is disgusting) Mar 20 16:56:42 zmatt: I never did like Perl. It was the first language I learned (or attempted to learn) back when I was a pre-teen. Mar 20 16:57:17 I like perl. especially for quick little scripts Mar 20 17:17:12 zmatt: can you verify the syntax of the line: perl -n - **/blkio.io_service_bytes_recursive <<'END' Mar 20 17:17:42 raffo: the script works Mar 20 17:18:00 that line is valid, keeping in mind it is the start of a here-doc Mar 20 17:19:17 pastebin changed the quote characters, and the downloaded file was in windows format. Mar 20 17:19:43 pastebin does not change quote characters Mar 20 17:20:32 something changed, after re-typing the line it works. Mar 20 17:22:27 if I download https://pastebin.com/raw/s3HwHpyp and change line-endings from CRLF to LF (a bit annoying that wget seems to have no option to do that for you) it works for me Mar 20 17:24:47 zmatt: dos2unix works fine for me. Mar 20 17:24:53 yeah that works Mar 20 17:25:58 now I just need some data. How do you reload systemd after modifying /etc/systemd/system.conf? Mar 20 17:26:34 systemctl daemon-reload but you may want to reboot to ensure block account is enabled for all units Mar 20 17:26:39 *accounting Mar 20 17:26:57 the default only applies to units started after reloading I think Mar 20 17:38:52 so if i'm using a minimal setup on the emmc * just the first 4MiB of sdcard copied to the emmc + a ext4 filesystem with just a /uEnv.txt .. will I have to manually keep the u-boot binary in sync by hand? Mar 20 17:39:06 running off usb hard disk Mar 20 17:41:02 in sync with what? in the rare case you want to update u-boot, you'll have to do it on eMMC obviously since that's where it's loaded from Mar 20 17:41:16 does the u-boot/mlo files change much? Mar 20 17:41:46 they are normally never updated, and in particular they are never updated automatically Mar 20 17:41:53 k .. good Mar 20 17:42:26 without the sdcard I had to add to the uEnv.txt Mar 20 17:42:28 mmcdev=0 Mar 20 17:42:28 mmcpart=1 Mar 20 17:42:52 that seems confusing seeing as the emmc is really /dev/mmcblk1p1 Mar 20 17:43:16 your uEnv.txt looked overall excessively complicated and confusing, but I didn't feel like digging into it Mar 20 17:43:38 k .. i basically copied the bbb-uEnv.txt and changed all mmc to usb Mar 20 17:43:49 "the bbb-uEnv.txt" ? Mar 20 17:44:02 ls /bbb-uEnv.txt Mar 20 17:44:10 came on my sdcard image Mar 20 17:44:21 no idea what that file is or what would ever consult it, probably some compat-thing for ancient bootloaders Mar 20 17:45:13 comments indicate you are supposed to copy that to /uEnv.txt Mar 20 17:45:36 that file is also normally never present, only when used for backwards-compat with ancient bootloaders Mar 20 17:45:55 ic Mar 20 17:46:11 * wonders why booting from hard disk is considered esoteric Mar 20 17:48:06 because generally you don't want your rootfs to be located on an external device that sicks out of the beaglebone I guess? Mar 20 17:48:11 *sticks Mar 20 18:03:12 i tend to use usb hubs to isolate my computers from stupid things i do with usb devices Mar 20 18:03:24 so i already have a lot of things sticking out Mar 20 18:03:42 yeah but most usb devices can be happily unplugged Mar 20 18:04:07 i'd rather fry a hub instead of a bbb Mar 20 18:04:10 or rpi Mar 20 18:04:34 frying something via usb? how on earth would you manage that? Mar 20 18:05:02 doing stupid things .. and it hasn't happened .. just want to at least feel somewhat protected Mar 20 18:06:20 actually I guess it might happen if you connect a woefully non-usb-compliant device to the beaglebone's usb host port (a raspberry pi for example) Mar 20 18:06:58 i've got this horrendous bluepills from china .. i don't really trust them to be safe Mar 20 18:07:04 (if I remember the rpi correctly) Mar 20 18:07:37 * horrendous but lots of fun Mar 20 18:07:56 * stm32f103c8t6 developement boards from aliexpress and ebay Mar 20 18:08:05 note that an example of a bad device to connect would be some crappy chinese powered usb hubs Mar 20 18:08:11 :P Mar 20 18:10:04 basically anything that backfeeds power or pulls up data lines without vbus present (the former implies the latter, since backfeeding power means you can't possibly have vbus detection) Mar 20 18:10:15 i have some plugable technology boards Mar 20 18:10:27 i think they are UK based Mar 20 18:11:17 maybe US Mar 20 18:11:24 * based on their open jobs Mar 20 18:11:30 https://plugable.com/about/careers/ Mar 20 18:12:19 wow, apparently so many usb hubs violate the specs that people actually have trouble finding usb hubs that behave properly Mar 20 18:12:34 rcn-ee: Not sure what is wrong with my buildroot u-boot build for AI, but it is saying "spl: could not find mmc device 0. error: -19" Mar 20 18:18:37 hum, either the regulator or mmc node, it's using spl-dt.. Mar 20 18:18:47 doh, I think I messed up the default dt. Mar 20 18:19:21 yeah, I think you ID'd it. surprised it built. called it am57xx-bbai one place and am57xx-beagleboneai in another. Mar 20 18:20:33 evil renames.. and we are still detecting the board on a lack of eeprom.. Mar 20 18:30:27 rcn-ee: grrr... the dt change didn't seem to fix it. maybe I broke the dt for u-boot? Mar 20 18:31:06 rcn-ee: you are using am57xx_evm_defconfig, yes? Mar 20 18:35:05 yeah, i was using the generic am57xx_evm_defconfig Mar 20 18:49:19 howdy behanw Mar 20 18:51:25 rcn-ee: have you seen my 0001-BeagleBone-AI.patch for u-boot? we probably need to work out a public place to share this work. wonder if we should just open up the github. Mar 20 18:52:32 other then the few blobs in teh git history, that should be fine. Mar 20 18:59:20 jkridner[m]: Hey! Mar 20 19:00:23 rcn-ee: maybe flatten the history with a direct copy? Mar 20 19:01:13 sure do a fresh clone, copy to new repo.. Mar 20 19:01:20 we probably need to do something that tells people that things can change before the board ships and something to discourage news and distributor folks from republishing? Mar 20 19:02:45 rcn-ee: I'll try to check with Christi to make sure we don't freek out either her or Embest, but it would be great if you helped clean-up the repo a bit to fix my hackery before publishing. Mar 20 19:03:21 I kinda messed up moving u-boot builds under u-boot at the same time as trying to clean up the name issue. Mar 20 19:03:44 and aligning the dts with what I was hacking on-target. Mar 20 19:14:50 <__ikki__> zmatt: commenting these 11-14 https://github.com/mvduin/overlay-utils/blob/master/spi0.dtsi#L11 didn't work either. Mar 20 19:15:10 __ikki__: in combination with disabling cape-universal? Mar 20 19:15:18 what error are you seeing? Mar 20 19:16:17 <__ikki__> yes, tried w/ and w/o disabling cape-universal. Mar 20 19:16:27 <__ikki__> No, errors as such. Mar 20 19:16:41 ? Mar 20 19:16:46 <__ikki__> Just driver doesn't probe Mar 20 19:18:00 that's a completely different result from earlier though ( https://pastebin.com/FSJu4Sa2 ) Mar 20 19:18:01 <__ikki__> disabling cape-universal results in no files under /dev/spi* Mar 20 19:18:07 none are expected Mar 20 19:18:54 or do you mean with an unmodified spi0.dtbo ? because then an /dev/spidev* device is expected Mar 20 19:19:02 but iirc you were trying to get a different driver working Mar 20 19:19:30 <__ikki__> with cape and commenting L11-14 results in same pastebin link as you posted. Mar 20 19:19:49 yes of course Mar 20 19:20:00 that's not what I asked though Mar 20 19:21:31 lines 11-14 were intended to prevent the issue in the pastebin when cape-universal is enabled. however, if they do not work, then disabling cape-universal is the only option, and lines 11-14 might themselves cause problems Mar 20 19:23:45 note that those errors should not prevent your actual device from working regardless Mar 20 19:24:08 can you pastebin the output of: ls -l /sys/bus/spi/devices/spi0.0/ Mar 20 19:24:42 (or is it spi1.0 ? not sure) Mar 20 19:29:27 <__ikki__> zmatt: I commented `enable_uboot_cape_universal=1` + using original spi0.dtbo = no errors as observed in the pastebin now. Mar 20 19:29:44 exactly, so that problem is solved Mar 20 19:30:23 <__ikki__> yes, "that" problem is solved. Mar 20 19:30:30 (it is an error you can ignore anyway, since it just complains about the spi devices declared by cape-universal, which you don't care about) Mar 20 19:30:46 <__ikki__> But still sensor doesn't probe. Mar 20 19:31:42 can you pastebin 1. your dtsi 2. ls -ld /sys/bus/spi/devices/*/* Mar 20 19:33:46 <__ikki__> zmatt: can you please confirm that P9.18 should be connected to SDO of sensor ? Mar 20 19:34:54 P9.18 is spi0_d1 in mode 0 Mar 20 19:35:02 no, P9.18 is output of the beaglebone and should definitely not be connected to SDO of the sensor, and doing so risks damaging both sides Mar 20 19:35:21 P9.21 is the input Mar 20 19:36:00 rcn-ee[m]: "d0"/"d1" doesn't mean anything to.. basically anyone Mar 20 19:36:37 - ti,pindir-d0-out-d1-in: Select the D0 pin as output and D1 as Mar 20 19:36:38 input. The default is D0 as input and Mar 20 19:36:39 D1 as output. Mar 20 19:37:06 see, even you had to look that up to know whether d1 is input or output in the default config ;) Mar 20 19:37:10 you can swap them in the device tree, if you already spun the board.. Mar 20 19:37:30 true, yes Mar 20 20:00:53 <__ikki__> zmatt: https://pastebin.com/V5SaKT6D Mar 20 20:01:23 "bme680" does not look like a valid compatible-string to me Mar 20 20:02:05 <__ikki__> zmatt: Hmm. should I put whole "bosch,bme680" and try ? Mar 20 20:05:21 looks like the driver doesn't declare any of_device_id. I don't know if there's a fallback mechanism to the spi device id, although if there were I'd assume it would have worked already Mar 20 20:05:32 doesn't hurt to just try it anyway of course Mar 20 20:08:10 <__ikki__> zmatt: It does declare as I added it and compiled new version Mar 20 20:08:18 <__ikki__> Linux beaglebone 4.19.25-ti-r15 #1xross SMP PREEMPT Sun Mar 17 13:29:01 IST 2019 armv7l GNU/Linux Mar 20 20:09:01 then whatever you declare there should match the compatible-string in DT, and should probably be "bosch,bme680" indeed Mar 20 20:10:03 <__ikki__> zmatt: sure, let me try it fill compatible string. Mar 20 20:10:08 <__ikki__> *with Mar 20 20:10:16 also, just to be on the safe side, run "sudo depmod" and "sudo update-initramfs -u" Mar 20 20:10:30 (if setting the correct compatible-string still doesn't work) Mar 20 20:11:28 <__ikki__> zmatt: OK. Mar 21 01:06:55 I have a beaglebone green and I changed am335x-evm.dtb file to dts files to add some board specification in it. Then again I changed the converted dts file to dtb file so that it can be read by the kernel during boot process. Mar 21 01:07:24 At the end, I added a line in /boot/uEnv.txt dtb=am335x-evm.dtb Mar 21 01:07:42 But now I am unable to boot into the BBG Mar 21 01:07:50 All the leds are ON Mar 21 01:08:22 What was rhe problem here? Mar 21 01:08:31 And how can I recover from this? Mar 21 01:14:26 is this because I am using am335x-evm.dtb and not am335x-bonegreen.dtb? Mar 21 01:38:28 shreeya: ehh, what did you expect? the beaglebone green is not the am335x evm, they are totally different boards Mar 21 01:39:38 recovery suggestion 1: boot from sd card, mount eMMC, remove the bogus line from /boot/uEnv.txt on eMMC, unmount eMMC Mar 21 01:40:59 recovery suggestion 2: use serial console cable to interrupt u-boot and manually boot the system with the correct dtb Mar 21 01:41:19 needless to say, the first option is easier Mar 21 02:47:24 i've been compiling on the BBB for 4 hours or so (msp430-elf-gcc) ... 106F that is normal yes? Mar 21 02:47:42 normally i can't even feel any heat Mar 21 02:49:00 you're compiling a cross-gcc-toolchain... on a beaglebone? o.O but why? Mar 21 02:49:15 to see how long it takes Mar 21 02:49:42 but why? :P Mar 21 02:49:48 heh .. you must have a fast desktop Mar 21 02:49:55 since the answer is: long enough that no sane person would do this Mar 21 02:50:03 my 2009 iMac isn't much faster than a bbb Mar 21 02:50:28 it probably is many times faster Mar 21 02:50:46 if i cranked up a compile on my iMac i would fee it Mar 21 02:50:48 feel it Mar 21 02:51:07 this is over there running in a xterm .. no pain .. Mar 21 02:51:23 just mild heat waves off the bbb :) Mar 21 02:51:47 a quick google says that a 2009 iMac is a 3 GHz Intel Core 2 Duo with 2 or 4GB ram Mar 21 02:51:58 yeah that is the top end model Mar 21 02:52:01 which isn't what i have Mar 21 02:52:17 2.something GHz is me Mar 21 02:52:41 2.66 - 3.06 GHz is the range listed, which I just round to 3 GHz :P Mar 21 02:52:55 2.16 is me Mar 21 02:53:00 odd Mar 21 02:53:09 core 2 duo Mar 21 02:53:10 crap Mar 21 02:53:24 i got this for work and never used it Mar 21 02:53:37 then my faster machine died and i turned it on and install linux on it Mar 21 02:53:45 2 GHz core 2 duo is still going to be many times faster than a 1 GHz Cortex-A8 Mar 21 02:53:55 with 16-bit DDR3-800 memory bus Mar 21 02:54:09 it only has 2GB memory Mar 21 02:54:15 the BBB only 512MB Mar 21 02:54:38 anyways it is sort of burn in test for the BBB Mar 21 02:55:16 i've compiled this stuff on a rpi 2 .. i don't think it took that long Mar 21 02:55:28 granted 4 cores vs 1 Mar 21 02:56:42 btw I see no 2009 iMac listed with 2.16 GHz, only really old ones (2006) have that speed listed (but don't have 2GB ram) Mar 21 02:57:17 doesn't really matter, it's still going to be a huge amount faster than the bbb :) Mar 21 02:57:56 i was wondering really about what temp the cpu will start getting throttled Mar 21 02:58:02 it doesn't Mar 21 02:58:06 really .. Mar 21 02:58:07 there's no cpu temp measurement Mar 21 02:58:19 the adc doesn't have a temp channel? Mar 21 02:58:24 nope Mar 21 02:58:26 k Mar 21 02:58:48 there's an internal bandgap temperature sensor, but it's so shit that it's been defeatured Mar 21 02:58:54 ic Mar 21 02:59:09 40C doesn't seem outrageous Mar 21 02:59:25 it has zero problems with that **** ENDING LOGGING AT Thu Mar 21 02:59:57 2019