• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 409 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-AM263P: AM263P Input Interrupt not triggering: gpio_input_interrupt_am263px

David Martinez
Intellectual 2101 points
Part Number: LP-AM263P
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hello,

I am using the gpio_input_interrupt_am263px-LP example and want to trigger an input interrupt using SPI1_CS0 or SPI0_D1.

I have changed only the settings for "GPIO PUSH BUTTON" as shown below.

In my test, I simply put 3.3V on pin J6.58 for SPI1_CS0, or J6.54 for SPI0_D1, but it won't trigger an interrupt.

I suspect the issue is XBAR. I have not changed the XBAR Input settings in sysconfig. Is this the issue? If so, how do I determine what settings XBAR should be for each input?

Best,

David

  • +1
    TI__Intellectual 2425 points

    Hi David,

    GPIO INT XBAR needs to be configured to route GPIO inputs to VIM. There are 4 inputs to each of the R5 VIM's from GPIO INT XBAR as shown below. This is selected as XBAR instance.

    There are a total of 144 GPIO Pins (GPIO 0 to 143), four instances of GPIO module (GPIO 0 to 3) and 9 GPIO Banks (GPIO 0 to 8).

    Each GPIO module is linked to one of the R5 cores and a GPIO pin can be linked to any of the GPIO modules. This is automatically taken care when Pinmux is configured for the GPIO Pin in a SysCfg context (It gets linked to the GPIO module of that core).

    Each GPIO bank contains a group of 16 GPIO pins. Bank 0 has GPIO 0 to 15, Bank 1 has GPIO 16 to 31 and so on.

    While selecting the XBAR Output, there are 2 options-

    #1 Select a Bank interrupt to be routed to VIM. This routes all GPIO interrupt in a bank to VIM instance. Corresponding Bank interrupt register can be read in the ISR to figure out the GPIO Pin which caused the interrupt. This allows multiple GPIO Pins interrupts to be routed on the same line.

    #2 Select a GPIO Pin interrupt to be connected to VIM instance. Any of the GPIO pin interrupts (0-143) will be routed to VIM instance. In this mode, only one GPIO pin interrupt will be routed to a GPIO instance.

    Regards,

    Ashwin

  • 0 in reply to Ashwin Raj
    TI__Intellectual 2101 points

    Thanks Ashwin,

    a follow up question: Can you clarify again how do I go about selecting the XBAR instance?

    Example:

    GPIO14

    XBAR Output: GPIO_0_bank_intr_0

    XBar Instance: GPIO_INT_XBAR_VIM_Module0_0

    Why does GPIO_INT_XBAR_VIM_Module0_0 work but not GPIO_INT_XBAR_VIM_Module0_1?

  • 0 in reply to David Martinez
    TI__Intellectual 2425 points

    Hi David,

    There are total of 16 GPIO INT XBAR instances connected to R5 VIM module (4 instances per R5 core)

    R50_0 instances - GPIO_INT_XBAR_VIM_Module0_0 to GPIO_INT_XBAR_VIM_Module0_3

    R50_1 instances - GPIO_INT_XBAR_VIM_Module1_0 to GPIO_INT_XBAR_VIM_Module1_3

    R51_0 instances - GPIO_INT_XBAR_VIM_Module2_0 to GPIO_INT_XBAR_VIM_Module2_3

    R51_1 instances - GPIO_INT_XBAR_VIM_Module3_0 to GPIO_INT_XBAR_VIM_Module3_3

    If you have changed GPIO_INT_XBAR_VIM_Module0_0 to GPIO_INT_XBAR_VIM_Module0_1, make sure to update the interrupt number being used for ISR registration.

    GPIO_INT_XBAR_VIM_Module0_0 -> CSLR_R5FSS0_CORE0_INTR_GPIO_INTRXBAR_OUT_14

    GPIO_INT_XBAR_VIM_Module0_1 -> CSLR_R5FSS0_CORE0_INTR_GPIO_INTRXBAR_OUT_15

    Regards,

    Ashwin