**** BEGIN LOGGING AT Sun Nov 05 03:00:03 2017 Nov 05 09:59:33 hey there, trying to get started with bbb on os x sierra. USB is plugged in, heartbeat LED is running, able to access mounted folder and install drivers. After a restart, I still can't access bbb. On Chrome I get ERR_CONNECTION_REFUSED for http://192.168.7.2/. On ssh I get Nov 05 09:59:37 ~: ssh -v debian@192.168.7.2 OpenSSH_7.4p1, LibreSSL 2.5.0 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 20: Applying options for * debug1: Connecting to 192.168.7.2 [192.168.7.2] port 22. debug1: connect to address 192.168.7.2 port 22: Connection refused ssh: connect to host 192.168.7.2 port 22: Connection refused Nov 05 10:00:15 How can I access the bbb via usb? Nov 05 18:17:12 hello? Nov 05 18:17:32 is anyone here Nov 05 18:18:03 no, all those people idling here are an illusion Nov 05 18:18:04 http://www.catb.org/esr/faqs/smart-questions.html Nov 05 18:19:08 Does anyone have any tips on getting two beaglebones to talk to each other via their ethernet ports? Nov 05 18:21:58 how would those ethernet ports be connected to each other? cable? cable and switch/hub? cable, switch, router, the big bad internet, router, switch, cable? Nov 05 18:23:12 lets say board to board via a cable Nov 05 18:23:28 could also be through a switch, though Nov 05 18:23:32 let's say that then you need a so called "cross over cable" Nov 05 18:23:58 as I don't think the bbb does auto-MDI/MDX Nov 05 18:24:49 if it's a switch, then you just assign them IP addresses and have them talk to each other. Linux networking 101. Details depend on the Linux distribution that you run on the boards. Nov 05 18:24:53 ok--what extra steps would I need to take if I end up using a switch\ Nov 05 18:25:01 ah nvm haha Nov 05 18:25:16 thank you Nov 05 18:25:28 which would you say is easier to set up? Nov 05 18:25:55 both are the same Nov 05 18:26:01 on the configuration side Nov 05 18:26:17 the direct cable connection requires a special cable though Nov 05 18:27:11 no sure if the BBB does support a normal cable. Easiest would be to just plug in cables and see if the LEDs light up Nov 05 18:27:18 if yes, no special cable needed Nov 05 18:27:34 ok thank you so much Nov 05 20:29:52 hey, im trying to use the adafruit 1.8" display with the pocketbeagle using fbtft, but i think im missing something. i've hooked the display's SPI pins up to SPI0 (as labelled on the board), and run this modprobe: Nov 05 20:29:58 modprobe fbtft_device busnum=1 name=adafruit18 debug=7 verbose=3 gpios=dc:89,reset:26,led:20 Nov 05 20:30:18 and in dmesg, i see this: Nov 05 20:30:20 fbtft_request_gpios: gpio_request_one('dc'=89) failed with -16 Nov 05 20:32:08 i think the sysfs gpio interface is blocking access to the pins, but i cant figure out how to disable it. the guides online reference /sys/devices/bone_capemgr.*, which doesnt exist on this system (latest debian iot image from bbb.io/latest) Nov 05 20:33:32 also, i see /dev/spi1.0 and /dev/spi2.0, but no /dev/spi0.0, which is what i expected since its labelled spi0 on the board. are the /dev/spi* devices offset by one, or do i need to enable spi0 somehow? Nov 05 20:33:55 all the existing guides online on this subject reference the beaglebone black and bone_capemgr Nov 05 20:50:17 darkengine: /sys/devices/bone_capemgr.* is indicative of really old guides (kernel 3.8) Nov 05 20:51:18 the spi device numbering off-by-one is a bogosity of the mcspi kernel driver, I actually patch that out in my own kernel builds :P Nov 05 20:53:56 gotcha, so /dev/spi1.0 is spi0 on the board Nov 05 20:54:49 and all the gpios being occupied is a result of cape-universal. you can disable it in /boot/uEnv.txt. you will then also need to load the DT overlay /lib/firmware/BB-SPIDEV0-00A0.dtbo which you can also config in /boot/uEnv.txt Nov 05 20:55:58 yeah spi1.0 is spi0 cs0 Nov 05 20:57:01 did you flash the latest image to eMMC or are you running from sd card? Nov 05 20:57:33 microSD card Nov 05 20:58:17 i was under the impression the pocketbeagle didnt have an emmc Nov 05 20:58:28 ohh, pocketbeagle, sorry my bad Nov 05 20:58:33 never mind then Nov 05 20:59:19 i changed enable_uboot_cape_universal to 0 in uenv.txt and rebooted, but i still have the /sys/class/gpio stuff Nov 05 21:00:08 I think you need to comment the line out, not set it to any particular value Nov 05 21:01:02 and note that some stuff in /sys/class/gpio always exists (gpiochip*, export, unexport) Nov 05 21:02:13 commented the line out; i still have the /sys/class/gpioN folders, but the modprobe worked Nov 05 21:02:18 so, i think that fixed it? Nov 05 21:02:29 screen didnt light up, but thats another problem entirely Nov 05 21:03:07 ah nope, still broken Nov 05 21:03:13 failed with -16 Nov 05 21:03:52 that's weird, disabling cape-universal should definitely release the claim on the gpios... lemme check something Nov 05 21:04:31 im not certain cape_universal has been disabled. i still see /dev/spi2.{0,1} and didnt enable the overlay for SPI1 Nov 05 21:06:40 oh this is disgusting, it looks like cape-universal is not a separate thing for the pocketbeagle but part of the main pocketbeagle dtb Nov 05 21:08:20 this is a thing you should probably complain about on the forum (or directly to rcn), but I can give you a temporary workaround at least if you hang on a moment Nov 05 21:22:50 grab this project: https://github.com/mvduin/overlay-utils Nov 05 21:23:12 make a file "no-gpio-export.dtsi" with this content: https://pastebin.com/raw/37uK44mr Nov 05 21:23:26 run: make no-gpio-export.dtbo Nov 05 21:23:55 stick that dtbo file in /lib/firmware/ Nov 05 21:25:03 apply that overlay by configuring it in /boot/uEnv.txt (either uboot_overlay_addr4 or dtb_overlay, I have no idea what the difference is) Nov 05 21:26:07 this doesn't fully disable cape-universal, it just prevents automatic exporting of gpios. you'll still need to use the 'config-pin' utility to configure the spi pins Nov 05 21:26:55 i will? i thought enable SPIDEV0 was enough? Nov 05 21:27:13 that overlay doesn't work because cape-universal Nov 05 21:27:20 ah Nov 05 21:27:26 cape-universal is so universal it conflicts with basically everything else :P Nov 05 21:28:01 it claims essentially all unused peripherals and pins, and allows runtime config of pin function Nov 05 21:28:27 convenient, until you need pins for a kernel driver Nov 05 21:29:12 hm, not sure it appreciated that dtbo Nov 05 21:29:23 usr1 and usr0 and solid on after a reboot Nov 05 21:29:29 eh Nov 05 21:31:59 oh I actually got the path wrong, it's /ocp/cape-universal ... oops. not very nice that u-boot completely bugs out on a nonexistent path, but I can't say I'm terribly surprised Nov 05 21:32:54 I hope you have a linux system available to mount the sd card and fix the /boot/uEnv.txt ? Nov 05 21:33:24 of course Nov 05 21:33:51 so the right dtsi content would use &{/ocp/cape-universal} { Nov 05 21:34:49 sweet, booting properly now Nov 05 21:35:47 nice! no gpioN folders Nov 05 21:36:01 oh shit! my screen works! Nov 05 21:36:07 thank you much :) Nov 05 21:36:49 cool :) if you're feeling adventurous you might also consider customizing the main dtb instead of using my overlay. then you can leave cape-universal mostly enabled but just remove the references to the pins you need for the display, and configure spi0 to be automatically enabled while you're at it Nov 05 21:37:11 it actually worked without any pin-configging Nov 05 21:37:15 just booted and modprobed Nov 05 21:37:50 oh, funky... maybe spi0 is enabled by default on the pocketbeagle Nov 05 21:38:06 on the regular beaglebones all pins are gpio by default Nov 05 21:39:22 ah it seems that's indeed not the default for all pins on the pocketbeagle, okay good to know Nov 05 21:40:27 gawd cape-universal is so disgusting when looking at it in the dts Nov 05 21:42:12 a typical .dts file contains maybe a few dozen lines... the pocketbeagle dts (am335x-pocketbeagle.dts), due to cape-universal, is over 2100 lines Nov 05 21:44:58 yikes Nov 05 21:45:24 https://github.com/RobertCNelson/dtb-rebuilder/blob/4.9-ti/src/arm/am335x-pocketbeagle.dts if you're curious Nov 05 21:46:33 that repository also allows you to easily tinker on dts files and rebuild the dtb (if you do so, I suggest making a copy and renaming it, not overwriting the original dtb) Nov 05 21:46:40 select branch to match kernel version Nov 05 22:46:19 I should either get a new beagle bone black or figure how to update my BBB with 2G EMC to a newer kernel suggestions? Nov 05 23:02:17 2G is fine for most purposes Nov 05 23:04:12 anyone else find Rob Nelson's eewiki.net pages dead? Nov 05 23:18:21 Hmm well I was wondering how much space I had to work with, I prefer to strip down things and only have what is necessary for the applications I want to run on the BBB to have space. Nov 05 23:19:16 GenTooMan: so start with a console image, removing any unnecessary crap that may still be on it, and then install what you want Nov 05 23:23:22 zmatt: right, I'll have to read the process to do that. I started with elinux pages, some of those are a bit dated, but I'll see how far I can get. The pocket beagle isn't bad it might have been nice to have 2 SD card slots on it instead of one. Nov 05 23:24:26 you can grab the latest stretch debian image from https://elinux.org/Beagleboard:BeagleBoneBlack_Debian Nov 05 23:36:32 (console image is the last one listed) Nov 06 00:08:39 .. Nov 06 00:10:31 Hello @all ! :) I use BBBlue with Debian 9.2 2017-10-10 via Putty. If I want to change Password with sudo passwd. It changes it "sucessfully", but after restart or just exiting putty default passwd is active again. Does anyone know how to solve this? Nov 06 00:36:35 Hey Beagle friends! I wonder if someone could help me with a question regarding PocketBeagle? Nov 06 00:40:00 Guest72321: you've changed the password of the root account, not the debian account Nov 06 00:40:13 use it without sudo to change the password of the debian account Nov 06 00:40:43 or use sudo passwd debian Nov 06 00:41:03 or that, but that's a bit pointless use of sudo Nov 06 00:41:23 not gonna disagree with that, but it's there. Nov 06 00:49:57 Hello... Nov 06 00:50:05 o/ Nov 06 00:51:12 I am dealing w/ a Motor Bridge Cape. I want to try to revert/downgrade back to kernel 4.1.x. I know this sounds silly since we have all moved on but the Motor Bridge Cape is giving me issues. I have tried every kernel past 4.1.x and I cannot get this Cape to work anymore. Nov 06 00:51:14 ... Nov 06 00:51:29 I am dealin' w/ a person online. I am actually trying to help this person w/ the Cape. Nov 06 00:52:15 ...I wanted to try and revert back to this kernel in hopes that I could salvage what the people were thinking when they made this Cape during the 2015 era. Nov 06 00:52:31 Can you help me? Nov 06 00:53:18 ... Nov 06 00:54:16 I am asking b/c the Cape was made in 2015 and I see some of our /latest-images part to the BBB.io site (the .img files) are not booting once put on the BBB. Nov 06 00:55:34 I tried three or four images, e.g. thinking I could get the older kernels. Nov 06 00:55:44 Does anyone know an easy (and specifically, wearable) way to add bluetooth or wifi connectivity to a PocketBeagle? Nov 06 00:56:06 , your're absolutely great! :) Nov 06 00:56:22 !!!! Nov 06 00:56:42 zadam, doesn't the pocketbeagle already have both of those? Nov 06 00:58:08 I could be wrong Nov 06 00:58:35 @Kitlith Doesn't seem to. It's not in the list of key features... https://beagleboard.org/pocket Nov 06 00:58:51 yeah, I took a look at that after I said that. Nov 06 00:59:50 there's stuff like this: https://shop.mikroe.com/click?type*=wi-fi,ble Nov 06 01:00:38 there's also https://github.com/beagleboard/pocketbeagle/wiki/FAQ#how-do-i-get-additional-usb-connections if you have a usb adapter you want to use. Nov 06 01:02:15 Ah, both of these look like good solutions. Thanks! Nov 06 01:04:31 So the BBConsole won't work with the Pocket, only the BeagleBone Black? Nov 06 01:04:33 http://beagleboard.org/project/BBConsole/ Nov 06 01:39:38 I cannot disable the softap nor change the password of my BBlue using:: Nov 06 01:39:45 connmanctl enable wifi Nov 06 01:39:52 connmanctl tether wifi on Nov 06 01:40:13 or:: connmanctl disable wifi Nov 06 01:40:30 :( Nov 06 01:50:33 conman states that I changed the default password and ssid? but in real I can connect to BBBlue with default SSID and default password Nov 06 01:50:38 /net/connman/technology/wifi Name = WiFi Type = wifi Powered = False Connected = False Tethering = False TetheringIdentifier = Dawain TetheringPassphrase = losimosi Nov 06 01:51:10 TetheringIdentifier == SSID ? **** ENDING LOGGING AT Mon Nov 06 03:00:01 2017