Difference between revisions of "Talk:Embedded Open Modular Architecture/EOMA68"
(→Alternative layout) |
|||
Line 1: | Line 1: | ||
− | = | + | = Confusion over definition of I2C Addresses = |
− | + | There has been considerable confusion even when developing the EOMA68 specification, after finding datasheets that do not correctly describe their addresses. The confusion stems from treating the first 8 bits as an 8-bit number (MSB first) and many datasheets - including that of the recommended part for the I2C EEPROM AT24C64) - propagate this confusion in ''direct'' violation of the I2C specification. | |
− | + | To correctly identify an I2C address, the first 7 bits must be treated as a 7-bit decimal number (MSB first). The 8th bit is a read-write indicator. Many datasheets '''incorrectly''' report two separate I2C "addresses", one is double that of the correct address and the other is double plus one. | |
− | + | '''Please ensure when complying with the EOMA68 specification that an EEPROM with the correct I2C address of 0x51 rather than 0xA2 and 0xA3 are used.''' | |
− | + | <pre> | |
− | + | > so what you're saying is that just because (if you were reading the 8 | |
− | + | > bits in sequence), the bit that comes *after* the I2Caddress (its LSB) | |
− | + | > is in the place that, if it *was* an 8-bit address, you'd call it bit | |
− | + | > 0. but you should never consider this to be so, instead should read | |
− | + | > the 7 bits only then treat the 8th bit as completely separate, right? | |
− | + | > | |
− | + | > so that would explain how i managed to read 0xA2 as being the I2C | |
− | + | > EEPROM read address and 0xA3 as the I2C EEPROM write address, when in | |
− | + | > fact they're *both* 0x51 and the R/W bit has absolutely nothing to do | |
− | + | > with the actual address, would that be right? | |
− | + | ||
− | + | Yes. I don't remember where I had read that, but somehow I remembered | |
− | + | that, to not be too surprised to hit actual cases of such confusion few | |
− | + | times later. I didn't really do my own due diligence, but good chance | |
− | + | to do it now. So, wikipedia https://en.wikipedia.org/wiki/I%C2%B2C | |
− | + | links to "Official I2C Specification, NXP" | |
− | + | http://www.nxp.com/documents/user_manual/UM10204.pdf . That clearly | |
− | + | states in section 3.1.10 that "This address is seven bits long | |
− | + | followed by an eighth bit which is a data direction bit (R/W)". | |
− | + | Googling for "i2c address confusion" in particular finds | |
− | + | http://www.totalphase.com/support/kb/10039/ which goes over 7/8 bit | |
− | + | confusion and which one is correct. | |
− | + | </pre> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 06:32, 11 October 2013
Confusion over definition of I2C Addresses
There has been considerable confusion even when developing the EOMA68 specification, after finding datasheets that do not correctly describe their addresses. The confusion stems from treating the first 8 bits as an 8-bit number (MSB first) and many datasheets - including that of the recommended part for the I2C EEPROM AT24C64) - propagate this confusion in direct violation of the I2C specification.
To correctly identify an I2C address, the first 7 bits must be treated as a 7-bit decimal number (MSB first). The 8th bit is a read-write indicator. Many datasheets incorrectly report two separate I2C "addresses", one is double that of the correct address and the other is double plus one.
Please ensure when complying with the EOMA68 specification that an EEPROM with the correct I2C address of 0x51 rather than 0xA2 and 0xA3 are used.
> so what you're saying is that just because (if you were reading the 8 > bits in sequence), the bit that comes *after* the I2Caddress (its LSB) > is in the place that, if it *was* an 8-bit address, you'd call it bit > 0. but you should never consider this to be so, instead should read > the 7 bits only then treat the 8th bit as completely separate, right? > > so that would explain how i managed to read 0xA2 as being the I2C > EEPROM read address and 0xA3 as the I2C EEPROM write address, when in > fact they're *both* 0x51 and the R/W bit has absolutely nothing to do > with the actual address, would that be right? Yes. I don't remember where I had read that, but somehow I remembered that, to not be too surprised to hit actual cases of such confusion few times later. I didn't really do my own due diligence, but good chance to do it now. So, wikipedia https://en.wikipedia.org/wiki/I%C2%B2C links to "Official I2C Specification, NXP" http://www.nxp.com/documents/user_manual/UM10204.pdf . That clearly states in section 3.1.10 that "This address is seven bits long followed by an eighth bit which is a data direction bit (R/W)". Googling for "i2c address confusion" in particular finds http://www.totalphase.com/support/kb/10039/ which goes over 7/8 bit confusion and which one is correct.