BSP Button events not getting triggered

RE: BSP Button events not getting triggered

Ron — Wed, 30 Jan 2019 22:25:29 GMT

Oops! 😳

That's the ticket. Working like a charm now. Thanks Einar!

RE: BSP Button events not getting triggered

Einar Thorsrud — Wed, 30 Jan 2019 06:59:48 GMT

Hi Ron,

The code you have added requests the HF clock, but that is not what is missing. The app timer use an RTC, which needs the 32 kHz LF clock, so you should request it by using nrf_drv_clock_lfclk_request() instead.

Regarding the GPIOTE driver that is not a problem. It is fine that you initialize it yourself, but if you had not it would have been initialized by app_button_init() which is called from bsp_init().

RE: BSP Button events not getting triggered

Ron — Wed, 30 Jan 2019 03:00:38 GMT

Thanks Einar,

Still no joy 😖

I added this to the top of main():

	if (nrf_drv_clock_init() != NRF_SUCCESS)
	{
		return NRF_ERROR_INTERNAL;
	}

	nrf_drv_clock_hfclk_request(NULL);
	while (!nrf_drv_clock_hfclk_is_running())
	{
	}

This is what's in sdk_config.h for the clock:

//==========================================================
// <e> CLOCK_ENABLED - nrf_drv_clock - CLOCK peripheral driver
//==========================================================
#ifndef CLOCK_ENABLED
#define CLOCK_ENABLED 1
#endif
// <o> CLOCK_CONFIG_XTAL_FREQ  - HF XTAL Frequency
 
// <0=> Default (64 MHz) 

#ifndef CLOCK_CONFIG_XTAL_FREQ
#define CLOCK_CONFIG_XTAL_FREQ 0
#endif

// <o> CLOCK_CONFIG_LF_SRC  - LF Clock Source
 
// <0=> RC 
// <1=> XTAL 
// <2=> Synth 

#ifndef CLOCK_CONFIG_LF_SRC
#define CLOCK_CONFIG_LF_SRC 1
#endif

// <o> CLOCK_CONFIG_IRQ_PRIORITY  - Interrupt priority
 

// <i> Priorities 0,2 (nRF51) and 0,1,4,5 (nRF52) are reserved for SoftDevice
// <0=> 0 (highest) 
// <1=> 1 
// <2=> 2 
// <3=> 3 
// <4=> 4 
// <5=> 5 
// <6=> 6 
// <7=> 7 

#ifndef CLOCK_CONFIG_IRQ_PRIORITY
#define CLOCK_CONFIG_IRQ_PRIORITY 7
#endif

// </e>

I noticed the doc for bsp_init() says the app_gpiote module is required, but the 14.2 SDK doc suggests this is deprecated in favour of nrf_drv_gpiote, which I am actively using, so I assume this is a non-issue? Not sure what else to look at.

RE: BSP Button events not getting triggered

Einar Thorsrud — Tue, 29 Jan 2019 09:22:48 GMT

Hi Ron,

The project needed some adjustment in order to build it (could not just be dropped in to the SDK 14.2 distribution). Therefore, I have not tested your code, but I think I spotted the problem. When not using BSP_SIMPLE, the BSP library uses app timers to handle buttons. However, the app_timer will not work if the 32 kHz clock is not started, and in that case, you will not get any button events.

You do not need to start the 32 kHz clock explicitly if you use a SoftDevice, as it will start it when the SoftDevice is enabled. However, I do not see that you enable a SoftDevice in your application, and then you have to start the 32 kHz clock explicitly.

RE: BSP Button events not getting triggered

Ron — Mon, 28 Jan 2019 18:01:42 GMT

Here you go...Google Drive

RE: BSP Button events not getting triggered

Einar Thorsrud — Mon, 28 Jan 2019 15:05:41 GMT

It should work... Can you upload the complete test project (including project files etc.) so that I can test on a DK on my side?

RE: BSP Button events not getting triggered

Ron — Mon, 28 Jan 2019 12:46:10 GMT

Got it. So any suggestions? Still not seeing the button press events fire 😕

RE: BSP Button events not getting triggered

Einar Thorsrud — Mon, 28 Jan 2019 10:09:21 GMT

Hi,

I will ignore the UART comment 🙂

Yes, you cannot use BSP_DEFINES_ONLY if you want full BSP functionality. The GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS has to be as high as the number of pins you want to use. That is because it is used to set the size of an array containing function pointers to event handlers, and for iterating over all pins in the interrupt handler for low power port events etc.

RE: BSP Button events not getting triggered

Ron — Thu, 24 Jan 2019 17:32:51 GMT

Ignore the comment about the UART. That is resolved and was unrelated.

RE: BSP Button events not getting triggered

Ron — Thu, 24 Jan 2019 16:35:45 GMT

Thanks Einar! I found removing BSP_SIMPLE was generating some unresolved symbols until I also undefined BSP_DEFINES_ONLY. I found I also had to increase GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS. I increased to 4, as it seemed to want one for each button?

So now the app compiles and runs again, but my breakpoint in the button event handler is still not being hit. Also, it seems as though the changes may have disabled logging over UART? In case it's material, these are the defines that are left (inherited from the original example):

c_preprocessor_definitions="BOARD_PCA10040;CONFIG_GPIO_AS_PINRESET;FLOAT_ABI_HARD;INITIALIZE_USER_SECTIONS;NO_VTOR_CONFIG;NRF52;NRF52832_XXAA;NRF52_PAN_74;"

RE: BSP Button events not getting triggered

Einar Thorsrud — Thu, 24 Jan 2019 13:49:40 GMT

Hi,

You will not get button interrupts if BSP_SIMPLE. So if you want to use the BSP with button events, you have to remove the BSP_SIMPLE define.