"app_button" functions doesn't work on XL1 gpio "P0.00"

RE: "app_button" functions doesn't work on XL1 gpio "P0.00"

Coder_hope — Tue, 28 Apr 2020 01:00:07 GMT

thank you very much,I think I should creat my own topic, that would be helpful.

RE: "app_button" functions doesn't work on XL1 gpio "P0.00"

Hugo — Mon, 27 Apr 2020 18:46:01 GMT

fine,
you might want to check NRF_GPIO->PIN_CNF[0] compared to NRF_GPIO->PIN_CNF[1], after config, and during loop.
If it change, something wrong happened, try to find where.
If it's not the case, you might need to create you own topic, as it's not the same bug than me 🙂
You might have a faster answer from someone from Nordic. Also, you might need to give more details about your problem.

RE: "app_button" functions doesn't work on XL1 gpio "P0.00"

Coder_hope — Mon, 27 Apr 2020 11:16:11 GMT

Thank you ,I do not use uart and I only use P0.00 to drive LED, I am sure that I didn`t init "NULL" in my gpio`s initlization.

this bug confused me for days。

RE: "app_button" functions doesn't work on XL1 gpio "P0.00"

Hugo — Mon, 27 Apr 2020 11:05:56 GMT

My problem was basically:
-I init the P0 fine
-I accidentally init again P0, though something like:

    app_uart_comm_params_t const comm_params =
    {
        .rx_pin_no    = NULL, //don't write NULL here but -1
        .tx_pin_no    = TX_PIN_NUMBER,
        .rts_pin_no   = RTS_PIN_NUMBER,
        .cts_pin_no   = CTS_PIN_NUMBER,

NULL was a very bad idea and "-1" worked much better. I hope this helps!

RE: "app_button" functions doesn't work on XL1 gpio "P0.00"

Coder_hope — Mon, 27 Apr 2020 10:48:54 GMT

I have the same issue on 52832,without 32.768k,config with this:

#define NRFX_CLOCK_CONFIG_LF_SRC 0
#define CLOCK_CONFIG_LF_SRC 0

#define NRF_SDH_CLOCK_LF_SRC 0

P0.01 works well,driving a LED,

P0.00 connected to LED too,but is not undercontrl.

RE: "app_button" functions doesn't work on XL1 gpio "P0.00"

Hugo — Thu, 14 Feb 2019 13:15:04 GMT

Thank you.
Actually, I got the bug: it's from the "..." after the init.
On several driver, asking me a pin that do not exist, I wrote "NULL" instead of the pin name. Null was unfortunately pin P0.00.
Sorry, I guess it was obvious, I was sure it had something to do with the clock setting.now it works perfect! thanks for your help!

RE: "app_button" functions doesn't work on XL1 gpio "P0.00"

Vidar Berg — Mon, 11 Feb 2019 10:26:23 GMT

Please try attached example and see if it works on your board. It works on the DK if you cut SB1.

devzone.nordicsemi.com/.../ble_5F00_app_5F00_uart_5F00_w_5F00_app_5F00_button.zip

RE: "app_button" functions doesn't work on XL1 gpio "P0.00"

Vidar Berg — Fri, 08 Feb 2019 12:11:34 GMT

Hi,

PIN0.0 is configured as input with pull-up and sense for low level according to log output. PIN_CNF[x] has a bit-field for SENSE configuration. The way I wrote it was a bit misleading. You can see the register description here.

Anyway, can you log the P0.0 register from your main loop to see if the value remains the same?

RE: "app_button" functions doesn't work on XL1 gpio "P0.00"

Hugo — Fri, 08 Feb 2019 11:22:23 GMT

Hi Vidar,

Thanks for your help.

of course:

#define BUTTON_PULL NRF_GPIO_PIN_PULLUP

Also, NRF_GPIO->PIN_CNF[0].SENSE doesn't exist. NRF_GPIO->PIN_CNF[PIN] is an integer. this is what I get (button 0 is 0):

    NRF_LOG_INFO("NRF_GPIO->PIN_CNF[0] %d",NRF_GPIO->PIN_CNF[0]);
    NRF_LOG_INFO("NRF_GPIO->PIN_CNF[BUTTON_1] %d",NRF_GPIO->PIN_CNF[BUTTON_1]);
     	nrf_gpio_cfg_input (0,NRF_GPIO_PIN_PULLUP);
//! if you want more buttons, change value GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS in sdk_config.h
    static app_button_cfg_t p_button[] = {  {BUTTON_0, APP_BUTTON_PUSH, BUTTON_PULL, button_pressed_handler},
                                            {BUTTON_1, APP_BUTTON_PUSH, BUTTON_PULL, button_pressed_handler},
                                            {BUTTON_2, APP_BUTTON_PUSH, BUTTON_PULL, button_pressed_handler},
                                            {BUTTON_3, APP_BUTTON_RELEASE, BUTTON_PULL, button_pressed_handler},
                                            {BUTTON_4, APP_BUTTON_PUSH, BUTTON_PULL, button_pressed_handler}};

    NRF_LOG_INFO("NRF_GPIO->PIN_CNF[0] %d",NRF_GPIO->PIN_CNF[0]);
    NRF_LOG_INFO("NRF_GPIO->PIN_CNF[BUTTON_1] %d",NRF_GPIO->PIN_CNF[BUTTON_1]);
    app_button_init(p_button,sizeof(p_button) / sizeof(p_button[0]),100);
    NRF_LOG_INFO("NRF_GPIO->PIN_CNF[0] %d",NRF_GPIO->PIN_CNF[0]);
    NRF_LOG_INFO("NRF_GPIO->PIN_CNF[BUTTON_1] %d",NRF_GPIO->PIN_CNF[BUTTON_1]);
    app_button_enable();
    NRF_LOG_INFO("NRF_GPIO->PIN_CNF[0] %d",NRF_GPIO->PIN_CNF[0]);
    NRF_LOG_INFO("NRF_GPIO->PIN_CNF[BUTTON_1] %d",NRF_GPIO->PIN_CNF[BUTTON_1]);

and its log:

<info> app: NRF_GPIO->PIN_CNF[0] 2
<info> app: NRF_GPIO->PIN_CNF[BUTTON_1] 2
<info> app: NRF_GPIO->PIN_CNF[0] 12
<info> app: NRF_GPIO->PIN_CNF[BUTTON_1] 2
<info> app: NRF_GPIO->PIN_CNF[0] 12
<info> app: NRF_GPIO->PIN_CNF[BUTTON_1] 12
<info> app: NRF_GPIO->PIN_CNF[0] 196620
<info> app: NRF_GPIO->PIN_CNF[BUTTON_1] 196620

I'm sorry, I cannot give you my code. I tryed with no success to make a standalone app_button example. (it seems complicated with timers, clock, etc...). But you have all the interesting part.
Kind regards,

RE: "app_button" functions doesn't work on XL1 gpio "P0.00"

Vidar Berg — Fri, 08 Feb 2019 08:43:51 GMT

Is BUTTON_PULL defined as "pull up" in your board header? In that case I don't see why app_button_init would clear this setting. Could you upload your project here so I can try to replicate it? Also if you could verify that NRF_GPIO->PIN_CNF[0].SENSE is not '0' after app_button_enable().

RE: "app_button" functions doesn't work on XL1 gpio "P0.00"

Hugo — Thu, 07 Feb 2019 14:18:24 GMT

I'm using 5 buttons(P0.28 P0.30,P0.00,P0.02,P0.03). Code is working for the 4 other buttons. Defining the button "P0.00" to pin P0.31 (a sixth button no defined at all yet anywhere in the code), works very fine.

This is my code:

nrf_gpio_cfg_input (0,NRF_GPIO_PIN_PULLUP);
//! if you want more buttons, change value GPIOTE_CONFIG_NUM_OF_LOW_POWER_EVENTS in sdk_config.h
static app_button_cfg_t p_button[] = {  {BUTTON_1, APP_BUTTON_PUSH, BUTTON_PULL, button_pressed_handler},
                                            {BUTTON_2, APP_BUTTON_PUSH, BUTTON_PULL, button_pressed_handler},
                                            {BUTTON_3, APP_BUTTON_PUSH, BUTTON_PULL, button_pressed_handler},
                                            {BUTTON_4, APP_BUTTON_RELEASE, BUTTON_PULL, button_pressed_handler},
                                            {BUTTON_5, APP_BUTTON_PUSH, BUTTON_PULL, button_pressed_handler}};

    app_button_init(p_button,sizeof(p_button) / sizeof(p_button[0]),100);
    app_button_enable();

By making this new test, one more info: I'm using internal pull-up. This pull up is not active.and in it I specify the pin 0 as input pull up, so the app_button_init seems to erase this setting.
If I change to P0.31, the pull-up works great on P0.00
At last, even if the pull up is not active, connecting the pin to the ground or VCC does not call an handler.

RE: "app_button" functions doesn't work on XL1 gpio "P0.00"

Vidar Berg — Thu, 07 Feb 2019 13:49:33 GMT

Hello,

There shouldn't be any restrictions on P0.00 as long as you use the internal RC. Are you using the same button/IO configuration for all the pins you test with and do you have pull up/down enabled so that isn't floating?