**** BEGIN LOGGING AT Wed Nov 29 03:00:02 2017
Nov 29 04:18:51 <Ageon> I'm looking for a development board to develop IIOT project
Nov 29 04:19:09 <Ageon> is beagle board suitable for industrial purposes
Nov 29 14:59:41 <snowdog> Does anyone have experience extracting eMMC contents from the BeagleBone Green Wireless?
Nov 29 15:00:34 <myself> ...extracting?
Nov 29 15:00:49 <myself> you mean like, mounting the partition and reading from it?
Nov 29 15:01:47 <snowdog> I guess so, I'm trying to follow the instructions here to create an SD card that I can use to flash other boards. https://elinux.org/BeagleBone_Black_Extracting_eMMC_contents
Nov 29 15:03:30 <snowdog> I have also posted a question here that has a bit more detail with a boot log https://groups.google.com/forum/#!category-topic/beagleboard/seeed-beaglebone-green-wireless/boot/u-boot/ZFMBepd9hIo
Nov 29 15:08:19 <zmatt> snowdog: there's a script that creates a flasher card from eMMC contents, located at /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh
Nov 29 15:10:39 <snowdog> zmatt: Thank you, I will take a look at this!
Nov 29 15:11:31 <myself> is it fair to say that for most of these things, "beaglebone black" tools apply to all the derivatives (green, green wireless, blue, enhanced, etc)? Basically excluding the white, x15, and original beagleboard. I'm not sure where the pocket fits on the scale of compatibility..
Nov 29 15:11:44 <zmatt> myself: the pocket has no eMMC
Nov 29 22:07:11 <maxton> Does anyone know if there is a library for the PRU that facilitates accessing the I2C controllers on the L4 interconnect? I have been searching, and found only a project that implements I2C on the PRU via bit-banging the EGPIO pins.
Nov 29 22:24:01 <zmatt> not specifically, although using the i2c controller from the pru isn't really different from using the i2c controller from the cortex-a8
Nov 29 22:24:45 <zmatt> (apart from configuring the pru interrupt controller, if you intend to use it)
Nov 29 22:26:05 <zmatt> do make sure that linux doesn't have an active driver for it at the same time.  you can unbind the driver from the peripheral via sysfs (and also force-enable it there, which avoids having to deal with PRCM yourself)
Nov 29 22:29:24 <zmatt> e.g.   echo 4802a000.i2c >/sys/bus/platform/drivers/omap_i2c/unbind ; echo on >/sys/bus/platform/devices/4802a000.i2c/power/control
Nov 29 22:30:46 <zmatt> (this applies only if the peripheral is enabled in linux to begin with, but this is the case in the default setup on beaglebones since a fair time ago)
Nov 29 22:44:34 <maxton> Oh well, I guess it's back to reading the technical reference manual then. Thanks for the info!
**** ENDING LOGGING AT Thu Nov 30 03:00:02 2017