This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: AT91SAM and I2C
- From: "Laurie Gellatly" <laurie dot gellatly at netic dot com>
- To: "Andrew Lunn" <andrew at lunn dot ch>, "Jan Jacobs" <hpjcon at mweb dot co dot za>
- Cc: <ecos-discuss at ecos dot sourceware dot org>
- Date: Mon, 7 Jan 2008 08:28:01 +1100
- Subject: RE: [ECOS] AT91SAM and I2C
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org]On Behalf Of Andrew Lunn
Sent: Monday, 7 January 2008 8:12 AM
To: Jan Jacobs
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] AT91SAM and I2C
On Sun, Jan 06, 2008 at 11:01:51PM +0200, Jan Jacobs wrote:
> Hi All,
>
> I need an I2C (TWI) driver for the AT91SAM7X. I have started doing
> something, but want to find out if somebody has done one or has any
advice?
>I think somebody is working on such a driver. It was mentioned last
>month. Take a look in the mail archive.
> Secondly, I think there might be a flaw with the I2C IO package.
> If the device you communication to does not use internal addressing (RTC,
> Sensor, etc) then the I2C IO API works.
> If the device requires internal addressing (EEPROM) I do not see how that
> gets conveyed via the I2C IO API?
>I don't really follow. Do you want to make it look like the EEPROM is
>memory mapped?
Jan,
When you talk to a EEPROM then part of the I2C message is a command followed
by the memory address then the data is exchanged all across teh I2C bus.
You should see this in the Datasheet.
(apologies for duplicate message Andrew).
...Laurie:{)
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss