Probably not. At minimum, not without modifications. The problem I have here is that I have no one wire devices to test all this stuff I'm suggesting to you. Otherwise I'd have a fix for you already.
On Mon, Apr 4, 2016 at 6:38 PM, <matthew.redd...@daf.qld.gov.au> wrote: > Thanks for the tip. > > > I tried correcting that line first to: > > gpios = <&gpio1 13 0>; > > > and then to > > > gpios = <&gpio2 13 0>; > > > I'm not sure which of these is correct, though I would have thought it was > gpios = <&gpio1 13 0>; > > > > But still no go. > > > Sounds like I need to change to 4.1. > > > I see that RCN's link leads to a bash script that allows > > more time for detection? Could this problem be related to > > not enough time being allowed for detection. > > > Would the script work under 3.8, and might it solve the problem? > > > Thanks > > > Matt > > > > On Tuesday, April 5, 2016 at 10:30:33 AM UTC+10, William Hermans wrote: >> >> gpios = <&gpio1 2 0> >> >> &gpio1 I'm pretty sure is reference to the gpio bank. There is 4 I think >> for all gpio's on the processor. The two numbers that follow . . . I >> honestly have no idea either. >> >> I can hoever tell you that: >> pinctrl-single,pins = <0x34 0x37 /* gpmc_ad13.gpio1_13, >> OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE7 - w1-gpio */ >; >> >> 0x34 is the pin number, and 0x37 is the pin mode. Which peripheral, or >> GPIO mode, whether it's input, or output, and whether pull up, or pull down >> is enabled. Pretty much my understanding here is a 32bit field with each >> bit indicating *something*. >> >> On Mon, Apr 4, 2016 at 5:25 PM, REDDING Matthew < >> matthew...@daf.qld.gov.au> wrote: >> >>> Eagle eyes! >>> >>> >>> >>> I’ll try changing that back and see what happens. >>> >>> I must confess, I don’t even know what gpios = <&gpio1 2 0>; does. >>> >>> So I’m not sure where any changes came from. >>> >>> >>> >>> I think I know what the other line you indicated does. >>> >>> >>> >>> >>> >>> Kind regards >>> >>> >>> >>> >>> >>> Matt Redding, Ph.D. >>> >>> Soil Chemist/Geochemist >>> >>> AgriScience Queensland >>> >>> Queensland DAFF >>> >>> >>> >>> 0408 787100 >>> >>> 07 46 88 1372 >>> >>> >>> >>> >>> >>> >>> >>> *From:* beagl...@googlegroups.com [mailto:beagl...@googlegroups.com] *On >>> Behalf Of *William Hermans >>> *Sent:* Tuesday, 5 April 2016 10:22 AM >>> *To:* beagl...@googlegroups.com >>> *Subject:* Re: [beagleboard] Re: Troubleshooting one-wire DS18B20 >>> detection on BBB, debian, kernel: 3.8.13-bone70 >>> >>> >>> >>> *Using the modprobe w1-gpio produces no output.* >>> >>> >>> >>> *Is this where the problem is?* >>> >>> >>> >>> *Thanks* >>> >>> >>> >>> *Matt* >>> >>> So, I'm not 100% sure what the problem is. I've never used One wire in >>> linux - ever - And I'm not 100% sure what driver needs to be loaded, if any >>> for this specific device. I'm just trying my best to help you troubleshoot >>> the problem, because obviously there is something wrong, if the device does >>> not show up on several boards, using several devices. >>> >>> So Matt, I noticed you've changed the GPIO pin here: >>> >>> gpios = <&gpio1 2 0>; >>> >>> But not here: >>> >>> pinctrl-single,pins = <0x34 0x37 /* gpmc_ad13.gpio1_13, >>> OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE7 - w1-gpio */ >; >>> >>> So do keep in mind that I'm no device tree file expert. So I'm not sure >>> if that is bad, or not. But it *seems* wrong to me. Maybe I'm wrong ? >>> >>> >>> >>> On Mon, Apr 4, 2016 at 5:14 PM, <matthew...@daf.qld.gov.au> wrote: >>> >>> Hi William and Peter... >>> >>> >>> >>> root@beaglebone:~# lsmod >>> Module Size Used by >>> arc4 1691 2 >>> zd1211rw 43946 0 >>> >>> mac80211 424813 1 zd1211rw >>> cfg80211 354018 2 mac80211,zd1211rw >>> rfkill 16672 2 cfg80211 >>> g_multi 50407 2 >>> libcomposite 15028 1 g_multi >>> omap_rng 4062 0 >>> mt7601Usta 639170 0 >>> >>> >>> >>> >>> >>> Using the modprobe w1-gpio produces no output. >>> >>> >>> >>> Is this where the problem is? >>> >>> >>> >>> Thanks >>> >>> >>> >>> Matt >>> >>> >>> >>> >>> On Tuesday, April 5, 2016 at 10:08:36 AM UTC+10, William Hermans wrote: >>> >>> william@beaglebone:~$ sudo modprobe w1-gpio >>> william@beaglebone:~$ lsmod >>> Module Size Used by >>> w1_gpio 3069 0 >>> wire 27112 1 w1_gpio >>> . . . >>> >>> *My understanding was that 3.8 and above kernels needed no module, >>> simply the DTO. It was pre 3.8 kernels that required the kernel module. Or >>> am I missing something there? Certainly, every page I'm reading referring >>> to 3.8 kernel 1Wire has absolutely no reference to kernel modules.* >>> >>> So, perhaps, but if there is something wrong with the device tree blob >>> file, the driver wont auto load. Which would give us an indication as to >>> what's wrong. >>> >>> >>> >>> >>> >>> On Mon, Apr 4, 2016 at 5:01 PM, Peter Lawler <relwa...@gmail.com> wrote: >>> >>> >>> >>> On 2016/04/05 9:49 AM, William Hermans wrote: >>> >>> Ok, so the device tree seems to load but where is >>> the output of lsmod ? It should look something like( more or less ) with >>> hopefully the generic one-wire module also loaded. >>> >>> >>> My understanding was that 3.8 and above kernels needed no module, simply >>> the DTO. It was pre 3.8 kernels that required the kernel module. Or am I >>> missing something there? Certainly, every page I'm reading referring to 3.8 >>> kernel 1Wire has absolutely no reference to kernel modules. >>> >>> P. >>> >>> >>> >>> -- >>> 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...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> -- >>> 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...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "BeagleBoard" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/beagleboard/nT93pfbvCzQ/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> beagleboard...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> ------------------------------ >>> >>> The information in this email together with any attachments is intended >>> only for the person or entity to which it is addressed and may contain >>> confidential and/or privileged material. There is no waiver of any >>> confidentiality/privilege by your inadvertent receipt of this material. >>> >>> Any form of review, disclosure, modification, distribution and/or >>> publication of this email message is prohibited, unless as a necessary part >>> of Departmental business. >>> >>> If you have received this message in error, you are asked to inform the >>> sender as quickly as possible and delete this message and any copies of >>> this message from your computer and/or your computer system network. >>> >>> ------------------------------ >>> >>> -- >>> 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...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > 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. > For more options, visit https://groups.google.com/d/optout. > -- 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. For more options, visit https://groups.google.com/d/optout.
