From: David A. Peters <davidp@matrixproductdev.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] soft or hard I2C code for AT91RM9200?
Date: Wed, 15 Sep 2004 09:06:43 -0500 [thread overview]
Message-ID: <FKEPIFNIDACFCCPMHMNPIEDKGHAA.davidp@matrixproductdev.com> (raw)
In-Reply-To: <FKEPIFNIDACFCCPMHMNPGEDCGHAA.davidp@matrixproductdev.com>
I have the soft I2C working except for one small problem. When I try to
read more than 2 bytes from the eeprom, I get the first two bytes, and
anything else that follows is 0xFF. I've verified that data is written to
the eeprom in other locations. I am using a 24AA256.
Has anyone else seen this problem?
-----Original Message-----
From: u-boot-users-admin@lists.sourceforge.net
[mailto:u-boot-users-admin at lists.sourceforge.net]On Behalf Of David A.
Peters
Sent: Tuesday, September 14, 2004 3:10 PM
To: U-Boot Users List
Subject: [U-Boot-Users] soft or hard I2C code for AT91RM9200?
Does anyone have I2C code for the AT92RM9200 that they would be willing to
share? I am trying to get the soft I2C working, but I am struggling.
Thank you!
-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users
next prev parent reply other threads:[~2004-09-15 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 20:10 [U-Boot-Users] soft or hard I2C code for AT91RM9200? David A. Peters
2004-09-15 14:06 ` David A. Peters [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-15 14:47 VanBaren, Gerald
2004-09-15 18:29 ` David A. Peters
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=FKEPIFNIDACFCCPMHMNPIEDKGHAA.davidp@matrixproductdev.com \
--to=davidp@matrixproductdev.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.