That is good news. I was getting suspicious when we failed in the 27th call to triplet
One thing I didn't include was the test of SM_BUS capabilities. All that would do, if failed,
is formally tell us that the i2c adapter isn't documented to support the needed calls.
Do you know what i2c chip is
Good news: current version operates without any problem on a x86-machine with
a self-made i2c-parallel-port-adapter (see
linux/Documentation/i2c/busses/i2c-parport). Tested with a DS2482-100 and a
DS2890 digital potentiometer. Reading from and writing to this 1-wire device
works fine. Even two
Added more debugging info. It looks like there was a problem reading
from the DS2482 status register. This may show why.
Paul
On 5/23/06, Paul Alfille <[EMAIL PROTECTED]> wrote:
Ok, fixed the directory caching problem.
Paul
On 5/23/06, Paul Alfille <[EMAIL PROTECTED]> wrote:
> Thank you, Dani
Ok, fixed the directory caching problem.
Paul
On 5/23/06, Paul Alfille <[EMAIL PROTECTED]> wrote:
Thank you, Daniel!
1. Detection seems to work
2. 1-wire search fails after 27 of 64 steps, Not sure why.
3. Clearly a failed directory listing is getting cached -- unrelated error.
I'll make some
Thank you, Daniel!
1. Detection seems to work
2. 1-wire search fails after 27 of 64 steps, Not sure why.
3. Clearly a failed directory listing is getting cached -- unrelated error.
I'll make some changes to see if we can figure out why the search is
failing. It seems like a timing, hardware or d
Hello Paul,
this is the debug output from owserver:
~ $ /usr/bin/owserver --foreground --error_level 9 -p 2000 /dev/i2c-1
CONNECT: Found an i2c device at /dev/i2c-1 address 24
CONNECT: i2c device at /dev/i2c-1 address 24 cannot be reset
CONNECT: Found an i2c device at /dev/i2c-1 address 25
CONNEC
Daniel,
This is better than I expected.
With your modifications, it sounds like:
1. The chip is detected
2. Reset and the start of a device search works.
I'm uploading a more heavily "instrumented" version -- more debugging
information -- which might help us figure out the problem.
Paul
On 5/2
My first attempt with the current CVS version failed, owserver did not print
anything on the console. I cannot find where DS2482_detect() is called, thus
I added the following code to the switch() statement in LibStart():
...
case bus_i2c:
ret = DS2482_detect(in);
break;
...
(Is th
The version in the CVS should be a first step. Run with --foreground
--error_level=9 and look at the initial detection. We'll work through
it sequentially.
Paul
On 5/18/06, Jan Kandziora <[EMAIL PROTECTED]> wrote:
Am Mittwoch, 17. Mai 2006 22:41 schrieb Paul Alfille:
> No Jan,
>
> I've been squ
Am Mittwoch, 17. Mai 2006 22:41 schrieb Paul Alfille:
> No Jan,
>
> I've been squashing other bugs.
> Let me review --smbus is no good? Must use i2c?
>
I'm not really sure. Christoph Scheurer mused about this (in message
<[EMAIL PROTECTED]>) a couple of weeks ago:
> > I see your problem, but on t
No Jan,
I've been squashing other bugs.
Let me review --smbus is no good? Must use i2c?
I have the high-level things in place, but haven't trasfered in al the
actual i2c calls.
Since you have a test platform, I'll get it done this week.
Paul
On 5/17/06, Jan Kandziora <[EMAIL PROTECTED]> wrote:
11 matches
Mail list logo
