SIMPLELINK-CC13X2-26X2-SDK: PIN_setInterrupt() calling multiple times even if the interrupt is enabled already hampers anything?

Mehul Dalal

Part Number: SIMPLELINK-CC13X2-26X2-SDK

IN my code, PIN_setInterrupt() is used to disable the interrupt for a specific pin.

However, I need to use PIN_setInterrupt() multiple times to enable the interrupt for a specific PIN even if sometimes the itnerrupt for this pin is already enabled. Calling PIN_setInterrupt() multiple times to enable the interrupt for the same pin for which the interrupt is also enabled causes any issue?

I am using SDK v3.20.

over 3 years ago

0 Elin W over 3 years ago

TI__Genius 14845 points

Hi Mehul,

Assigning an expert to comment.

Thanks,
Elin

0 Siri over 3 years ago in reply to Elin W

TI__Guru* 79361 points

When enabling an interrupt on a pin (that is already enabled), you risk loosing an interrupt since in the PINCC26XX_setIoCfg, you will clear any pending events from the previous pin configuration before we write the new interrupt settings:

PINCC26XX_clrPendInterrupt(pinId);
HWREG(IOC_BASE + IOC_O_IOCFG0 + 4 * pinId) = tmpConfig;

Siri

0 Mehul Dalal over 3 years ago in reply to Siri

Expert 2140 points

Yes, I agree and it has been mentioned in the API description as well. If we think that it is fine to loose any pending interrupts, are there any other risk?

0 Siri over 3 years ago in reply to Mehul Dalal

TI__Guru* 79361 points

I cannot see any other issues related to it.

Siri

Bluetooth®︎

Bluetooth forum

SIMPLELINK-CC13X2-26X2-SDK: PIN_setInterrupt() calling multiple times even if the interrupt is enabled already hampers anything?