SDFlash_Serial_RefGuide_v3_3

| Building a more connected world. Copyright © 2023 by Silicon Laboratories Rev. 0.1 UG435.08: Network Co-Processor Applications with Silicon Labs Connect v3.x This chapter of the Connect v3.x User's Guide describes how to run the Silicon Labs Connect stack in Network Co-Processor (NCP) mode. The Connect stack is delivered as part of the Silicon Labs Proprietary Flex SDK v3.0 and higher. The Connect v3.x User's Guide assumes that you have already installed the Simplicity Studio development environment and the Flex SDK, and that you are familiar with the basics of configuring, compiling, and flashing Connect-based applications. Refer to UG435.01: About the Connect v3.x User's Guide for an overview of the chapters in the Connect v3.x User's Guide. The Connect v3.x User's Guide is a series of documents that provides in-depth infor-mation for developers who are using the Silicon Labs Connect Stack for their application development. If you are new to Connect and the Proprietary Flex SDK, see QSG168: Proprietary Flex SDK v3.x Quick Start Guide. Proprietary is supported on all EFR32FG devices. For others, check the device's data sheet under Ordering Information > Protocol Stack to see if Proprietary is supported. In Proprietary SDK version 2.7.n, Connect is not supported on EFR32xG22. KEY POINTS • Introduces the NCP. • Discusses NCP, CPC, and Host applica-tions. • Explains the Connect Serial Protocol. UG435.08: Network Co-Processor Applications with Silicon Labs Connect v3.x Introduction | Building a more connected world. Rev. 0.1 | 2 1 Introduction NCP stands for Network Co-processor. By adding a Wireless Gecko (EFR32™) System on Chip (SoC) in NCP mode to your system, you can implement a Connect-based wireless application that leverages the EFR32 Radio feature set. The original customer application (running on a Host device—PC, MCU) interfaces to and controls the NCP through the Universal Asynchronous Receiver-Transmitter (UART) interface as shown in the following figure. Note: NCP should not be confused with virtual Network Co-processor (vNCP). For more information on vNCP, see AN1153: Develop- ing Connect vNCP Applications with Micrium OS. Messages sent from the Host to the NCP are known as commands. Messages sent from the NCP to the Host are known as callbacks. To carry commands and responses between a Host processor and an NCP, Connect uses a Co-Processor Communication (CPC) end-point. UG435.08: Network Co-Processor Applications with Silicon Labs Connect v3.x NCP, CPCd, and Host Applications | Building a more connected world. Rev. 0.1 | 3 2 NCP, CPCd, and Host Applications In the NCP approach, a typical Connect-based application is divided into three separate applications: NCP, Host, and the Co-processor Communication daemon (CPCd). The NCP runs on the EFR32, while the Host application and CPCd runs on the Host device. 2.1 CPC Daemon The CPC daemon provides a unified interface for various projects requiring co-processor communication. CPC calls the host device primary, and the NCP (EFR32) device secondary. CPCd can be downloaded from github: https:///SiliconLabs/cpc-daemon. In the most common use case, CPCd is running as a daemon on Linux, connecting to the primary’s application via the CPC library (libcpc.so) and connecting to the secondary’s application on UART (other communication channels are supported as well). CPC supports multiple endpoints, so it can be used to implement dynamic multiprotocol applications, or another endpoint can be created on the same device to implement something on the secondary that is not connected to the radio stack. Modifying the CPCd is not recommended and should not be needed. 2.2 NCP Application (SoC) The NCP application runs on the EFR32 and supports communication with CPCd over a CPC endpoint. The NCP application can be built with the default configuration, or optionally can be augmented with customizations for target hardware. The application provided is called Connect – NCP. The NCP application can be used out-of-the-box without any modification. However, the radio configuration must be set in the NCP Application. We do not recommend implementing new commands on the same endpoint, if you need further, not Connect related control of the NCP device, we recommend creating a separate CPC endpoint for the new commands. UG435.08: Network Co-Processor Applications with Silicon Labs Connect v3.x NCP, CPCd, and Host Applications | Building a more connected world. Rev. 0.1 | 4 2.3 Host Application The Host application can be compiled to almost any device where libcpc is available. Currently, the Host application examples are imple-mented for the Linux operating system only. These applications are not available in Simplicity Studio, but available on github: https:///SiliconLabs/Connect-NCP-Host. Physical layer (PHY) parameters can be set only at compile time and only in the NCP application. Radio parameters are not configura- ble on the Host side.

……………………………………………………………最新资料推荐…………………………………………………

最新精品资料整理推荐，更新于二〇二〇年十二月三十一日2020年12月31日星期四19:24:59 第1章 EL-TAB-ARM-II实验系统的资源介绍

硬件资源概述

EL-TAB-ARM-II型教学实验系统属于一种综合的教学实验系统，它是集学习、应用编程、开发研究于一体ARM实验教学系统。用户可根据自己的需求选用不同类型的CPU适配板，兼容ARM7与ARM9、ARM10，而不需要改变任何配置，同时，实验系统上的Tech_V总线能够拓展较为丰富的实验接口板。用户在了解Tech_V标准后，更能研发出不同用途的实验接口板。除此之外，在实验板上有丰富的外围扩展资源（数字量IO输入输出，语音编解码、人机接口等单元），可以完成ARM的基础实验和数据通信实验、以太网实验。

1.1 实验系统的硬件资源总揽

图1-1-1 EL-ARM-830实验教学系统的功能框图 S3C241010M网口USB设备CPLD音频录放640X480触摸屏16位色LCD8.4寸640X4804X4键盘8位数码管主USB模拟数字量输入输出总线扩展接口……………………………………………………………最新资料推荐…………………………………………………

最新精品资料整理推荐，更新于二〇二〇年十二月三十一日2020年12月31日星期四19:24:59

1.2 核心板ARM9的资源介绍

1. 核心板的硬件资源（ARM920T核）

☆ CPU：ARM920T，芯片三星的S3C2410，工作频率最高202MHz；

☆ 动态存储器：64MB，芯片HY57V561620；

☆ 海量存储器：32MB，芯片K9F5608；

☆ USB单元： 1个主接口，两个设备接口，芯片PDIUSBD12；

☆ 网络单元： 10/100M以太网，芯片AX88796；

解决OpenOCD烧录STM32失败,⽆法通过SWD连接的问题

OpenOCD烧录STM32失败的问题

Linux下使⽤ OpenOCD 烧录 STM32, 出现了 Error: init mode failed (unable to connect to the target) 错误.

如果在代码中, 不⼩⼼将 PA13,PA14 的 SWD 功能关闭, 例如使⽤了下⾯的代码

rcc_periph_clock_enable(RCC_GPIOA); // Need GPIOA clock

gpio_primary_remap(

AFIO_MAPR_SWJ_CFG_JTAG_OFF_SW_OFF, // Optional

AFIO_MAPR_TIM2_REMAP_NO_REMAP); // This is default: TIM2.CH2=GPIOA1

或者在 STM32CubeMX 中忘记勾选 PA13/PA14 的串⼝调试功能, 都会导致后续烧录和连接失败, 出现

Uploading .pio/build/bluepill_f103c8/firmware.elf

xPack OpenOCD x86_64 Open On-Chip Debugger 0.11.0+dev (2021-10-16-21:15)

Licensed under GNU GPL v2

For bug reports, read

/doc/doxygen/bugs.html

debug_level: 1

hla_swd

none separate

Error: init mode failed (unable to connect to the target)

in procedure 'program'

** OpenOCD init failed **

shutdown command invoked

*** [upload] Error 1

Rev. 0.2 4/20Copyright © 2020 by Silicon Laboratories

AN333AN333

TOOLSTICK VIRTUAL TOOLS USER’S GUIDE

RELEVANT DEVICES

All Silicon Labs MCUs.

1. Introduction

The ToolStick development platform consists of a ToolStick Base Adapter and a ToolStick Daughter card. The

ToolStick Virtual Tools application provides a set of tools for the PC that can be controlled via the UART serial

interface of the ToolStick Base Adapter. The ToolStick Virtual Tools application includes the following components:

ToolStick Terminal

ToolStick Virtual LCD

ToolStick Virtual Oscilloscope

Figure1 shows a system block diagram of the ToolStick platform and the communication path between the

ToolStick Virtual Tools application and the MCU firmware.

Figure1.ToolStick Development Platform Block Diagram

2. Getting Started

The ToolStick Virtual Tools installer can be downloaded from /mcuniversity. This installer includes