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.
1) LM4F120H5QR ROM USER'S GUIDE ROM-LM4F120H5QR-UG-730 suggests to define TARGET_IS_BLIZZARD_RA1, which causes the rom.h from TivaWare 1.0 NOT to export any EEPROM API functions.
2) Tiva" TM4C1233H6PM ROM USER’S GUIDE ROM-TM4C1233H6PM-UG-750 suggests to define TARGET_IS_BLIZZARD_RB1, which causes the rom.h from TivaWare 1.0 to export EEPROM API functions. However, the TM4C1233H6PM ROM user''s guide doesn't document any EEPROM functions.
(where the TM4C1233H6PM should be identical to the LM4F120H5QR)
3) Looking in the ROM table for an example LM4F120H5QR Rev A3 shows EEPROM functions and:
- Calling ROM_EEPROMSizeGet returns the expected value of 2048.
- Calling ROM_EEPROMBlockCountGet returns the expected value of 32.
My questions are:
a) When compiling for a LM4F120H5QR should TARGET_IS_BLIZZARD_RA1 or TARGET_IS_BLIZZARD_RB1 be defined?
b) Should the ROM EEPROM functions be described as supported in the LM4F120H5QR and/or TM4C1233H6PM ROM user guides?
Chester Gillon When compiling for a LM4F120H5QR should TARGET_IS_BLIZZARD_RA1 or TARGET_IS_BLIZZARD_RB1 be defined?
However, the TivaWare 1.0 user's guide doesn't appear to have an up to date list of the defines expected by driverlib/rom.h since section 29.2 lists the following macros:
Whereas the list of defines expected by the TivaWare 1.0 driverlib/rom.h are actually:
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Chester Gillon:
For the TM4C123GH6PGE MCU, which Blizzard class should be designated? And where is this list? All previously listed links are BROKEN!!!
In reply to Evelyn Sabbag1:
When using TM4C123 or LM4F please check the SYSCTL.DID0 register at address 0x400FE000
This is mentioned in the Data Sheet as well for the description of the above register.
If the value shows 0x18050001: The last byte which shows 01 and byte before it shows 00 means RA1
If the value shows 0x18050101: The last byte which shows 01 and byte before it shows 01 means RB1
In reply to Amit Ashara:
In reply to Joseph Forrest:
Holy Zombie Thread!
In reply to Robert Adsett:
Sure it's a "Zombie" - yet it's a Zombie w/terrific search/find capability. Where's Buffy when we need her?
(if not, "Best Tag ever - damn close!) Or you can bore us to death w/vendor's part number...
In reply to cb1:
Robert AdsettSomeone from xyz should have an answer.
If they don't - may we drive a stake thru this Franken-post?
In reply to cb1_mobile:
Sounds (exactly) like (another) day in Margaritaville...
Recall - we exhausted the torches - last "eclipse viewing..." I've several hundred "Stellaris match books" left over (they had "flash" issues) - might they do?
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.