**** BEGIN LOGGING AT Fri Jul 27 03:00:01 2018 Jul 27 03:08:42 looks like best bet would be mcdeoliveira python3 lib, and mqtt to bridge between Jul 27 04:45:22 e Jul 27 04:50:51 * MrCurious nods at jkridner Jul 27 04:50:57 hola Jul 27 04:52:07 asked above if there was an easy way to control BB blue's motor drivers and quadrature readers from java. best i can find is do it in python and use mqtt to remote command. any thoughts? Jul 27 04:55:02 MrCurious: probably best with a JNI interface. Jul 27 04:55:36 that was my suspicion. at which point better just to message pass and use the more efficiently bound languages Jul 27 04:56:01 thanks for the answer :) Jul 27 06:41:24 hello Jul 27 08:13:35 hi Jul 27 09:38:36 i am really struggeling to get the usb and network working, journalctl tells me that for the network it faild to get interface index: no such device Jul 27 09:38:53 and libusb returns -99 Jul 27 09:39:02 so, eth0 is not even showing in 'ip link' ? Jul 27 09:39:16 for as far as i can see dmesg reports that all the drivers are loaded Jul 27 09:40:29 root Jul 27 09:40:31 oops Jul 27 09:40:49 no the interface do not show up in ip link Jul 27 09:41:21 can you pastebin the full output of dmesg? Jul 27 09:41:36 also, how sure are you the right dtb is being loaded? Jul 27 09:43:22 the dtb is compiled and i load it with uboot. the dts is copied from the older kernel source, and it compiles without a error. Jul 27 09:44:03 older? how much older? Jul 27 09:44:56 you can't blindly assume a dts from an old kernel will work correctly with a new kernel (even though officially it is the intention that this should work, it's not always true in practice) Jul 27 09:45:29 i see Jul 27 09:48:46 https://pastebin.com/QKn72ji2 Jul 27 09:48:50 is dmesg Jul 27 09:50:14 the older kernel was 3.13 and the newer is 4.9.69 Jul 27 09:50:38 i have no experience with writing device trees though Jul 27 09:50:52 so i assumed if it compiles it's fine :D Jul 27 09:51:26 it looks like the ethernet subsystem is not being recognized at all, I see zero messages related to it Jul 27 09:51:40 same for the usb subsystem Jul 27 09:52:11 so, you're using a custom dts but compiled against the new .dtsi files? Jul 27 09:52:21 yes Jul 27 09:52:29 maybe it's just missing some declarations to enable things? Jul 27 09:54:45 maybe i should compare my device tree with a new one see if i see anything obvious :) Jul 27 09:55:53 basically any subsystem or peripheral that has a status = "disabled"; property in am33xx.dtsi will need that property overridden with status = "okay"; if you want it enabled Jul 27 09:57:32 for example, these are the declarations used to enable ethernet: Jul 27 09:57:34 https://github.com/beagleboard/linux/blob/4.9/arch/arm/boot/dts/am335x-bone-common.dtsi#L418-L436 Jul 27 09:57:42 (along with the referenced pinmux nodes) Jul 27 09:58:26 usb: https://github.com/beagleboard/linux/blob/4.9/arch/arm/boot/dts/am335x-bone-common.dtsi#L232-L260 Jul 27 09:59:04 in case it's not clear, &foo references a previously-declared node that has been labeled with foo: Jul 27 10:00:26 this is what my usb node looks like https://pastebin.com/sNADYFzY it's indeed diffrent from what you posted :) Jul 27 10:01:22 well it looks like it could be somewhat similar, if the various nodes that are referenced by label in the example are linked are child-nodes of &usb with those exact names Jul 27 10:01:40 and I think some of them are, but I very much doubt control@44e10000 exists as a child of &usb Jul 27 10:02:03 oh, I stand corrected Jul 27 10:02:12 wow lol that's garbage, but okay Jul 27 10:02:50 so, if you look at https://github.com/beagleboard/linux/blob/4.9/arch/arm/boot/dts/am33xx.dtsi#L787-L802 Jul 27 10:03:01 it becomes clear that Jul 27 10:03:13 &usb { control@44e10620 { status = "okay"; }; }; Jul 27 10:03:15 is equivalent to Jul 27 10:03:25 &usb_ctrl_mod { status = "okay"; }; Jul 27 10:05:06 i see Jul 27 10:05:21 the only one that's clearly wrong in your dts is the dma controller node Jul 27 10:06:06 but I don't think that would be required, so I'm not sure why you're not seeing any evidence of usb working whatsoever Jul 27 10:06:36 regardless, referring to the nodes by label is a better idea as it is less error-prone and more stable against future changes Jul 27 10:07:37 that meens replacing 'dma-controller@07402000' with &cppi41dma right ? Jul 27 10:07:52 yeah and moving that block outside &usb { } Jul 27 10:07:57 to the top-level Jul 27 10:08:03 i was just going to ask that :) Jul 27 10:08:41 &whatever { .. }; blocks can only appear at the top-level since they reference a specific existing node in the device-tree Jul 27 10:09:09 conversely, a top-level node must either be / { .. }; or &whatever { .. }; Jul 27 10:09:26 nodename { .. }; blocks can only appear inside another node block Jul 27 10:12:32 giving it another try now :) Jul 27 10:12:59 did not work yet Jul 27 10:14:08 like I said, your usb declarations look like they should have mostly worked, so I don't know why there seems to be no evidence whatsoever of the usb subsystem in your kernel log Jul 27 10:16:04 got it working Jul 27 10:16:06 :D Jul 27 10:16:17 what change was the trick? Jul 27 10:17:09 i just copied over all those nodes Jul 27 10:17:13 from you past e Jul 27 10:17:15 lol ok Jul 27 10:17:16 link* Jul 27 10:17:48 ok next up network :D Jul 27 10:18:30 so with the usb dma controller node disabled, it breaks the whole usb subsystem *silently* ? that's... nice Jul 27 10:19:21 what do you meen by disabled Jul 27 10:19:30 status = "disabled"; Jul 27 10:19:52 oh but it wasn't disabled in the original device tree Jul 27 10:20:17 it's disabled in am33xx.dtsi Jul 27 10:20:34 that's why you need all those status = "okay"; overrides Jul 27 10:21:17 i copied from here https://github.com/beagleboard/linux/blob/4.9/arch/arm/boot/dts/am335x-bone-common.dtsi#L232-L260 and there is set to "okay" Jul 27 10:21:57 exactly Jul 27 10:22:37 in the original source it was referenced by dma-controller@07402000 and it was set to "okay" Jul 27 10:22:40 and the only difference compared to what you had is that your old declarations used the wrong node name for the dma controller Jul 27 10:22:48 ah Jul 27 10:22:49 07402000 is wrong Jul 27 10:23:00 oh yea your right :D didn't notice that Jul 27 10:23:09 so you just created a new empty node containing nothing but the status = "okay"; declaration Jul 27 10:24:55 i see what you meen, so the node is wrong, the status doesn't get overriden and it stays disabled, and that cause it to not work at al. Jul 27 10:25:20 yeah, and bizarrely not even result in an error Jul 27 10:25:35 I don't understand why all those child nodes have a status = "disabled"; to begin with Jul 27 10:25:59 putting it on the parent &usb node should be perfectly sufficient Jul 27 10:32:48 hi all can anyone help me how can i connect a sensor device to beaglebone black wireless. i am working with cc2650 stk sensortag that has got both bluetooth and wifi. Jul 27 10:33:36 zmatt: not sure but it's probably there for a reason. Jul 27 10:33:59 zmatt: your awesome :) for helping me out :D Jul 27 10:38:14 *you're Jul 27 10:38:15 ;) Jul 27 11:10:56 zmatt: oh your one of those Jul 27 11:11:00 :D Jul 27 11:26:46 :P Jul 27 11:42:23 oke ! got one network interface back one more to go :) Jul 27 12:44:51 hi Jul 27 12:45:08 i just destroyed my network with faulty devicetree for my netwerk configuration :D Jul 27 12:47:09 neat Jul 27 12:47:12 how so Jul 27 12:48:38 do not really know, but both the network phy's were cross talking, which ended up confusing my switch Jul 27 12:48:47 anyway gotta go, brb Jul 27 12:49:46 you're using both ethernet interfaces and connect them to the same switch? o.O Jul 27 12:50:36 be sure to enable dual-emac mode to prevent the two ports from being cross-connected by the integrated switch Jul 27 12:52:45 the first thing i'd do with a time machine is go back and slap whoever thought to use mentor graphic's nonpublic non-ehci compliant musb OTG controller Jul 27 12:53:15 kremlin: you can find its non-public datasheet online Jul 27 12:53:58 "i got it from my friend Victor from Ukraine" is not really cutting it these days Jul 27 12:55:47 *shrug* Jul 27 13:58:15 zmatt: both my ethernet interfaces work now! :) Jul 27 13:58:41 hurray Jul 27 14:06:40 learned so much on how embedded linux works :) Jul 27 14:41:11 Hi, I got a new BBBW and can't execute 'sudo ap-get update' https://pastebin.com/cN97QNBX Jul 27 14:42:07 It looks like you have no network Jul 27 14:42:53 What should I do now ? Jul 27 14:43:32 Guest14150: how are you connected to a network? Jul 27 14:43:50 by cable? maybe you could do ip a to see if there is a link :) Jul 27 14:44:13 Duality: "BBBW" Jul 27 14:44:21 i.e. no ethernet port Jul 27 14:44:36 ah yea Jul 27 14:44:44 it needs to connect to a wifi network Jul 27 14:45:11 How do I connect beagle to a wifi ? Jul 27 14:45:27 Yes, I have Beaglebone Black Wireless. Jul 27 14:46:16 Guest14150: connect to the beaglebone via usb or serial, then connect to your wifi network by following step 3 of this: https://dougreese.com/beaglebone-black-wireless-initial-setup-and-wifi-connect.html Jul 27 14:48:09 Ok, Thanks :) I'm trying. But isn't it that this info should be in official page ? Jul 27 14:51:45 probably yeah Jul 27 14:51:48 jkridner[m]: why isn't it? Jul 27 14:52:46 I have spent 3 hours for this ;) Jul 27 14:53:24 Would save people's time if it were on "Getting Started" page Jul 27 14:53:51 it's on the first page of google search results for "beaglebone wifi" though Jul 27 14:58:15 But I prefer to refer "official" documentation. Jul 27 14:58:31 Anyway it worked. thanks Jul 27 20:18:25 Is anyone else using a USB Wifi adapter to connect to their BBB Black? Jul 27 20:19:48 no, you're the only person in the entire world Jul 27 20:20:57 I knew it thank you zmatt :) Jul 27 20:23:05 usually an irc channel isn't the best place to do a poll to determine how many people are doing X with Y, but fortunately for you I'm omniscient Jul 27 20:24:00 (tip: if you have an actual technical question, ask that instead) Jul 27 20:24:48 Hahaha zmatt your awesome Jul 27 20:25:02 :) Jul 27 20:27:11 I'm pretty new to this board and received it with one already attached. I've been trying to find out if the Alfa AWSUS1900 is compatible Jul 27 20:27:19 zmatt: haven't sat down and written an SRM for Black Wireless yet. I can throw something on the wiki. Jul 27 20:27:49 jkridner: connecting to a wifi network is a pretty standard thing to want obviously Jul 27 20:28:17 Ch1Cav3: the obvious way to find out is by sticking it in and see if a network interface shows up Jul 27 20:28:27 can I copy-and-paste https://github.com/beagleboard/beaglebone-blue/wiki/Wifi ? Jul 27 20:28:45 jkridner: you're asking me? I don't use connman *at all* Jul 27 20:28:57 Yeah I figured as much. I was hoping to find out before ordering it. Jul 27 20:29:36 Ch1Cav3: huh, I'm confused, I thought you said you received a BBB with usb wifi adapter already attached? Jul 27 20:30:18 jkridner: I do know that people have had success with the steps here: dougreese.com/beaglebone-black-wireless-initial-setup-and-wifi-connect.html Jul 27 20:30:49 jkridner: which are basically the steps from some digikey page, except with 'tether wifi disable' added Jul 27 20:30:55 zmatt: yeah but wanted to know if i can extend the range with the Alfa adapter Jul 27 20:31:51 well I mean if this adapter worked it would Jul 27 20:33:52 Ch1Cav3: based on some quick googling it seems that stick has no mainline linux support Jul 27 20:35:00 although I'm seeing some reports of success Jul 27 20:35:14 with some out-of-tree driver Jul 27 20:37:42 it definitely doesn't look like a very safe choice Jul 27 20:38:55 zmatt: yeah on their site it says linux support but believe it said kernel 3.0 but i thought i read that the board was 2.63 Jul 27 20:39:35 the board? the bbb you mean? lol what? Jul 27 20:39:39 current images use a 4.14 kernel Jul 27 20:39:56 I've never seen or heard of anyone using a 2.6 kernel Jul 27 20:40:10 yes sorry the bbb, and oh cool. Jul 27 20:40:46 what the hell did I read then lol Jul 27 20:41:53 I have no clue Jul 27 20:43:31 * jkridner needs to figure out how to format https://github.com/beagleboard/beaglebone-black-wireless/wiki/Wifi Jul 27 21:09:02 is https://github.com/beagleboard/beaglebone-black-wireless/wiki/Wifi readable now? Jul 27 21:12:37 is there any effort to upstream the beaglebone kernel changes? Jul 27 21:14:12 that is, so that mainline runs OK? Jul 27 21:14:36 there've been a few. not aware of anything active right now. maybe a couple of patches. TI is pushing all the TI patches. I know dlech recently did a push of pru-rproc. Jul 27 21:15:00 mainline does run fine. Jul 27 21:15:24 several people test against mainline pretty often. Jul 27 21:15:41 I have a beaglebone green and the last time I tried to run mainline it wouldn't work Jul 27 21:15:42 just a few missing features. pru-rproc, eqep. Jul 27 21:15:56 I don't know pru-rproc or eqep are Jul 27 21:16:17 s/know/know what/ Jul 27 21:16:42 eqep = quadrature encoders Jul 27 21:16:59 sorry, still no better off :-) Jul 27 21:17:07 pru-rproc = PRU microcontroller interface where kernel loads the firmware. the UIO driver is mainline. Jul 27 21:17:37 you might need a working .config and help loading the right device tree. Jul 27 21:17:54 oh, you mean knowing what I mean by quadrature encoders. Jul 27 21:18:00 yeah I did all that Jul 27 21:18:04 the kernel was fine Jul 27 21:18:18 it had the right drivers and the right dtb, it just didn't work :-) Jul 27 21:18:20 eqep's count pulses with a peripheral. Jul 27 21:18:36 pastebin Jul 27 21:18:44 the ethernet interface would sometimes start on boot but mostly not Jul 27 21:18:46 full serial log. Jul 27 21:18:54 I mailed the mailing list Jul 27 21:18:59 I went through all that Jul 27 21:19:03 I'm not looking for help now Jul 27 21:19:07 I'm just saying Jul 27 21:19:12 hmmm.... there is a hack for Ethernet PHY reset, but I thought it was mainline. Jul 27 21:19:14 last time I tried mainline, it didn't work Jul 27 21:20:34 whereas the beaglebone.org kernel did work Jul 27 21:20:38 is the critical thing Jul 27 21:24:23 Ethernet the only issue? Jul 27 21:35:25 I don't recall I'm afraid Jul 27 22:41:40 nice interview on the amp hour, jkridner[m]! Jul 27 22:53:26 we're back to using the BBB in a commercial product Jul 27 22:53:37 although i guess eventually will lift the am335x off Jul 27 22:53:42 not sure if we need to stick with the 8 Jul 27 22:54:15 its been like two years in the making **** ENDING LOGGING AT Sat Jul 28 02:59:59 2018