GPIOTE using Pin13-16 on 52DK and BMD-300

RE: GPIOTE using Pin13-16 on 52DK and BMD-300

xhr0428 — Tue, 22 Aug 2017 18:03:14 GMT

Hi Jørn, I have created a case. ID is 38387. Please take a look.

RE: GPIOTE using Pin13-16 on 52DK and BMD-300

Jørn — Tue, 22 Aug 2017 06:07:23 GMT

I would need to see all your main code to assess this I think. I just removed BSP_INIT_BUTTONS from the unchanged characteristic tutorial code and it works as expected. I suspect there is something else in your code that generates that error. If your code is confidential you can create a mypage case at nordicsemi.com, and refer to this case. If it isn't confidential you can just upload your main.c file to your original question here.

RE: GPIOTE using Pin13-16 on 52DK and BMD-300

xhr0428 — Mon, 21 Aug 2017 23:57:51 GMT

Hi Jørn, removing BSP_INIT_BUTTONS from the bop_init() gets the following error:

Name : m_error_data

Details:{fault_id = 16385, pc = 0, error_info = 536936404, p_assert_info = 0x0, p_error_info = 0x2000ffd4, err_code = 8, line_num = 1177, p_file_name = 0x2be6c "../../../main.c"}

What's the issue here?

RE: GPIOTE using Pin13-16 on 52DK and BMD-300

Jørn — Mon, 21 Aug 2017 17:18:57 GMT

The following code

uint32_t err_code = bsp_init(BSP_INIT_LED,APP_TIMER_TICKS(100, APP_TIMER_PRESCALER),bsp_event_handler);

Should only initialize the LEDS present on the board, as defined in the board header file. It is only necessary to call if you want to keep the functionality offered by the bsp module in regards of led indication of current state. If you cannot see the device advertising it might be because there are additional problems generating an error. You could try to debug and see if the function returns an error code.

RE: GPIOTE using Pin13-16 on 52DK and BMD-300

xhr0428 — Mon, 21 Aug 2017 16:47:58 GMT

Hi Jørn, Thanks for the reply. Creating a custom.h and changing button definition solved the issue.

But the other approach, removing BSP_INIT_BUTTONS from the bop_init() didn't seem to work. Here is the code I have

uint32_t err_code = bsp_init(BSP_INIT_LED,APP_TIMER_TICKS(100, APP_TIMER_PRESCALER), bsp_event_handler);

Another question is do I have to call buttons_leds_init() in the first place? If I comment this function out, I couldn't see advertising as well.

RE: GPIOTE using Pin13-16 on 52DK and BMD-300

Jørn — Mon, 21 Aug 2017 11:12:41 GMT

Hello xr0428

In the characteristics tutorial the function buttons_leds_init() is called from main. This in turn calls

uint32_t err_code = bsp_init(BSP_INIT_LED | BSP_INIT_BUTTONS,APP_TIMER_TICKS(100, APP_TIMER_PRESCALER), bsp_event_handler);

This function is part of the board support (bsp) module, and it configures the buttons and leds of the board you are using. For the 52832DK the board defines are found in the pca10040.h header file. The bsp_init function configures the button pins as GPIOTE inputs with low power events.

When you add your code for pins 13-16 you are trying to initialize GPIOTE for the same pins as the bsp_init function do. This will then trigger the NRF_ERROR_INVALID_STATE error.

If you are using a custom board you can create a header file called custom_board.h, and remove pca10040.h from the include list. You can place this file in the same directory as the main.c file, as this path is already added. Then remove BOARD_PCA10040 from the preprocessor symbols and add BOARD_CUSTOM (as defined in boards.h). Your custom_board.h should then contain all pin defines similar to what pca10040.h does.

Alternatively you can remove BSP_INIT_BUTTONS from the bsp_init() arguments. The function will then not configure the buttons, and you can configure them yourself as you please.

Best regards

Jørn Frøysa