• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 33 subscribers
  • Views 1222 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.

TM4C129 class missing ROM_GPIOPadConfigSet

Scott McFarland
Intellectual 840 points

Other Parts Discussed in Thread: TM4C1294NCPDT

Device: TM4C1294NCPDT (custom pcb)

TivaWare: version 2.1.0.12573

CCS version: 5.5.0.00077

Problem: For above mentioned version of TivaWare, rom.h does not allow

ROM_GPIOPadConfigSet() for target class TM4C129. Must I use GPIOPadConfigSet() from driverlib?

  • 0
    TI__Guru**** 244440 points

    Hello Scott,

    Yes. you would ahve to use the GPIOPadConfigSet from the driverlib. A better way if I am may suggest is to use MAP_GPIOPadConfigSet so that if the ROM version is not available for a Silicon Rev then it will automatically map to the driverlib version.

    Regards

    Amit

  • 0 in reply to Amit Ashara
    Expert 1775 points

    I ran into this today. I noticed that in rom.h there is the following:

    #if defined(TARGET_IS_TM4C123_RA1) || \
    defined(TARGET_IS_TM4C123_RA3) || \
    defined(TARGET_IS_TM4C123_RB1)
    #define ROM_GPIOPadConfigSet \
    ((void (*)(uint32_t ui32Port, \
    uint8_t ui8Pins, \
    uint32_t ui32Strength, \
    uint32_t ui32PadType))ROM_GPIOTABLE[5])
    #endif
    #if defined(TARGET_IS_TM4C123_RA1) || \
    defined(TARGET_IS_TM4C123_RA3) || \
    defined(TARGET_IS_TM4C123_RB1) || \
    defined(TARGET_IS_TM4C129_RA0) || \
    defined(TARGET_IS_TM4C129_RA1)
    #define ROM_GPIOPadConfigGet \
    ((void (*)(uint32_t ui32Port, \
    uint8_t ui8Pin, \
    uint32_t *pui32Strength, \
    uint32_t *pui32PadType))ROM_GPIOTABLE[6])
    #endif

    The TARGET_IS_TM4C129... checks are missing for the Set function. Is this an over-site or intentional?

    Thanks

  • 0 in reply to Amit Ashara
    Guru 47900 points

    Amit Ashara said:
    A better way if I am may suggest is to use MAP_GPIOPadConfigSet so that if the ROM version is not available for a Silicon Rev then it will automatically map to the driverlib version.

    In general - use of "MAP" does insure that the function call is executed.  But - keying to the, "better way" characterization - might there be some time and/or execution penalty (or other) which is imposed by use of, "MAP?"  (i.e. "free school lunch is rarely "free")

    Surely usage of MAP makes great sense - "if" any penalty imposed is known and accepted.  (I can't find this point ever mentioned nor analyzed)