<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Full event list and description on s132</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/19116/full-event-list-and-description-on-s132</link><description>I&amp;#39;m a user of nRF52 DK with S132.
I want to modify the event handler in the example application code such as ble_uart_c.
Where can i find the full list and description of events that S232 stack support ?</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 08 Jul 2022 12:10:59 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/19116/full-event-list-and-description-on-s132" /><item><title>RE: Full event list and description on s132</title><link>https://devzone.nordicsemi.com/thread/376202?ContentTypeID=1</link><pubDate>Fri, 08 Jul 2022 12:10:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fc52f674-31bb-4a61-ac18-3c4fc65ffe2b</guid><dc:creator>Marius Heil</dc:creator><description>&lt;p&gt;As I needed the same thing and it took me some time to compile the List, I am posting it here in case anyone needs the same list:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;//This list was taken from nRF SDK 17.1 from the S132 header files
//It is useful for looking up events if they are only known
//as decimal or binary numbers

  BLE_EVT_INVALID = 0 (0x0)

enum BLE_COMMON_EVTS
{
  BLE_EVT_USER_MEM_REQUEST = 1 (0x1),   /**&amp;lt; User Memory request. See @ref ble_evt_user_mem_request_t  \n Reply with @ref sd_ble_user_mem_reply. */
  BLE_EVT_USER_MEM_RELEASE = 2 (0x2),   /**&amp;lt; User Memory release. See @ref ble_evt_user_mem_release_t */
};

enum BLE_GAP_EVTS
{
  BLE_GAP_EVT_CONNECTED                   = 16 (0x10),  /**&amp;lt; Connected to peer.                              \n See @ref ble_gap_evt_connected_t             */
  BLE_GAP_EVT_DISCONNECTED                = 17 (0x11),  /**&amp;lt; Disconnected from peer.                         \n See @ref ble_gap_evt_disconnected_t.         */
  BLE_GAP_EVT_CONN_PARAM_UPDATE           = 18 (0x12),  /**&amp;lt; Connection Parameters updated.                  \n See @ref ble_gap_evt_conn_param_update_t.    */
  BLE_GAP_EVT_SEC_PARAMS_REQUEST          = 19 (0x13),  /**&amp;lt; Request to provide security parameters.         \n Reply with @ref sd_ble_gap_sec_params_reply.  \n See @ref ble_gap_evt_sec_params_request_t. */
  BLE_GAP_EVT_SEC_INFO_REQUEST            = 20 (0x14),  /**&amp;lt; Request to provide security information.        \n Reply with @ref sd_ble_gap_sec_info_reply.    \n See @ref ble_gap_evt_sec_info_request_t.   */
  BLE_GAP_EVT_PASSKEY_DISPLAY             = 21 (0x15),  /**&amp;lt; Request to display a passkey to the user.       \n In LESC Numeric Comparison, reply with @ref sd_ble_gap_auth_key_reply. \n See @ref ble_gap_evt_passkey_display_t. */
  BLE_GAP_EVT_KEY_PRESSED                 = 22 (0x16),  /**&amp;lt; Notification of a keypress on the remote device.\n See @ref ble_gap_evt_key_pressed_t           */
  BLE_GAP_EVT_AUTH_KEY_REQUEST            = 23 (0x17),  /**&amp;lt; Request to provide an authentication key.       \n Reply with @ref sd_ble_gap_auth_key_reply.    \n See @ref ble_gap_evt_auth_key_request_t.   */
  BLE_GAP_EVT_LESC_DHKEY_REQUEST          = 24 (0x18),  /**&amp;lt; Request to calculate an LE Secure Connections DHKey. \n Reply with @ref sd_ble_gap_lesc_dhkey_reply.  \n See @ref ble_gap_evt_lesc_dhkey_request_t */
  BLE_GAP_EVT_AUTH_STATUS                 = 25 (0x19),  /**&amp;lt; Authentication procedure completed with status. \n See @ref ble_gap_evt_auth_status_t.          */
  BLE_GAP_EVT_CONN_SEC_UPDATE             = 26 (0x1a),  /**&amp;lt; Connection security updated.                    \n See @ref ble_gap_evt_conn_sec_update_t.      */
  BLE_GAP_EVT_TIMEOUT                     = 27 (0x1b),  /**&amp;lt; Timeout expired.                                \n See @ref ble_gap_evt_timeout_t.              */
  BLE_GAP_EVT_RSSI_CHANGED                = 28 (0x1c),  /**&amp;lt; RSSI report.                                    \n See @ref ble_gap_evt_rssi_changed_t.         */
  BLE_GAP_EVT_ADV_REPORT                  = 29 (0x1d),  /**&amp;lt; Advertising report.                             \n See @ref ble_gap_evt_adv_report_t.           */
  BLE_GAP_EVT_SEC_REQUEST                 = 30 (0x1e),  /**&amp;lt; Security Request.                               \n Reply with @ref sd_ble_gap_authenticate  \n or with @ref sd_ble_gap_encrypt if required security information is available. \n See @ref ble_gap_evt_sec_request_t.          */
  BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST   = 31 (0x1f),  /**&amp;lt; Connection Parameter Update Request.            \n Reply with @ref sd_ble_gap_conn_param_update. \n See @ref ble_gap_evt_conn_param_update_request_t. */
  BLE_GAP_EVT_SCAN_REQ_REPORT             = 32 (0x20),  /**&amp;lt; Scan request report.                            \n See @ref ble_gap_evt_scan_req_report_t. */
  BLE_GAP_EVT_PHY_UPDATE_REQUEST          = 33 (0x21),  /**&amp;lt; PHY Update Request.                             \n Reply with @ref sd_ble_gap_phy_update. \n See @ref ble_gap_evt_phy_update_request_t. */
  BLE_GAP_EVT_PHY_UPDATE                  = 34 (0x22),  /**&amp;lt; PHY Update Procedure is complete.               \n See @ref ble_gap_evt_phy_update_t.           */
  BLE_GAP_EVT_DATA_LENGTH_UPDATE_REQUEST  = 35 (0x23),  /**&amp;lt; Data Length Update Request.                     \n Reply with @ref sd_ble_gap_data_length_update. \n See @ref ble_gap_evt_data_length_update_request_t. */
  BLE_GAP_EVT_DATA_LENGTH_UPDATE          = 36 (0x24),  /**&amp;lt; LL Data Channel PDU payload length updated.     \n See @ref ble_gap_evt_data_length_update_t. */
  BLE_GAP_EVT_QOS_CHANNEL_SURVEY_REPORT   = 37 (0x25),  /**&amp;lt; Channel survey report.                          \n See @ref ble_gap_evt_qos_channel_survey_report_t. */
  BLE_GAP_EVT_ADV_SET_TERMINATED          = 38 (0x26),  /**&amp;lt; Advertising set terminated.                     \n See @ref ble_gap_evt_adv_set_terminated_t. */
};

enum BLE_GATTC_EVTS
{
  BLE_GATTC_EVT_PRIM_SRVC_DISC_RSP               = 48 (0x30),  /**&amp;lt; Primary Service Discovery Response event.          \n See @ref ble_gattc_evt_prim_srvc_disc_rsp_t.          */
  BLE_GATTC_EVT_REL_DISC_RSP                     = 49 (0x31),  /**&amp;lt; Relationship Discovery Response event.             \n See @ref ble_gattc_evt_rel_disc_rsp_t.                */
  BLE_GATTC_EVT_CHAR_DISC_RSP                    = 50 (0x32),  /**&amp;lt; Characteristic Discovery Response event.           \n See @ref ble_gattc_evt_char_disc_rsp_t.               */
  BLE_GATTC_EVT_DESC_DISC_RSP                    = 51 (0x33),  /**&amp;lt; Descriptor Discovery Response event.               \n See @ref ble_gattc_evt_desc_disc_rsp_t.               */
  BLE_GATTC_EVT_ATTR_INFO_DISC_RSP               = 52 (0x34),  /**&amp;lt; Attribute Information Response event.              \n See @ref ble_gattc_evt_attr_info_disc_rsp_t. */
  BLE_GATTC_EVT_CHAR_VAL_BY_UUID_READ_RSP        = 53 (0x35),  /**&amp;lt; Read By UUID Response event.                       \n See @ref ble_gattc_evt_char_val_by_uuid_read_rsp_t.   */
  BLE_GATTC_EVT_READ_RSP                         = 54 (0x36),  /**&amp;lt; Read Response event.                               \n See @ref ble_gattc_evt_read_rsp_t.                    */
  BLE_GATTC_EVT_CHAR_VALS_READ_RSP               = 55 (0x37),  /**&amp;lt; Read multiple Response event.                      \n See @ref ble_gattc_evt_char_vals_read_rsp_t.          */
  BLE_GATTC_EVT_WRITE_RSP                        = 56 (0x38),  /**&amp;lt; Write Response event.                              \n See @ref ble_gattc_evt_write_rsp_t.                   */
  BLE_GATTC_EVT_HVX                              = 57 (0x39),  /**&amp;lt; Handle Value Notification or Indication event.     \n Confirm indication with @ref sd_ble_gattc_hv_confirm.  \n See @ref ble_gattc_evt_hvx_t. */
  BLE_GATTC_EVT_EXCHANGE_MTU_RSP                 = 58 (0x3a),  /**&amp;lt; Exchange MTU Response event.                       \n See @ref ble_gattc_evt_exchange_mtu_rsp_t.            */
  BLE_GATTC_EVT_TIMEOUT                          = 59 (0x3b),  /**&amp;lt; Timeout event.                                     \n See @ref ble_gattc_evt_timeout_t.                     */
  BLE_GATTC_EVT_WRITE_CMD_TX_COMPLETE            = 60 (0x3c),  /**&amp;lt; Write without Response transmission complete.      \n See @ref ble_gattc_evt_write_cmd_tx_complete_t.       */
};

enum BLE_GATTS_EVTS
{
  BLE_GATTS_EVT_WRITE                             = 80 (0x50),  /**&amp;lt; Write operation performed.                                           \n See @ref ble_gatts_evt_write_t.                 */
  BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST              = 81 (0x51),  /**&amp;lt; Read/Write Authorization request.                                    \n Reply with @ref sd_ble_gatts_rw_authorize_reply. \n See @ref ble_gatts_evt_rw_authorize_request_t. */
  BLE_GATTS_EVT_SYS_ATTR_MISSING                  = 82 (0x52),  /**&amp;lt; A persistent system attribute access is pending.                     \n Respond with @ref sd_ble_gatts_sys_attr_set.     \n See @ref ble_gatts_evt_sys_attr_missing_t.     */
  BLE_GATTS_EVT_HVC                               = 83 (0x53),  /**&amp;lt; Handle Value Confirmation.                                           \n See @ref ble_gatts_evt_hvc_t.                   */
  BLE_GATTS_EVT_SC_CONFIRM                        = 84 (0x54),  /**&amp;lt; Service Changed Confirmation.                                        \n No additional event structure applies.          */
  BLE_GATTS_EVT_EXCHANGE_MTU_REQUEST              = 85 (0x55),  /**&amp;lt; Exchange MTU Request.                                                \n Reply with @ref sd_ble_gatts_exchange_mtu_reply. \n See @ref ble_gatts_evt_exchange_mtu_request_t. */
  BLE_GATTS_EVT_TIMEOUT                           = 86 (0x56),  /**&amp;lt; Peer failed to respond to an ATT request in time.                    \n See @ref ble_gatts_evt_timeout_t.               */
  BLE_GATTS_EVT_HVN_TX_COMPLETE                   = 87 (0x57),  /**&amp;lt; Handle Value Notification transmission complete.                     \n See @ref ble_gatts_evt_hvn_tx_complete_t.       */
};

enum BLE_L2CAP_EVTS
{
  BLE_L2CAP_EVT_CH_SETUP_REQUEST      = 112 (0x70),    /**&amp;lt; L2CAP Channel Setup Request event. \n Reply with @ref sd_ble_l2cap_ch_setup. \n See @ref ble_l2cap_evt_ch_setup_request_t. */
  BLE_L2CAP_EVT_CH_SETUP_REFUSED      = 113 (0x71),    /**&amp;lt; L2CAP Channel Setup Refused event. \n See @ref ble_l2cap_evt_ch_setup_refused_t. */
  BLE_L2CAP_EVT_CH_SETUP              = 114 (0x72),    /**&amp;lt; L2CAP Channel Setup Completed event.  \n See @ref ble_l2cap_evt_ch_setup_t. */
  BLE_L2CAP_EVT_CH_RELEASED           = 115 (0x73),    /**&amp;lt; L2CAP Channel Released event. \n No additional event structure applies. */
  BLE_L2CAP_EVT_CH_SDU_BUF_RELEASED   = 116 (0x74),    /**&amp;lt; L2CAP Channel SDU data buffer released event. \n See @ref ble_l2cap_evt_ch_sdu_buf_released_t. */
  BLE_L2CAP_EVT_CH_CREDIT             = 117 (0x75),    /**&amp;lt; L2CAP Channel Credit received. \n See @ref ble_l2cap_evt_ch_credit_t. */
  BLE_L2CAP_EVT_CH_RX                 = 118 (0x76),    /**&amp;lt; L2CAP Channel SDU received. \n See @ref ble_l2cap_evt_ch_rx_t. */
  BLE_L2CAP_EVT_CH_TX                 = 119 (0x77),    /**&amp;lt; L2CAP Channel SDU transmitted. \n See @ref ble_l2cap_evt_ch_tx_t. */
};&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Full event list and description on s132</title><link>https://devzone.nordicsemi.com/thread/73956?ContentTypeID=1</link><pubDate>Sun, 22 Jan 2017 00:36:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:deac379e-73cb-4941-85d4-d91a847e3832</guid><dc:creator>Jusang Kim</dc:creator><description>&lt;p&gt;Thank you so much.
Let me try to do the way that you mentioned.&lt;/p&gt;
&lt;p&gt;Have a nice weekend.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Full event list and description on s132</title><link>https://devzone.nordicsemi.com/thread/73955?ContentTypeID=1</link><pubDate>Fri, 20 Jan 2017 07:48:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9846ca0c-3938-4c1d-a6fd-c6876b476b8c</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;You can find our API documentation &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v3.0.0/index.html?cp=2_3_0_1_1"&gt;here&lt;/a&gt;. Not sure what you want to do, but I recommend looking at the message sequence chart for the given procedure to know what events you should handle.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>