- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
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
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
