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.

66AK2G12: SYS/BIOS: "spirious" GPIO interrupt

Part Number: 66AK2G12
Other Parts Discussed in Thread: SYSBIOS

Tool/software:

Hi all,

A strange problem has appeared.
Hardware configuration:
- SPI device (MAX11040 in daisy-chain) connected to SPI1 on K2GEVM. The peculiarity is that this ADCs produces a signal when it completes the analog-to-digital conversion on all channels and they can be read. This is quite convenient.
- the utility for reading data from the SPI (at the customer's request) is executed on the DSP processor (C66).
- the data readiness interrupt is implemented as a GPIO interrupt.
Tested:
- a separate utility that processes this interrupt signal and reads data from the SPI assembled with the CCS - works as expected
- a separate utility with the same functionality but loaded from Linux using the mpmcl command - works as expected
- the same code but added as a separate task in the "IPC Bigdata" example performs only a few readings from the SPI.
Diagnostics:
- debug output has been added to the GPIO driver (GPIO_v0.c) in the function GPIO_v0_hwiFxn(). 
I found that the GPIO interrupt appears, this function is called but reading the interrupt cause register (INTSTATXX) got 0s. So the interrupt is there, but it is not detected in the driver. Surprisingly, several interrupts are handled correctly before lost one.


Can anyone suggest an idea about this?

Thanks.