• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 578 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.

TM4C123GH6PM: Internal EEPROM bare metal driver

user5175619
Intellectual 310 points
Part Number: TM4C123GH6PM

Hello, so I've been trying to find any source to understand the order and the way of writing bare-metal driver for accessing,reading,writing to and from the internal EEPROM but didn't find.

at least if someone can guide me what is the way to do so, I've the data sheet and I was reading register functions but I don't understand the order or what to do on what time.

  • 0
    Guru 117855 points

    May it be asked why you'd, "Even want to attempt such a project?"    The EEProm is especially complex - and HAS noted Errata - and "Just as you cleverly note" - the "Order of operations" proves "key/critical."

    And "All of that" has been handled for you - via the API.

    A "mistake" in this area (may) have lasting repercussions - should you,  "Invite such RISK?"      And if so - to what purpose?

    Pardon - but it would seem a far better & more productive - "Use of Your Valued Time" - to attack  "other areas."    (it would prove of interest to "Learn your motivation (for such choice)"  - yet STILL ...  myself (and I would bet heavily) Vendor Agents - would "Second" this advice...)

  • 0
    TI__Guru 72500 points

    Please look at the TivaWare library functions for EEPROM emulation. Once installed, you will find the functions described in section 9 of the User's Guide at: C:\ti\TivaWare_C_Series-2.1.4.178\docs\SW-TM4C-DRL-UG-2.1.4.178.pdf. The source for these functions is in the file: C:\ti\TivaWare_C_Series-2.1.4.178\driverlib\eeprom.c

  • 0 in reply to cb1_mobile
    Intellectual 310 points

    hi
    1- so I am working with a team for a proof of concept and we already built a big system by our own and now we are stuck at this point. I can't use Tivaware now after 3 months of programming, maybe in next project.
    Also in my region at least it's a prerequisite to have deep understanding to work in embedded industry so I got used to do that since 1.5 year ago. u can say I'm low layer embedded programmer.

    2- so what repercussions are you talking about? you mean permanently ? even if I reset the MCU?

    3-so what other areas I can hit to benefit the most out of my time?

    4- Excuse me but is the errata different from the TM4C123GH6 data sheet?

  • 0 in reply to Bob Crosby
    Intellectual 310 points
    Thanks Bob, I already checked it earlier but I thought I would have a better source to back me up with theory. actually it will long to move the chunk I need from eeprom.c to my keil project.

    I've another question : Why is the data sheet not clear about this part? for example SPI is explained by order and everything in data sheet. and how did the people who designed eeprom.c write the driver library?
  • 0 in reply to user5175619
    Guru 117855 points

    Should you employ the API - and review the pertinent MCU Registers - it is my (proven) belief that you'll gain a (similar or superior) "Deep Understanding."    And - importantly - not "take forever" in its accomplishment.

    I too - "Work in the embedded industry - and managed to co-found - then take a tech firm PUBLIC - without being a great "low-level" guy!      Instead I aimed to become  a, "Deadline Meeting & Effectively Deploying" guy!     Thus (your) idea of  "prerequisite" appears NOT to match mine...    (and a "Prancing Horse" ... resides my garage)

    To repercussions - should your "exhaustive, self-developed technique" fail sufficiently - you may (seriously) degrade the "EEProm Region" of the MCU's Flash Memory.    (on occasion - even greater horrors may result.)

    Would your "Low Level Desires" be better served - by your employ of a, "Task Proven - external,  (i.e. REAL EEprom?")     You will note that the MCU's version - proves highly demanding and  (VERY) SLOW!    (Might the "demands" of the Low Level - have obscured - that ready fact?     We note that "obscuring" - to so often - prove the case!)

    Firm/I generally realize our greatest success by focusing upon the "Competitive Advantages" which we can create - with the investment of  "reasonable:  Funds,  Time &  Effort."     (which only rarely - results from extensive, "low level" ONLY focus.)     As we "Raise Funds for other Tech Biz - & Start-Ups" - we  KNOW  this to prove true.    (simply consult your nearest VC...)

    You must have noted that the "Race is to the Swift" - and he, "Arriving to Market EARLY" - realizes BY FAR the HIGHEST PROFIT MARGINS!    (those - greatly slowed - and rendered "uncertain" - by  "Low Level Obsession" - may NEVER reach the market - or arrive SO LATE - that profit opportunities prove meager!   ... If any...)

    Errata issues are best answered by Vendor Staff...