STM32CubeX-CUBE-CELLULAR入门指南：2G, 3G, LTE Cat M1, NB-IoT连接

stm32cube

需积分: 9 76 浏览量更新于2024-07-18 收藏 2.45MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

“Getting started with the X-CUBE-CELLULAR - STM32Cube 扩展包，包含2G、3G、LTE Cat M1、NB-IoT的示例程序” 本文档详细介绍了STMicroelectronics的X-CUBE-CELLULAR，这是一个专为STM32Cube设计的扩展包，旨在提供STM32微控制器的蜂窝网络连接功能。该扩展包支持多种网络接入技术，包括2G、3G、LTE Category M1（Cat M1）以及窄带物联网（NB-IoT，也称为NB1），以满足不同场景下的无线通信需求。 X-CUBE-CELLULAR的主要特点是提供了一套标准化的API接口，这些接口基于HTTP协议，简化了云服务连接器的集成过程。通过这些API，开发者可以轻松地将设备连接到云端，并实现数据的双向传输——设备向服务器报告数据，同时接收远程服务器的命令。 STM32CubexX-CUBE-CELLULAR提供了一个应用示例，此示例程序展示了如何使用HTTP协议连接并订阅云服务。这有助于设备与服务器之间的数据交互，比如设备发送数据到服务器，以及服务器向设备发送指令。该扩展包适用于两种硬件平台：P-L496G-CELL01和P-L496G-CELL02。这两个细胞云包都包含一个基于STM32L496的Discovery主机板，通过STMod+连接器与附加的蜂窝调制解调器相连。P-L496G-CELL01的附加板采用了特定的蜂窝调制解调器，而P-L496G-CELL02可能有所不同，具体配置取决于实际的硬件选型。在使用X-CUBE-CELLULAR时，开发者需要了解STM32Cube生态系统，这是一个强大的软件开发环境，它提供了自动代码生成、HAL（硬件抽象层）库以及中间件等工具，极大地简化了STM32微控制器的开发工作。通过将X-CUBE-CELLULAR整合进STM32Cube，用户可以快速实现基于STM32的蜂窝通信应用，无需从头构建底层通信框架。为了开始使用X-CUBE-CELLULAR，开发者需要下载相应的STM32Cube扩展包，然后导入STM32CubeIDE或其它兼容的开发工具。根据提供的用户手册（UM2426）逐步配置项目，包括设置网络参数、调用API进行连接和通信，以及调试示例代码。此外，还需要了解和遵循相关的无线通信标准和法规，确保应用程序符合当地的网络要求和安全规范。 X-CUBE-CELLULAR是STM32开发者快速实现蜂窝网络连接功能的强大工具，无论是在2G、3G、Cat M1还是NB-IoT网络环境下，都能为IoT设备提供稳定可靠的通信支持。通过充分利用其提供的API和示例代码，开发者可以缩短产品开发周期，加速物联网应用的市场投放。

资源详情

资源推荐

Package description UM2426

12/72 UM2426 Rev 1

The cellular connectivity stack exposes two main interfaces to the application:

• The control plane interface: there are two interfaces for control. The cellular init library

provides an API to initialize SW components and starts the Cellular Service. The Data

Cache interface is used to read information related to cellular network like Signal

Strength. (RSSI), and to get event notification like network registration state changes

and network interface readiness.

• The data plane interface: also referred to as the COM interface, it is used to send and

receive TCP or UDP segments to and from a remote client or server. The interface is

based on standard BSD socket API in order to ease the integration of the application.

The IPC layer abstracts the actual HW bus interface used with the modem. The IPC

supports two logical channels, each composed of one Tx (to the IPC) and one Rx (from the

IPC). One is used for exchanging AT commands with the modem while the other one is

used to carry PPP frames when LwIP is used. The selection of the active channel is

controlled by Cellular Service.

4.3.2 Static architecture view

X-CUBE-CELLULAR static architecture is presented in Figure 3.

Figure 3. Static architecture view

06Y9

'HYHORSPHQWERDUGV

'ULYHUV

+DUGZDUHDEVWUDFWLRQOD\HU

0LGGOHZDUH

,3&

$7FXVWRP

$7VHUYLFH

0RGHP

V\VWHP

FRQWURO

26OLEUDU\&HOOXODU6HUYLFHOLEUDU\

&HOOXODU6HUYLFHWDVN

333R6L)

333FOLHQWWDVN

/Z,3

1HW,)333

)UHH5726

'DWD&DFKH

&20,)

VRFNHW$3,

&HOOXODU,QLW

1,)0$1

WDVN

$SSOLFDWLRQV

+773FOLHQW 3,1*

&RQQHFWLYLW\6HUYLFHOD\HU

;&8%(&(//8/$5$3,

VRIWZDUH

&06,6

8WLOLWLHV

&HOOXODU

6HUYLFH

&6//$3,

&6+/$3,

UM2426 Rev 1 13/72

UM2426 Package description

• HTTP client: implements an HTTP client, which sends requests to the

www.grovestreams.com cloud in the application. The HTTP client uses the Data Cache

to monitor the network interface state changes (from NIFMAN), and the COM socket

interface to send or receive HTTP packets over TCP. The HTTP client also implements

recovery as defined by GSMA TS 34 when a remote HTTP server is not reachable.

• Connectivity Service layer:

– Data Cache: framework that decouples the management of producer and

consumer data (resource). Any resource state updated by a producer is pushed to

the Data Cache (in RAM), which in turn informs the final consumer(s) to process

the updated resource state via the callback provided by the consumer application.

Data Cache is used by Cellular Service tasks to publish the Cellular network

information like RSSI. It is also used by NIFMAN to publish the network interface

readiness.

– COM IF: a library that provides a collection of BSD-like socket functions to open,

configure, and send or receive application PDU to remote TCP or UDP

applications.

– NIFMAN: the network interface manager task controls network interface

activation. When LwIP is used, NIFMAN monitors the PPP server status (on the

modem side), and starts or stops the PPP client accordingly. The application can

then monitor the network interface status before opening a socket for data

transfer.

– Cellular init library: exposes a basic function to initialize and start Cellular

Service components.

• PPP client task / PPPoSIF: optional component. It is only present when LwIP is used.

It is in charge of establishing the PPP link with the modem.

• LwIP / Net IF: the LwIP component and its adaptation to PPP.

• Cellular Service:

– Cellular Service task controls modem power-on and initialization, instructs the

modem to perform network registration, activates the PDN (PDP context), and

enters data transfer mode. It informs NIFMAN to setup the network interface (PPP

link). It uses AT service to send AT commands to the modem.

It implements a generic finite state machine to maintain consistent service state

based on modem internal state change events (such as FOTA or reset), network

registration state change events, and events related to the and PDP context

status. It implements the network friendly features (NFMC) as defined in [4]. For

example, when PDP activation fails because of a wrong APN, the Cellular Service

task performs a new attempt after expiration of a back-off timer.

The Cellular Service task stores the cellular configuration and network access

parameters into the Flash memory, and configure the modem as per need. The

configuration for example encompasses APN and CID settings, enabling and

disabling NFMC, and setting the back-off timers.

For system robustness, the Cellular Service task ensures that the modem is

always operational by regularly polling the modem RSSI.

– Cellular Service OS: is a library that offers a collection of functions to low-level

Cellular Service. The library serializes the access to the single AT channel

interface that is used to communicate with the modem. The functions are called by

the COM service and the Cellular Service task.

– Cellular Service library: offers a collection of blocking function calls to interact

with a modem. Cellular Service is in charge of translating the request from the

Package description UM2426

14/72 UM2426 Rev 1

Cellular Service task or COM service to a sequence of AT commands that must be

sent to the modem. It finally calls a callback function (from the Cellular Service

task or COM service) when an asynchronous event (URC) is received from the

modem.

– AT Service: provides a framework to send or receive AT commands to or from the

modem over IPC. The AT Core task is in charge of processing the Cellular Service

requests and translate them into AT commands. It is also in charge of processing

AT commands response and URCs from the modem and forward them to Cellular

Service. AT is split into two parts:

1. a generic part, "core" (AT framework and manage standard AT commands)

2. a specific part, "custom" (implements specific modem behavior and AT

commands)

– Modem system control: support modem HW system control signaling (power

on/off, reset). It is split into a generic and a specific part. The generic part exposes

the generic API to the application (Cellular Service) while the specific part controls

the GPIO dedicated to the modem.

• IPC: abstracts the actual physical interface (UART) to the upper layer. Supports the

logical channel handler (FIFO) that is mapped to a physical channel. Supports two

channels: character mode and stream mode:

– Stream mode is used for data transfer (PPP).

– Character mode is used to send AT commands.

• Utilities: provides tools such as debug and trace. Also provides the setup menu (over

any terminal through a serial interface) to change the default configuration, which is

hard coded during compilation and image creation.

• FreeRTOS™ (and CMSIS): provides RTOS services to create the resources and

scheduler needed by the software to run, such as threads and tasks, dynamic memory

allocation, mutexes, and semaphores. A default task (freertos.c) is in charge of system

initialization, creation of all application tasks. It finally initializes and starts the Cellular

Service components by calling cellular_init() and cellular_start().

剩余71页未读，继续阅读

wocgjjc

粉丝: 4
资源: 24

STM32CubeX-CUBE-CELLULAR入门指南：2G, 3G, LTE Cat M1, NB-IoT连接

Qualcomm-Cellular-V2X-AESIN-Oct-2016.pptx

Qualcomm-Cellular-V2X-AESIN-Oct-2016.zip

CELLULAR V2X是什么？

CSI-RS bitmap

apple-mobile-web-app-status-bar-style

3gpp nr-v2x

iov、c-v2x、v2v和v2i之间的关系

木材多尺度本构模型的相关文献

5g c-v2x.asn

Annotation of spatially resolved single-cell data with STELLAR

C-V2X车路协同技术是什么，它能带来哪些好处？

LTE-V2X关键技术

合成热力图的（Cellular Automata Model，CAM）是哪篇论文提出来的，论文题目是什么

TRANSPORT_CELLULAR

iterative source steering

setPositionMode android

Microdosimetry of BNCT

最新资源