Hello there,
I am trying to add a PINT interrupt into a NXP BLE Stack example design using the #QN9090
I have taken the PINT example code from the drivers and placed it at the main_task() function in the "ApplMain.c" file. The pin used in the QN9090 is the PIO15(also tested with PIO7 and PIO4 from the expansion board).
The Interrupt is defined in the PIN via HW Config tools like:
The initialization code looks like:
The set-up code to trigger the interrupt contains only 2 commands(aside from the print-out):
"pint_intr_callback" function prints-out a message every time the interrupt is called. However this message never gets called or the interrupt never gets listed when I read the Pint interrupts with the command :
PINT_PinInterruptGetStatusAll(PINT)
It looks like the Interrupt has not been set-up correctly or the Pin Interrupts are not enabled
What could I do to make it work?
Hi Eduardo,
Problem solved.
Following your suggestions to add an additional switch functionality on the code, it allowed me to realize how the PINT are being used in the NXP BLE example design.
The file 'board.c' configures the switch pins on the Devkit and assigns them with an Interrupt and a physical PIN. Then I saw the PINT_0 & PINT_1 Interrupts were already being used.
On the top of that the different functions associated to configure the 'dk6_button_io_pins[]' also call other functions to clear-out the associated Interrupts registers which caused the problem that even though my code was assign the PIN_0 to my pin, this interrupt could be cleared out by another callback function.
Solution:
Assign to my own PINT any interrupt not being used by the devkit switches: PINT_2 or PINT_3
Alternatively, Devkit switches can be disabled by commenting out : KBD_Init(App_KeyboardCallBack); on main_task()
Hi,
Please, try the following:
- In source/app_preinclude.h file, set gKBD_KeysCount_c to 3 and, if implemented, disable (set to 0) low-power features (UsePowerDownMode and FullPowerDownMode)
- In board/gpio_pins.h, define Port0 Pin7 as BUTTON3
- In source/main.c (for example private_profile_server.c), in BleApp_HandleKeys() function (which handles keyboard events), add the event corresponding to PB3, gKBD_EventPB3_c:
Regards,
Eduardo.
Hi Eduardo,
Problem solved.
Following your suggestions to add an additional switch functionality on the code, it allowed me to realize how the PINT are being used in the NXP BLE example design.
The file 'board.c' configures the switch pins on the Devkit and assigns them with an Interrupt and a physical PIN. Then I saw the PINT_0 & PINT_1 Interrupts were already being used.
On the top of that the different functions associated to configure the 'dk6_button_io_pins[]' also call other functions to clear-out the associated Interrupts registers which caused the problem that even though my code was assign the PIN_0 to my pin, this interrupt could be cleared out by another callback function.
Solution:
Assign to my own PINT any interrupt not being used by the devkit switches: PINT_2 or PINT_3
Alternatively, Devkit switches can be disabled by commenting out : KBD_Init(App_KeyboardCallBack); on main_task()
Hi Eduardo,
Thank you for enquiring about this.
The PINT is NOT going to be used as a wake-up pin for the QN9090 BLE sleep mode.
The pin in question is going to be used as a means to let the QN9090 to know there is some data available on one of its Communication ports. Basically, the QN9090 is a Slave device and a Master device toggles/enables this pin to force the QN9090 to read from certain port
I did some debugging on the registers via MCUXpresso. I can see the PINTSEL[0] for the PINT0 interrupt pointing to the PIO selected for the purpose, PIO_4 or PIO_7. See image
Then PINT registers are cleared and enabled for an active LOW interrupt on this pin. With the callback function listed:
So a few things I would like to find out are:
- How do I know there is a clock associated for the PINT to be triggered?
- How could I find out the NVIC interrupt for the PINT0 is enabled?
Regards
Blas
