Port-arm archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Using 1-wire on ODROID C2
I found this thread, which is not very encouraging:
http://mail-index.netbsd.org/tech-embed/2021/07/thread1.html
I've created a sys/arch/evbarm/conf/GENERIC64.local with the following
lines:
# 1- Wire support
gpioow* at gpio?
onewire* at gpioow?
# 1-Wire devices
owtemp* at onewire? # Temperature sensors
and I'm rebuilding the kernel and modules.
However, once I'll have an owtemp kernel module, I still don't know what
to do with it. :/
That's where an example would help.
Once I'll have a working device, the man pages related to envsys seem
clear enough.
On 19/09/2022 23:43, Vincent DEFERT wrote:
I could use owtemp/envsys, but I can't find any example of use, and no
documentation except the man pages.
On 19/09/2022 23:33, Michael van Elst wrote:
vincent.defert%posteo.net@localhost (Vincent DEFERT) writes:
There's no /dev/onewire0, and I have no clue as to how is my
application
is supposed to communicate with the DS18B20 connected to this GPIO
line.
There is no userland interface for onewire(4).
So far there are two users of onewire(4):
- the owtemp driver for e.g. a DS18B20 which attaches as a sensor to
the envsys framework. You can query the sensor with the envstat
command.
- a rudimentary oweeprom driver for e.g. a DS2430, that just dumps
the content
to the console.
Home |
Main Index |
Thread Index |
Old Index