OneWire (w1) Stopped Detecting Sensors

GoogleGroups
1

I previously had a few DS18b20 sensors working fine. I can’t really pinpoint what happened, but it all of a sudden they stopped working. Can anyone provide some direction?
I’m running: Linux debian-armhf 3.8.13-bone30
cat /sys/devices/bone_capemgr.9/slots:

4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
7: ff:P-O-L Override Board Name,00A0,Override Manuf,w1

dmesg:

[ 1.663645] bone-capemgr bone_capemgr.9: loader: done slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 1.672272] bone-capemgr bone_capemgr.9: loader: check slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 1.695708] bone-capemgr bone_capemgr.9: loader: after slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 1.721104] bone-capemgr bone_capemgr.9: slot #6: Requesting firmware ‘cape-boneblack-hdmin-00A0.dtbo’ for board-name ‘Bone-Black-HDMIN’, version ‘00A0’
[ 1.764142] usb usb1: Manufacturer: Linux 3.8.13-bone30 musb-hcd
[ 1.775711] bone-capemgr bone_capemgr.9: slot #6: dtbo ‘cape-boneblack-hdmin-00A0.dtbo’ loaded; converting to live tree
[ 1.796045] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[ 1.805652] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[ 1.812426] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 95.047835] bone-capemgr bone_capemgr.9: part_number ‘w1’, version ‘N/A’
[ 95.059627] bone-capemgr bone_capemgr.9: slot #7: generic override
[ 95.066271] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 7
[ 95.074344] bone-capemgr bone_capemgr.9: slot #7: ‘Override Board Name,00A0,Override Manuf,w1’
[ 95.085875] bone-capemgr bone_capemgr.9: slot #7: Requesting part number/version based 'w1-00A0.dtbo
[ 95.095993] bone-capemgr bone_capemgr.9: slot #7: Requesting firmware ‘w1-00A0.dtbo’ for board-name ‘Override Board Name’, version ‘00A0’
[ 95.134512] bone-capemgr bone_capemgr.9: slot #7: dtbo ‘w1-00A0.dtbo’ loaded; converting to live tree
[ 95.148143] bone-capemgr bone_capemgr.9: slot #7: #2 overlays
[ 95.166203] bone-capemgr bone_capemgr.9: slot #7: Applied #2 overlays.

bb@debian-armhf:~$ ls /sys/bus/w1/devices
w1_bus_master1

What else should I check? There are a few errors popping up in dmesg, but it appears that it is loading correctly. I double and triple checked my wiring- I’ve tried three different sensors plugged directly into the BB and some via breadboard connection.

2

I found this command: cat /sys/kernel/debug/gpio

`

GPIOs 0-31, gpio:
gpio-6 (mmc_cd ) in lo

GPIOs 32-63, gpio:
gpio-45 (w1 ) in lo
gpio-52 (eMMC_RSTn ) out lo
gpio-53 (beaglebone:green:usr) out lo
gpio-54 (beaglebone:green:usr) out lo
gpio-55 (beaglebone:green:usr) out hi
gpio-56 (beaglebone:green:usr) out lo
gpio-59 (McASP Clock Enable P) out hi
gpio-60 (sysfs ) in hi

`

It looks like the appropriate PIN is loading and listening correctly. I’m at a loss

3

if nothing changed on the software side then I would look at the hardware as in possible connector problem, cabling problem, shorted device problem, shorted cable problem, etc.

if you’ve got your device addrs hard coded in software maybe remove one and test it with a new/known cable and/or run your test software on a known good device first.

Doug

4

Yea that was my first thought too. I've tried sensors that were working
fine. I wonder if I inadvertently messed up something on the software side.
I just don't know where to check. The only information I have is the error
that shows the device tree is having trouble from dmesg log above.

5

I see Linux kernel 3.8.13 shown above and thought I read that not all the cape firmware has been ported to 3.8.13 from 3.8.2.

Did you do a kernel update? Do you still have the 3.8.2 kernel around to boot to see if that’s it?

Doug