ArmMbedOS是专为物联网中的“事物”而设计的开源嵌入式操作系统资源-CSDN文库

共2000个文件

h：816个

c：555个

cpp：452个

操作系统

前沿技术

8 浏览量 2023-12-03 12:01:04 上传评论收藏 75.05MB ZIP 举报

资源推荐

资源详情

资源评论

收起资源包目录

Arm Mbed OS 是专为物联网中的“事物”而设计的开源嵌入式操作系统（2000个子文件）

arm_common_tables.c 841KB

arm_dct4_init_f32.c 770KB

arm_dct4_init_q31.c 409KB

arm_rfft_init_f32.c 354KB

arm_dct4_init_q15.c 268KB

ssl_tls.c 264KB

arm_rfft_init_q31.c 211KB

configuration_store.c 171KB

arm_rfft_init_q15.c 139KB

ssl_srv.c 136KB

splashImage11.c 122KB

splashImage12.c 122KB

splashImage14.c 122KB

splashImage15.c 122KB

splashImage13.c 122KB

splashImage10.c 122KB

splashImage02.c 122KB

splashImage08.c 122KB

splashImage06.c 122KB

splashImage03.c 122KB

splashImage04.c 122KB

splashImage07.c 122KB

splashImage05.c 122KB

splashImage09.c 122KB

splashImage01.c 122KB

sn_coap_protocol.c 118KB

ssl_cli.c 117KB

device_manager_peripheral.c 110KB

usb1_function_dataio.c 108KB

usb0_function_dataio.c 108KB

usb1_host_dataio.c 99KB

usb0_host_dataio.c 99KB

ssl_ciphersuites.c 98KB

usb1_function_lib.c 76KB

usb0_function_lib.c 75KB

x509_crt.c 72KB

rsa.c 69KB

lfs.c 67KB

ecp.c 66KB

pstorage.c 59KB

bignum.c 58KB

usb1_host_lib.c 58KB

usb0_host_lib.c 57KB

fds.c 57KB

ecp_curves.c 56KB

ohci_wrapp_RZ_A1.c 55KB

arm_cfft_radix4_q15.c 54KB

aes.c 51KB

sn_coap_builder.c 47KB

em_usbd.c 47KB

cipher_wrap.c 44KB

pkparse.c 42KB

error.c 42KB

arm_conv_partial_fast_q15.c 42KB

unity.c 40KB

arm_cfft_radix4_q31.c 39KB

arm_conv_fast_q15.c 38KB

ecjpake.c 37KB

arm_correlate_fast_q15.c 36KB

aria.c 36KB

support_funcs.c 34KB

camellia.c 34KB

arm_cfft_radix4_f32.c 34KB

sn_coap_parser.c 33KB

cmac.c 32KB

usb1_function_dmacdrv.c 31KB

usb0_function_dmacdrv.c 31KB

usb0_host_dmacdrv.c 31KB

usb1_host_dmacdrv.c 31KB

usb0_host_dmacdrv.c 31KB

usb1_host_dmacdrv.c 31KB

des.c 31KB

gcm.c 30KB

arm_fir_f32.c 29KB

x509.c 29KB

ble_advdata.c 28KB

usb0_host_drv_api.c 27KB

usb1_host_drv_api.c 27KB

usb0_host_userdef.c 27KB

usb1_host_userdef.c 27KB

usb0_host_userdef.c 27KB

usb1_host_userdef.c 27KB

id_manager.c 27KB

usb0_function_userdef.c 27KB

usb1_function_userdef.c 27KB

usb0_function_userdef.c 27KB

usb1_function_userdef.c 27KB

共 2000 条

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.

"New functionality" describes how to use new features and functionality offered by this version of the SoftDevice. Not all newNote:

functionality may be covered; the release notes will contain a full list of new features and functionality.

Each section describes how to migrate to a given version from the previous version. If you are migrating to the current version from the

previous version, follow the instructions in that section. To migrate between versions that are more than one version apart, follow the

migration steps for all intermediate versions in order.

Example: To migrate from version 5.0.0 to version 5.2.0, first follow the instructions to migrate to version 5.1.0 from version 5.0.0, then follow

the instructions to migrate to version 5.2.0 from version 5.1.0.

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

Change IROM1 Start to . 0x23000

If the project uses a scatter file or linker script instead, they must be updated accordingly.

The RAM usage of the SoftDevice has also changed. should be used to find the APP_RAM_BASE for a particular sd_ble_enable()

configuration.

API renaming and updates

Some APIs are renamed or removed. Applications that use the old API names must be updated:

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()

NRF_CLOCK_LF_XTAL_ACCURACY renamed to NRF_CLOCK_LF_ACCURACY

nrf_clock_lf_cfg_t struct member renamed to .xtal_accuracy accuracy

A new event BLE_GAP_EVT_PHY_UPDATE_REQUEST has been added. The application must check for this event and respond to it

by calling the SV call sd_ble_gap_phy_update(). For more information, please refer to the 2 Mbps PHY support section in New

functionality.

RC Oscillator accuracy

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

may be raised when a PHY Update procedure is completed but the application is not required to take any actions for this event. DATE,

API Updates

A new SV call, , has been added to request the controller to attempt to change to a new PHY, or tosd_ble_gap_phy_update()

respond to a peer-initiated PHY Update procedure.

Usage

ble_gap_phys_t phys = {BLE_GAP_PHY_2MBPS, BLE_GAP_PHY_2MBPS};

sd_ble_gap_phy_update(conn_handle, &phys);

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

case BLE_GAP_EVT_PHY_UPDATE_REQUEST:

{

/* The PHYs requested by the peer can be read from the event parameters:

p_ble_evt->evt.gap_evt.params.phy_update_request.peer_preferred_phys.

* Note that the peer's TX correponds to our RX and vice versa. */

/* Allow SoftDevice to choose PHY Update Procedure parameters automatically. */

ble_gap_phys_t phys = {BLE_GAP_PHY_AUTO, BLE_GAP_PHY_AUTO};

sd_ble_gap_phy_update(p_ble_evt->evt.gap_evt.conn_handle, &phys);

break;

}

case BLE_GAP_EVT_PHY_UPDATE:

{

if (p_ble_evt->evt.gap_evt.params.phy_update.status ==

BLE_HCI_STATUS_CODE_SUCCESS)

{

/* PHY Update Procedure completed, see

p_ble_evt->evt.gap_evt.params.phy_update.tx_phy and

p_ble_evt->evt.gap_evt.params.phy_update.rx_phy for the currently active PHYs of

the link. */

}

break;

}

Connection-Oriented Channels in LE Credit Based Flow Control Mode

The SoftDevice now supports Connection-Oriented Channels in the LE Credit Based Flow Control Mode. To be able to use this feature, the

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

Usage

/* Set L2CAP Connection Configuration for connection identified by coc_conn_cfg_tag

ble_cfg_t cfg;

memset(&cfg, 0, sizeof(ble_cfg_t));

cfg.conn_cfg.conn_cfg_tag = coc_conn_cfg_tag;

cfg.conn_cfg.params.l2cap_conn_cfg.rx_mps = BLE_L2CAP_MPS_MIN;

cfg.conn_cfg.params.l2cap_conn_cfg.tx_mps = BLE_L2CAP_MPS_MIN;

cfg.conn_cfg.params.l2cap_conn_cfg.rx_queue_size = 5;

cfg.conn_cfg.params.l2cap_conn_cfg.tx_queue_size = 5;

cfg.conn_cfg.params.l2cap_conn_cfg.ch_count = 1;

sd_ble_cfg_set(BLE_CONN_CFG_L2CAP, &cfg, ...);

[...]

/* Enable the BLE Stack */

sd_ble_enable(...);

Setting L2CAP Connection Configuration

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

uint16_t local_cid = BLE_L2CAP_CID_INVALID;

ble_l2cap_ch_setup_params_t ch_setup_params;

ch_setup_params.le_psm = 0x25;

ch_setup_params.rx_params.rx_mtu = BLE_L2CAP_MTU_MIN;

ch_setup_params.rx_params.rx_mps = BLE_L2CAP_MPS_MIN;

ch_setup_params.rx_params.sdu_buf = NULL;

sd_ble_l2cap_ch_setup(conn_handle, &local_cid, &ch_setup_params);

case BLE_L2CAP_EVT_CH_SETUP_REQUEST:

{

/* An L2CAP channel setup request has been received from the peer. */

uint16_t local_cid = p_ble_evt->evt.l2cap_evt.local_cid;

ble_l2cap_ch_setup_params_t ch_setup_params;

ch_setup_params.le_psm = 0x25;

ch_setup_params.rx_params.rx_mtu = BLE_L2CAP_MTU_MIN;

ch_setup_params.rx_params.rx_mps = BLE_L2CAP_MPS_MIN;

ch_setup_params.rx_params.sdu_buf = NULL;

sd_ble_l2cap_ch_setup(p_ble_evt->evt.l2cap_evt.conn_handle, &local_cid,

&ch_setup_params);

break;

}

The SV call can be used to transmit an SDU (Service Data Unit) on an L2CAP channel. The event sd_ble_l2cap_ch_tx() BLE_L2CAP_

is generated by the SoftDevice to notify the application that the SDU has been transmitted.EVT_CH_TX

Usage

Creating a new L2CAP Channel

Responding to a L2CAP Channel setup request

ble_data_t sdu_to_send;

uint8_t data[] = "Sample";

sdu_to_send.len = strlen(data);

sdu_to_send.p_data = data;

sd_ble_l2cap_ch_tx(conn_handle, local_cid, &sdu_to_send);

[...]

case BLE_L2CAP_EVT_CH_TX:

/* The SDU is transmitted. */

break;

[...]

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

is generated by the SoftDevice to notify the application that an SDU has been received. The application shall not_L2CAP_EVT_CH_RX

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

Usage

[...]

ble_data_t sdu_buf;

uint8_t data[150];

sdu_buf.len = strlen(data);

sdu_buf.p_data = data;

sd_ble_l2cap_ch_rx(conn_handle, local_cid, &sdu_buf));

[...]

case BLE_L2CAP_EVT_CH_RX:

/* An SDU is received by the SoftDevice from the peer and is available in

p_ble_evt->evt.l2cap_evt.params.rx.sdu_buf */

break;

[...]

Network Privacy Mode

The SoftDevice now supports the Network Privacy Mode. In Network Privacy Mode, a device will only accept advertising packets from peer

devices that contain private addresses.

Transmitting on an L2CAP Channel

Receiving on an L2CAP Channel

评论收藏

内容反馈

Java程序员-张凯

粉丝: 1w+
资源: 6834

Arm Mbed OS 是专为物联网中的“事物”而设计的开源嵌入式操作系统

Arm Mbed OS是专为物联网中的“事物”设计的开源嵌入式操作系统

mbed-os：Arm Mbed OS是为物联网设计的平台操作系统

Arm Mbed OS:专为物联网设计的平台操作系统-开源

Arm Mbed OS是专为物联网设计的平台操作系统-C/C++开发

cpp-ARMmbedOS是为物联网设计的平台操作系统

PlatformIO Storage:物联网开发的开源生态系统-开源

blynk-library：用于嵌入式硬件的Blynk库。 适用于Arduino，ESP8266，Raspberry Pi，英特尔EdisonGalileo，LinkIt ONE，Particle CorePhoton，Energia，ARM mbed等

STM32循迹小车（灰度+OpenMV权重判断）

谭浩强C语言程序设计第五版详细答案

MQTT协议设备客户端与图传APP.zip

北邮国院，embeddedSystem嵌入式系统期末复习

lcd1602程序流程图

mingw64.zip

Keil.STM32H7xx-DFP.3.1.1.pack

基于stm32f407的示波器+FFT频谱分析

zlib-1.2.13.tar.gz

c51单片机流水灯c51单片机流水灯

C语言求一个正整数的位数

基于STM32的FFT频谱分析+波形识别

ORIGIN消除demo字样，适用ORIGIN2018版本

猴子吃桃问题c语言.猴子吃桃问题c语言

vc6.0企业版

基于51单片机智能温控风扇设计

STM32CubeIDE 1.14.0 自动补全代码

这里提供的是《C Primer Plus》第六版的高清 PDF 下载，内容完整，附带目录标签

【软件下载】Modbus Poll 7.0.1 + Modbus Slave 6.1.3

STM32F103系列的HAL库函数说明（中文版）

最新资源

blynk-library：用于嵌入式硬件的Blynk库。适用于Arduino，ESP8266，Raspberry Pi，英特尔EdisonGalileo，LinkIt ONE，Particle CorePhoton，Energia，ARM mbed等