public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
* Problem Configuring Micron sensor MT9D131 using i2c
@ 2008-05-30 11:06 Tekkalkot, Seetaram (IE10)
       [not found] ` <1106299A6DFA0E4D8E13CFD83A7611F09E2CA1-8tR4ov5Cr7uXeP9mKtfZqKJzXdaVS04K4Jgwf8ORaLoAvxtiuMwx3w@public.gmane.org>
  0 siblings, 1 reply; 4+ messages in thread
From: Tekkalkot, Seetaram (IE10) @ 2008-05-30 11:06 UTC (permalink / raw)
  To: i2c-GZX6beZjE8VD60Wz+7aTrA


[-- Attachment #1.1: Type: text/plain, Size: 930 bytes --]

Hi,

 

I am trying to configure the Micron sensor MTD131 using Linux 2.6 i2c.

 

The sensor data sheet mentions 0x90 as the write i2c address and 0x91 as
read i2c address.

It also mentions that, the last bit in the address is used to indicate
read or write operation.

I am using 0x48 (0x90 shifted right once to get 7 bit i2c address) to
detect the sensor using i2cdetect tool.

I am not able to detect this device!. I tried reading this device using
i2cget tool but it fails to read.

 

I have the following questions.

 

1.	As per the datasheet the i2c read address is 0x91 and write
address is 0x90, should I set any of these slave addresses based on
whether I am reading or writing?
2.	I am using 7 bits from 0x91 which 0x48, is this correct?
3.	Why i2cdetect doesn't detect this device and also i2cget can't
read from register 0x00?

 

Please suggest.

 

Regards

Seetaram


[-- Attachment #1.2: Type: text/html, Size: 4812 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Problem Configuring Micron sensor MT9D131 using i2c
       [not found] ` <1106299A6DFA0E4D8E13CFD83A7611F09E2CA1-8tR4ov5Cr7uXeP9mKtfZqKJzXdaVS04K4Jgwf8ORaLoAvxtiuMwx3w@public.gmane.org>
@ 2008-05-30 14:33   ` Wolfram Sang
  2008-05-30 20:23   ` Guennadi Liakhovetski
  1 sibling, 0 replies; 4+ messages in thread
From: Wolfram Sang @ 2008-05-30 14:33 UTC (permalink / raw)
  To: Tekkalkot, Seetaram (IE10); +Cc: i2c-GZX6beZjE8VD60Wz+7aTrA


[-- Attachment #1.1: Type: text/plain, Size: 953 bytes --]

Hi,

On Fri, May 30, 2008 at 04:36:03PM +0530, Tekkalkot, Seetaram (IE10) wrote:

> 1.	As per the datasheet the i2c read address is 0x91 and write
> address is 0x90, should I set any of these slave addresses based on
> whether I am reading or writing?
The datasheet seems obscure. An I2C-address is 7-bit and then there is a
bit stating if the access shall be r/w. Of course, together they form a
byte, but the address is 7 bit _only_ (there is a 10 bit extension, but
this exception does not apply here). So, the _address_ is 0x48.

> 2.	I am using 7 bits from 0x91 which 0x48, is this correct?
Yes.

> 3.	Why i2cdetect doesn't detect this device and also i2cget can't
> read from register 0x00?
Is there anything detected on that bus? Is there something else
connected to that bus?

All the best,

   Wolfram

-- 
  Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Problem Configuring Micron sensor MT9D131 using i2c
       [not found] ` <1106299A6DFA0E4D8E13CFD83A7611F09E2CA1-8tR4ov5Cr7uXeP9mKtfZqKJzXdaVS04K4Jgwf8ORaLoAvxtiuMwx3w@public.gmane.org>
  2008-05-30 14:33   ` Wolfram Sang
@ 2008-05-30 20:23   ` Guennadi Liakhovetski
       [not found]     ` <Pine.LNX.4.64.0805302218580.13362-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
  1 sibling, 1 reply; 4+ messages in thread
From: Guennadi Liakhovetski @ 2008-05-30 20:23 UTC (permalink / raw)
  To: Tekkalkot, Seetaram (IE10); +Cc: i2c-GZX6beZjE8VD60Wz+7aTrA

On Fri, 30 May 2008, Tekkalkot, Seetaram (IE10) wrote:

> I am trying to configure the Micron sensor MTD131 using Linux 2.6 i2c.
> 
> The sensor data sheet mentions 0x90 as the write i2c address and 0x91 as
> read i2c address.
> 
> It also mentions that, the last bit in the address is used to indicate
> read or write operation.
> 
> I am using 0x48 (0x90 shifted right once to get 7 bit i2c address) to
> detect the sensor using i2cdetect tool.
> 
> I am not able to detect this device!. I tried reading this device using
> i2cget tool but it fails to read.

I understand it is connected to a camera-host interface. Some cameras, 
including Micron cameras, do not reply to i2c commands until the camera 
interface (master clock) is activated.

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Problem Configuring Micron sensor MT9D131 using i2c
       [not found]     ` <Pine.LNX.4.64.0805302218580.13362-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
@ 2008-06-02  6:37       ` Tekkalkot, Seetaram (IE10)
  0 siblings, 0 replies; 4+ messages in thread
From: Tekkalkot, Seetaram (IE10) @ 2008-06-02  6:37 UTC (permalink / raw)
  To: Guennadi Liakhovetski; +Cc: i2c-GZX6beZjE8VD60Wz+7aTrA

Thanks for the valuable inputs.

The master clock signal is derived from within the sensor board using an
oscillator. I am getting 11.2 Mhz clock to the sensor. The host
interface includes Data lines (d0 to d7), pixel clock, line valid and
frame valid signals. All these are output signals.Currently these wires
are not connected to the host and are left open. I have only connected,
SDA, SCLk and power to the sensor board. When I run i2cdetect, some
devices on the host i2c-0 bus are getting detected at the address 0x50,
0x51 etc. But my Sensor board is not getting detected.
Please advice.

Thanks
seetaram


-----Original Message-----
From: Guennadi Liakhovetski [mailto:g.liakhovetski-Mmb7MZpHnFY@public.gmane.org] 
Sent: Saturday, May 31, 2008 1:54 AM
To: Tekkalkot, Seetaram (IE10)
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [i2c] Problem Configuring Micron sensor MT9D131 using i2c

On Fri, 30 May 2008, Tekkalkot, Seetaram (IE10) wrote:

> I am trying to configure the Micron sensor MTD131 using Linux 2.6 i2c.
> 
> The sensor data sheet mentions 0x90 as the write i2c address and 0x91
as
> read i2c address.
> 
> It also mentions that, the last bit in the address is used to indicate
> read or write operation.
> 
> I am using 0x48 (0x90 shifted right once to get 7 bit i2c address) to
> detect the sensor using i2cdetect tool.
> 
> I am not able to detect this device!. I tried reading this device
using
> i2cget tool but it fails to read.

I understand it is connected to a camera-host interface. Some cameras, 
including Micron cameras, do not reply to i2c commands until the camera 
interface (master clock) is activated.

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-06-02  6:37 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-30 11:06 Problem Configuring Micron sensor MT9D131 using i2c Tekkalkot, Seetaram (IE10)
     [not found] ` <1106299A6DFA0E4D8E13CFD83A7611F09E2CA1-8tR4ov5Cr7uXeP9mKtfZqKJzXdaVS04K4Jgwf8ORaLoAvxtiuMwx3w@public.gmane.org>
2008-05-30 14:33   ` Wolfram Sang
2008-05-30 20:23   ` Guennadi Liakhovetski
     [not found]     ` <Pine.LNX.4.64.0805302218580.13362-0199iw4Nj15frtckUFj5Ag@public.gmane.org>
2008-06-02  6:37       ` Tekkalkot, Seetaram (IE10)

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox