All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Krause <Martin.Krause@tqs.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] IXP and I2C - support
Date: Fri, 2 Mar 2007 08:53:41 +0100	[thread overview]
Message-ID: <47F3F98010FF784EBEE6526EAAB078D1024F8466@tq-mailsrv.tq-net.de> (raw)
In-Reply-To: <20070302070527.GA10206@takaisin.fi>

Hi Teemu,

madcat at takaisin.fi wrote on Friday, March 02, 2007 8:05 AM: 
> Iprobe - gets the addresses pretty much what it supposed to be, but
> the 
> problem is the reading with imd -command. Some times the command seems
> to be working almost fine. Some times the results are difrerent every
> time I read the chip when it should be the same since I'm trying to
> read a chip that has constant data(for example eeprom). Most of the
> time 
> not all the data is read. Maybe first 3-4 bytes are ok and rest of the
> bytes are either 00 or ff.
> 
> Should I somehow reset the I2C-bus, am I doing something wrong or
> maybe 
> there is some configuration error or maybe even a bug in a code?!

Msybe you are using the wrong number of address bytes when accessing 
your I2C device. It depends on your device, how many address bytes are
needed (0, 1 or 2 bytes). The number of address bytes is specified
by a "." and the desired number directly after "address" in the imd
command:

# help imd
imd chip address[.0, .1, .2] [# of objects]
    - i2c memory display

Example (read 0x10 bytes from an EEPROM with the I2C address 0x54,
beginning at offset 0 and using one address byte):

# imd 54 0.1 10
0000: 51 2d 02 00 61 02 00 00 c9 b6 35 01 df 32 89 45    Q-..a.....5..2.E

Regards,
Martin

  reply	other threads:[~2007-03-02  7:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 15:20 [U-Boot-Users] IXP and I2C - support Martijn de Gouw
2007-03-02  7:05 ` madcat at takaisin.fi
2007-03-02  7:53   ` Martin Krause [this message]
2007-03-02  8:18     ` madcat at takaisin.fi
  -- strict thread matches above, loose matches on Subject: below --
2007-03-01 12:51 madcat at takaisin.fi

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=47F3F98010FF784EBEE6526EAAB078D1024F8466@tq-mailsrv.tq-net.de \
    --to=martin.krause@tqs.de \
    --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.