**** BEGIN LOGGING AT Fri Mar 18 02:59:58 2016 Mar 18 04:35:45 SPI1 and SPI0 pins of Beaglebone black conflicting with the 4D 7.0" LCD CAPE pins, Any solutions for this?. I dont see any .dts file to modify **** BEGIN LOGGING AT Fri Mar 18 04:52:37 2016 Mar 18 05:57:40 hey can anyone help me out for hcr04 ultrasonic sensor to be interfaced with BBB. i am newbie. please any one suggest me Mar 18 06:02:11 nipun: you should look at its datasheet Mar 18 06:03:06 and then you could ask your favourite search engine about "beaglebone black ultrasonic sensor" Mar 18 06:05:33 had a look.. analyzed it. but by looking at it looks simple as jz to initiate a trigger signal. wait for the echo and then calculate the time lapsed. but i didnt get any help of how to do it al. Mar 18 06:06:02 you surely must have found this one? https://github.com/luigif/hcsr04 Mar 18 06:06:14 it essentially gives *exact steps* Mar 18 06:06:54 yeah i tried for this, but i am getting incorrect answers... wrong distance measurements... Mar 18 06:08:20 well you might need to compare the datasheets for both sensors if they behave the same or if you need to adjust the code Mar 18 06:15:06 they are exactly identical Mar 18 06:19:15 then you should investigate your setup further for possible causes of error Mar 18 06:20:45 i have provided seperate 5v supply to the sensor. rest is same as shown on https://github.com/luigif/hcsr04 Mar 18 06:22:28 make sure you have ground connected from the BBB to the sensor Mar 18 06:24:59 yeah thanx.. i havent tried it... will try it nd rply u!! Mar 18 09:53:16 goodmorning, I'm looking for the machinekit people, can someone, better versed in in the beaglebone ecosystem point me to their irc channel? I was unable to locatie it myself Mar 18 10:30:29 hey everyone, i am working on image processing on BBB under linux. i am having confusion in selecting camera for capturing images. i am thinking to use 'OV9655' but i am not sure about it. will this work properly with my bbb or should i use some another one? any idea? Mar 18 10:48:05 This controller is creative. It's 256 time units in an hour. Mar 18 10:48:13 OF COURSE THAT MAKES PERFECT SENSE. Mar 18 11:05:47 receiving garbage characters from J1 Header Mar 18 11:44:00 hey everyone, i am working on image processing on BBB under linux. i am having confusion in selecting camera for capturing images. i am thinking to use 'OV9655' but i am not sure about it. will this work properly with my bbb or should i use some another one? any idea? Mar 18 12:39:42 ok, so no machintkit volks around atm, does anyone have a good idea on which capes are still in stock somewhere that could drive 3+ steppermotor drivers? Mar 18 13:33:11 failbaitr: Replicapes are in stock ATM. Mar 18 13:37:11 Nevyn|Work: thanks, ill see if it fits our requirements Mar 18 13:37:43 http://www.thing-printer.com/product/replicape/ Mar 18 13:39:59 thnx, looking of the specs now, are they available without the onboard drivers? (we just need the step/dir) for each motor Mar 18 13:42:13 Not that I'm aware of, no. But here's a list with links of capes: http://blog.machinekit.io/p/hardware-capes.html Mar 18 13:42:57 Yup, I saw that, but sadly the once's that caught my eye are not available or only prototypes. Mar 18 13:43:15 Which ones? Mar 18 13:44:29 failbaitr: http://pico-systems.com/osc2.5/catalog/product_info.php?cPath=5&products_id=35 Mar 18 13:46:58 yup, that one's the only real competitor atm Mar 18 14:23:52 * zmatt yawns Mar 18 14:23:54 mornin Mar 18 14:31:00 amazeballs, I got a reply on Mar 18 14:31:06 my e2e post already Mar 18 14:31:37 "Feedback from the factory team: The break signal associated with iloop was originally added for a very special (non-PRU) use case. The break signal was never used by the PRU." Mar 18 14:40:45 zmatt: Good response too. Maybe not the most pleasant answer, but hey. Mar 18 14:43:14 indeed, it's unfortunate they didn't connect it, but at least I have a definitive answer Mar 18 14:44:24 I am now curious about the use-case though, since I've also not found any ILOOP in the firmware of the keystone PDSPs Mar 18 14:49:20 Mmmmm, funky Mar 18 15:12:33 hi Mar 18 15:14:28 i'm wondering if all beaglebone black are running on Angstrom Mar 18 15:15:28 no, nowadays the default image is debian based Mar 18 15:16:06 ok, so when we buy it the default image is now Debian Mar 18 15:16:13 yes Mar 18 15:16:18 thanks Mar 18 15:45:08 Hey guys! do you think I can access to a BeagleBone Black server using MeteorJS ? Mar 18 15:46:13 I can access to my BBB using ssh from my Terminal... But I aim to turn a LED ON and OFF using MeteorJS, so do you think this combination can work? Mar 18 16:22:01 Is this channel always sleepy? Mar 18 16:22:11 WAKE UP FOLKS! Mar 18 16:25:03 houssam: https://github.com/belisarius222/meteor-beaglebone-black Mar 18 16:25:12 now stop yelling please Mar 18 16:25:28 LOL Thanks @wmat :) Mar 18 16:25:33 who is the fool, who disturbes my slumber? Mar 18 16:25:34 But I am here just to talk Mar 18 16:25:50 you guys are familiar with the BB :) Mar 18 16:26:21 so I wanted to know if Meteor can collaborate with BB B : Mar 18 16:26:21 yes, i did hold one in my hand... a couple of years ago Mar 18 16:27:22 You killed it @KotH hahahaha Mar 18 16:28:04 KotH: http://static.tvtropes.org/pmwiki/pub/images/bullying_a_dragon_862.jpg Mar 18 16:28:05 ;) Mar 18 16:28:08 he coated it with cocolate Mar 18 16:28:22 zmatt: :-) Mar 18 16:28:53 apropos chocolate.. i havent eaten any today Mar 18 16:29:00 geez ! Mar 18 16:29:04 i need to correct this imediately! Mar 18 16:30:22 I'd like to try an older kernel on the BBB to check if that affects an issue I'm having. Mar 18 16:30:40 I can cross-compile one, but I'd really just like to test an older kernel first. Mar 18 16:30:52 Is there a repo of older kernels I could try? Mar 18 16:31:03 rcn-ee's debian repositories definitely still has 3.8 kernels Mar 18 16:31:11 or do you mean *really* old? :P Mar 18 16:31:22 Like 3.2 or older. Mar 18 16:31:32 I figured rcn-ee would have something to do with it. Mar 18 16:31:33 I'm assuming you've tried apt-get search? Mar 18 16:32:01 (note: you will need a beaglebone-specific kernel if they're that old) Mar 18 16:32:21 apt-cache search? Mar 18 16:32:26 yes sorry Mar 18 16:32:28 rcn-ee's kernels/builds are really good Mar 18 16:33:05 otherwise, presumably older kernels can be found somewhere on the web Mar 18 16:33:30 ds2: you here? ;) Mar 18 16:34:12 ? Mar 18 16:34:32 I seem to recall you had experience with pre-DT kernels on the bbb? Mar 18 16:34:53 Wait, what version did dt start with? Mar 18 16:35:01 no idea Mar 18 16:35:29 round 3.0-ish IIRC Mar 18 16:35:29 yes Mar 18 16:35:38 i prefer non DT kernels Mar 18 16:35:46 and at least BBW had old non-dt 2.6 kernels Mar 18 16:36:05 3.2 I think is my well tested kernel Mar 18 16:37:57 ebay says my BBB's are for delivery on the 22nd. USPS says 'out for delivery.' Mar 18 16:38:01 Yay! Mar 18 18:56:54 Well, kernel versions aside, I am still looking for a way to turn off the 25MHz XTAL that drives the PHY. Mar 18 18:58:48 I'm able to electrically disable it but then the BBB won't boot; the kernel complains that the cpsw module fails. Attempts to blacklist that module so that the BBB will boot without the module have failed. Mar 18 18:59:21 ecdhe: I need to do shopping first, but poke me again in an hour or so and I'll see if I can help you with that Mar 18 18:59:49 do try disabling or removing the relevant DT node first Mar 18 19:00:36 at least, that should fix booting when the phy is electrically disabled Mar 18 19:01:17 it would also open up the possibility of commanding the phy into powerdown after boot Mar 18 19:02:05 (you can do that also without disabling it in the kernel, but that would get it quite confused Mar 18 19:03:07 thanks zmatt! Mar 18 19:05:22 zmatt, would you "disable of remove" the relevant DT node by removing a file in /lib/firmware? Mar 18 19:05:33 Or by blacklisting it in uEnv.txt? Mar 18 19:07:17 no, by changing the device tree source file and recompiling it into a .dtb ... maybe someone here is willing to explain in more detail Mar 18 19:07:36 zmatt, I can build those. Mar 18 19:07:48 afk Mar 18 19:07:52 (bbl) Mar 18 20:52:10 ecdhe: trying to fiddle with the mdio controller atm... Mar 18 20:52:18 okay, thanks! Mar 18 20:52:35 I found http://lxr.free-electrons.com/source/arch/arm/boot/dts/am335x-bone-common.dtsi Mar 18 20:53:19 It appears to implement the pin config for the cpsw driver, but nothing suggests to me that disabling that overlay would keep the cpsw driver from freaking out at boot. Mar 18 20:54:41 lines 378 and 371 are the magic ones Mar 18 20:58:53 you could comment out those lines, or the containing &mac and &davinci_mdio blocks, or override them in the top-level dts by appending a &mac { status = "disabled"; }; block (and similar for davinci_mdio, though maybe it's not needed) Mar 18 21:10:18 zmatt, I can compile that .dtsi to a .dtbo. Where do I place the .dtbo so that it is run? Mar 18 21:21:30 no, you need to recompile the main dts to a dtb Mar 18 21:25:28 this isn't something you can override with an overlay Mar 18 21:25:28 (afaik) Mar 18 21:25:28 note: food-insertion in progress, my response latency may vary ;) Mar 18 21:25:36 Okay. Mar 18 21:26:07 Last meal of the day? Mar 18 21:27:08 that sounds rather dramatic Mar 18 21:27:59 It's time for your *rolling tympanis stop* last! meal! of! the day! Mar 18 21:29:05 you know, looking at the phy registers, sometimes I wonder why people even bother trying to come up with register names other than "misc0, misc1, misc2, ..." :P Mar 18 22:26:54 ecdhe: http://gerbil.xs4all.nl/mdio.tgz <-- toggles phy powerdown mode Mar 18 22:27:14 thanks zmatt! Mar 18 22:27:45 oh shoot, I forgot the prcm enable, so it actually won't work if eth is disabled in the kernel Mar 18 22:28:09 however it seems to play fine with eth enabled in the kernel... it just shows link down (and on running it a second time link goes up again) Mar 18 22:29:04 Okay, so if the phy is electrically disabled, the BBB will still boot? Mar 18 22:29:30 just run this on a normal kernel with eth enabled, that will let you check if setting the phy in powerdown mode suffices to solve your problem Mar 18 22:31:07 note that the kernel apparently does *not* touch this bit by itself as you previously hypothesized **** ENDING LOGGING AT Sat Mar 19 02:59:58 2016