GPIO_PortGetInterruptFlags / GPIO_PortClearInterruptFlags / KSDK 2.4

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

GPIO_PortGetInterruptFlags / GPIO_PortClearInterruptFlags / KSDK 2.4

1,296 Views
manfredschnell
Contributor IV

Hello,

we use MK64FN1M0_VLQ12, KSDK 2.4.2

When I build Driver library out of KSKS 2.4.2 sources, two functions are excluded although they should be built.

GPIO_PortGetInterruptFlags() and GPIO_PortClearInterruptFlags() are excluded because in features header "MK64F12_features.h"  section "GPIO module features" a definition is missing.

MK64F12_features.h    (KSDK2.4.2)

**     Version:             rev. 2.15, 2016-03-21
**     Build:               b180410

/* @brief Has fast (single cycle) access capability via a dedicated memory region. */
#define FSL_FEATURE_GPIO_HAS_FAST_GPIO (0)
/* @brief Has port input disable register (PIDR). */
#define FSL_FEATURE_GPIO_HAS_INPUT_DISABLE (0)
/* @brief Has dedicated interrupt vector. */
#define FSL_FEATURE_GPIO_HAS_PORT_INTERRUPT_VECTOR (1)
//      !!!!
// by MS
/* @brief set to 1 if device has no port interrupt */
#define FSL_FEATURE_GPIO_HAS_NO_PORTINTERRUPT (0)
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Please check this and confirm my completion.

Best regards

Manfred

Labels (1)
0 Kudos
2 Replies

1,012 Views
danielchen
NXP TechSupport
NXP TechSupport

Hi Manfred:

I imported the gpio_input_interrupt demo into MCUXpresso IDE, the two functions are included. Please see the shadow of the code, excluded code is light grey. I would suggest you check the macro defines in your project.

pastedImage_2.png

Regards

Daniel

1,012 Views
manfredschnell
Contributor IV

Hi Daniel,

thank you for your answer.

I was wrong. I didn't realize the change from:

KSDK2.0                                        -->            KSDK2.4

GPIO_GetPinsInterruptFlags()       -->       GPIO_PortGetInterruptFlags()

GPIO_ClearPinsInterruptFlags()    -->       GPIO_PortClearInterruptFlags() 

Best regards

Manfred

0 Kudos