nRF52832 Custom Board Pin In Use By GPIOTE Fault in BSP

RE: nRF52832 Custom Board Pin In Use By GPIOTE Fault in BSP

BendaEng — Tue, 27 Aug 2019 18:10:11 GMT

Fire up! I figured out the issue. Similar to your original suggestion, just in a different location. Simple, but still difficult to find. When I redefined the BSP_BUTTON_# for all 15 of my buttons, I accidentally defined the failing button as the following.

   #ifdef BSP_BUTTON_10
    {BSP_BUTTON_11, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_10

The correct definition (in bsp.c) should be as follows for more buttons.

#ifndef BSP_SIMPLE
static const app_button_cfg_t app_buttons[BUTTONS_NUMBER] =
{
    #ifdef BSP_BUTTON_0
    {BSP_BUTTON_0, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_0

    #ifdef BSP_BUTTON_1
    {BSP_BUTTON_1, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_1

    #ifdef BSP_BUTTON_2
    {BSP_BUTTON_2, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_2

    #ifdef BSP_BUTTON_3
    {BSP_BUTTON_3, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_3

    #ifdef BSP_BUTTON_4
    {BSP_BUTTON_4, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_4

    #ifdef BSP_BUTTON_5
    {BSP_BUTTON_5, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_5

    #ifdef BSP_BUTTON_6
    {BSP_BUTTON_6, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_6

    #ifdef BSP_BUTTON_7
    {BSP_BUTTON_7, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_7

    #ifdef BSP_BUTTON_8
    {BSP_BUTTON_8, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_8

    #ifdef BSP_BUTTON_9
    {BSP_BUTTON_9, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_9

    #ifdef BSP_BUTTON_10
    {BSP_BUTTON_10, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_10

    #ifdef BSP_BUTTON_11
    {BSP_BUTTON_11, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_11

    #ifdef BSP_BUTTON_12
    {BSP_BUTTON_12, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_12

    #ifdef BSP_BUTTON_13
    {BSP_BUTTON_13, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_13

    #ifdef BSP_BUTTON_14
    {BSP_BUTTON_14, false, BUTTON_PULL, bsp_button_event_handler},
    #endif // BUTTON_14

};

This at least got me past that error, going to start testing the rest of it now.

RE: nRF52832 Custom Board Pin In Use By GPIOTE Fault in BSP

BendaEng — Tue, 27 Aug 2019 16:42:13 GMT

Hi,

I see the confusion you were having with the naming of the buttons (i.e. #define BSP_BUTTON_1 BUTTON_2). However, in my program I'm defining my buttons in a very specific way (i.e. #define BSP_BUTTON_12 PN_BT) so I don't think there would be any issues there. As well as the file where the definition of buttons happens (bsp_btn_ble.c) as far as I can tell doesn't get called at all yet at the point of failure.

It seems like the issue has more to do with GPIOTE Channels and their limitations, but I'm not sure how I can modify to support more than 8 since the documentation states the following:

"Only one GPIOTE channel can be assigned to one physical pin. Failing to do so may result in unpredictable behavior."

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.nrf52832.ps.v1.1%2Fgpiote.html

Or is the GPIOTE channels just the way to be able to deal with GPIO tasks and events? I see there is some more documentation regarding Port Events (PORT is an event that can be generated from multiple input pins using the GPIO DETECT signal.).

Does anyone know if it's possible to modify the BSP functionality to support more than 8 buttons? In this case 15? Is there a way to modify the BSP functions to support Port Events (if this is the way that is required for more I/O)? If so how would this be done?

Thanks!

RE: nRF52832 Custom Board Pin In Use By GPIOTE Fault in BSP

hmolesworth — Tue, 27 Aug 2019 15:50:02 GMT

Worth checking these (slightly confusing) mappings, as Button 1 isn't ..:

#define BUTTON_2        14
#define SPIM2_MISO_PIN  14  // SPI Master In Slave Out GPIO pin number.
#define ARDUINO_3_PIN   14  // Digital pin 3

#define #define BSP_BUTTON_1   BUTTON_2
BUTTONS_LIST       { BUTTON_1, BUTTON_2, BUTTON_3, BUTTON_4 }

There are a few others worth reviewing:

#define BSP_BOARD_BUTTON_2 2

#ifdef BSP_BUTTON_2
#define BSP_BUTTON_2_MASK (1<<BSP_BUTTON_2)
#define BUTTON_CAPSLOCK   BSP_BUTTON_2_MASK

#define BTN_ID_WAKEUP             0  /**< ID of button used to wake up the application. */
#define BTN_ID_SLEEP              0  /**< ID of button used to put the application into sleep mode. */
#define BTN_ID_DISCONNECT         0  /**< ID of button used to gracefully terminate a connection on long press. */
#define BTN_ID_WAKEUP_BOND_DELETE 1  /**< ID of button used to wake up the application and delete all bonding information. */
#define BTN_ID_WHITELIST_OFF      1  /**< ID of button used to turn off usage of the whitelist. */

Since Button 1 is really button 2 fiddling with (say) the whitelist can have unexpected pin assignments .. I was confused, if I recall ..