Re: i2cset question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux GPIO]     [Linux SPI]     [Linux Hardward Monitoring]     [LM Sensors]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux