Query related to KW45B41Z83AFTA bluetooth Example

[Ganesh_Pawar]

Hello NXP team,

This query is related to bluetooth example Temperature sensor and collector baremetal.

I am using KW45B41Z normal evk (not the LOC evk), with SDK version : SDK_2_12_5_KW45B41Z-EVK with MCUXpresso IDE v11.9.0.2144.

As per the bluetooth Example demo guide document, once the device enters into sleep mode, it is made to wake up either using SW2 or SW3 connected to PTC6 and PTD1 pins.

question here is, instead of using SW2 and SW3 is it possible to wake up using other gpio pins which supports WUU input pins as per the data sheet.

if yes, what are the things or API to be considered for changes.

Requesting for your inputs on this. 

Thanks and regards

Ganesh Pawar

[luis_maravilla]

Hello,

Could you please kindly clarify what is the procedure you have configured for button handle?

I will recommend on checking the file board_lp.h

You will need to change the Wake-up source button from GPIOD to PTB4 in this scenario

BOARD_WAKEUP_SOURCE_BUTTON0 (uint32_t) PM_WSID_GPIOD_LOW

is declared for SW2 using GPIOD (PTD1) instead the configuration will be

PM_WSID_PTB4_FALLING_EDGE.

Thank you for your interest in NXP Semiconductor products.

Best Regards

Luis

[Ganesh_Pawar]

Hi @luis_maravilla,

Thanks for your reply much appreciated.

I have explained the software configurations and the changes done in detail in the attached document.

The problem I am facing is, In the Button task list the Callback is assigned to GPIOD Interrupt handler, It is defined in the startup file IRQ as "intdefaultHandler".

So where do i assign the callback/interrupt handler from GPIOD to GPIOB. where is this interrupt assigned taken care?

I hope the query is understood, if not please revert back.

Thanks and regards,

Ganesh Pawar

[luis_maravilla]

Hello,

Sorry for the inconveniences this might cause you but reviewing the KW45 EVK schematics PTB3 and PTB4 have connections to debugger LPC55 so it may cause some troubles for your application if you change the configuration.

I will recommend you taking a look at the Schematics available in the Design Files [KW45B41Z-EVK_SCH] to confirm the pins that are available and that do not interfere with other interfaces. Also, please check if the pin can be used as wake up source; You can consult the following information in Chapter 2.2 to configure the wakeup source pin and the recommendations for developers, this information includes where to search the list for available wakeup sources and an example for initializing low power framework and wakeup sources LowPower — MCUXpresso SDK Documentation

Also, I would recommend updating to the latest SDK version too [25.06] you can check this in the following link Dashboard | MCUXpresso SDK Builder

Best Regards

Luis

[sera94]

Hello,
Assuming you are working with the SDK_2_12_5_KW45B41Z-EVK, the relevant files and APIs would typically be found in the boards folder (for board-specific pinmux and clock configurations) and the drivers folder (for GPIO, PORT, and Power Management APIs).

[Ganesh_Pawar]

Hi @sera94,

Thanks for your reply much appreciated.

I understand that the API's are available in the driver files in the SDK .

Concern here is that, since SW2 (PTD1) connected to the switch, instead of using the Switch to trigger from low power, i have connected to one of the WUU input supported pin (PTB4).

I have configured it as a button handle with interrupt triggered at falling edge same as the switch, I have disabled the Switch configuration as defined in the EVK, but i observed that the PTD1 (SW2) IRQ is still observed in the task list by default and the button list handler is waiting for that PTD1 irq handler to trigger it out of low power. 

The IRQ definition for PTD1 is intdefaultHandler in the vector table.

I want to know where is this irq handler is being configured and how do i proceed.

please provide inputs on this.

Thanks and regards,

Ganesh Pawar