• State Verified Answer
  • Replies 3 replies
  • Subscribers 75 subscribers
  • Views 739 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 314471
Options

I2C how to check device readiness?

MrHarmonSr

I am using code from nRF5_SDK_17.1.0\examples\peripheral\twi_master_with_twis_slave for accessing an EEPROM.  The code seemed to work fine for a 24c512.
I am now trying to use it with a 24c64 device and I am running into issues!!!  Data seems to wrap at 32 bytes, the page size

The code comment says " * @attention If you wish to communicate with real EEPROM memory chip, check its readiness
* after writing the data."

What does this mean?  Does this translate into an nrf_twi_xxx function call??

Parents
  • 0

    Hi 

    You can find the 24c64 datasheet here. It is correct that it has a page size of 32 bytes, meaning you can only read or write 32 bytes in each transaction. 

    The 24c512 for comparison has 128 byte pages, and will allow longer transactions. 

    The code comment says " * @attention If you wish to communicate with real EEPROM memory chip, check its readiness
    * after writing the data."

    Write and erase operations are generally slow for flash memory devices, and after performing one of these operations you need to check the status of the device before issuing more commands. 

    Many flash devices allow you to read out a status register, which indicates whether or not the device is busy executing a write or erase. 

    Apparently the 24C series don't have any status registers to read, but I found the following statement in the datasheet:

    BYTE WRITE: A write operation requires two 8-bit data word addresses following the device address word and acknowledgment. Upon receipt of this address, the EEPROM will again respond with a zero and then clock in the first 8-bit data word. Following receipt of the 8-bit data word, the EEPROM will output a zero and the addressing device, such as a microcontroller, must terminate the write sequence with a stop condition. At this time the EEPROM enters an internally-timed write cycle, tWR, to the nonvolatile memory. All inputs are disabled during this write cycle and the EEPROM will not respond until the write is complete (refer to Figure 2).

    In other words you should get a NACK on the I2C bus if you try to issue more commands while the previous command is being executed. 

    Best regards
    Torbjørn

Reply
  • 0

    Hi 

    You can find the 24c64 datasheet here. It is correct that it has a page size of 32 bytes, meaning you can only read or write 32 bytes in each transaction. 

    The 24c512 for comparison has 128 byte pages, and will allow longer transactions. 

    The code comment says " * @attention If you wish to communicate with real EEPROM memory chip, check its readiness
    * after writing the data."

    Write and erase operations are generally slow for flash memory devices, and after performing one of these operations you need to check the status of the device before issuing more commands. 

    Many flash devices allow you to read out a status register, which indicates whether or not the device is busy executing a write or erase. 

    Apparently the 24C series don't have any status registers to read, but I found the following statement in the datasheet:

    BYTE WRITE: A write operation requires two 8-bit data word addresses following the device address word and acknowledgment. Upon receipt of this address, the EEPROM will again respond with a zero and then clock in the first 8-bit data word. Following receipt of the 8-bit data word, the EEPROM will output a zero and the addressing device, such as a microcontroller, must terminate the write sequence with a stop condition. At this time the EEPROM enters an internally-timed write cycle, tWR, to the nonvolatile memory. All inputs are disabled during this write cycle and the EEPROM will not respond until the write is complete (refer to Figure 2).

    In other words you should get a NACK on the I2C bus if you try to issue more commands while the previous command is being executed. 

    Best regards
    Torbjørn

Children
Related
Terms of service