On Mon, 5 Aug 2002 10:39:02 -0700, "Keith Outwater" writes:
>
>Murray -
>Thanks for the info! Yes, I think that having an I2C_M_NOSTOP option
>would do what I want, but that option is not available in the kernel I'm
>using.
No, my comment was that for completeness there should be an I2C_M_NOSTO
On Fri, 2 Aug 2002 13:36:13 -0700, "Keith Outwater" writes:
>I am trying to talk to an I2C device (Analog Devices AD9888) using the
>MPC860 CPM I2C interface from userland.
You should probably state which kernel and i2c driver you are using - there are
a lot of different versions around.
Your m
Murray -
Thanks for the info! Yes, I think that having an I2C_M_NOSTOP option
would do what I want, but that option is not available in the kernel I'm
using.
>
> You should probably state which kernel and i2c driver you are
> using - there are
> a lot of different versions around.
I'm using a
hi
I think u r missing onr thing.
sequence should be like this
> Start signal
> Slave address (r/w/ bit = write)
> Register address
> Start signal
> Slave address (r/w/ bit = read)
> Read register data
>NO ack...u have to give
> Stop signal
Try to give No ack after readin
Greetings all -
I am trying to talk to an I2C device (Analog Devices AD9888) using the
MPC860 CPM I2C interface from userland.
Writes work fine, but the chip requires a strange write-read sequence
for reading back registers. For example, to read a register:
Start signal
Slave address (r/w/ bit
hello everybody,
i use a mpc860 with iic,fec and ethernet at SCC3; iic-communication normally
works fine, but sometimes
especially if there is heavy traffic on SCC3 or fec (eg. download of big files)
iic-communication stops with error
... iic-read; short, wanted 32 got 1 ...
also the data seems
