ANR008
W IRELESS C ONNECTIVITY SDKV ERSION 1.12
J UNE 27, 2024

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

Revision history
ManualversionVersion for
STM32

1.0

-

• Initial version of this document

April 2019

1.2-

• Updated file name to new applicationnote name structure. Updated importantnotes, legal notice & license terms
chapters.

June 2019

1.3-• Updated supported modules

September
2019

1.4

-

• Updated supported modules

May 2020

Notes

Date

• Updated supported modules
1.5-• Updated supported libraries

February 2021

• Updated installation instructions• Added description for SPI interfaces• Fixed wrong links
1.6-• Updated installation description of FTDI
drivers

August 2021

• Renamed USB radio sticks variants

1.7

1.0.0

• Added new driver for STM32 microcontrollers (see chapter 2).

August 2021

• Restructured chapters for better overview

1

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK• The STM32 SDK is now the primaryversion of the SDK. The Raspberry Pi
version has been archived.
1.8

1.2.0

May 2022• Updated supported modules• Updated chapter 2 (Wireless Connectivity
SDK)

1.9

1.10

1.5.0

1.7.2

• Updated SDK history of STM32 version(chapter 2.2)

• Wireless Connectivity SDK for Raspberryhas been archived

April 2023

July 2023• Updated Important notes and meta data

1.11

2.0.0

• Removed documentation WirelessConnectivity SDK for Raspberry Pi(legacy version)

January 2024

• Explained new structure of WirelessConnectivity SDK for STM32 of
version 2.0.0

1.12

2.1.0

• Updated chapter Version history

June 2024? For SDK version history see chapter Version history

2

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

Abbreviations
Abbreviation

Name

CS

Check sum

DC

Duty cycle

Active transmission time per hour expressed aspercentage. 1% means, channel is occupied for 36
seconds per hour.

FSE

Field Sales
EngineerSupport and sales contact person responsible forlimited sales area

0xhh [HEX]Hexadecimal

The prefix 0x indicates hexadecimal values. All othernumbers are decimal values.

HAL

HardwareAbstraction Layer

HIGH

High signal level

LOW

Low signal level

LPM

Low power mode

Operation mode with reduced energy consumption.

LRMLong range modeTx mode increasing the RX sensitivity by using
spreading and forward error correction

LSB

Least significant
bit

MSB

Most significant bit

PL

Payload

The real, non-redundant information in aframe/packet.

RFRadio frequency

Describes everything relating to the wirelesstransmission.

SDK

Softwaredevelopment kit

Software code that implements the commandinterface of various Würth Elektronik eiSos products
Universal Asynchronous Receiver Transmitter - a
serial data transmission interface

UART
VDD

Description

Supply voltage

3

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDKContents
1 Introduction
1.1
Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5
7

2 Wireless Connectivity SDK
2.1
Content and structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2
Version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3
Host integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4
Running sample applications on the STM32 Nucleo board . . . . . . . . . . . .
2.4.1 Hardware connections . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2 Run the project with STM32CubeIDE . . . . . . . . . . . . . . . . . . .

9
9
11
12
14
14
15

3 References

17

4 Important notes

18

4

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

1 Introduction
The Würth Elektronik eiSos wireless modules provide an easy to use radio interface to any embedded application. The host processor of the embedded application can operate the module
by sending commands via UART to the module’s command interface.
The Wireless Connectivity SDK is a set of software tools that enable quick software integrationof Würth Elektronik eiSos wireless modules into any of the most commonly used host processors. It consists of drivers and examples in C-code that use the UART of the underlying
platform to communicate with the attached radio device.
The Wireless Connectivity SDK has been developed for the STM32 platform.

A legacy version was available for Raspberry Pi 3. It has been archived andwill no longer be maintained.

5

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

Customer host MCU
Customer application

Wireless
Connectivity
SDK driver
Host peripherals(UART, GPIOs)

UARTRadio module
Radio module peripherals(UART, GPIOs)
Command interface

Radio stack

Figure 1: Wireless connectivity SDK driver as part of the end product6

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

1.1 Motivation
The aim of the Wireless Connectivity SDK is to minimize the effort required on customer side
to enable his host MCU to communicate with Würth Elektronik eiSos radio modules. It contains
the implementation of all available commands in pure C-code. In order to integrate any Würth
Elektronik eiSos wireless module, the user has to simply copy the corresponding C-code andadapt the platform specific parts to his host processor.
Würth Elektronik eiSos products, like the 868 MHz proprietary radio module Tarvos-III, use a socalled command interface1 for configuration and operation tasks. This interface provides up
to 30 commands that accomplish tasks like updating various device settings, transmitting/receiving data and putting the module into one of various low power modes.
The commands of the interface can be divided into 3 categories:
1. Requests: The host requests the module to trigger an action, e.g. in case of the request
CM_RESET_REQ the host asks the module to perform a reset.
2. Confirmations: On each request the module answers with a confirmation message asa feedback on the requested operation status. In case of a CM_RESET_REQ, the moduleanswers with a CMD_RESET_CNF to tell the host whether it is ready to run the reset process
or not.
3. Indications and Responses: In case of special events, the module indicates the same
spontaneously to the host. The CMD_DATAEX_IND indicates for example that data has
been received via radio.
The commands itself have the following format:
Start byte

CommandLengthPayloadCS

0x02

1 Byte1 ByteLength Bytes

1 ByteExample: CMD_DATA_REQ of the Tarvos-III
The CMD_DATA_REQ has the command number 0x00. It provides a simple data transfer. The
length field indicates the number of bytes to be transmitted via radio.
Format:Start byte

CommandLengthPayload

CS

0x02

0x00

1 ByteLength Bytes

1 ByteExample: Sending "Hello World!"

1

There are Würth Elektronik eiSos wireless modules that support a second operation mode, the so called transparent mode. When using the transparent mode the device does not accept commands sent via UART. Please
make sure that the connected radio device runs in command mode as specified in the respective radio module
user manual, when using the Wireless Connectivity SDK.

7

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

Start byte

Command

0x02

0x00

LengthPayloadCS

0x0C

0x48 0x65 0x6C
0x6C 0x6F 0x20
0x57 0x6F 0x72
0x6C 0x64 0x21

0x0F

With the above command, we are sending 12 bytes (0x0C), corresponding to the ASCII string"Hello World!" (0x48 0x65 0x6C 0x6C 0x6F 0x20 0x57 0x6F 0x72 0x6C 0x64 0x21) and theresulting checksum is 0x0F.
To use the complete feature set of such a radio device, all available commands of the corresponding command interface have to be implemented on the custom host processor. This
involves considerable effort for the user and this is the main reason why Würth Elektronik eiSos
offers the Wireless Connectivity SDK.

8

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

2 Wireless Connectivity SDK
2.1 Content and structure
The radio modules supported by the latest version of the Wireless Connectivity SDK are:
SDK version

Radio standard
®

2.0.0

Radio module & USB dongle

Bluetooth LE
Cellular
LoRa WAN
Proprietary 868 MHz
Proprietary 915 MHz
Proprietary 2.4 GHz
WiFi / WLAN
WiFi / Bluetooth® LE
combo
Wireless M-BUS

Proteus-II, Proteus-III, Proteus-eAdrastea-I
Daphnis-I
Tarvos-III, Thebe-II
Telesto-III, Themisto-I
Thyone-I, Thyone-e
CalypsoStephano-I
Shared driver for Metis-II, Metis-I, Mimas-I

Table 1: Wireless Connectivity SDK for STM32

The driver is designed in a way, that several modules of different type can be
run at the same time. See also the "multi module" examples present in the
Wireless Connectivity SDK.
At the topmost level, the Wireless Connectivity SDK directory structure looks as follows.

/

WCON_SDK................................................. Root directory of the SDK
STM32F4xx..................STM32F4 driver (HAL, peripherals, ...) and project le
STM32L0xx.................. STM32L0 driver (HAL, peripherals, ...) and project le
WCON_Drivers........................... Wireless module drivers and example code
Readme.md ........................................................... Readme leFigure 2: Folder structure

The root directory of the Wireless Connectivity SDK (WCON_SDK) contains the HAL driver directories for each supported family of STM32 micro controllers (STM32F4xx and STM32L0xx)
as well as the WCON_Drivers directory. Within this directory, each supported radio module
has its own subdirectory containing the implementation of its command interface and one orseveral files containing various examples.
Besides the module-specific directories, the subdirectory global contains all the shared functions as well as definitions related to the serial communication and GPIO interfaces of the

9

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

underlying host.

/

WCON_Drivers.........................Contains the code to be ported to custom hosts
main.c.................. main le linking to the respective examples of each module
globalglobal_types.h........................Declares global types used by the drivers
global.h....................... Declares functions to be dened on custom hosts
global.c.................... Implements functions to be dened on custom hosts
global_F4xx.c ............ STM32F4-specic implementations of global functions
global_L0xx.c ............ STM32L0-specic implementations of global functions...
ProteusIII.......................... Command interface of the Proteus-III module
ProteusIII.h
ProteusIII.c
ProteusIII_Examples.c ..................... Example of the Proteus-III module
TarvosIII............................ Command interface of the Tarvos-III module
TarvosIII.h
TarvosIII.c
TarvosIII_Examples.c ....................... Example of the Tarvos-III module...
...
Figure 3: Folder structure

10

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

2.2 Version history
Version 1.0.0 "Release"• Initial version of the SDK
Version 1.1.0 "Release"• Added driver for the Calypso WiFi radio module
Version 1.2.0 "Release"• Added driver for the Proteus-e Bluetooth LE module• Updated Proteus-III driver
Version 1.3.0 "Release"• Improvement of the Thyone-I driver
Version 1.4.0 "Release"• Improvement of the Calypso driver
Version 1.5.0 "Release"• Improvement of the Proteus-III driver• Added Proteus-II driver• Restructured AT-command codes for coming radio modules
Version 1.7.0 "Release"• Added driver for Adrastea-I
Version 2.0.0 "Release" January 2024
• Added driver for Daphnis-I, Stephano-I, Thyone-e• Changed driver structure to support multiple modules at the same time
• Implemented a second UART interface on STM32F4xxxx and STM32L0xxxx• Added example for multi module support
Version 2.1.0 "Release" June 2024
• Added functions of firmware version 3.3.0 of radio modules Tarvos-III, Telesto-III,
Thebe-II, Themisto-I• Bug fix in writing user settings of Proteus and Thyone variants• Bug fix in Stephano-I driver• Improvements in UART definition and debug interface for STM32

11

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

2.3 Host integration
As described in chapter 2.1, the Wireless Connectivity SDK provides implementations for the
STM32L0 and STM32F4 platforms. In order to use the drivers with a different type of hostmicro controller, they have to be ported to the new platform. This is shown in the following
example, on base of the Proteus-III drivers and example.
1. The directories WCON_Drivers/global and WCON_Drivers/ProteusIII have to be copied
to the custom project.
2. The file global_types.h declares global types used by the drivers. The file global.hdeclares the shared functions that deal with delay- and GPIO-related functions.
/*** @brief Switch pin to output high/low** @param[in] pin Output pin to be set* @param[in] out Output level to be set* @return true if request succeeded, false otherwise*/
extern bool WE_SetPin(WE_Pin_t pin, WE_Pin_Level_t out);/*** @brief Sleep function.
** Note that WE_MICROSECOND_TICK needs to be defined to enable microsecond timer
resolution.
** @param[in] sleepForUsec Delay in microseconds*/
extern void WE_DelayMicroseconds(uint32_t sleepForUsec);

Code 1: Code snippet of the file global.h
When integrating the Wireless Connectivity SDK into a custom host, the implementationof the functions defined in global.h must be done in the global.c file.
3. Furthermore, the files global_L0xx.h/c and global_F4xx.h/c contain the UART implementation of the respective STM32 platform. For the custom host a source and header
file containing the respective UART functions must be be created.
extern void WE_SystemClock_Config(void);/*** @brief Initialize and start the UART.
** @param[in] baudrate Baud rate of the serial interface* @param[in] flowControl Enable/disable flow control* @param[in] parity Parity bit configuration* @param[in] rxByteHandlerP Pointer to the handle rx byte function inside thedriver*/extern bool WE_UART1_Init(uint32_t baudrate,
WE_FlowControl_t flowControl,
WE_Parity_t parity,
WE_UART_HandleRxByte_t *rxByteHandlerP);

12

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK/*** @brief Deinitialize and stop the UART.
*/
extern bool WE_UART1_DeInit();/*** @brief Transmit data via UART.
** @param[in] data Pointer to data buffer (data to be sent)* @param[in] length Number of bytes to be sent*/
extern bool WE_UART1_Transmit(const uint8_t *data, uint16_t length);

Code 2: Functions needed for custom host
4. Last, in the example code the GPIO pins used by the module driver are defined, before themodule’s init function is called (here: ProteusIII_Examples() in file ProteusIII_Examples.c).
ProteusIII_pins.ProteusIII_Pin_Reset.port = (void*)GPIOA;
ProteusIII_pins.ProteusIII_Pin_Reset.pin = GPIO_PIN_10;
ProteusIII_pins.ProteusIII_Pin_SleepWakeUp.port = (void*)GPIOA;
ProteusIII_pins.ProteusIII_Pin_SleepWakeUp.pin = GPIO_PIN_9;...
ProteusIII_uart.baudrate = PROTEUSIII_DEFAULT_BAUDRATE;
ProteusIII_uart.flowControl = WE_FlowControl_NoFlowControl;
ProteusIII_uart.parity = WE_Parity_None;
ProteusIII_uart.uartInit = WE_UART1_Init;
ProteusIII_uart.uartDeinit = WE_UART1_DeInit;
ProteusIII_uart.uartTransmit = WE_UART1_Transmit;
ProteusIII_Init(&ProteusIII_uart, &ProteusIII_pins,
ProteusIII_OperationMode_CommandMode, callbackConfig);

Code 3: Selection of GPIO and UART
After dealing with these steps the driver is functional.

13

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

2.4 Running sample applications on the STM32 Nucleo board
2.4.1 Hardware connections
The Wireless Connectivity SDK has been developed on the STM32 Nucleo-L073RZ [1] andNucleo-F401RE [2] development boards using STM32CubeIDE [3]. To run the examples provided by the SDK on one of these boards, first connect the respective pins of the board to theradio module (typically mounted on the corresponding EV-Board). Besides the VCC, GND andthe UART pins, other product-specific pins such as the Reset pin should be connected. Consult the Wireless Connectivity SDK Readme file and/or the user manual of the used wirelessmodule for additional information.
Please note that table 2 and figure 4 show a standard set of GPIOs used bymost of the Würth Elektronik eiSos wireless modules. Depending on the used
module and the application being developed, it may be necessary to makedifferent connections.

Function

Pin

I/O

Function

Pin

I/O

VCC

+3V3

-

GND

GND

-

UART RX

PB7

Input

UART CTS

PA11

Input

UART TX

PB6

OutputUART RTS

PA12

Output

Reset

PA10

Output

Wake_up

PA9

OutputBoot

PA7

OutputMode

PA8

OutputTable 2: Used pins of the STM32 Nucleo board

Figure 4: Layout for STM32 NUCLEO-L073RZ [4]14

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

2.4.2 Run the project with STM32CubeIDE
First download the Wireless Connectivity SDK [5] and save it on your computer. Then installand start the STM32CubeIDE [3] (recommended version 1.14.0 or higher). When starting,
you will be asked for a workspace path. In case you already have a workspace from previous
projects, select the desired path. In case you want to use a new workspace, create a new
empty directory and select that directory.

Figure 5: Choose workspace
After the STM32CubeIDE started, go to "File→Open Projects from File System" and select thepath where you saved the Wireless Connectivity SDK.

Figure 6: Open project
Select the project which you would like to import depending on the microcontroller family thatyou intend to use (e.g. STM32L0xx). Press the "Finish" button, so that the project is loaded
into the "Project Explorer".

The Wireless Connectivity SDK includes the examples and drivers for all supported products in
one STM32CubeIDE project. Thus to evaluate a single product, the right radio module example
must be selected first. To do so, open the main.c file and comment/uncomment the example
functions.
/* select the example to run */15

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK//Adrastea_Examples();//Calypso_Examples();//DaphnisI_Examples();//Metis_Examples();//ProteusE_Examples();//ProteusII_Examples();ProteusIII_Examples();//StephanoI_Examples();//ThyoneE_Examples();//ThyoneI_Examples();//TarvosIII_Examples();//TelestoIII_Examples();//ThebeII_Examples();//ThemistoI_Examples();//MultiModule_ProteusIII_TarvosIII_Examples();

Code 4: Select example in main.c file
Then press "Build" and "Run" to flash the firmware on the STM32 controller. If the debug
output is enabled by defining the macro "WE_DEBUG", you can see the debug messages on
the serial interface (115200 Baud, 8n1), that is available on the USB connector of the Nucleo
board.

16

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

3 References[1] STMicroelectronics.
nucleo-l073rz.html.

NucleoL073RZ.

https://www.st.com/en/evaluation-tools/[2] STMicroelectronics.
nucleo-f401re.html.

NucleoF401RE.

https://www.st.com/en/evaluation-tools/[3] STMicroelectronics.
stm32cubeide.html.

STM32CubeIDE.

https://www.st.com/en/development-tools/[4] STMicroelectronics . UM1724 - User manual - STM32 Nucleo-64 boards (MB1136). https://www.st.com/.
[5] Würth Elektronik. Wireless Connectivity SDK for STM32 - Radio module drivers in C-code.
https://github.com/WurthElektronik/WirelessConnectivity-SDK_STM32.

17

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

4 Important notes
The Application Note and its containing information ("Information") is based on Würth Elektronik eiSos GmbH & Co. KG and its subsidiaries
and affiliates ("WE eiSos") knowledge and experience of typical requirements concerning these areas. It serves as general guidance and shallnot be construed as a commitment for the suitability for customer applications by WE eiSos. While WE eiSos has used reasonable efforts toensure the accuracy of the Information, WE eiSos does not guarantee that the Information is error-free, nor makes any other representation,
warranty or guarantee that the Information is completely accurate or up-to-date. The Information is subject to change without notice. To
the extent permitted by law, the Information shall not be reproduced or copied without WE eiSos’ prior written permission. In any case, theInformation, in full or in parts, may not be altered, falsified or distorted nor be used for any unauthorized purpose.

WE eiSos is not liable for application assistance of any kind. Customer may use WE eiSos’ assistance and product recommendations forcustomer’s applications and design. No oral or written Information given by WE eiSos or its distributors, agents or employees will operate
to create any warranty or guarantee or vary any official documentation of the product e.g. data sheets and user manuals towards customer
and customer shall not rely on any provided Information. THE INFORMATION IS PROVIDED "AS IS". CUSTOMER ACKNOWLEDGESTHAT WE EISOS MAKES NO REPRESENTATIONS AND WARRANTIES OF ANY KIND RELATED TO, BUT NOT LIMITED TO THE NONINFRINGEMENT OF THIRD PARTIES’ INTELLECTUAL PROPERTY RIGHTS OR THE MERCHANTABILITY OR FITNESS FOR A PURPOSEOR USAGE. WE EISOS DOES NOT WARRANT OR REPRESENT THAT ANY LICENSE, EITHER EXPRESS OR IMPLIED, IS GRANTEDUNDER ANY PATENT RIGHT, COPYRIGHT, MASK WORK RIGHT, OR OTHER INTELLECTUAL PROPERTY RIGHT RELATING TO ANYCOMBINATION, MACHINE, OR PROCESS IN WHICH WE EISOS INFORMATION IS USED. INFORMATION PUBLISHED BY WE EISOSREGARDING THIRD-PARTY PRODUCTS OR SERVICES DOES NOT CONSTITUTE A LICENSE FROM WE eiSos TO USE SUCH PRODUCTS OR SERVICES OR A WARRANTY OR ENDORSEMENT THEREOF.
The responsibility for the applicability and use of WE eiSos’ components in a particular customer design is always solely within the authority of the customer. Due to this fact it is up to the customer to evaluate and investigate, where appropriate, and decide whether the device
with the specific characteristics described in the specification is valid and suitable for the respective customer application or not. The technicalspecifications are stated in the current data sheet and user manual of the component. Therefore the customers shall use the data sheets anduser manuals and are cautioned to verify that they are current. The data sheets and user manuals can be downloaded at www.we-online.com.
Customers shall strictly observe any product-specific notes, cautions and warnings. WE eiSos reserves the right to make corrections, modifications, enhancements, improvements, and other changes to its products and services at any time without notice.
WE eiSos will in no case be liable for customer’s use, or the results of the use, of the components or any accompanying written materials. IT IS CUSTOMER’S RESPONSIBILITY TO VERIFY THE RESULTS OF THE USE OF THIS INFORMATION IN IT’S OWN PARTICULAR
ENGINEERING AND PRODUCT ENVIRONMENT AND CUSTOMER ASSUMES THE ENTIRE RISK OF DOING SO OR FAILING TO DO SO.
IN NO CASE WILL WE EISOS BE LIABLE FOR CUSTOMER’S USE, OR THE RESULTS OF IT’S USE OF THE COMPONENTS OR ANY
ACCOMPANYING WRITTEN MATERIAL IF CUSTOMER TRANSLATES, ALTERS, ARRANGES, TRANSFORMS, OR OTHERWISE MODIFIES THE INFORMATION IN ANY WAY, SHAPE OR FORM.
If customer determines that the components are valid and suitable for a particular design and wants to order the corresponding components, customer acknowledges to minimize the risk of loss and harm to individuals and bears the risk for failure leading to personal injury
or death due to customers usage of the components. The components have been designed and developed for usage in general electronicequipment only. The components are not authorized for use in equipment where a higher safety standard and reliability standard is especiallyrequired or where a failure of the components is reasonably expected to cause severe personal injury or death, unless WE eiSos and customer
have executed an agreement specifically governing such use. Moreover WE eiSos components are neither designed nor intended for use
in areas such as military, aerospace, aviation, nuclear control, submarine, transportation, transportation signal, disaster prevention, medical,
public information network etc. WE eiSos must be informed about the intent of such usage before the design-in stage. In addition, sufficientreliability evaluation checks for safety must be performed on every component which is used in electrical circuits that require high safety andreliability functions or performance. COSTUMER SHALL INDEMNIFY WE EISOS AGAINST ANY DAMAGES ARISING OUT OF THE USE
OF THE COMPONENTS IN SUCH SAFETY-CRITICAL APPLICATIONS.

18

Version 1.12, June 2024

www.we-online.com/wcs

WIRELESS CONNECTIVITY & SENSORS
ANR008 - Wireless Connectivity SDK

List of Figures
1
2
3
4
5
6

Wireless connectivity SDK driver as part of the end product . . . . . . . . . . . .
Folder structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Folder structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Layout for STM32 NUCLEO-L073RZ [4] . . . . . . . . . . . . . . . . . . . . . . .
Choose workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Open project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6
9
10
14
15
15

List of Tables
1
2

Wireless Connectivity SDK for STM32 . . . . . . . . . . . . . . . . . . . . . . . . 9
Used pins of the STM32 Nucleo board . . . . . . . . . . . . . . . . . . . . . . . . 14

19

Version 1.12, June 2024

www.we-online.com/wcs

Contact
Würth Elektronik eiSos GmbH & Co. KG
Division Wireless Connectivity & Sensors
Max-Eyth-Straße 174638 Waldenburg
Germany
Tel.: +49 651 99355-0
Fax.: +49 651 99355-69
www.we-online.com/wireless-connectivity