Re: [beagleboard] Re: device tree dallas 1 wire ubuntu - loads but odd behaviour
Matt,
Did you solve your problem? I have a very similar issue to yours right now.
I've been trying to find a solution for a few days.
Andrew
On Wednesday, December 11, 2013 7:13:39 AM UTC-5, Sika wrote:
>
> Pretty recent, actually, Mike...
>
> 3.8.13-bone20
>
> And the pins are changing -- it's outputing 37:
>
> sudo cat $PINS|grep 840
> pin 16 (44e10840) 0037 pinctrl-single
>
> and the multimeter says it is pulled up.
>
> I used a different overlay tree as well -- and get the same thing
> /dts-v1/;
> /plugin/;
>
> / {
> compatible = "ti,beaglebone", "ti,beaglebone-black";
> part-number = "BB-W1";
> version = "00A0";
>
> exclusive-use = "P9.15", "gpio1_16";
>
> fragment@0 {
> target = <&am33xx_pinmux>;
> __overlay__ {
> bb_w1_pins: pinmux_bb_w1_pins {
> pinctrl-single,pins = <
> 0x040 0x37 /*pin P9_15 input with pullup mode 7 -
> w1-gpio */
> >;
> };
> };
> };
>
> fragment@1 {
> target = <&ocp>;
> __overlay__ {
> onewire@0 {
> status = "okay";
> compatible = "w1-gpio";
> pinctrl-names = "default";
> pinctrl-0 = <&bb_w1_pins>;
>
> gpios = <&gpio2 16 0>; /*grrr I think this means gpio1_16
> (using 1 to 4 instread of 0-3)*/
> };
> };
> };
> };
>
>
> I'd greatly appreciate any help on this I can get!
>
> Kind regards
>
> Matt
>
>
>
>
>
>
> On Wednesday, December 11, 2013 7:57:21 PM UTC+10, Mike Bremford wrote:
>>
>> Which kernel - "uname -a"? I don't think you can change the pinmux for
>> pins under 3.12 yet - well I couldn't anyway, although it worked for me
>> under 3.8. Check by doing "grep 44e10840
>> /sys/kernel/debug/pinctrl/44e10800.pinmux/pins" - is it 0037? Is the
>> pin actually pulled up? Test with a multimeter and/or add an external
>> pullup resistor.
>>
>>
>> On 11 December 2013 08:29, Sika wrote:
>>
>>> Well it says it loads -- but it does not work. Help appreciated!
>>>
>>> Thanks
>>>
>>> Matt
>>>
>>>
>>> On Tuesday, December 10, 2013 6:31:12 PM UTC+10, Sika wrote:
Oh, by the way ...the blob is loaded:
grubby@ubuntu-armhf:~/python/projects$ cat $SLOTS
0: 54:PF---
1: 55:PF---
2: 56:PF---
3: 57:PF---
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
6: ff:P-O-L Override Board Name,00A0,Override Manuf,w1
>>
--
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/groups/opt_out.
Re: [beagleboard] Re: device tree dallas 1 wire ubuntu - loads but odd behaviour
Pretty recent, actually, Mike...
3.8.13-bone20
And the pins are changing -- it's outputing 37:
sudo cat $PINS|grep 840
pin 16 (44e10840) 0037 pinctrl-single
and the multimeter says it is pulled up.
I used a different overlay tree as well -- and get the same thing
/dts-v1/;
/plugin/;
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";
part-number = "BB-W1";
version = "00A0";
exclusive-use = "P9.15", "gpio1_16";
fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
bb_w1_pins: pinmux_bb_w1_pins {
pinctrl-single,pins = <
0x040 0x37 /*pin P9_15 input with pullup mode 7 -
w1-gpio */
>;
};
};
};
fragment@1 {
target = <&ocp>;
__overlay__ {
onewire@0 {
status = "okay";
compatible = "w1-gpio";
pinctrl-names = "default";
pinctrl-0 = <&bb_w1_pins>;
gpios = <&gpio2 16 0>; /*grrr I think this means gpio1_16
(using 1 to 4 instread of 0-3)*/
};
};
};
};
I'd greatly appreciate any help on this I can get!
Kind regards
Matt
On Wednesday, December 11, 2013 7:57:21 PM UTC+10, Mike Bremford wrote:
>
> Which kernel - "uname -a"? I don't think you can change the pinmux for
> pins under 3.12 yet - well I couldn't anyway, although it worked for me
> under 3.8. Check by doing "grep 44e10840
> /sys/kernel/debug/pinctrl/44e10800.pinmux/pins" - is it 0037? Is the
> pin actually pulled up? Test with a multimeter and/or add an external
> pullup resistor.
>
>
> On 11 December 2013 08:29, Sika > wrote:
>
>> Well it says it loads -- but it does not work. Help appreciated!
>>
>> Thanks
>>
>> Matt
>>
>>
>> On Tuesday, December 10, 2013 6:31:12 PM UTC+10, Sika wrote:
>>>
>>> Oh, by the way ...the blob is loaded:
>>>
>>>
>>> grubby@ubuntu-armhf:~/python/projects$ cat $SLOTS
>>> 0: 54:PF---
>>> 1: 55:PF---
>>> 2: 56:PF---
>>> 3: 57:PF---
>>> 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
>>> 6: ff:P-O-L Override Board Name,00A0,Override Manuf,w1
>>>
>>>
>
--
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/groups/opt_out.
Re: [beagleboard] Re: device tree dallas 1 wire ubuntu - loads but odd behaviour
Which kernel - "uname -a"? I don't think you can change the pinmux for pins under 3.12 yet - well I couldn't anyway, although it worked for me under 3.8. Check by doing "grep 44e10840 /sys/kernel/debug/pinctrl/44e10800.pinmux/pins" - is it 0037? Is the pin actually pulled up? Test with a multimeter and/or add an external pullup resistor. On 11 December 2013 08:29, Sika wrote: > Well it says it loads -- but it does not work. Help appreciated! > > Thanks > > Matt > > > On Tuesday, December 10, 2013 6:31:12 PM UTC+10, Sika wrote: >> >> Oh, by the way ...the blob is loaded: >> >> >> grubby@ubuntu-armhf:~/python/projects$ cat $SLOTS >> 0: 54:PF--- >> 1: 55:PF--- >> 2: 56:PF--- >> 3: 57:PF--- >> 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 >> 6: ff:P-O-L Override Board Name,00A0,Override Manuf,w1 >> >> -- 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/groups/opt_out.
[beagleboard] Re: device tree dallas 1 wire ubuntu - loads but odd behaviour
Well it says it loads -- but it does not work. Help appreciated!
Thanks
Matt
On Tuesday, December 10, 2013 6:31:12 PM UTC+10, Sika wrote:
>
> Oh, by the way ...the blob is loaded:
>
>
> grubby@ubuntu-armhf:~/python/projects$ cat $SLOTS
> 0: 54:PF---
> 1: 55:PF---
> 2: 56:PF---
> 3: 57:PF---
> 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
> 6: ff:P-O-L Override Board Name,00A0,Override Manuf,w1
>
>
> On Tuesday, December 10, 2013 6:13:43 PM UTC+10, Sika wrote:
>>
>> Hi All,
>>
>> A puzzle:
>>
>> the following device tree
>>
>>
>>
>>
>> /*
>> * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
>> *
>> * This program is free software; you can redistribute it and/or modify
>> * it under the terms of the GNU General Public License version 2 as
>> * published by the Free Software Foundation.
>> *
>> * Modified by Russell Senior from the weather cape's DTS file.
>> * Minor formatting by C W Rose. Minor additions and mistakes M.Redding
>> */
>> /dts-v1/;
>> /plugin/;
>> / {
>> compatible = "ti,beaglebone", "ti,beaglebone-black";
>> part-number = "BB-W1";
>> version = "00A0";
>> exclusive-use = "P9.15";
>>
>> fragment@0 {
>> target = <&am33xx_pinmux>;
>> __overlay__ {
>> bb_w1_pins: pinmux_bb_w1_pins {
>> pinctrl-single,pins = <
>> 0x040 0x37 /*pin P9_15 input with pullup mode 7 -
>> w1-gpio */
>> >;
>> };
>> };
>> };
>> fragment@1 {
>> target = <&ocp>;
>> __overlay__ {
>> onewire@0 {
>> status = "okay";
>> compatible = "w1-gpio";
>> pinctrl-names = "default";
>> pinctrl-0 = <&bb_w1_pins>;
>> gpios = <&gpio2 16 0>; /*grrr I think this means gpio1_16
>> (using 1 to 4 instread of 0-3)*/
>> };
>> };
>> };
>> };
>>
>>
>>
>>
>> This thing loads -- on ubuntu, but does not seem to produce an accessible
>> device:
>>
>>
>> ls /sys/bus/w1/
>>
>> devices drivers drivers_autoprobe drivers_probe uevent
>>
>> ls /sys/bus/w1/devices
>>
>> w1_bus_master1
>>
>>
>> ls /sys/bus/w1/devices/w1_bus_master1
>> driver uevent w1_master_max_slave_count
>> w1_master_pullup w1_master_slave_count
>> power w1_master_add w1_master_name
>> w1_master_remove w1_master_slaves
>> subsystem w1_master_attempts w1_master_pointer
>> w1_master_search w1_master_timeout
>>
>>
>> hmm so, any suggestions where w1_slave might be, so I can access it
>> from python?
>>
>> Thanks for your help
>>
>> Kind regards
>>
>> Matt
>>
>>
>>
>>
>>
>>
--
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/groups/opt_out.
[beagleboard] Re: device tree dallas 1 wire ubuntu - loads but odd behaviour
Oh, by the way ...the blob is loaded:
grubby@ubuntu-armhf:~/python/projects$ cat $SLOTS
0: 54:PF---
1: 55:PF---
2: 56:PF---
3: 57:PF---
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
6: ff:P-O-L Override Board Name,00A0,Override Manuf,w1
On Tuesday, December 10, 2013 6:13:43 PM UTC+10, Sika wrote:
>
> Hi All,
>
> A puzzle:
>
> the following device tree
>
>
>
>
> /*
> * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
> *
> * This program is free software; you can redistribute it and/or modify
> * it under the terms of the GNU General Public License version 2 as
> * published by the Free Software Foundation.
> *
> * Modified by Russell Senior from the weather cape's DTS file.
> * Minor formatting by C W Rose. Minor additions and mistakes M.Redding
> */
> /dts-v1/;
> /plugin/;
> / {
> compatible = "ti,beaglebone", "ti,beaglebone-black";
> part-number = "BB-W1";
> version = "00A0";
> exclusive-use = "P9.15";
>
> fragment@0 {
> target = <&am33xx_pinmux>;
> __overlay__ {
> bb_w1_pins: pinmux_bb_w1_pins {
> pinctrl-single,pins = <
> 0x040 0x37 /*pin P9_15 input with pullup mode 7 -
> w1-gpio */
> >;
> };
> };
> };
> fragment@1 {
> target = <&ocp>;
> __overlay__ {
> onewire@0 {
> status = "okay";
> compatible = "w1-gpio";
> pinctrl-names = "default";
> pinctrl-0 = <&bb_w1_pins>;
> gpios = <&gpio2 16 0>; /*grrr I think this means gpio1_16
> (using 1 to 4 instread of 0-3)*/
> };
> };
> };
> };
>
>
>
>
> This thing loads -- on ubuntu, but does not seem to produce an accessible
> device:
>
>
> ls /sys/bus/w1/
>
> devices drivers drivers_autoprobe drivers_probe uevent
>
> ls /sys/bus/w1/devices
>
> w1_bus_master1
>
>
> ls /sys/bus/w1/devices/w1_bus_master1
> driver uevent w1_master_max_slave_count w1_master_pullup
> w1_master_slave_count
> power w1_master_add w1_master_name w1_master_remove
> w1_master_slaves
> subsystem w1_master_attempts w1_master_pointer w1_master_search
> w1_master_timeout
>
>
> hmm so, any suggestions where w1_slave might be, so I can access it
> from python?
>
> Thanks for your help
>
> Kind regards
>
> Matt
>
>
>
>
>
>
--
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/groups/opt_out.
