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.

TM4C129CNCZAD: difference and Impact ROM & MAP suffix

Part Number: TM4C129CNCZAD

Dear Di,

When to use ROM_ suffix and MAP_ Suffix.

What is main diffrence and imapct on Code.

ROM_GPIOPinIntDisable(GPIO_PORTM_BASE, GPIO_PIN_6); //Disable the Individual Pin sensing intrrupt

MAP_GPIOPinIntDisable(GPIO_PORTM_BASE, GPIO_PIN_6); //Disable the Individual Pin sensing intrrupt

Both are correct. I can use any of them in code?

Kindly explain

  • Both behave the same and create the same code usually.

    Functions that begin with the ROM_ prefix are functions that are contained in the on-chip ROM of the device. Using the on-chip ROM will reduce the amount of flash space required for your code. The same function exists in the TivaWare library without the ROM_ prefix. If you invoke that function, it will be placed in the flash.

    On occasion, a bug is found in a ROM_ function. Since we cannot update the ROM on a device, the next version of TivaWare will deprecate that function and replace it with a fixed version in the TivaWare library. The ROM_ version will no longer be defined in the new version of TivaWare and a link error will result. There is a header file in TivaWare (rom_map.h) that defines all functions with MAP_ as ROM_ unless the function has been deprecated. In that case it defines the MAP_ function as the flash version (without a prefix).

    Use ROM_ if you want the function in ROM and you want to be notified when updating TivaWare if the function has been depricated. (Then you would edit the code and delete the ROM_ prefix.)

    Use MAP_ if you want the function in ROM unless it has been deprecated and you do not want to be notified with a link error.