All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Cole <clecol-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: i2cset question
Date: Fri, 17 Apr 2009 12:23:58 -0400	[thread overview]
Message-ID: <49E8AD1E.1070805@gmail.com> (raw)
In-Reply-To: <20090417174845.471d4d9d-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>

> You are very lucky that you didn't write to a byte location < 0x40,
> that would have broken the checksum and you would no longer be able to
> boot your system.
> 
> I encourage you to restore the value of byte 0x50 to what it originally
> was and never ever again touch this SPD EEPROM.
> 
> The "readback failed" warning is presumably because it takes some time
> to the EEPROM to write the new data and in the meantime you can't read
> from it.
> 
> The MAX5434L has I2C address 0x28 or 0x29. It doesn't show on
> i2cdetect. Check whether it's properly soldered. If it is, try i2cget
> instead of i2cdetect, maybe the Maxim chip doesn't like the probes
> i2cdetect does.
> 

Ok, I think we were getting confused about the MAX45434L data sheet 
addressing and thought the address of 0x50 corresponded to the chip. I 
now see that the address should be 0x28, however I know it's soldered 
properly and I still can't see it with i2cget...am I dead in the water 
or is there possibly another way to approach this?

Thanks,
   Chris

  parent reply	other threads:[~2009-04-17 16:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 14:33 i2cset question Chris Cole
     [not found] ` <49E89342.1010807-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-04-17 15:48   ` Jean Delvare
     [not found]     ` <20090417174845.471d4d9d-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-04-17 16:23       ` Chris Cole [this message]
     [not found]         ` <49E8AD1E.1070805-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-04-17 16:33           ` Jean Delvare
2012-10-17 12:07     ` Javi
     [not found]       ` <loom.20121017T134619-899-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2012-10-17 12:43         ` Jean Delvare

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=49E8AD1E.1070805@gmail.com \
    --to=clecol-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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 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.