I have been looking for way too long so maybe I don’t know what to search for.
I am attempting to get the ds18B20 temperature sensor working on a rev b beaglebone black that is running jessie 4.5 that I downloaded from the official place. I have a beaglebone rev c that uses the capemgr device tree mechanism and I know how to make that work. I can’t seem to find any reference that will get me started with the no capemgr device tree implementation.
Can someone point me to a place that will help me figure this out? Or should I go back to the original angstrom distribution?
In addition to what Robert has shown you there . . . the internet is literally littered with guides, blogs, and random ramblings on getting the ds18x20 devices working on both the Beaglebone’s, and the rPI . . . Heres one.
Thank to both of you, I do appreciate the information.
I have read and implemented several of the instructions that have the cape manager in /sys/devices/cape_mgr.9/slots to read the temperature and they work sure enough. The problem is, I have an older Rev B device that is running the image debian-8.3-ixqt and the device tree is slightly different. I followed a couple of examples and I couldn’t get it to work so I figured I needed to understand how the mechanism works because eventually I need to turn on and off some devices via a transistor and just copying something from the web doesn’t tell me what each section of the device tree does. and how the two versions, different capemgr locations, are different.
The last example i tried suggested i put the dtbo in /boot/uEnv.txt and now the bone won’t boot, all four led’s stay lit so I feel it is time to stop counting on guess work and hope that what someone writes in a blog somewhere actually has worked on a recent image and figure out what I am doing.
BR:
I got it working by adding this line:
cape_enable=bone_capemgr.enable_partno=BB-W1-P9.12
to /boot/uEnv.txt and rebooting.
Now the problem is I can’t use the other gpio pins:
# config-pin -q P9_11
P9_11 pinmux file not found!
cape-universala overlay not found
run “config-pin overlay cape-universala” to load the cape # config-pin overlay cape-universala
Loading cape-universala overlay
sudo: unable to resolve host yoder-debian-bone
bash: line 0: echo: write error: No such file or directory
Error loading device tree overlay file: cape-universala
Do I have to edit a dts file to get both working? What’s the proper way to do it?
I would say yes, you have to make your own overlay. I ran into this before too. The way I did this was simply merge the pin definitions I needed from both files into a single file. A unique file of course.
Unless you know the different overlays are not going to have pin conflicts, or collisions. You should probably write your own overlay.