lis3dh三轴传感器计步实现C源码

s13x_nrf5x migration document

Introduction to the s13x_nrf5x migration document

About the document

This document describes how to migrate to new versions of the s130_nrf51 and s132_nrf52 SoftDevices. The s130_nrf51 and s132_nrf52

release notes should be read in conjunction with this document.

For each version, we have the following sections:

"Required changes" describes how an application would have used the previous version of the SoftDevice and how it must now use

this version for the given change.

the instructions to migrate to version 5.2.0 from version 5.1.0.

Copyright (c) Nordic Semiconductor ASA. All rights reserved.

s132_nrf52_5.0.0

This section describes how to migrate to s132_nrf52_5.0.0 from s132_nrf52_4.0.3.

Required changes

SoftDevice flash and RAM usage

The size of the SoftDevice has changed requiring a change to the application project file.

For Keil this means:

Go into the properties of the project and find the Target tab

The timeout source has been removed. Use the existing BLE_GAP_TIMEOUT_SRC_SECURITY_REQUEST BLE_GAP_EVT_AUTH_ST

instead.ATUS {auth_status: BLE_GAP_SEC_STATUS_TIMEOUT}

BLE_GAP_ADV_NONCON_INTERVAL_MIN has been removed because the lower limit for the advertising interval for non-connectable

advertisement has been lowered to .BLE_GAP_ADV_INTERVAL_MIN

The compatibility mode is removed because the SoftDevice now accepts overlappingBLE_GAP_OPT_COMPAT_MODE_2

peer-initiated Link Layer control procedures as a slave.

NRF_ERROR_BUSY will no longer be returned by , , sd_ble_gap_adv_start() sd_ble_gap_scan_start() sd_ble_gap_auth

and .enticate() sd_ble_gap_connect()

NRF_ERROR_BUSY can now be returned when calling , sd_ble_user_mem_reply() sd_ble_gatts_rw_authorize_reply()

or .sd_ble_gap_sec_params_reply()

The RC oscillator accuracy can now be set to any of the defined values and there is no default value anymore.NRF_CLOCK_LF_ACCURACY

In other words, the parameter now has the same functionality when used with the RCOSC clockaccuracynrf_clock_lf_cfg_t::

source as with the XTAL clock source. The RC oscillator accuracy should be set to a value appropriate for the chip.

New functionality

2 Mbps PHY support

This SoftDevice supports 2 Mbps PHY data transmission for already established connections. Either the application or the peer can request

switching to 2 Mbps PHY in order to achieve higher throughput. Both sides need to agree on the PHYs before a PHY change can occur. The

application has to respond to the PHY Update procedure when that is initiated by the peer, otherwise the link will be disconnected. This

makes it necessary for the application to pull a new event: . Another event, BLE_GAP_EVT_PHY_UPDATE_REQUEST BLE_GAP_EVT_PHY_UP

A new event, , has been added to notify the application that the peer has initiated a PHYBLE_GAP_EVT_PHY_UPDATE_REQUEST

Update procedure, to which the application must respond with its PHY preferences.

A new event, , has been added to notify the application that a self-initiated or peer-initiated PHYBLE_GAP_EVT_PHY_UPDATE

Update procedure has been completed.

Usage

application has to set an L2CAP connection configuration using the configuration API as shown below.sd_ble_cfg_set()

Usage

The usage of some of the SV calls and events related to this feature is explained below. For the complete list of SV calls and events, please

refer to the API documentation available in ble_l2cap.h.

A new SV call, , has been added to request the setup of an L2CAP channel, or to respond to a setup requestsd_ble_l2cap_ch_setup()

from a peer.

Usage

The SV call be used to provide the SoftDevice with a buffer to receive an SDU from the peer. The event sd_ble_l2cap_ch_rx () shall BLE

change the buffer provided to the SoftDevice before receiving the event.

Usage