Write faster on AT24C32 The 2019 Stack Overflow Developer Survey Results Are InEeprom write function does not seem to write in more than 100 locationsHow do you write to a free location on an external EEPROM?Problem reading an EEPROM chip using the I2C protocolEEPROM write timeUnderstanding bitwise operationsProblems Writing and Clearing 24FC512 EEPROM using Arduino UnoWhat values are the Atmel MCUs EEPROMs preloaded with?Extending EEPROM lifeWrite to EEPROM before shutdownHow to manage variable I2C read lengths requiring address incrementation (Wire/I2C/EEPROM IC emulation)

How come people say “Would of”?

How to manage monthly salary

For what reasons would an animal species NOT cross a *horizontal* land bridge?

Should I use my personal e-mail address, or my workplace one, when registering to external websites for work purposes?

Have you ever entered Singapore using a different passport or name?

Why is my custom API endpoint not working?

What do hard-Brexiteers want with respect to the Irish border?

Worn-tile Scrabble

What is the closest word meaning "respect for time / mindful"

What are the motivations for publishing new editions of an existing textbook, beyond new discoveries in a field?

If a Druid sees an animal’s corpse, can they wild shape into that animal?

Why didn't the Event Horizon Telescope team mention Sagittarius A*?

Are there any other methods to apply to solving simultaneous equations?

Are there incongruent pythagorean triangles with the same perimeter and same area?

Who coined the term "madman theory"?

Right tool to dig six foot holes?

Falsification in Math vs Science

Is a "Democratic" Feudal System Possible?

What is the meaning of the verb "bear" in this context?

Resizing object distorts it (Illustrator CC 2018)

Are children permitted to help build the Beis Hamikdash?

Is an up-to-date browser secure on an out-of-date OS?

I see my dog run

Does the shape of a die affect the probability of a number being rolled?



Write faster on AT24C32



The 2019 Stack Overflow Developer Survey Results Are InEeprom write function does not seem to write in more than 100 locationsHow do you write to a free location on an external EEPROM?Problem reading an EEPROM chip using the I2C protocolEEPROM write timeUnderstanding bitwise operationsProblems Writing and Clearing 24FC512 EEPROM using Arduino UnoWhat values are the Atmel MCUs EEPROMs preloaded with?Extending EEPROM lifeWrite to EEPROM before shutdownHow to manage variable I2C read lengths requiring address incrementation (Wire/I2C/EEPROM IC emulation)










1















I'm using AT24C32 EEPROM chip from ATmel. I found code that will write and read bytes from chip.
Code writes and reads bytes correctly and without any problem.



But I have to write few 8-byte values often(every 10-15 seconds). I did "cut" those variables to 48 bit(so 6-byte variable) and with that I speeded up saving but it's still slow.



Is there any chance to speed up saving proccess? Code is below



void EEPROMClass::write48(int16_t address, uint64_t value)

uint8_t byteValue = (value & 0xFF);
write8(address, byteValue);

byteValue = ((value >> 8) & 0xFF);
write8(address + 1, byteValue);

byteValue = ((value >> 16) & 0xFF);
write8(address + 2, byteValue);

byteValue = ((value >> 24) & 0xFF);
write8(address + 3, byteValue);

byteValue = ((value >> 32) & 0xFF);
write8(address + 4, byteValue);

byteValue = ((value >> 40) & 0xFF);
write8(address + 5, byteValue);


void EEPROMClass::write8(int16_t const address, uint8_t const value)

Wire.beginTransmission(AT24C32);

Wire.write(highAddressByte(address));
Wire.write(lowAddressByte(address));

Wire.write(value);
delay(2);
Wire.endTransmission();



delay of 2ms is required otherwise EEPROM will write different value. Code has 4 "6-byte" variables(total of 24 bytes). Every byte is minimum 2ms, so total time to save only "6-byte" variables is 48ms(round to 50ms). That is too slow for me. How to speed up write function?










share|improve this question


























    1















    I'm using AT24C32 EEPROM chip from ATmel. I found code that will write and read bytes from chip.
    Code writes and reads bytes correctly and without any problem.



    But I have to write few 8-byte values often(every 10-15 seconds). I did "cut" those variables to 48 bit(so 6-byte variable) and with that I speeded up saving but it's still slow.



    Is there any chance to speed up saving proccess? Code is below



    void EEPROMClass::write48(int16_t address, uint64_t value)

    uint8_t byteValue = (value & 0xFF);
    write8(address, byteValue);

    byteValue = ((value >> 8) & 0xFF);
    write8(address + 1, byteValue);

    byteValue = ((value >> 16) & 0xFF);
    write8(address + 2, byteValue);

    byteValue = ((value >> 24) & 0xFF);
    write8(address + 3, byteValue);

    byteValue = ((value >> 32) & 0xFF);
    write8(address + 4, byteValue);

    byteValue = ((value >> 40) & 0xFF);
    write8(address + 5, byteValue);


    void EEPROMClass::write8(int16_t const address, uint8_t const value)

    Wire.beginTransmission(AT24C32);

    Wire.write(highAddressByte(address));
    Wire.write(lowAddressByte(address));

    Wire.write(value);
    delay(2);
    Wire.endTransmission();



    delay of 2ms is required otherwise EEPROM will write different value. Code has 4 "6-byte" variables(total of 24 bytes). Every byte is minimum 2ms, so total time to save only "6-byte" variables is 48ms(round to 50ms). That is too slow for me. How to speed up write function?










    share|improve this question
























      1












      1








      1








      I'm using AT24C32 EEPROM chip from ATmel. I found code that will write and read bytes from chip.
      Code writes and reads bytes correctly and without any problem.



      But I have to write few 8-byte values often(every 10-15 seconds). I did "cut" those variables to 48 bit(so 6-byte variable) and with that I speeded up saving but it's still slow.



      Is there any chance to speed up saving proccess? Code is below



      void EEPROMClass::write48(int16_t address, uint64_t value)

      uint8_t byteValue = (value & 0xFF);
      write8(address, byteValue);

      byteValue = ((value >> 8) & 0xFF);
      write8(address + 1, byteValue);

      byteValue = ((value >> 16) & 0xFF);
      write8(address + 2, byteValue);

      byteValue = ((value >> 24) & 0xFF);
      write8(address + 3, byteValue);

      byteValue = ((value >> 32) & 0xFF);
      write8(address + 4, byteValue);

      byteValue = ((value >> 40) & 0xFF);
      write8(address + 5, byteValue);


      void EEPROMClass::write8(int16_t const address, uint8_t const value)

      Wire.beginTransmission(AT24C32);

      Wire.write(highAddressByte(address));
      Wire.write(lowAddressByte(address));

      Wire.write(value);
      delay(2);
      Wire.endTransmission();



      delay of 2ms is required otherwise EEPROM will write different value. Code has 4 "6-byte" variables(total of 24 bytes). Every byte is minimum 2ms, so total time to save only "6-byte" variables is 48ms(round to 50ms). That is too slow for me. How to speed up write function?










      share|improve this question














      I'm using AT24C32 EEPROM chip from ATmel. I found code that will write and read bytes from chip.
      Code writes and reads bytes correctly and without any problem.



      But I have to write few 8-byte values often(every 10-15 seconds). I did "cut" those variables to 48 bit(so 6-byte variable) and with that I speeded up saving but it's still slow.



      Is there any chance to speed up saving proccess? Code is below



      void EEPROMClass::write48(int16_t address, uint64_t value)

      uint8_t byteValue = (value & 0xFF);
      write8(address, byteValue);

      byteValue = ((value >> 8) & 0xFF);
      write8(address + 1, byteValue);

      byteValue = ((value >> 16) & 0xFF);
      write8(address + 2, byteValue);

      byteValue = ((value >> 24) & 0xFF);
      write8(address + 3, byteValue);

      byteValue = ((value >> 32) & 0xFF);
      write8(address + 4, byteValue);

      byteValue = ((value >> 40) & 0xFF);
      write8(address + 5, byteValue);


      void EEPROMClass::write8(int16_t const address, uint8_t const value)

      Wire.beginTransmission(AT24C32);

      Wire.write(highAddressByte(address));
      Wire.write(lowAddressByte(address));

      Wire.write(value);
      delay(2);
      Wire.endTransmission();



      delay of 2ms is required otherwise EEPROM will write different value. Code has 4 "6-byte" variables(total of 24 bytes). Every byte is minimum 2ms, so total time to save only "6-byte" variables is 48ms(round to 50ms). That is too slow for me. How to speed up write function?







      eeprom






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 3 hours ago









      SilvioCroSilvioCro

      817




      817




















          2 Answers
          2






          active

          oldest

          votes


















          2














          after writing a value to EEPROM, and terminating the I2C connection with a STOP, the EEPROM enters a self writing mode to write what you have sent to it, to it's internal memory. (you don't actually write the values to the memory section; you write them to a buffer, and then the internal controller writes them to its memory section).



          this "self writing mode" takes about 5ms, and you cant do anything about it. but you can use "page writing" instead of byte writing. that 32K model, has a 32 bytes page buffer. you have to send all the bytes (as long as they are under 32 bytes) at once in one I2C transaction. this time, the chip fills its page buffer and then after a STOP, writes it all at once on its memory. in your code, you just write one byte in your buffer each time in a single transaction. like sending a bus with just one passenger at a time.



          remember in this mode, you only set the address of the first byte. the next bytes automatically settle in the next addresses.






          share|improve this answer






























            1














            Mostly the best speed you get, is if you use the 'page' size, which is 32 bytes. It will take longer than 4 bytes, but less then 4 times 8 bytes.



            You could do a check to see if using one page write (of 32 bytes) is faster than 6 times a one byte write.



            However, it depends if you can change your design so it writes 32 bytes at a time.
            E.g. by writing 60 seconds 4 times 8 bytes (32 bytes) in one page write, instead of every 15 seconds 8 bytes. This will be much faster.






            share|improve this answer























              Your Answer






              StackExchange.ifUsing("editor", function ()
              return StackExchange.using("schematics", function ()
              StackExchange.schematics.init();
              );
              , "cicuitlab");

              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "540"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: false,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2farduino.stackexchange.com%2fquestions%2f63364%2fwrite-faster-on-at24c32%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              2














              after writing a value to EEPROM, and terminating the I2C connection with a STOP, the EEPROM enters a self writing mode to write what you have sent to it, to it's internal memory. (you don't actually write the values to the memory section; you write them to a buffer, and then the internal controller writes them to its memory section).



              this "self writing mode" takes about 5ms, and you cant do anything about it. but you can use "page writing" instead of byte writing. that 32K model, has a 32 bytes page buffer. you have to send all the bytes (as long as they are under 32 bytes) at once in one I2C transaction. this time, the chip fills its page buffer and then after a STOP, writes it all at once on its memory. in your code, you just write one byte in your buffer each time in a single transaction. like sending a bus with just one passenger at a time.



              remember in this mode, you only set the address of the first byte. the next bytes automatically settle in the next addresses.






              share|improve this answer



























                2














                after writing a value to EEPROM, and terminating the I2C connection with a STOP, the EEPROM enters a self writing mode to write what you have sent to it, to it's internal memory. (you don't actually write the values to the memory section; you write them to a buffer, and then the internal controller writes them to its memory section).



                this "self writing mode" takes about 5ms, and you cant do anything about it. but you can use "page writing" instead of byte writing. that 32K model, has a 32 bytes page buffer. you have to send all the bytes (as long as they are under 32 bytes) at once in one I2C transaction. this time, the chip fills its page buffer and then after a STOP, writes it all at once on its memory. in your code, you just write one byte in your buffer each time in a single transaction. like sending a bus with just one passenger at a time.



                remember in this mode, you only set the address of the first byte. the next bytes automatically settle in the next addresses.






                share|improve this answer

























                  2












                  2








                  2







                  after writing a value to EEPROM, and terminating the I2C connection with a STOP, the EEPROM enters a self writing mode to write what you have sent to it, to it's internal memory. (you don't actually write the values to the memory section; you write them to a buffer, and then the internal controller writes them to its memory section).



                  this "self writing mode" takes about 5ms, and you cant do anything about it. but you can use "page writing" instead of byte writing. that 32K model, has a 32 bytes page buffer. you have to send all the bytes (as long as they are under 32 bytes) at once in one I2C transaction. this time, the chip fills its page buffer and then after a STOP, writes it all at once on its memory. in your code, you just write one byte in your buffer each time in a single transaction. like sending a bus with just one passenger at a time.



                  remember in this mode, you only set the address of the first byte. the next bytes automatically settle in the next addresses.






                  share|improve this answer













                  after writing a value to EEPROM, and terminating the I2C connection with a STOP, the EEPROM enters a self writing mode to write what you have sent to it, to it's internal memory. (you don't actually write the values to the memory section; you write them to a buffer, and then the internal controller writes them to its memory section).



                  this "self writing mode" takes about 5ms, and you cant do anything about it. but you can use "page writing" instead of byte writing. that 32K model, has a 32 bytes page buffer. you have to send all the bytes (as long as they are under 32 bytes) at once in one I2C transaction. this time, the chip fills its page buffer and then after a STOP, writes it all at once on its memory. in your code, you just write one byte in your buffer each time in a single transaction. like sending a bus with just one passenger at a time.



                  remember in this mode, you only set the address of the first byte. the next bytes automatically settle in the next addresses.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 2 hours ago









                  Tirdad Sadri NejadTirdad Sadri Nejad

                  1512




                  1512





















                      1














                      Mostly the best speed you get, is if you use the 'page' size, which is 32 bytes. It will take longer than 4 bytes, but less then 4 times 8 bytes.



                      You could do a check to see if using one page write (of 32 bytes) is faster than 6 times a one byte write.



                      However, it depends if you can change your design so it writes 32 bytes at a time.
                      E.g. by writing 60 seconds 4 times 8 bytes (32 bytes) in one page write, instead of every 15 seconds 8 bytes. This will be much faster.






                      share|improve this answer



























                        1














                        Mostly the best speed you get, is if you use the 'page' size, which is 32 bytes. It will take longer than 4 bytes, but less then 4 times 8 bytes.



                        You could do a check to see if using one page write (of 32 bytes) is faster than 6 times a one byte write.



                        However, it depends if you can change your design so it writes 32 bytes at a time.
                        E.g. by writing 60 seconds 4 times 8 bytes (32 bytes) in one page write, instead of every 15 seconds 8 bytes. This will be much faster.






                        share|improve this answer

























                          1












                          1








                          1







                          Mostly the best speed you get, is if you use the 'page' size, which is 32 bytes. It will take longer than 4 bytes, but less then 4 times 8 bytes.



                          You could do a check to see if using one page write (of 32 bytes) is faster than 6 times a one byte write.



                          However, it depends if you can change your design so it writes 32 bytes at a time.
                          E.g. by writing 60 seconds 4 times 8 bytes (32 bytes) in one page write, instead of every 15 seconds 8 bytes. This will be much faster.






                          share|improve this answer













                          Mostly the best speed you get, is if you use the 'page' size, which is 32 bytes. It will take longer than 4 bytes, but less then 4 times 8 bytes.



                          You could do a check to see if using one page write (of 32 bytes) is faster than 6 times a one byte write.



                          However, it depends if you can change your design so it writes 32 bytes at a time.
                          E.g. by writing 60 seconds 4 times 8 bytes (32 bytes) in one page write, instead of every 15 seconds 8 bytes. This will be much faster.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered 2 hours ago









                          Michel KeijzersMichel Keijzers

                          6,97251939




                          6,97251939



























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Arduino Stack Exchange!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2farduino.stackexchange.com%2fquestions%2f63364%2fwrite-faster-on-at24c32%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Are there any comparative studies done between Ashtavakra Gita and Buddhim?How is it wrong to believe that a self exists, or that it doesn't?Can you criticise or improve Ven. Bodhi's description of MahayanaWas the doctrine of 'Anatta', accepted as doctrine by modern Buddhism, actually taught by the Buddha?Relationship between Buddhism, Hinduism and Yoga?Comparison of Nirvana, Tao and Brahman/AtmaIs there a distinction between “ego identity” and “craving/hating”?Are there many differences between Taoism and Buddhism?Loss of “faith” in buddhismSimilarity between creation in Abrahamic religions and beginning of life in Earth mentioned Agganna Sutta?Are there studies about the difference between meditating in the morning versus in the evening?Can one follow Hinduism and Buddhism at the same time?Are there any prohibitions on participating in other religion's practices?Psychology of 'flow'

                              fallocate: fallocate failed: Text file busy in Ubuntu 17.04? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)defragmenting and increasing performance of old lubuntu system with swap partitionIssue with increasing the root partition from the swapthis /usr/bin/dpkg returned error || ubuntu-16.04, 64bitDefault 17.04 swap file locationHow to Resize Ubuntu 17.04 Zesty Swap file size?Ubuntu freezes from online formsMy Laptop is not starting after upgrade ubuntu 16.04 (Kernel 4.8.0-38 to 04.10.0-36)hcp: ERROR: FALLOCATE FAILED!Not sure my swap is being usedWine 3.0 asking for more virtual free swap

                              Where else does the Shulchan Aruch quote an authority by name?Parashat Metzora+HagadolPesach/PassoverShulchan Aruch UTF-8Anonymous glosses in the Shulchan AruchWhy is the Shulchan Aruch definitive?Siman 32, Kitzur Shulchan Aruch: UntranslatedLitvaks/Yeshivish and Shulchan AruchBuying a Shulchan AruchEnglish version of SHULCHAN ARUCHIs there any place where Shulchan Aruch rules with the Rosh against the Rif and Rambam?Are there practices where Sepharadim do not hold by Shulchan Aruch?5th part of the shulchan aruch