**** BEGIN LOGGING AT Thu Aug 02 03:00:01 2018 Aug 02 05:19:54 I can't get my beaglebone black to boot from the SDcard while holding down S2 during power. What steps to trouble shoot this? Aug 02 05:20:23 there's no led activity at all? (besides the power led) Aug 02 05:20:48 also, it does boot from sd card when *not* using the S2 button? Aug 02 05:24:29 tchristle_: hello? Aug 02 05:27:34 I'm here Aug 02 05:28:22 I am trying to follow the steps at http://beagleboard.org/getting-started Aug 02 05:28:59 that doesn't answer either of my two questions Aug 02 05:29:21 I get stuck at 'Step #0.F' Aug 02 05:29:55 after solding s2 i only get power LED Aug 02 05:30:25 without holding s2 and SDcard inserted, it boot from emmC Aug 02 05:31:06 then the card is simply not bootable at all (neither a bootloader nor a valid OS is present), so you probably did something wrong with flashing the sd card Aug 02 05:31:51 I suspect that etcher isn't writing a bootable card Aug 02 05:32:14 what's the name of the image you used? Aug 02 05:32:30 do I need to setup a volume/partition before using ethcer? Aug 02 05:32:35 (the image file you wrote to sd card) Aug 02 05:32:36 no Aug 02 05:33:16 bone-debian-9.4-lxqt-armhf-2018-06-17-4gb.img.xz Aug 02 05:34:00 hmm, should be fine (although I'd recommend the iot image instead of the lxqt image) Aug 02 05:34:30 odd Aug 02 05:35:27 really odd, especially since etcher validates the image after writing it Aug 02 05:35:28 i'll give IOT a try Aug 02 05:37:10 when I boot from eMMc I get this version 'Linux beaglebone 4.14.49-ti-r54' Aug 02 05:38:09 the recommendation of the iot image is separate from your issue though, it's mostly because the desktop environment on the lxqt image is unnecessary bloat for most users, slows down boot, and leaves very little space on a 4gb card (or eMMC) Aug 02 05:38:29 okay that sounds like you have a pretty recent image on eMMC Aug 02 05:38:44 you can find the image date by doing: cat /etc/dogtag Aug 02 05:40:01 i get command not found when I try cat Aug 02 05:40:31 ehh, are you sure you didn't mistype anything? since that's 100% certain a command that exists Aug 02 05:41:00 you're logged in via ssh? Aug 02 05:41:34 no. usb comport Aug 02 05:41:41 yeah that works too Aug 02 05:44:11 also, maybe try this: after booting from eMMC, insert sd card and then type the command: ls /dev/mmcblk0* Aug 02 05:44:38 got it. BeagleBoard.org Debian Image 2015-11-15 Aug 02 05:44:45 what Aug 02 05:44:51 a 2015 image with a 4.14 kernel? Aug 02 05:45:26 I ordered this as BBB OEM from Arrow Aug 02 05:45:38 this makes absolutely no sense to me Aug 02 05:46:11 beagleboard.org images didn't start shipping with a 4.14 until quite recently Aug 02 05:46:54 or have you upgraded the kernel yourself? I got the impression you were just getting started for the first time, but maybe I misunderstood Aug 02 05:47:19 regardless, a 2015 image is certainly a good reason to reflash it Aug 02 05:47:23 This is my first time touching it. Aug 02 05:47:29 okay that's really bizarre Aug 02 05:48:11 jkridner[m]: ping. a BBB shipped with a 2015 image containing a 4.14-ti kernel? wth? Aug 02 05:48:53 There is a ID.txt in the mass storage that says the same thing Aug 02 05:49:47 tchristle_: anyway, have you tried what I said a few minutes ago? Aug 02 05:50:23 re-fashing it? Aug 02 05:50:35 07:44 < zmatt> also, maybe try this: after booting from eMMC, insert sd card and then type the command: ls /dev/mmcblk0* Aug 02 05:51:50 I am still waiting for IOT image write to SDcard Aug 02 05:51:58 ok Aug 02 05:53:33 it done Aug 02 05:54:05 what am i looking for after 'ls /dev/mmcblk0*' Aug 02 05:54:51 '/dev/mmcblk0 /dev/mmcblk0boot1 /dev/mmcblk0p2 /dev/mmcblk0boot0 /dev/mmcblk0p1' Aug 02 05:55:14 huh o.O wth Aug 02 05:55:29 why is the eMMC mmcblk0 ... on a 4.14 kernel? wtf is going on here Aug 02 05:55:38 okay then ls /dev/mmcblk1* Aug 02 05:56:15 '/dev/mmcblk1 /dev/mmcblk1p1' Aug 02 05:56:30 okay that looks okay Aug 02 05:56:38 well, try booting from it I guess? Aug 02 05:57:10 just unplug USB power. hold down S2 and plug it back in? Aug 02 05:57:26 yes Aug 02 05:58:40 I'm only getting solid power button Aug 02 05:59:34 okay, my current theory is that there are ghosts in your BBB. it needs an exorcism Aug 02 06:00:24 ohhhhhhhh wait a second, I probably understand why it saw a 4.14 kernel Aug 02 06:00:38 if you boot from eMMC without any sd card inserted, what does it say then? Aug 02 06:02:36 since on really ancient systems I know that it was possible to have a situation where the kernel would get loaded from a different location as the one used as root filesystem Aug 02 06:03:10 BeagleBoard.org Debian Image 2015-11-15 Aug 02 06:03:16 yeah but which kernel? Aug 02 06:03:54 Linux beaglebone 4.1.13-ti-r30 #1 SMP PREEMPT Fri Nov 13 21:54:17 UTC 2015 armv7l GNU/Linux Aug 02 06:04:06 okay now things make more sense again Aug 02 06:04:10 jkridner[m]: false alarm ;) Aug 02 06:04:31 tchristle_: so back to the big question of why it doesn't boot properly from it Aug 02 06:05:47 since we've established that the card is being detected and it looks correctly partitioned, which means the image must have been correctly written to card Aug 02 06:06:44 ehm Aug 02 06:10:07 I'm still leaning towards the ghost-theory on that ;) I'm also slightly distracted atm Aug 02 06:10:29 brb Aug 02 06:11:50 I might have to put it down and try again tommorrow. If there are any links you can post with alternative flashing instruction then I will give it a try. Aug 02 06:42:28 Hello! We are trying to buy a beaglebone board or raspberry pie to connect with different PLCs out there (for Mitsubishi, Schneider and Regen), which one would you recommend? Aug 02 06:46:18 obviously in here we recommend a beagle Aug 02 06:46:39 also depends on how you want to interface with things Aug 02 15:18:52 gosh i used to have a command so that i could forward ssh ports from my webserver to my local BBB and my friends could SSH into my local BBB Aug 02 15:19:01 it was a ssh -R or -L command, i don't remember it requiring much setup Aug 02 15:19:47 iirc -R is for opening a listener on the server you ssh to and forward connections to a destination on the client side while -L is the opposite Aug 02 15:20:06 in both cases the argument is listenport:desthost:destport Aug 02 15:22:45 oh actually you'll need the full form bindaddress:listenport:desthost:destport with bindaddress left empty or '*', otherwise it'll bind to loopback address Aug 02 15:23:14 i feel like we're so close but i'm trying to figure out Aug 02 15:23:37 if i want all incoming connections to my webserver on 8080 to forward to my BBB, what do i run on my bbb, that's what i'm trying to figure out Aug 02 15:23:50 ssh -R :8080:127.0.0.1:22 webserver Aug 02 15:24:39 i wonder if i need to change settings in sshd? Aug 02 15:25:10 GatewayPorts clientspecified Aug 02 15:25:13 AH Aug 02 15:25:23 you know what i have to do, i ssh into webserver, and then connect to 8080 locally Aug 02 15:25:45 yes that works too Aug 02 15:26:46 by default (GatewayPorts no) it'll only be able to bind to the loopback address, hence you can then only connect to the port locally on the webserver Aug 02 15:31:58 thanks zmatt Aug 02 18:17:29 is pin-config (i might have named it wrong) in the repos? Aug 02 18:17:43 config-pin Aug 02 18:17:48 it is undoubtedly in a repo Aug 02 18:18:23 hmm yah i'm apt-getting config-pin but it's not coming Aug 02 18:18:29 i'll search Aug 02 18:18:53 oh you meant whether it has a debian package... it very well might but no idea Aug 02 18:19:12 yeah its def a github repo lemme look Aug 02 18:25:46 I don't think it has a debian package Aug 02 18:25:55 at least I don't see a plausible candidate Aug 02 18:32:43 How do you enable mimo for the bbb wireless? Aug 02 18:36:08 I've come across editing the wl18xx.conf file but I'm not sure it's working. Aug 02 18:38:02 akben: it should be enabled already Aug 02 18:38:21 although it might not work well because the antennae are too close together Aug 02 18:39:48 Do you know of any documentation on the macro's used for wl18xx ht_mode. Aug 02 18:41:15 MIMO: use wl18xx.ht.mode=0 SISO40: use wl18xx.ht.mode=1 (default) SISO20: use wl18xx.ht.mode=2 Aug 02 18:41:17 I'm not even sure what you're referring to... it's been a while since I looked at wl18xx stuff Aug 02 18:41:45 I think by default it's set to SISO40 Aug 02 18:42:11 I'm pretty sure they've overridden that Aug 02 18:42:25 Oh have they? Aug 02 18:42:48 check /etc/modprobe.d/wl18xx.conf Aug 02 18:43:13 That's currently what i'm referencing. Sorry I should have been more explicit Aug 02 18:43:28 It currently has "options sl18xx ht_mode=default" Aug 02 18:43:57 this post indicates that was done to enable MIMO: https://www.mail-archive.com/beagleboard@googlegroups.com/msg40479.html Aug 02 18:43:58 That's what I meant by macro's used. What default is a macro for. Aug 02 18:44:18 oh okay, that's very confusing since nobody would call that a "macro" Aug 02 18:44:25 so I had no idea what you were talking about Aug 02 18:45:19 it seems strange to me they're doing this in the first place, the correct way to enable MIMO is by using the right config Aug 02 18:46:14 What do you mean right config? Aug 02 18:46:41 /lib/firmware/ti-connectivity/wl18xx-conf.bin Aug 02 18:47:14 that's where the ht_mode normally comes from Aug 02 18:47:43 That's where I got the options for the modes that I posted earlier Aug 02 18:49:31 hence the reason I was asking about macro "define." Where macro I mean #define or some way of indicating to the preprocessor that it represents some defined number. Aug 02 18:49:50 I've lost you again Aug 02 18:52:58 So an example being in C you can do #define and assign it a value. lets say...#define default 1. So now you can use the word default and it will really mean 1. So at compile time it's invoked initially replace all defaults with 1. Aug 02 18:53:18 I know what a macro is, I don't understand why you're talking about macros Aug 02 18:53:44 so far nothing involving macro-processing has been introduced anywhere in the conversation Aug 02 18:54:00 options wl18xx ht_mode=default Aug 02 18:54:06 what does default mean Aug 02 18:54:55 no idea what it does, I'd need to check the driver Aug 02 18:56:09 https://github.com/beagleboard/linux/blob/4.14/drivers/net/wireless/ti/wl18xx/main.c#L1998-L2009 Aug 02 18:57:26 https://github.com/beagleboard/linux/blob/4.14/drivers/net/wireless/ti/wl18xx/conf.h#L97-L106 Aug 02 18:57:56 so options wl18xx ht_mode=default overrides the ht mode to be 0 Aug 02 18:58:19 thus making sure MIMO is enabled even if ht mode is configured incorrectly in the wl18xx.conf Aug 02 19:55:40 Sorry I got called to a meeting. I appreciate you looking into that Aug 02 19:57:28 Oh okay so yeah it's implemented to be default mimo Aug 02 19:59:33 if you suddenly have to leave while in the middle of a conversation it would be polite to say so before leaving (even if it's something as brief as "bbl") Aug 02 20:02:11 I apologize, I wasn't expecting it to happen. Aug 02 20:03:17 I understand, and it's not a big deal Aug 02 20:03:31 I really do appreciate your help. Aug 02 20:03:57 and the last link you supplied has fully answered my question. Aug 02 20:22:59 akben: in case it's of any use, this is what I have in /lib/firmware/ti-connectivity => https://liktaanjeneus.nl/wilink8/ti-connectivity.tar.xz the various configuration files were generated by me using TI's wlconf and ini files, except for the "bb" config which is just the config in rcn's debian package Aug 02 20:23:39 akben: I haven't really analyzed the differences between the bb config and the configs I produced using TI's tools Aug 02 20:24:51 the .conf files are plaintext versions of the .bin files Aug 02 20:25:39 Oh okay I didn't know that. Aug 02 20:26:06 I was investigating wlconf when I first contacted you. Aug 02 20:29:58 So I found the ti's firmware but I was in the process of figuring out how to get wlconf. Aug 02 20:31:26 git://git.ti.com/wilink8-wlan/18xx-ti-utils Aug 02 20:31:35 subdirectory wlconf Aug 02 20:42:14 Did you use WL18xx scripts to install wlconfg? Aug 02 20:44:17 I didn't install wlconf, I just compiled it and then used this bash script to generate the various configs: https://pastebin.com/raw/XRqSMziC Aug 02 22:27:07 Hello...I have been trying to configure spi with Beaglebone black as a slave device , I am unable to do so. Any ideas Aug 02 22:27:27 ? Aug 02 22:45:58 (good luck with that) Aug 02 23:11:29 zmatt: Alright I've been reading up on wlconf and calibrator. This should help me diagnose the data rate issue. Thank you for your help. I shall return! Aug 02 23:13:33 akben: good luck! **** ENDING LOGGING AT Fri Aug 03 03:00:00 2018