• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 199 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.

TM4C129XNCZAD: Peripheral Disable, Reset, Enable sequence

Felipe
Prodigy 10 points
Part Number: TM4C129XNCZAD

Hi,

When is it enough to use only (for e.g.):

SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOA);

 

When to use the whole sequence:

SysCtlPeripheralDisable(SYSCTL_PERIPH_GPIOA);
SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOA);
SysCtlPeripheralReset(SYSCTL_PERIPH_GPIOA);

And is there a difference when reversing reset and enable like this:

SysCtlPeripheralDisable(SYSCTL_PERIPH_GPIOA);
SysCtlPeripheralReset(SYSCTL_PERIPH_GPIOA);
SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOA);

You can give some examples and use cases.

  • 0
    TI__Guru**** 191296 points

    Hi,

      If you look at most of the TivaWare examples (e.g. GPIO, UART, SSI or etc) you would normally see just SysCtlPeripheralEnable() getting called during initialization because the peripherals after a reset will be in their default state which means they are disabled. All of three example sequences you show will work. SysCtlPeripheralEnable is used to enable the clock for the selected peripheral while SysCtlPeripheralReset is used to reset the selected peripheral to its default state.