**** BEGIN LOGGING AT Thu Sep 21 03:00:03 2017 Sep 21 03:18:53 sef_ are you using windows 10 with a new BBB? Sep 21 03:19:07 nevermind he left Sep 21 03:19:13 hey beagle hows it going Sep 21 03:19:27 it's been a while zmatt i hope you're doing well Sep 21 03:19:55 yo Sep 21 03:20:12 sure Sep 21 03:23:23 we're working on relocating offices, so it's actually been a fairly relaxed week Sep 21 04:25:25 i am new to beaglebone, kindly help. Does any one know how to reset the beglebone green and make it as a fresh beaglebone? Sep 21 06:57:41 I am currently having issues with establishing a serial connection between my BBB and PC. I have installed the FTDI drivers as well as the drivers included on the getting started page. Sep 21 07:01:15 and patience issues as well Sep 21 09:44:35 getting pms? Sep 21 09:44:58 errr that could be taken two ways Sep 21 10:09:44 I have a beagle bone running 3.8.13-bone80. I need to make a fix in the kernel (related to eMMC version on newer hardware). I downloaded the source of 3.8.13-bone80 from https://github.com/RobertCNelson/linux-dev/releases and seem to have built, modified and rebuilt resulting in a .zImage file. Any ideas how I upgrade the kernel on my existing BBB with the new kernel zImage file? Sep 21 12:46:59 Hi, do anyone have measured mains AC current by ACS712 current probe ?? Its output has a voltage related to current flowing , but in case of AC, output will be a sine wave do be sampled by AINx and calculated. Any hint ? Sep 21 15:10:52 http://bbb.io/pb Sep 21 15:10:57 $25 ^^^ Sep 21 15:12:02 There's nothing on that link Sep 21 15:12:13 that must be a lie ... there is a $0.25 coin next to it ! Sep 21 15:12:27 Oh no, script blocking Sep 21 15:13:18 What's that in real money ? ;) Sep 21 15:17:27 :-) Sep 21 15:17:50 Stanto: sorry about not providing the direct link Sep 21 15:18:00 np Sep 21 15:42:52 anyone post to reddit? Sep 21 17:45:25 do beaglebone and beagleboard use the same processor? Sep 21 17:51:35 nevermind, found the info Sep 21 18:17:07 is beagleboard (not beaglebone) a hard float processor? armhf? Sep 21 18:18:54 pretty sure it is, yes. Sep 21 18:19:54 omap3, if i recall Sep 21 18:20:26 ok, i ran a yocto dora build to get a toolchain, it built gnueabi instead of gnueabihf for some reason Sep 21 18:21:57 i can't tell: http://www.ti.com/product/am5728 Sep 21 18:23:35 i think am5728 is something else Sep 21 18:24:27 that would make sense Sep 21 18:25:11 zarzar1: you're referring to this board? http://beagleboard.org/beagleboard Sep 21 18:26:39 zarzar1: or this one? http://beagleboard.org/x15 Sep 21 18:29:08 vagrantc: i'm not sure which one is "beagleboard" in dora Sep 21 18:29:47 vagrantc: i do now its not what i thought it was, not compatible with beaglebone or imx6 Sep 21 18:31:20 yes, all the beagleboard.org boards are TI, not imx* Sep 21 18:31:23 (i think) Sep 21 18:31:26 http://beagleboard.org/boards Sep 21 18:32:49 yes i know they are not imx6, but i did not know b-board processor was not the same arch type/vfp/ect as b-bone Sep 21 18:33:44 well, there are numerous boards Sep 21 18:34:39 i think they're all armhf capable Sep 21 18:34:48 e.g. gnueabihf Sep 21 18:39:56 may be compatible with gnueabihf but yocto dora builds for gnueabi for some reason Sep 21 18:40:15 when building beagleboard Sep 21 18:40:25 * vagrantc shrugs Sep 21 18:40:29 all good, i think i have to change the bagleboard.conf Sep 21 18:40:42 the original beagleboard is quite an old board at this point Sep 21 18:40:51 you sure that's what you have? Sep 21 18:44:28 i don't have that, i have beaglebone, but i need a 4.8.1 version cross toolchain built for beaglebone, the same used in yocto 1.5 dora Sep 21 18:44:56 but yocto 1.5 dora only supported beagleboard Sep 21 18:49:41 hello Sep 21 18:58:46 except for the x15, they are all cortex-a8's Sep 21 19:09:23 I think sometimes a non-hf system is used on omap3 since it is then possible there to power down the neon unit for energy saving (and only power it up for specific applications when needed), but that's not really relevant on the beagleboard... more something for smartphones Sep 21 19:10:41 gnueabihf wasn't as mature when the original beagleboard came out Sep 21 19:10:51 so it probably just has the original configuration Sep 21 19:15:42 zarzar1: for reference, the SoC on the various boards are: original beagleboard = omap3530, beagleboard-xm = dm3730, beaglebone (all variants) = am3358, beagleboard-x15 = am5728 Sep 21 19:40:31 thanks zmatt Sep 21 19:54:35 * jkridner kicks PTI for letting X15s go out of stock again. Sep 21 19:55:05 the dm3730 is really just an omap3 (same die as omap3630), but the later two SoCs are very different Sep 21 21:23:30 hello, I have been trying to network connect my beaglebone for the past week, but it refuses to ping 8.8.8.8 (Destination Host Unreachable). I used this tutorial to set up usb network connections: https://www.digikey.com/en/maker/blogs/how-to-connect-a-beaglebone-black-to-the-internet-using-usb/cdf66181b3a5436e9ad730e4ed4cf9ee Sep 21 21:24:29 Anyone else experience this? Sep 21 21:27:05 why not connect it to your LAN using ethernet? Sep 21 21:27:56 I've tried that as well with no luck Sep 21 21:28:21 I cant even seem to login through the LAN ethernet Sep 21 21:28:24 isp Sep 21 21:31:48 well... Sep 21 21:32:06 which software image do you run on your BBB? Sep 21 21:32:25 the most current image of Debian off of the beaglebone page Sep 21 21:34:06 then I'd expect the board to acquire a network address if plugged into a local network with DHCP Sep 21 21:35:15 which can be found with ifconfig right? Sep 21 21:35:49 yes Sep 21 21:36:06 or the newer thing is "ip addr" Sep 21 21:37:29 yea, so I found the eth0 inet ip address, but when I try to sign on using putty with that ip, it hangs. I'll try again though Sep 21 21:37:53 yeah, ifconfig has been superceded by "ip" (which, contrary to its name, works for all kinds of network interfaces/protocols and not just ip) Sep 21 21:39:10 make sure it's not out of the 169.254.0.0/16 APIPA range Sep 21 21:39:39 yea mine is in that range Sep 21 21:40:13 says network is unreachable Sep 21 21:40:19 when I put that ip into putty Sep 21 21:40:58 that means it didn't get a valid address Sep 21 21:41:16 did you plug the cable into your router or into your PC? Sep 21 21:41:34 cable is plugged into wall ethernet Sep 21 21:42:50 for what it's worth, the ethernet lights on the BB are blinking so that's something Sep 21 21:47:01 also usb network used to work but I think it was when I downgraded my kernel is when it stopped, but flashing to the most recent image should fix that.....right? Sep 21 23:25:08 hi tbr are you still around? I'm sorry my work campus internet got knocked out for a solid hour Sep 21 23:31:33 Hello! I updated my BBB to Stretch and now my device tree overlay system is borked. Whenever I try to export an overlay, the system just hangs. I have to kill the connection and re-ssh back into the BBB. Is it worth the trouble to diag, or should I just flash back to Wheezy? Sep 22 01:19:31 RenHoek: wheezy is really really obsolete Sep 22 01:19:37 what does your DT overlay do? Sep 22 01:24:46 cat slots give me this: 0: ------ -1, 1: ---l-- -1, 2: ---l-- -1, 3: ---l-- -1 When I export an overlay the system hangs and I have to re-ssh in. Then cat sots gives me: 0: ------ -1, 1: ---l-- -1, 2: ---l-- -1, 3: ---l-- -1, 4: --O--- -1 Sep 22 01:26:33 I can then un-export the overlay with no problem. do get an unusual LED flashing pattern, though and the BBB gets quite hot, until it is rebooted. Sep 22 01:29:13 I meant what is it *supposed* do to, but okay.. so it doesn't immediately crash, that means you can inspect the kernel log to see what error(s) are being produced Sep 22 01:30:12 loading an overlay at runtime usually conflicts with "cape-universal", so you may need to disable that in /boot/uEnv.txt Sep 22 01:31:24 Thanks for giving me a direction to go in ... cheers! Sep 22 01:39:27 Sep 22 01:35:03 beaglebone kernel: bone_capemgr bone_capemgr: part_number 'BB-SPIDEV0-00A0', version 'N/A' Sep 22 01:39:38 Sep 22 01:35:03 beaglebone kernel: bone_capemgr bone_capemgr: slot #4: override Sep 22 01:39:47 please don't paste multi-line stuff here Sep 22 01:39:47 Sep 22 01:35:03 beaglebone kernel: bone_capemgr bone_capemgr: slot #4: auto loading handled by U-Boot Sep 22 01:39:55 use a paste service like pastebin.com Sep 22 01:41:27 Didn't think it worth the trouble for 3 lines, but I stand corrected. I'll edit uEnv.txt and report back. Sep 22 01:45:07 well those three lines actually don't seem to indicate any error, although I have no idea what it means with that third line Sep 22 01:46:04 Agreed, but the last two lines were coded red, which generally suggests an error. Sep 22 01:46:28 hm Sep 22 01:46:36 odd Sep 22 01:47:17 I mean, u-boot overlays were introduced a while ago, but I didn't think that would affect runtime loading in any way Sep 22 01:47:36 I don't know that much about it though, I don't use overlays at all myself Sep 22 01:51:01 OK, I edited uEnv.txt and rebooted. now, when I try to export an overlay, I receive the following error: sh: echo: I/O error. Looking at the logs now ... Sep 22 01:51:21 you probably mean "load an overlay" Sep 22 01:51:27 "export an overlay" makes no sense Sep 22 01:59:49 Apologies ... I'm a noob w/ embedded hardware. Just getting my feet wet. Sep 22 02:01:00 :) Sep 22 02:01:11 I didn't see anything in the log. Just realized no haste client on this laptop. Give me a moment and I'll get some log entries posted. Sep 22 02:05:00 https://hastebin.com/raw/ezepoyeqat Sep 22 02:08:06 these look like successes to me Sep 22 02:10:31 note that for sufficiently simple usage, you may want to try reenabling cape-universal and using that instead of using overlays. it lets you configure pin functionality at runtime using the 'config-pin' tool Sep 22 02:11:03 not 100% sure whether 'sufficiently simple usage' includes SPI though... I think it used to be an issue but I'm not sure if that's still true (I don't use cape-universal myself) Sep 22 02:11:55 Ah, something has happened. I have PF output now. Never seen this with Stretch: $ cat /sys/devices/platform/bone_capemgr/slots 0: PF---- -1, 1: PF---- -1, 2: PF---- -1, 3: PF---- -1 Going to try and load another one. Sep 22 02:13:16 Nope, still getting: sh: echo: I/O error Sep 22 02:13:32 yet no errors in kernel log? Sep 22 02:13:51 (check output of "dmesg") Sep 22 02:14:40 I think all kernel output should also end up in journal, but it's better (and less noisy) to just check the kernel log directly Sep 22 02:16:28 No, same log entries. It looks like this last attempt successfully used slot#6, but of course I have no joy. dmesg shows identical feedback. Sep 22 02:17:07 well, really shitty diagnostics are one of the many reasons I avoid overlays :) Sep 22 02:17:19 ;) Sep 22 02:19:07 I think I'm about ready to give up on Stretch. i'll sleep on it and see if I have any brilliant ideas. If not, I'll try a new IMG. Thanks so much for your help!!! Sep 22 02:23:00 RenHoek: if it's of any help, I personally use stretch very happily Sep 22 02:23:28 I don't think it's a desirable thing to be stuck on some obsolete (and eventually unmaintained) release indefinitely Sep 22 02:24:06 keep in mind even 'jessie' is regarded as obsolete by the debian project, and wheezy is even older than that Sep 22 02:26:53 ... which is why I upgraded to Stretch to begin with. Nothing but problems since, though. Glad to hear that your board is behaving itself. I found two other folks on the Internet reporting the same problems, but no solution as yet. perhaps it's not Stretch per se, but just a bad build? Sep 22 02:29:34 doubtful. my guess is it's probably due to using techniques that are kinda obsolete and no longer well tested. it's hard to say though, like I would *expect* that the overlays you tried to load ought to work still, but I'm not sure how often that's still tested Sep 22 02:34:08 Even the command to load the overlays has changed, but I found nothing about this in the official documentation. I need to get SPI to work, but I've also tried I2C, UART, PWM and others, all with the same result. If one, or two overlays failed, I'd say that perhaps they weren't nmaintained. But all of them suggests a problem on my end. Sep 22 02:35:25 well, most or all of them are kinda obsolete since cape-universal allows using those functionalities without loading any overlay whatsoever, and cape-universal is enabled by default nowadays Sep 22 02:36:40 Really ... I wasn't aware of that. Can you point me towards some reading material???? Sep 22 02:36:54 config-pin --help Sep 22 02:38:18 That'll get me started. Yer a gentleman and a scholar! Sep 22 02:38:30 there's hopefully also some real docs out there, but if so then I don't know where (since I don't use cape-universal myself) Sep 22 02:38:44 Understood **** ENDING LOGGING AT Fri Sep 22 03:00:00 2017