Thanks William. I'll try out your suggestions when I get to the office.
On Monday, December 5, 2016 at 8:51:37 PM UTC-7, William Hermans wrote:
>
> Nope, actually that persons overlay file is wrong. So yeah I don;t know
> time to learn Linux and start troubleshooting your problems ;)
>
> On Mon,
Nope, actually that persons overlay file is wrong. So yeah I don;t know
time to learn Linux and start troubleshooting your problems ;)
On Mon, Dec 5, 2016 at 8:47 PM, William Hermans wrote:
> Actually the last bit probably wont work because:
>
> william@beaglebone:~$ ls
Actually the last bit probably wont work because:
william@beaglebone:~$ ls /sys/devices/platform/ocp/*.gpio/gpio/
/sys/devices/platform/ocp/44e07000.gpio/gpio/:
gpiochip0
/sys/devices/platform/ocp/4804c000.gpio/gpio/:
gpiochip32
/sys/devices/platform/ocp/481ac000.gpio/gpio/:
gpiochip64
On Mon, Dec 5, 2016 at 7:30 PM, acheesehead wrote:
> Tried your workflow today without success. Everything is OK up to the
> lsmod | grep w1 step. I only get the w1_gpio entry. I am not a Linux kernel
> expert, so I don't know how to troubleshoot why the other entries
Tried your workflow today without success. Everything is OK up to the lsmod
| grep w1 step. I only get the w1_gpio entry. I am not a Linux kernel
expert, so I don't know how to troubleshoot why the other entries aren't
showing up.
I didn't see any activity on the oscilloscope either.
On
*OR* P8.26 . . . *smacks hardware designer / buddy . . .
*william@beaglebone:~/dev/bb.org-overlays$* diff
src/arm/BB-W1-P8.26-00A0.dts src/arm/BB-W1-P8.14-00A0.dts
4c4
< * Virtual cape for onewire on connector pin P8.26
---
> * Virtual cape for onewire on connector pin P8.14
21c21
<
I repeated this process for P8.14, and it works fine. This is just to let
others who may not be aware that you can use 1-wire on any gpio pin that is
not already in use by the system. Again, double check the pins in the
schematic, to make sure they're not being used by somethign like HDMI(
which
@ Sebastian
Ah I forgot to mention loading capes from /boot/uEnv.txt. So . . .
*william@beaglebone:~$* cat /boot/uEnv.txt |grep cape
#cmdline=coherent_pool=1M quiet cape_universal=enable
video=HDMI-A-1:1024x768@60e
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=
On Sat, Dec 3, 2016 at 10:52 AM, Sebastián Sáez wrote:
> 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
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
On Fri, Dec 2, 2016 at 8:10 PM, Dennis Lee Bieber
wrote:
> Is that safe? I'd think the 5V would influence the swing of the
> data
> line, and I thought the BBB is supposed to only have 3.3V on the inputs.
>
You know, it ran over night no problems, the sensor still
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,
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 2:37 PM, acheesehead 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
sorry Williams but now I have another problem with this.
My temperature sensor work fine but when I load our overlay the Mraa module
stop working. I think our overlay replace this overlay "univ-bbgw"
root@beaglebone:/firmware# python test.py
> Traceback (most recent call last):
> File
Thanks William. I'll try out your instructions on Mon.
On Thursday, December 1, 2016 at 10:50:19 PM UTC-7, William Hermans wrote:
>
>
> On Thu, Dec 1, 2016 at 10:39 PM, acheesehead > wrote:
>
>> In all of the examples that I have seen, the P9.x -> GPIO bank.port
>>
That's it !, Many thanks Williams
It works perfect
On Thursday, December 1, 2016 at 9:28:16 PM UTC-8, William Hermans wrote:
>
> *1-wire workflow:*
>
> *Hardware setup:*
>
> Everything is directly connected via jumper wires, with no additional
> components.
>
> DS18B20 PIN1 connected to
Note the "mode7" column to the far right.
On Thu, Dec 1, 2016 at 10:51 PM, William Hermans wrote:
> Ah forgot the screenshot . . .
>
> On Thu, Dec 1, 2016 at 10:50 PM, William Hermans
> wrote:
>
>>
>> On Thu, Dec 1, 2016 at 10:39 PM, acheesehead
On Thu, Dec 1, 2016 at 10:39 PM, acheesehead wrote:
> In all of the examples that I have seen, the P9.x -> GPIO bank.port
> translates to GPIO (bank +1).port between lines in the overlay script.
>
That's incorrect if I understand what you're trying to say. the P8/P9
I should probably note that when I connected everything up. I had the
beaglebone powered down, and completely disconnected from everything.
On Thu, Dec 1, 2016 at 10:28 PM, William Hermans wrote:
> *1-wire workflow:*
>
> *Hardware setup:*
>
> Everything is directly connected
*1-wire workflow:*
*Hardware setup:*
Everything is directly connected via jumper wires, with no additional
components.
DS18B20 PIN1 connected to Beaglebone P9.1 (ground)
DS18B20 PIN2 connected to Beaglebone P9.22 (1-wire data)
DS18B20 PIN3 connected to Beaglebone P9.5 (Vdd 5v)
Remove any
Another problem I'm seeing with your "wiring diagram". You're powering the
sensor via 3v3, but you still have the parasitic power resistor in place.
It is my understanding if you're wanting to power the DS18B20 from the
dataline. In whcih case the resistor would be between Vdd, and DQ pins
(pins 2
On Thu, Dec 1, 2016 at 10:57 AM, Sebastián Sáez wrote:
> Hi Dennis,
>
> I attach my circuit. It's connected to P9_22 with a pullup 4.7K resistor.
> Now I'm trying with BBGW-blank-debian-8.5-seeed-iot-armhf-2016-06-19-4gb
>
> I try with this module from this tutorial
>
23 matches
Mail list logo