From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: "Tekkalkot,
Seetaram (IE10)"
<Seetaram.Tekkalkot-TF0kVB3jB5US+FvcfC7Uqw@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: Problem Configuring Micron sensor MT9D131 using i2c
Date: Fri, 30 May 2008 16:33:22 +0200 [thread overview]
Message-ID: <20080530143322.GA4872@pengutronix.de> (raw)
In-Reply-To: <1106299A6DFA0E4D8E13CFD83A7611F09E2CA1-8tR4ov5Cr7uXeP9mKtfZqKJzXdaVS04K4Jgwf8ORaLoAvxtiuMwx3w@public.gmane.org>
[-- 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
next prev parent reply other threads:[~2008-05-30 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080530143322.GA4872@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=Seetaram.Tekkalkot-TF0kVB3jB5US+FvcfC7Uqw@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox