Again, thanks Williams... that was it. I commented everything about P9.22 in ./bb.org-overlays/src/arm/univ-bbgw-00A0.dts Then build and install with your instruccions :)
Which is an elegant way to mount the w1 overlay automatically after reboot? By the way, I switched my VCC to 3.3V regards, Sebatián On Friday, December 2, 2016 at 5:39:38 PM UTC-8, William Hermans wrote: > > Sebastián, > > I do not know what to say. You possibly have a pin conflict in one of your > overlays somewhere. I'd check through all the source file for the dtbo's > you're using, and make sure there are no P9.22 references in an of them. > Except the 1-wire overlay file. > > On Fri, Dec 2, 2016 at 6:37 PM, William Hermans <yyr...@gmail.com > <javascript:>> wrote: > >> By the way, for informational purposes. The board file I'm loading( >> am335x-boneblack-emmc-overlay.dtb >> ) for my BBB should also work with BBG's too. At least I've used it with >> several Greens, and have had zero problems with it. Now, when I say >> "several" think in the range of 40-50 different boards . . . >> >> On Fri, Dec 2, 2016 at 6:33 PM, William Hermans <yyr...@gmail.com >> <javascript:>> wrote: >> >>> >>> On Fri, Dec 2, 2016 at 2:37 PM, acheesehead <achee...@gmail.com >>> <javascript:>> wrote: >>> >>>> Thanks William. I'll try out your instructions on Mon. >>>> >>> >>> One thing I did not mention last night was that I did all this one a >>> beaglebone black running . . . >>> >>> william@beaglebone:~$ cat /etc/dogtag >>> BeagleBoard.org Debian Image 2016-10-30 >>> william@beaglebone:~$ uname -r >>> 4.4.27-ti-r62 >>> >>> So, someone mentioned in the last couple of days ( I think ) that >>> they're using a 3.8.x kernel. A couple of concerns with this is that a) the >>> overlays as described by me may not work the same. Meaning, I do not recall >>> if 3.8.x overlays are slightly different or not. Through the source, or in >>> how dtc compiles the source into "binaries". b) The sysfs file entries are >>> possibly going to be different. >>> >>> Honestly, I could not say for sure, because last night was the very >>> first time I've setup 1-wire on the beaglebone. I just know / knew how to >>> modify the overlay's source in order for it to be proper. How to wire up >>> the sensor through a buddy of mine( someone with 35+ years electronics >>> design experience ). Here, see everyone on the web is saying to run a 4.7k >>> resistor between Vdd, and DQ on the sensor. Even if you're externally >>> powering the sensor. Where I've been told this is not necessary, and that >>> the resistor is only needed if you're going to parasitically power the >>> sensor through the DQ pin. Which my buddy does not seem convinced that this >>> sensor can be powered through a Beaglebone GPIO. So "erroring" on the side >>> of caution least I burn out a GPIO pin, or worse yet the processor. I opted >>> to power via an external power source. Also reading the datasheet I noticed >>> the input voltage range for the sensor is something like 2v8 to 5v6 ish . . >>> . I just powered the sensor straight off P9.5( 5v ). Indeed, in the end, it >>> seems to work perfectly fine this way. But I did not double check the temp >>> output to make sure it was accurate. I am however reasonably convinced it's >>> fine. I'll double check later with another kind of temperature sensor that >>> I know is accurate within a degree or two. Close enough for me . . . we >>> even have some K-type thermocouplers here( MAX31855 ) that are very >>> accurate if it ever comes to that. I haven't done SPI on the beaglebone yet >>> though . . . Anyway . . . >>> >>> The image I'm using is the one Robert says is the latest Jessie >>> "release" image that will be shipping with the BBGW's soon( I believe ). >>> Everything else as far as I can remember is pretty stock. Except I've >>> installed a few Debian packages that should have no bearing on this subject >>> at all ( build-essential, git, nfs-client. acpid, maybe i2c-tools, etc ). >>> >>> Wait, one thing I did change in /boot/uEnv.txt: >>> >>> ##BeagleBone Black: HDMI (Audio/Video) disabled: >>> dtb=am335x-boneblack-emmc-overlay.dtb >>> >>> I do not think this overlay is loaded by default on the stock image. For >>> the pin I chose, I do no think it's related to hdmi at all. But if you're >>> going ot use a different pin, you should double check to make the pin does >>> not conflict with the hdmi pins. Or some other board function. Picking >>> I2C0, or I2C2 pins would also not work out very good. As well as the eMMC >>> pins, if you're running off the eMMC . . . standard double check everything. >>> >>> >>> >>> >>> >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c652716e-0ca5-4962-acbe-00b34e0a88de%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
