which changes are require in code when use of wakeup button ?

RE: which changes are require in code when use of wakeup button ?

VSN — Mon, 15 Apr 2019 12:22:49 GMT

**@brief Application's Stack ANT event handler.
 *
 * @param[in]   p_ant_evt   Event received from the stack.
 */
static void on_ant_evt(ant_evt_t * p_ant_evt)
{
	uint32_t err_code;
    /*if (p_ant_evt->channel == ANT_HRMRX_ANT_CHANNEL)// oeration of the HRT channel
    {
        switch (p_ant_evt->event)
        {
            case EVENT_RX:
                on_ant_evt_rx(p_ant_evt);
                break;

            case EVENT_CHANNEL_CLOSED:
                on_ant_evt_channel_closed();
                break;

            default:
                // No implementation needed.
                break;
        }
    }*/
		
		if (p_ant_evt->channel == ANT_FALCOTX_ANT_CHANNEL) // operation of the falco-motor channel 
		{
			 switch (p_ant_evt->event)
        {
						case EVENT_TX: // if transmisson 
                 //channel_event_handle(event); // boradcast the Hx_M motor  data  
									on_ant_evt_tx(p_ant_evt);		
                 break;	
					
            case EVENT_RX:
                on_ant_evt_rx(p_ant_evt);
                break;

            case EVENT_CHANNEL_CLOSED:
                on_ant_evt_channel_closed();

						err_code = sd_ant_channel_open(ANT_FALCOTX_ANT_CHANNEL); // open the Motor CH0 
								APP_ERROR_CHECK(err_code);
	            
              
                break;

            default:
                // No implementation needed.
                break;
        }
			
			
		}
   else if (p_ant_evt->channel == ANT_FALCOTTX_ANT_CHANNEL) // operation of the falco-motor channel 
		{
			 switch (p_ant_evt->event)
        {
						case EVENT_TX: // if transmisson 
                 //channel_event_handle(event); // boradcast the Hx_M TS sensor data
									on_ant_evt_tx(p_ant_evt);	
                 break;
						
            case EVENT_RX:
                on_ant_evt_rx(p_ant_evt);
                break;

            case EVENT_CHANNEL_CLOSED:
                on_ant_evt_channel_closed();
						
								err_code = sd_ant_channel_open(ANT_FALCOTTX_ANT_CHANNEL);// open the TS CH1 
								APP_ERROR_CHECK(err_code);				
							
                break;

            default:
                // No implementation needed.
                break;
        }
			
			
		}

RE: which changes are require in code when use of wakeup button ?

VSN — Mon, 15 Apr 2019 12:18:37 GMT

There is need to reopen channel of ANT to receive data then how this function reinitialize at main() ?

RE: which changes are require in code when use of wakeup button ?

VSN — Mon, 15 Apr 2019 12:10:47 GMT

yes sir I checked it.But what exact changes are required in main() file

RE: which changes are require in code when use of wakeup button ?

Kenneth — Mon, 08 Apr 2019 09:16:06 GMT

Hi,

After wakeup from system OFF the code execution will start from the beginning of main() - same as Power On and soft reset. You need to check NRF_POWER -> RESETREAS register to find the cause of reset (e.g. wakeup from System OFF).

Best regards,
Kenneth

RE: which changes are require in code when use of wakeup button ?

VSN — Fri, 05 Apr 2019 07:36:27 GMT

Hello sir,After system power off reset button is activated at p0.23 and SRU532 module is on but data will not come.There is any re-initialization is required after system power off? e.g channel re-initialization.devzone.nordicsemi.com/.../ble_5F00_ant_5F00_app_5F00_hrm_5F00_s310_5F00_pca10028.uvprojx

I have attached my source code please find this attachment

RE: which changes are require in code when use of wakeup button ?

VSN — Thu, 14 Mar 2019 12:50:28 GMT

Ok I will check it.Thank you for response

RE: which changes are require in code when use of wakeup button ?

Kenneth — Thu, 14 Mar 2019 12:19:20 GMT

I don't have a good suggestion than to study the ble_app_uart example to try to find the cause. Maybe you can add debug output, and for instance print out the BLE events that occurs, and compare if some events are missing or changed.

RE: which changes are require in code when use of wakeup button ?

VSN — Thu, 14 Mar 2019 11:13:06 GMT

Thank you for response.I have define "#define WAKEUP_BUTTON_ID BUTTON_A" and uncomment lines "err_code = bsp_buttons_enable((1 << WAKEUP_BUTTON_ID) | (1 << BOND_DELETE_ALL_BUTTON_ID));
APP_ERROR_CHECK(err_code); " and reset button is added externally to SRU532 module at pin p0.23.When systems power on then module become on and after 3 minutes it will auto off.after that press rest button then it gives data when connected with Android App.First time of reset pressing data is given but after that it is connected with App but not gives data.Please give me solution for that.

RE: which changes are require in code when use of wakeup button ?

Kenneth — Mon, 11 Mar 2019 15:16:10 GMT

The easiest may just be to have a global variable that you set on button press, and when advertisement time-out (BLE_ADV_EVT_IDLE event), then check if the global variable is set, and if set then clear global variable and start advertisement again.

RE: which changes are require in code when use of wakeup button ?

VSN — Fri, 08 Mar 2019 09:50:06 GMT

Thank you for response.I want only one button in use #define BUTTON_A 23 for reset #define APP_ADV_TIMEOUT_IN_SECONDS 180, this time.Then what exact changes are require to do that?

RE: which changes are require in code when use of wakeup button ?

Kenneth — Thu, 07 Mar 2019 09:20:00 GMT

There is an old tutorial on board support package, maybe you can take a look at it:
https://devzone.nordicsemi.com/tutorials/b/software-development-kit/posts/board-support-package-bsp

RE: which changes are require in code when use of wakeup button ?

VSN — Wed, 06 Mar 2019 05:35:28 GMT

Thanks for it.I want one button used for reset BLE advertising time which is by default 180 sec in given code.Here used SRU532 module,SDK 9.0 and softdevice s310 for nRF51422.How one pin of SRU532 module is configured from software as well as hardware side?

 #include <stdbool.h> #include <stdint.h> #include <stdio.h> #include <string.h> #include "app_uart.h" #include "app_error.h" #include "nrf_delay.h" #include "nordic_common.h" #include "nrf.h" #include "app_error.h" #include "nrf_gpio.h" #include "nrf51_bitfields.h" #include "ble.h" #include "ble_hci.h" #include "ble_srv_common.h" #include "ble_advdata.h" #include "ble_hrs.h" #include "ble_dis.h" #include "ble_conn_params.h" #include "ble_nus.h" #include "boards.h" #include "sensorsim.h" #include "softdevice_h #include "app_timer.h" #include "device_manager.h" #include "ant_parameters.h" #include "ant_interface.h" #include "pstorage.h" #include "app_trace.h" #include "bsp.h" #include "ant_error.h" #include "ant_stack_config.h" #include "ant_stack_ha

//#include "nrf_drv_rtc.h" //#include "nrf_drv_clock.h"

#define WAKEUP_BUTTON_ID #define BOND_DELETE_ALL_BUTTON_ID

#define DEVICE_NAME

//#define DEVICE_NAME #define MANUFACTURER_NAME #define APP_ADV_INTERVAL #define APP_ADV_TIMEOUT_IN_SECONDS #define NUS_SERVICE_UUID_TYPE

#define IS_SRVC_CHANGED_CHARACT_PRESENT #define APP_TIMER_PRESCALER //#define APP_TIMER_MAX_TIMERS #define APP_TIMER_MAX_TIMERS #define APP_TIMER_OP_QUEUE_SIZE

#define MOTOR_DATA_MEAS_INTERVAL //#define TS_DATA_MEAS_INTERVAL

#define SECOND_1_25_MS_UNITS #define SECOND_10_MS_UNITS #define MIN_CONN_INTERVAL #define MAX_CONN_INTERVAL #define SLAVE_LATENCY #define CONN_SUP_TIMEOUT

#define FIRST_CONN_PARAMS_UPDATE_DELAY #define NEXT_CONN_PARAMS_UPDATE_DELAY #define MAX_CONN_PARAMS_UPDATE_COUNT

#define SEC_PARAM_TIMEOUT #define SEC_PARAM_BOND #define SEC_PARAM_MITM #define SEC_PARAM_IO_CAPABILITIES #define SEC_PARAM_OOB #define SEC_PARAM_MIN_KEY_SIZE #define SEC_PARAM_MAX_KEY_SIZE

#define DEAD_BEEF

andler.h" ndler_types.h" 0 /**< Button used to wake up the application. */ 1 /**< Button used for deleting all bonded centrals during startup. */ "Nordic_UART" /**< Name of device. Will be included in the advertising data. */ "nrf51422_HRM" /**< Name of device. Will be included in the advertising data. */ "NordicSemiconductor" /**< Manufacturer. Will be passed to Device Information Service. */ 40 /**< The advertising interval (in units of 0.625 ms. This value corresponds to 25 ms). */ 3600 /**< The advertising timeout in units of seconds. */ BLE_UUID_TYPE_VENDOR_BEGIN /**< UUID type for the Nordic UART Service (vendor specific). */ 0 /**< Whether or not to include the service_changed characteristic. If not enabled, the server's database cannot be changed for the lifetime of the device */ 0 /**< Value of the RTC1 PRESCALER register. */ (2 + BSP_APP_TIMERS_NUMBER) /**< Maximum number of simultaneously created timers. */ (4 + BSP_APP_TIMERS_NUMBER) /**< Maximum number of simultaneously created timers. */ 4 /**< Size of timer operation queues. */ APP_TIMER_TICKS(500, APP_TIMER_PRESCALER) /**< MOTOR data measurement interval (ticks). */ APP_TIMER_TICKS(1000, APP_TIMER_PRESCALER) /**< Torque sensor data measurement interval (ticks). */ 800 /**< Definition of 1 second, when 1 unit is 1.25 ms. */ 100 /**< Definition of 1 second, when 1 unit is 10 ms. */ (SECOND_1_25_MS_UNITS / 2) /**< Minimum acceptable connection interval (0.5 seconds), Connection interval uses 1.25 ms units. */ (SECOND_1_25_MS_UNITS) /**< Maximum acceptable connection interval (1 second), Connection interval uses 1.25 ms units. */ 0 /**< Slave latency. */ (4 * SECOND_10_MS_UNITS) /**< Connection supervisory timeout (4 seconds), Supervision Timeout uses 10 ms units. */ APP_TIMER_TICKS(5000, APP_TIMER_PRESCALER) /**< Time from initiating event (connect or start of notification) to first time sd_ble_gap_conn_param_update is called (5 seconds). */ APP_TIMER_TICKS(30000, APP_TIMER_PRESCALER) /**< Time between each call to sd_ble_gap_conn_param_update after the first call (30 seconds). */ 3 /**< Number of attempts before giving up the connection parameter negotiation. */ 30 /**< Timeout for Pairing Request or Security Request (in seconds). */ 1 /**< Perform bonding. */ 0 /**< Man In The Middle protection not required. */ BLE_GAP_IO_CAPS_NONE /**< No I/O capabilities. */ 0 /**< Out Of Band data not available. */ 7 /**< Minimum encryption key size. */ 16 /**< Maximum encryption key size. */ 0xDEADBEEF /**< Value used as error code on stack dump, can be used to identify stack location on stack unwind. */

#define BOND_DELETE_ALL_BUTTON_ID, It is require when wakeup button in use?

uint32_t bsp_buttons_enable()
{
#if (BUTTONS_NUMBER > 0) && !defined(BSP_SIMPLE)
    return app_button_enable();
#else
    return NRF_ERROR_NOT_SUPPORTED;
#endif
}

uint32_t bsp_buttons_disable()
{
#if (BUTTONS_NUMBER > 0) && !defined(BSP_SIMPLE)
    return app_button_disable();
#else
    return NRF_ERROR_NOT_SUPPORTED;
#endif
}

uint32_t bsp_wakeup_buttons_set(uint32_t wakeup_buttons)
{
#if (BUTTONS_NUMBER > 0) && !defined(BSP_SIMPLE)
    for (uint32_t i = 0; i < BUTTONS_NUMBER; i++)
    {
        uint32_t new_cnf = NRF_GPIO->PIN_CNF[m_buttons_list[i]];
        uint32_t new_sense = ((1 << i) & wakeup_buttons) ? GPIO_PIN_CNF_SENSE_Low : GPIO_PIN_CNF_SENSE_Disabled;
        new_cnf &= ~GPIO_PIN_CNF_SENSE_Msk;
        new_cnf |= (new_sense << GPIO_PIN_CNF_SENSE_Pos);
        NRF_GPIO->PIN_CNF[m_buttons_list[i]] = new_cnf;
    }
    return NRF_SUCCESS;
#else
    return NRF_ERROR_NOT_SUPPORTED;
#endif

There is need of change in bsp.c file?

#define BUTTONS_NUMBER 4

//IO board pull-up buttons
/*#define BUTTON_A     23 //BUTTON A on N5 Starter Kit IO Board
#define BUTTON_B     2  //BUTTON B on N5 Starter Kit IO Board
#define BUTTON_C     12 //BUTTON C on N5 Starter Kit IO Board
#define BUTTON_D     11 //BUTTON D on N5 Starter Kit IO Board
#define BUTTON_PULL  NRF_GPIO_PIN_PULLUP*/

//SRU532 board pull-up buttons
#define BUTTON_A     23 //BUTTON A on N5 Starter Kit IO Board
#define BUTTON_B     2  //BUTTON B on N5 Starter Kit IO Board
#define BUTTON_C     30 //BUTTON C on N5 Starter Kit IO Board
#define BUTTON_D     10 //BUTTON D on N5 Starter Kit IO Board
#define BUTTON_PULL  NRF_GPIO_PIN_PULLUP




#define BSP_BUTTON_0   BUTTON_A
#define BSP_BUTTON_1   BUTTON_B
#define BSP_BUTTON_2   BUTTON_C
#define BSP_BUTTON_3   BUTTON_D

#define BSP_BUTTON_0_MASK (1<<BSP_BUTTON_0)
#define BSP_BUTTON_1_MASK (1<<BSP_BUTTON_1)
#define BSP_BUTTON_2_MASK (1<<BSP_BUTTON_2)
#define BSP_BUTTON_3_MASK (1<<BSP_BUTTON_3)

#define BUTTONS_MASK   0x00801804 // b100000000001100000000100
#define BUTTONS_LIST { BUTTON_A, BUTTON_B, BUTTON_C, BUTTON_D }

//Battery board pull-up switches
#define SWITCH_1     5  // Switch 1 on N5 Starter Kit Battery Board
#define SWITCH_2     0  // Switch 2 on N5 Starter Kit Battery Board
#define SWITCH_3     6  // Switch 3 on N5 Starter Kit Battery Board
#define SWITCH_4     24 // Switch 4 on N5 Starter Kit Battery Board
#define SWITCH_5     9  // Switch 5 on N5 Starter Kit Battery Board
#define SWITCH_PULL  NRF_GPIO_PIN_PULLUP

#define SWITCHES_NUMBER 5

#define BSP_SWITCH_0 SWITCH_1
#define BSP_SWITCH_1 SWITCH_2
#define BSP_SWITCH_2 SWITCH_3
#define BSP_SWITCH_3 SWITCH_4
#define BSP_SWITCH_4 SWITCH_5

#define SWITCHES_MASK 0x01000261

#endif

Want to use one button from it,how can I use it at hardware as well as in software?

RE: which changes are require in code when use of wakeup button ?

Kenneth — Tue, 05 Mar 2019 14:25:23 GMT

Hi,

Please refer for instance to the \examples\ble_peripheral\ble_app_hids_keyboard on how to achieve this:

[...]

uint32_t bsp_btn_ble_sleep_mode_prepare(void)
{
    uint32_t err_code = bsp_wakeup_button_enable(BTN_ID_WAKEUP); 
    RETURN_ON_ERROR_NOT_NOT_SUPPORTED(err_code);

    err_code = bsp_wakeup_button_enable(BTN_ID_WAKEUP_BOND_DELETE); 
    RETURN_ON_ERROR_NOT_NOT_SUPPORTED(err_code);
    
    return NRF_SUCCESS;
}

[...]

static void sleep_mode_enter(void)
{
    uint32_t err_code = bsp_indication_set(BSP_INDICATE_IDLE);

    APP_ERROR_CHECK(err_code);

    // Prepare wakeup buttons.
    err_code = bsp_btn_ble_sleep_mode_prepare();
    APP_ERROR_CHECK(err_code);

    // Go to system-off mode (this function will not return; wakeup will cause a reset).
    err_code = sd_power_system_off();
    APP_ERROR_CHECK(err_code);
}

[...]

sleep_mode_enter();
while(1);

[...]