• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 941 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.

LP-AM263: AM263x GPIO interrupts

Michael Nickelson
Prodigy 60 points
Part Number: LP-AM263


Hi,

I'm working on a project to interface with a third party sensor array. The HAL test provided by the vendor involves using a GPIO pin that is polled as well as being connected to an ISR.

I am starting from the gpio_input_interrupt example in SDK version 08.05.00.24. When I change the syscfg file so that gpio1.GPIO_gpioPin.$assign = "EPWM0_A" and connect a wire to J2.11 on my launchpad, the interrupt is never triggered when I connect that pin between GND and 3.3V. Is there another step that I'm missing to connect that pin to an interrupt?

Also, when using the original pin connected to SW4, I added the line "DebugP_log("Current key value: %d\r\n", GPIO_pinRead(bankNum, pinNum)" to get the current value of the interrupt pin, but it always reads as 0, even when I am holding the button. Is there another function that should be used to read interrupt pins?

Thanks,

Mike

  • +1
    TI__Expert 7586 points

    HI Mike

    You can try the following to debug this issue:

    1. Check if the GPIO pin is configured as input direction.

    2. Check if the GPIO Interrupt XBAR is also configured for the same pin, in the syscfg:

    (Step 2 --> I made the below change along with changing the GPIO pin and it worked for me)

    3. For the GPIO Initialisation in the main code, Check if the pinMode API is being called for GPIO 43.

    4. Check if you are clearing the correct Interrupt status in the ISR.

    Hope this helps

    Regards

    Sri Vidya

  • 0 in reply to Sri Vidya Gunturi
    Prodigy 60 points

    Thank you Sri. I think the Xbar muxing is what I had missed.