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.

TM4C1231H6PGE: MCU pin 12 can be timer configurable?

Part Number: TM4C1231H6PGE
Other Parts Discussed in Thread: EK-TM4C123GXL

Hi Team,

 We are using the Pin#12 of the MCU Part # TM4C1231H6PGEI7, configured as an Output, to assert a state signal (named MCU_LOAD_SHUT_MUX).

This signal will be asserted based on another signal at Pin#133 configured as Input (named MUX_AUX_PD_DETECT_MCU).

The logic on the signal at Pin#12 will be driven based on the Pin#133 input signal state.

In that case, would it be possible to drive this signal (output) with some delay after receiving the input signal at pin#133?

If it is possible, would there be any constraints on min and max delay in timing?

 Kindly give your input on these queries.

Best Regards,
Spandana Peramala.

  • Hello Spandana,

    This would be very possible to do.

    Using interrupts, you can set the GPIO interrupt for Pin #133 to trigger the start of a Timer.

    Then when the Timer expires, it can trigger the GPIO output on Pin #12.

    The minimum delay timing would be based on CPU clock cycles to execute the APIs used though if you need that tight of a delay then you would forgo the timer and just add a few NOP's before togging the pin.

    The maximum delay would depend what on timer you are using and how you have the system clock configured. A 16-bit timer has a count of 65535, a 16-bit timer with a prescale of 8 bits would get up to 16777215, and for 32-bit, you'd have 50+ seconds minimum at max system clock.

    Our timers example for the EK-TM4C123GXL demonstrates a lot of what you are looking for in terms of using a Timer to trigger a GPIO output.

    Best Regards,

    Ralph

  • Thanks for the response Ralph