**** BEGIN LOGGING AT Tue Apr 04 03:00:02 2017 Apr 04 10:30:06 hi all Apr 04 10:30:22 just a quick question regarding the beaglebone blue Apr 04 10:31:21 does anyone know if the 8 pwm channels on the BBBlue are only configured to run as Servo PWM signals Apr 04 10:32:13 vs full pwm Apr 04 10:33:38 see https://gist.github.com/ajfisher/8c5146bff264b88d04cc Apr 04 11:16:00 I am trying to enable uart1 on bbb with Jessi IOT image but its not working:( Apr 04 13:10:24 should i be concerned that writes which occur during typical operation of a debian-like linux system running off a microSD will wear out the microSD? Apr 04 13:10:58 any pointers corroborating either a "yes" or "no" would be appreciated Apr 04 13:11:24 assume we're using ext4 Apr 04 13:14:20 i've already googled and couldn't find anything which clearly states one way or the other Apr 04 13:15:04 zmatt: how are you, man? Apr 04 13:26:18 Guest1130: what are you doing exactly? Apr 04 13:33:40 whoami Apr 04 13:34:25 johanhenselmans: there is no Guest1130 on this channel now. Apr 04 13:35:19 Sorry, Noticed a request for help from a Guest1130 a few hours ago with no response, just tried to help. Apr 04 14:15:40 hello Apr 04 14:17:25 is it possible through some act of nature that my bbb becomes unresponsive only when I access it through external ip? Apr 04 14:18:00 the second i ping it via its internal ip it "wakes up" and becomes responsive when accessed via the external ip Apr 04 14:19:42 yates: trying to figure out why I can't seem to make a systemd service wait for the devices it needs to be available Apr 04 14:20:22 it stays responsive for like an hour or so and then goes away again Apr 04 14:20:30 I know how it's supposed to work, if I google I find those steps being given with a "thanks, it works" reply from whoever asked, yet I've seen the service run before the device was available... too many times Apr 04 14:21:01 painy: o.O what on earth are you describing? Apr 04 14:21:48 I mean we have many beaglebones that are on 24/7 and we almost always access them via ethernet Apr 04 14:21:53 I just flashed the new debian image for iot Apr 04 14:21:59 i have installed nginx Apr 04 14:22:07 what do you eman with it "wakes up" when you ping it? Apr 04 14:22:11 *mean Apr 04 14:22:21 I mean I can access it from the external ip again. Apr 04 14:23:13 it's probably a debian issue because I have ran arch on this too and it worked fine Apr 04 14:23:38 it's not a "debian issue" since I've never heard of anything like what you're describing Apr 04 14:23:59 ok Apr 04 14:24:02 it sounds like some really weird stuff going on perhaps due to misconfig, or maybe connman does funny things Apr 04 14:24:30 and what you do you mean by internal/external ip ? Apr 04 14:24:32 does it have some sort of sleep functionality? Apr 04 14:24:55 internal ip: 192.168.100.5, external ip you can probably find out from a whois Apr 04 14:25:19 ehm, you mean via NAT ? Apr 04 14:25:46 "internal" and "external" requests don't look any different to the beaglebone Apr 04 14:25:54 your modem/router is the issue Apr 04 14:26:13 intredasting Apr 04 14:26:18 maybe it and the beaglebone disagree about when the DHCP lease has expired Apr 04 14:26:20 ok i'll look into it Apr 04 14:26:59 or the modem concludes for some other reason that the BBB isn't on / reachable Apr 04 16:25:33 Hi, I want to know the latest BeagleBone Black will come with inbuilt Wi-Fi module or not? Apr 04 16:26:35 nope. Apr 04 16:26:45 BBB has never had wifi nor will. Apr 04 16:26:57 ok Apr 04 16:27:16 But can we externally attach to it? Apr 04 16:27:45 the Beaglebone Wireless does .. but thats not a 'black' per-se :) Apr 04 16:27:58 you can attach a WiFi dongle to anything wtih a USB port .. so . everything :D Apr 04 16:29:13 I want to attch WiLink module to BBB. So, it is not possible. Am i correct? Apr 04 16:33:05 Does BBB or any other BeagleBone will support to AirPlay? Apr 04 16:34:16 oh my bad .. its branded the "beaglebone black wireless" :( =facepalm= my apologies ... Apr 04 16:34:24 https://beagleboard.org/blog/2016-09-26-meet-beaglebone-black-wireless/ Apr 04 16:34:29 it has the wilink on board Apr 04 16:35:42 unlikely to get IOS apps under linux .. so airplay .. probably not. Apr 04 16:41:42 Exactly i want to Stream Audio from iPhone to BBB via Wifi(Airplay support) Apr 04 16:42:41 Can you suggest me any other BeagleBone which does this use case. Apr 04 16:43:53 not really .. get another iphone .. Apr 04 16:44:12 I think there is limited support with apps like Kodi Apr 04 16:44:58 ok Thanks Apr 04 16:50:57 but i found one link which does audio streaming using airplay on beagle bone and WiLink . Apr 04 16:51:16 i am still confused Apr 04 16:52:27 can anyone help me? Apr 04 16:52:49 outta my league, sorry :) Apr 04 16:54:48 please check http://processors.wiki.ti.com/index.php/WL18xx_Audio_Demo_Kit_QuickStart_Guide​ Apr 04 16:56:57 hi Apr 04 17:27:31 * zmatt has done a little experiment... https://liktaanjeneus.nl/emmc-ecsd-before-after.png Apr 04 18:24:28 Hello, was working on some stuff with the Beaglebone, and have run into what appears to be a PHY detection issue. The project in question is baremetal so no linux available. Just wondering if anyone knows if this is an ongoing issue, if the discussion about this issue is still ongoing and where, and if there is the ability to detect this issue from software (e.g. from MDIO or CPSW registers). Sorry not very familiar with ethernet and Apr 04 18:32:13 should i be concerned that writes which occur during typical operation of a debian-like linux system running off a microSD will wear out the microSD? any pointers corroborating either a "yes" or "no" would be appreciated. Apr 04 18:40:42 zmatt: what am I seeing there? Apr 04 18:43:55 Trip_: the phy sometimes comes up at the wrong address, this was worked around in the kernel by scanning for the phy's actual address Apr 04 18:44:20 Trip_: note that the MDIO controller actually already scans for phys automatically Apr 04 18:44:31 yates: eventually Apr 04 18:46:25 zmatt: ah.., right. 0 information in that statement. Apr 04 18:46:37 the sun will rise tomorrow, too. Apr 04 18:46:40 yates: readonly data is only not infinitely retained (though a *good* controller would hopefully also move unmodified data blocks around every now and then to ensure they get refreshed and for wear leveling) Apr 04 18:47:31 iirc Spidler's wear-out incident involved a lot of data, but not remotely as much data as anticipated Apr 04 18:48:32 possibly there was also write-amplification going on (tip: run "fstim /" every now and then, especially whenever a lot of space has just been freed up) Apr 04 18:48:55 zmatt: yes, wear-levelling is the technique i was hinting at. i guess i'm asking if that is enabled/implemented, or can easily enabled, on a standard ext4 filesystem? Apr 04 18:49:22 (if mounted with discard, fstrim should be needed at most once) Apr 04 18:49:29 wear leveling is done by the eMMC Apr 04 18:50:00 (or sd card) Apr 04 18:52:07 thinkfat: dumps of the ecsd of the eMMC of one of our beaglebones, diff'd before and after experiment :) Apr 04 18:52:15 or, in a sense the experiment is still ongoing Apr 04 18:53:12 (the "card specific data" (csd) / "extended card specific data" (ecsd) is basically a sort of memory-mapped register space of the card.... it's a mess) Apr 04 18:56:29 yates: I'm not sure there's a good answer to your question, since it'll probably depend very much on the card, the usage patterns, how much free space there is (known to the card), etc Apr 04 18:58:25 if you get a decent eMMC nowadays you can get health information from the card, e.g. an estimate at how many % till wear-out the card is Apr 04 18:59:41 or if it's running dangerously low on spare blocks, the card can invite you to sacrifice some capacity in exchange for an extension of the lifetime of the remaining storage Apr 04 18:59:48 pretty nice stuff Apr 04 19:00:10 maybe sd has similar things, but I suspect it's less likely Apr 04 19:01:31 thinkfat: so what I did was I configured the whole card into SLC instead of MLC, and set the "write reliability bit" Apr 04 19:03:59 since of course kingston leaves the "I care about SPEED" vs "I care about getting my data back intact" setting on "speed" by default :) Apr 04 19:04:57 oh Apr 04 19:05:04 that can be done? Apr 04 19:06:04 how much capacity do you sacrifice? Apr 04 19:06:14 zmatt: i'm confused: i thought a microSD WAS a eMMC drive/ Apr 04 19:06:23 s///./ Apr 04 19:10:21 thinkfat: MLC stores 2 bits per cell, SLC stores 1 bit per cell Apr 04 19:12:13 yates: SD and MMC are two similar but incompatible interfaces/specs for "managed NAND flash", MMC physical cards have died out but it flourished in embedded form as eMMC, whereas SD took the physical cards market (they also have embedded SD but I've never seen or heard of anyone using it) Apr 04 19:12:23 microSD is just SD in a smaller form factor Apr 04 19:13:38 thinkfat: i.e. converting all of it to SLC required sacrificing 50% capacity. you can also see that near the top of the diff (Sector Count) Apr 04 19:14:06 thinkfat: you can also convert only part of it Apr 04 19:15:52 you can choose it for each of the GP hardware partitions, if you choose to use them, and for one contiguous subregion of the "user area". the boot blocks and RPMB are always SLC Apr 04 19:16:32 (in those cases where the eMMC supports "enhanced" storage at all, and where this means SLC. Apr 04 19:16:35 ) Apr 04 19:18:39 note that all of this is irreversible Apr 04 19:35:43 I and then there was silence... Apr 04 19:39:13 HA! Apr 04 19:39:29 can't a make go to the bathroom?!? Apr 04 19:39:34 s/make/man/ Apr 04 19:39:37 heh Apr 04 19:39:43 (shew - i've been running gnumake too much...) Apr 04 19:39:49 sure he can, if he has a laptop Apr 04 19:40:08 i don't do smartphones or laptops or ipad or minipads.. Apr 04 19:41:08 i could get a long extension cord... Apr 04 19:44:23 zmatt: isn't the bbb interface to the microSD eMMC? Apr 04 19:44:52 ok now I understand your confusion Apr 04 19:45:10 perpetual, it seems... Apr 04 19:45:36 "MMC" is used to refer to the (now afaik extinct) cards and the protocol to communicate with them Apr 04 19:46:06 and by extension for MMC controller instances Apr 04 19:46:27 but microSD's use the MMC interface? Apr 04 19:47:08 SD uses the same link layer (at least originally), just somewhat different commands, so an "MMC controller" is typically an "MMC/SD controller" Apr 04 19:47:32 MMC predates SD hence got priority in the naming Apr 04 19:47:49 i also didn't understand what you meant by "SD took the physical cards market". what is the "physical cards market"? what physical cards are you referring to? Apr 04 19:47:59 ok Apr 04 19:48:09 flash drives? Apr 04 19:48:11 https://www.google.com/search?q=sd+card Apr 04 19:48:53 oh, you mean (e.g.) the microSDs. Apr 04 19:49:27 and the fact that there are no longer MMC cards in the same form factor on the market Apr 04 19:49:37 mmc used to use basically the same form-factor: (compatible for the "standard size" cards at least) https://en.wikipedia.org/wiki/MultiMediaCard Apr 04 19:49:37 [WIKIPEDIA] MultiMediaCard | "The MultiMediaCard (MMC) is a memory card standard used for solid-state storage. Unveiled in 1997 by SanDisk and Siemens AG, it is based on a surface contact low pin-count serial interface using a single memory stack substrate assembly, and is therefore much smaller than earlier systems based on high..." Apr 04 19:50:22 both MMC and SD also come in BGAs to be used for internal memory, especially embedded systems, and these are called eMMC and eSD Apr 04 19:51:06 did you mean "spidler" or "spider"? Apr 04 19:51:08 funny enough physical MMC cards are gone today, but eMMC flourished. Conversely eSD is obscure but SD cards are everywhere) Apr 04 19:51:24 * zmatt points at Spidler Apr 04 19:51:27 that's not a spider Apr 04 19:53:44 it's probably confusing because it is confusing... Apr 04 19:53:49 naming is loose.. Apr 04 19:54:29 it's not that odd to name a protocol after the device that uses it Apr 04 19:57:30 gotta reboot.. Apr 04 20:21:50 is it possible to identify a beaglebone via bash? Apr 04 20:38:51 Soopaman: your question is too vague... what do you mean by "identify" exactly? Apr 04 20:41:51 want to write a bash script to differentiate between beagle bone hardware revisions Apr 04 20:42:18 ala cat /proc/cpuinfo Apr 04 20:42:22 or something along those lines Apr 04 20:42:41 you can read the eeprom Apr 04 20:44:00 this should work on sufficiently recent kernels: Apr 04 20:44:05 sudo hexdump -C /sys/bus/nvmem/devices/0-0050*/nvmem Apr 04 20:46:35 which would identify which? Apr 04 20:50:13 I think that's documented, probably in he system reference manual Apr 04 20:50:22 k Apr 04 20:50:24 A335 = this is an am335x-based board Apr 04 20:50:25 thx Apr 04 20:50:54 bnl = boneblack (historical reasons) Apr 04 20:51:00 BNLT I mean Apr 04 20:51:51 then comes the pcb revision, "00C0" (i.e. revision C) **** ENDING LOGGING AT Wed Apr 05 03:00:03 2017