• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 30 subscribers
  • Views 523 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Does the Battery Backed RAM in TM4C129ENCPDTI3's Hibernate Module have an infinite number of writes?

Bill Sousan
Intellectual 380 points


We want to store key data in the battery backed RAM in the TM4C129ENCPDTI3's hibernate module.  Does this memory have a finite number of writes similar to Flash memory, or is it like RAM where there is an infinite number of writes?

Thanks,

Bill

  • 0
    Guru 27285 points

     Battery backed ram is an USUAL low power static ram not flash so ram I don't know it wear out.

  • 0
    Guru 117855 points

    Bill Sousan said:
    ...is it like RAM where there is an infinite number of writes?

    In general agree w/poster Roberto - yet does not this detail reside w/in MCU manual - buried deep in the cheap seats?  (MCU electrical specs - usually organized/grouped by MCU peripheral - found at the very end of the manual) 

    Expect to see voltage minimums, current requirements, and (one hopes) any such usage restrictions/limitations/life issues...

    Final point - modern MCUs have vastly expanded number of Flash writes - unless your application is, "machine gunning" such "key data" during "live" operation - it seems Flash will provide an acceptable alternative.

  • 0 in reply to cb1_mobile
    TI__Guru**** 244400 points

    Hello All

    My 2 cents on the topic: The Key data if critical must not be stored on something accessible like the Battery backed RAM, but on the EEPROM which can be secured using Password.

    Other than that Roberto and cb1, thanks.

    Regards

    Amit

  • 0 in reply to Amit Ashara
    Guru 117855 points

    What if that "key data" is to be, "Quickly Saved?"  Would use of the "password" and access time penalties incurred by EEPROM prove ideal?

    The use and activity of such "key data" may dictate poster's "best handling" of such "key data."  A "universal approach" may not satisfy all masters...

  • 0 in reply to cb1_mobile
    TI__Guru**** 244400 points

    Hello cb1

    Yes, indeed if it needs to be quickly saved, then BBRAM is a good place, but then the "key" is very loosely defined as well. Is this some encryption/decryption key or a important variable value to be used key.

    Regards

    Amit

  • 0 in reply to Amit Ashara
    Intellectual 380 points

    Yes in my case it needs to be quickly saved and saved often (and is only 32 bytes long).  "Key" data refers to data that needs to be saved - but not encrypted/secure.  So for my app, I think the battery backed RAM makes sense.


    Thanks for your insight,

    Best,

    Bill

  • 0 in reply to Bill Sousan
    TI__Guru**** 244400 points

    Thanks to cb1 for bringing up the topic as well with a well considered view

    Regards

    Amit

  • 0 in reply to Amit Ashara
    Guru 117855 points

    Thanks for that kind mention, Amit.

    Many years in the MCU, FPGA, & memory trenches leads to a, "bigger picture" view.  It's (often) necessary to tease out poster's real application - even when that may reduce or eliminate the full recitation (and use) of all MCU features.

    Indeed the MCU's EEPROM adds value - yet the whole of the application must always be fully/properly considered - only then is the best/most appropriate MCU feature-handling revealed.