**** BEGIN LOGGING AT Mon Jan 09 03:00:00 2017 Jan 09 07:54:32 hello, who know how to configre beagebone black'u-boot Jan 09 14:47:50 Hi all, with zmatt's help, I was able to figure out that the BBGW has a few pins that are reserved for the Wilink chip. IS there a way I can disable this completely so that I can use pin P8.12? I don't see any capes loaded, and I don't know where else it would reserve those pins. Jan 09 14:54:13 clockman: it'll be in Device-Tree somewhere .. hunt amongst the dts source files in the uboot/kernel Jan 09 14:56:06 okay, but wouldn't that be listed on the bone_mgr/slots? Jan 09 14:56:11 no Jan 09 14:56:26 oh, okay Jan 09 14:57:14 its not a cape .. virtual or otherwise . its physical hardware on the baseboard :P Jan 09 14:59:47 and if you reuse it you also need to ensure the ws2812 isn't going to have a problem with what you're doing Jan 09 15:00:07 although iirc it was one of the mmc2 data pins right? so then that's relatively straightforward Jan 09 15:02:44 Well balls. If I'm going to have to recompile the kernel, then this is way more trouble than it's worth. Jan 09 15:02:55 recompiling the kernel is trivial, but not needed for this Jan 09 15:03:09 actually, it was for ws2812 chain right, so you're using the cpu as output? Jan 09 15:03:38 then just unbinding the driver might actually suffice Jan 09 15:03:39 Sorry. Can you rephrase. I don't know what you mean. Jan 09 15:03:46 what did you need the pin for? Jan 09 15:03:53 digital output Jan 09 15:04:06 is it okay it if toggles a bit during boot? Jan 09 15:04:18 should be fine. Jan 09 15:04:30 I just need to modprobe -r the right module? Jan 09 15:04:37 or blacklist the module? Jan 09 15:05:16 clockman: nothing is trivial in embedded electronics :P Jan 09 15:05:29 you'll need to unbind the mmc driver from mmc2 in sysfs Jan 09 15:05:30 but .. once you got the principles down, anything is possible :P Jan 09 15:05:48 cd /sys/bus/platform/drivers/omap_hsmmc/ Jan 09 15:06:18 you should see three write-only attributes (bind, unbind, uevent) and three symlinks Jan 09 15:07:11 47810000.mmc is your enemy Jan 09 15:07:18 ooo, then i just echo the that to the unbind? Jan 09 15:07:23 yep Jan 09 15:07:27 and then hope for the best Jan 09 15:08:08 hopefully the higher layers won't be too shocked that the mmc host interface just went up in smoke Jan 09 15:08:55 if it didn't panic, then hopefully this should release the pins... you can check that with show-pins Jan 09 15:09:40 the level of introspection linux provides on these targets is quite amazing Jan 09 15:09:57 that's really not specific to these targets afaik Jan 09 15:10:25 well okay on pcs some stuff might be behind opaque walls of ACPI stuff I guess Jan 09 15:10:41 although there's a ton of into there too if you dig Jan 09 15:12:03 well that seemed to turn off the pin. I think we're getting somewhere Jan 09 15:14:36 clockman: note that once you're used to it, changing the DT is basically just changing some config file (and when needed, recompiling the kernel is maybe 10 minutes of work) Jan 09 15:15:22 oh, compiling the kernel isn't the problem for me. I just always have trouble finding the .config that was used for the specific kernel that I'm using. Jan 09 15:15:59 I always use rcn's build scripts Jan 09 15:16:37 though recompiling the kernel is of course not needed to merely update the DT Jan 09 15:48:05 awesome. all the pins I need are working. Now to do some testing to make sure there isn't any inherent problems. Thanks for your help, guys. Jan 09 16:02:08 yw enjoy ! :D Jan 09 20:02:33 Hello? Jan 09 20:04:39 Im working with a BBBWL and I cant seem to connect to it wirelessly, I installed the most recent debian image on a micro sd and put it in the device but nothing seems to make it work Jan 09 20:04:47 I am working on a windows 10 Jan 09 20:11:51 George__: I've only dealt with BBGW - but mine creates a SoftAP that I can connect to. Does yours do that? Jan 09 20:12:30 I'm not sure Jan 09 20:12:49 I'm not familiar with soft app Jan 09 20:12:59 well how are you telling it to connect to your WiFi? Jan 09 20:13:32 Im trying to connect my computer to the BBB wirelessly Jan 09 20:13:57 in available neworks in my computer I can see the option BeagleBone Jan 09 20:14:04 I plug in the right PIN Jan 09 20:14:57 But I get the error windows cant get network settings from router Jan 09 20:17:39 I had this problem too, don't know exactly what the cause was, but once I logged in through the debug port, I could program it. Do you have external antennas plugged in? Jan 09 20:25:20 It has its own antennas plugged in already Jan 09 20:26:51 I'm thinking its a windows problem, it just doesn't want to connect to the board Jan 09 20:28:33 it connects via usb just fine Jan 09 20:41:23 Failed loading drivers for BeagleBone V2 on Windows 10 running as Admin. Is there a trick to getting the drivers to load? Jan 09 21:22:30 I just got a BBGW by seedstudio and I'm stuck on step 1, connecting to the wifi AP. I see the AP in my network list, but when I try to connect, it tells me I cannot connect. I am powering the BBGW from USB on my macbook pro. Does anyone know how to solve this? Jan 09 21:33:55 I've had that problem too. I think you need to power it with external power on pins 1or2 (GND) and 5or6 (5V) on header P9. Jan 09 21:34:11 I think the wifi needs more power Jan 09 21:42:03 thank you, I will try it now Jan 09 21:54:13 YES it worked! I have a macbook air that says it puts out 5v, 500ma, so I assumed it would work. I also tried in a mac mini without success. The BBGW didn't ship with the AC power adapter, so I plugged the USB into an AC charging block and I was able to connect right away to the AP. Thanks again. Jan 09 22:54:35 anyone knows if suspend to ram is working in current mainline kernel for beagleboard? Jan 09 22:56:24 sorry, I would mean for beaglebone black Jan 10 01:28:09 Ahem anyone use the Enlightenment window manager? Jan 10 02:41:55 eballetbo: try it as see? I don't know if it is capable of bringing up the wakeup-m3 yet (although you can check boot log for that) Jan 10 02:43:29 the driver seems there... https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/remoteproc/wkup_m3_rproc.c Jan 10 02:43:39 so that's encouraging Jan 10 02:46:06 oh Jan 10 02:47:09 there's no arch/arm/mach-omap2/sleep33xx.S in current mainline, so unless that code has moved elsewhere (seems unlikely), suspend is not supported Jan 10 02:49:26 eballetbo: of course there's an easy way to find out: try it and see. Jan 10 02:50:16 clockman: "1or2 (GND) and 5or6 (5V)" is incorrect Jan 10 02:50:26 it's "1and2 (GND) and 5and6 (5v)" Jan 10 02:51:13 due to max current rating of the connector pins **** ENDING LOGGING AT Tue Jan 10 03:00:01 2017