Descripancies in ROM support for EEPROM functions

Chester Gillon

Other Parts Discussed in Thread: TM4C1233H6PM, TM4C123GH6PGE, TM4C123GH6PM

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?

over 10 years ago

0 Chester Gillon over 10 years ago

Guru 92251 points

Chester Gillon said:
When compiling for a LM4F120H5QR should TARGET_IS_BLIZZARD_RA1 or TARGET_IS_BLIZZARD_RB1 be defined?

The ROM users guides didn't make it clear the significance of the suffix for the TARGET_IS_BLIZZARD macros. The "Using the ROM" section of the TivaWare™ Peripheral Driver Library USER’S GUIDE SW-DRL-UG-1.0 clarifies that the suffix represents the silicon revision targetted. i.e. for a LM4F120H5QR rev A3 this means TARGET_IS_BLIZZARD_RA3 should 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:

- TARGET_IS_DUSTDEVIL_RA0

- TARGET_IS_TEMPEST_RB1

- TARGET_IS_TEMPEST_RC1

- TARGET_IS_TEMPEST_RC3

- TARGET_IS_TEMPEST_RC5

- TARGET_IS_FIRESTORM_RA2

- TARGET_IS_BLIZZARD_RA1

Whereas the list of defines expected by the TivaWare 1.0 driverlib/rom.h are actually:

- TARGET_IS_BLIZZARD_RA1

- TARGET_IS_BLIZZARD_RA3

- TARGET_IS_BLIZZARD_RB1

0 Evelyn Sabbag1 over 10 years ago in reply to Chester Gillon

Prodigy 180 points

For the TM4C123GH6PGE MCU, which Blizzard class should be designated? And where is this list? All previously listed links are BROKEN!!!

0 Amit Ashara over 10 years ago in reply to Evelyn Sabbag1

TI__Guru**** 244380 points

Hello Evelyn,

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

Regards

Amit

0 Joseph Forrest over 8 years ago in reply to Amit Ashara

Prodigy 40 points

For the TM4C123GH6PM I have 0x18050102 in the SYSCTL.DIDO register. Would that indicate RB2? Unfortunately I don't see RB2 in the rom.h file. I would greatly appreciate any help.

0 Robert Adsett over 8 years ago in reply to Joseph Forrest

Guru 27665 points

Holy Zombie Thread!

Robert

0 cb1 over 8 years ago in reply to Robert Adsett

Guru 47900 points

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...

0 Robert Adsett over 8 years ago in reply to cb1

Guru 27665 points

It is definitely on point and no disrespect to Joseph.

Better searching than most newcomers do actually

Someone from TI should have an answer.

Robert

0 cb1_mobile over 8 years ago in reply to Robert Adsett

Guru 117850 points

Robert Adsett said:
Someone from xyz should have an answer.

If they don't - may we drive a stake thru this Franken-post?

0 Robert Adsett over 8 years ago in reply to cb1_mobile

Guru 27665 points

You bring the torches, I'll see to the pitch forks.

Robert

0 cb1_mobile over 8 years ago in reply to Robert Adsett

Guru 117850 points

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?

0 Amit Ashara over 8 years ago in reply to Joseph Forrest

TI__Guru**** 244380 points

Hello Josephy

Which TivaWare release are you using for application development?

Regards
Amit

0 Joseph Forrest over 8 years ago in reply to Amit Ashara

Prodigy 40 points

Hey Amit

I'm using the tm4c123gh6pm.

Joseph

0 Robert Adsett72 over 8 years ago in reply to Joseph Forrest

Guru 10570 points

That's the processor, Amit's asking about the TivaWare version.

Robert

0 Amit Ashara over 8 years ago in reply to Joseph Forrest

TI__Guru**** 244380 points

Hello Joseph

TARGET_IS_TM4C123_RB2 is used in rom.h file. This is available in TivaWare version 2.1.2.111

Regards
Amit

0 Joseph Forrest over 8 years ago in reply to Amit Ashara

Prodigy 40 points

Hey Amit

First off, thanks for the help. I am using the 2.1.2.111 version of the tivaware and I found where TM4C123_RB2 is used but I'm still not sure as to why it was used. I tried searching the user guide for the tm4c123gh6pm, the tm4c123x rom users guide, and the tivaware peripheral driver library users guide for an explanation but didn't find anything.

Joseph

0 Robert Adsett over 8 years ago in reply to Joseph Forrest

Guru 27665 points

Which is a very good point Joseph.

Amit, these particular defines pop up on occasion but I do not remember seeing them documented anywhere. Where are they documented?

Robert

0 cb1_mobile over 8 years ago in reply to Robert Adsett

Guru 117850 points

And while poster Robert, "Seizes this particular moment/issue" does not this, "Unclear locating" (to be kind) of, "Vital Tech Data" extend far beyond this focused request?

Many note the pristine, unmissable, RED BAR - spanning the forum's top - reserved for the "uber-important" blogs, groups videos - yet there is ...NO SPACE for, "Vital Tech Data!"

How can this possibly be justified?

0 Chester Gillon over 8 years ago in reply to Joseph Forrest

Guru 92251 points

Joseph Forrest said:
I tried searching the user guide for the tm4c123gh6pm, the tm4c123x rom users guide, and the tivaware peripheral driver library users guide for an explanation but didn't find anything.

Section 34.2 Direct ROM Calls of the TivaWareTM Peripheral Driver Library USER’S GUIDE SW-TM4C-DRL-UG-2.1.2.111 has a description of the TARGET_IS_* macros. Does that answer your question?

0 Chester Gillon over 8 years ago

Guru 92251 points

Chester Gillon said:
b) Should the ROM EEPROM functions be described as supported in the LM4F120H5QR and/or TM4C1233H6PM ROM user guides?

The latest TivaTM C Series TM4C123x ROM USER’S GUIDE UG-ROM-TM4C123x-818 SPMU367 dated May 2014 still doesn't contain mention of EEPROM functions, so I submitted documentation feedback.

[Whereas the TivaTM C Series TM4C129x ROM USER’S GUIDE UG-ROM-TM4C129x-818 SPMU363 does document the EEPROM functions]

0 Amit Ashara over 8 years ago in reply to Joseph Forrest

TI__Guru**** 244380 points

Hello Joseph,

As different version of the Silicon or Software are released, it may be possible that a bug gets introduced which requires the function to be updated. Since the ROM functions cannot be updated like a software release, they appropriate define can then be deprecated in the software, until a new release of the device fixes the issue in ROM.

Regards
Amit

0 Joseph Forrest over 8 years ago in reply to Chester Gillon

Prodigy 40 points

hey chester

I did run across that section but I wasn't sure what silicon revision was or which to use(A1, A3, B1...). I honestly don't know enough about these things to know what that even does so I ended up picking one and it worked. I may never know why but I think its time to move on for now. Thank you for the help and all others.

cheers,
Joseph

Arm-based microcontrollers

Arm-based microcontrollers forum

Descripancies in ROM support for EEPROM functions