Am 14.03.2016 um 16:30 schrieb Timo Engel:
>
> Is there any update about this issue?
> Do you have some hints how to get this debugged?
>
So far, no. I have no time to look for owfs until starting of April, I
don't have the chip yet and there is other housekeeping work in owfs to
do already.
So
Is there any update about this issue?
Do you have some hints how to get this debugged?
Timo
On 09.03.2016 09:33, Timo Engel wrote:
>
> I tried the latest git version from Feb 18th with several different
> kernel versions: 3.10.25, 3.12.28, 3.12.35, 4.1.13
> The behaviour is always the same: I
I tried the latest git version from Feb 18th with several different
kernel versions: 3.10.25, 3.12.28, 3.12.35, 4.1.13
The behaviour is always the same: It is not possible to read from the
uncached EEPROM pages. However, it is possible to read the uncached
temperature.
On 19.02.2016 15:43, Jan
Am 16.02.2016 um 09:36 schrieb Timo Engel:
>
> This is the log generated for one call of owget. It excludes the
> messages for startup and shutdown of owserver.
> Version is 11325b6674a255a9797a1096e89870572ecf4db8.
>
Well, it seems either the w1 netlink communication has changed *again*
or there
Am 15.02.2016 um 14:30 schrieb Timo Engel:
>
> I am using bitbanging on an GPIO.
>
Then you have no choice but to use --w1. OWFS has no bitbanging driver
of its own, only drivers for RS232, USB and I²C based adaptors.
Unfortunately, I don't have a DS2433 nor DS2436 at hand to check it
myself. Co
On 13.02.2016 01:35, Jan Kandziora wrote:
> Am 12.02.2016 um 16:57 schrieb Timo Engel:
>>
>> The output of owserver is attached.
>> owget does not output anything when using the "uncached" path.
>>
> This looks a lot like the netlink layer has still (or again)
> communication problems with owlib.
Am 12.02.2016 um 16:57 schrieb Timo Engel:
>
> The output of owserver is attached.
> owget does not output anything when using the "uncached" path.
>
This looks a lot like the netlink layer has still (or again)
communication problems with owlib.
* Please make sure you are indeed using the owfs f
Am 12.02.2016 um 10:03 schrieb Timo Engel:
>
> Thanks for your reply, I checked this again now. I'm using owfs from
> git 11325b6674a255a9797a1096e89870572ecf4db8 from Sun Dec 6 20:57:29
> 2015 and Kernel 4.1.13-v7+ (raspbian jessie).
>
Ah, ok. So you have the w1 patch included.
>
> $ hexdump -
On 04.02.2016 15:00, Jan Kandziora wrote:
>> it seems to be useless because of the caching mechanism of owfs. I
>> know about the "uncached" directory, but reading from there makes owfs
>> stop working.
>>
> No. If it does for you, your installation is broken. Which version of
> OWFS do you use?
Am 04.02.2016 um 14:06 schrieb Timo Engel:
>
> I'm wondering what is the correct procedure to read/write form/to an
> EEPROM. Is it sufficient to use write() and write 32 bytes for example
> to pages/page.0?
>
Yes.
> Are there any status information if the last write()
> was successful?
>
If the
Hello,
I'm using owfs to read/write the EEPROM of DS2436 and DS2433 devices.
Mostly, this works nice and without problems. However, sometimes wrong
data is stored on the EEPROM.
I'm wondering what is the correct procedure to read/write form/to an
EEPROM. Is it sufficient to use write() and write
11 matches
Mail list logo
