SILICON LABS AN1321 Configuring Peripherals for 32 Bit Devices with Zigbee EmberZNet 7.0 and Higher User Guide

June 10, 2024
SILICON LABS

SILICON LABS AN1321 Configuring Peripherals for 32 Bit Devices with Zigbee EmberZNet 7.0 and Higher User Guide
SILICON LABS AN1321 Configuring Peripherals for 32 Bit Devices with Zigbee
EmberZNet 7.0 and Higher

Peripherals for Zigbee devices, running applications built with EmberZNet SDK 7.0 and higher, are configured using the Pin Tool in Simplicity Studio® 5. The Pin Tool simplifies peripheral configuration by presenting peripherals and peripheral properties in a graphical user interface. For some SDKs, many peripherals can also be configured in the Simplicity IDE as component options.

If you are developing with the EmberZNet SDK 6.10.x and lower, see AN1115: Configuring Peripherals for 32-Bit Devices using Hardware Configurator.

KEY POINTS

  • Introducing peripheral configuration
  • Using the Pin Tool in Simplicity Studio
  • Pin Tool functions

Introduction

Pin Tool is an advanced graphical editor that allows developers to easily configure the peripherals on their Zigbee system. It provides three configuration perspectives to let the developers intuitively map physical pins and peripheral instances to software components on the target device.

Pin Tool editor is also flexible enough to be used in different development flows. The bottom-up approach lets developers start configuration with pins and connect them  tofunctions/peripherals and then software components. However, an opposite but equally effective top-down approach lets developers starts with software component selections for peripherals and work down to peripheral functions and pins when required.

When a Zigbee application project is first created, an initial set of header files are provided to the new project based on the target board’s configurations, EmberZNet SDK version, and so on, as shown in the following figure. Any subsequent customization of the peripherals can be made through the Pin Tool. Developers using EmberZet can also modify hardware options through the Component Editor. All customizations and changes through Pin Tool are updated to the configuration header files which are included by the application.
Connections

The C header files with hardware-specific configurations are used and monitored by the Pin Tool. These files can be found in the following project directory. The hardware-specific configurations are stored in the Pin Config section of the generated C header files.

//config/

Using the Pin Tool

This chapter discusses the basic operation and functions of the Pin Tool. Before proceeding to the next section, it may be helpful to understand the GPIO functionality and peripheral signal routing controls of the target devices by reviewing AN0012: General Purpose Input Output, device datasheets, and reference manuals.

Opening the Pin Tool in Simplicity Studio

Open Pin Tool directly by double-clicking on the .pintool file in the Project Explorer, as shown in the following figure.
Opening the Pin Tool in Simplicity Studio

Pin Tool may also be started from the Project Configurator’s CONFIGURATION TOOLS tab.
Opening the Pin Tool in Simplicity Studio

Pin Tool Functions

The following figure shows the Pin Tool editor window once it is open. The left “Port I/O” pane shows the device package’s Port I/O view.
The right “Configure” has three tabs –Pin, Functions, and Peripherals. Each of these tabs gives a different detailed perspective with which to configure the hardware.
Pin Tool Functions

Port I/O Pane

The Port I/O Pane is essentially a Pinout diagram that displays the physical pin locations on the target device package.
The Pinout diagram has the following color coding:

  • Pins in blue are in use
  • Pins in white are unused.
  • Pins in red show unallowed conflicts with two or signals going into the same pin.
  • Pins in orange show allowed conflicts with two or more signals going into the same pin (not shown in the diagram).
  • Pins, such as E5/Vss, are greyed out because they are unavailable for configuration
  • All pins configured for GPIO modes are marked by the boldfaced letter G.
  • When one or more pins are selected in the Configure panel (e.g., K13), the corresponding pins are highlighted in yellow.”
    Port I/O Pane

The Zoom controls at the lower left corner of the Port I/O pane provide a convenient way to zoom in to a specific location on the Pinout diagram to see more detailed information of a given pin.
Port I/O Pane

A printable report can be generated by right-clicking the pinout diagram and selecting Pin Configuration Report. This opens a report as a webpage in a browser that can be saved, printed, or archived. The Module Configuration Report option generates a similar set of tables organized by module rather than by pin order.
Port I/O Pane

Pins Tab

The Pins tab gives a pin-centric table view of the device, similar to the datasheet’s GPIO Functionality Table. The Pins table lets the user assign any valid alternate function to a pin, as shown in the following drop-down menu under the Function column
Pins Tab

The Search box shown in the above figure allows user to quickly locate a Pin in a table.

Once a pin and the function have been chosen, the software component can be selected from the Software Component drop-down menu for the pin. The following figure shows the pin PA4 has been configured for GPIO  mode and assigned to the software component MX25 Flash Shutdown with usart. Alternatively, the user can assign the pin through the  Component Editor.
Pins Tab

As a convenience, the user can open the Component Editor for a given component by double-clicking the blue circle in the “Software Component” cell as shown below.
Pins Tab

The “Custom Pin Name” column allows users to enter the custom pin name for a given pin.

Functions Tab

The Functions tab provides an alternate function-centric view of the device, similar to the datasheet’s Alternate Functionality Table. The Functions tab lets the user assign available pins to an alternate function.

The valid pin for a specific alternate function can be selected from the drop- down menu in the “Pin Name” column. The blue dot for a pin  in the same drop- down menu indicates the pin is already in use. The Component Editor can be opened for the entries in the “Software Component” column.
Functions Tab

Peripherals Tab

The Peripherals tab shows a list of the peripherals on the device and their mapping to software components. The drop-down menu allows the user to select an available software component for a specific peripheral, as shown in the following figure.
Peripherals Tab

The Software Component cell for a peripheral appears grey when no software component that uses the peripheral exists, and white when one exists but has not been assigned. The user can also provide a custom name for a given peripheral in the “Custom Peripheral Name” column.
Peripherals Tab

Simplicity Studio
One-click access to MCU and wireless tools, documentation, software, source code libraries & more. Available for Windows, Mac and Linux!

ApplicationIoT Portfolio
www.silabs.com/IoT

ApplicationSW/HW
www.silabs.com/simplicity

ApplicationQuality
www.silabs.com/quality

ApplicationSupport & Community
www.silabs.com/community

Disclaimer
Silicon Labs intends to provide customers with the latest, accurate, and in- depth documentation of all peripherals and modules available for system and software implementers using or intending to use the Silicon Labs products. Characterization  data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and “Typical” parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Labs reserves the right to make changes without further notice to the product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the included information. Without prior notification, Silicon Labs may update product firmware during the manufacturing process for security or reliability reasons. Such changes will not alter the specifications or the performance of the product. Silicon Labs shall have no liability for the consequences of use of the information supplied in this document. This document does not imply or expressly grant any license to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any FDA Class III devices, applications for which FDA premarket approval is required or Life Support Systems without the specific written consent of Silicon Labs. A “Life Support System” is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant personal injury or death. Silicon Labs products are not designed or authorized for military applications. Silicon Labs products shall under no circumstances be used in weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons. Silicon Labs disclaims all express and implied warranties and shall not be responsible or liable for any injuries or damages related to use of a Silicon Labs product in such unauthorized applications.
Note: This content may contain offensive terminology that is now obsolete. Silicon Labs is replacing these terms with inclusive language wherever possible. For more information, visit www.silabs.com/about-us /inclusive-lexicon-project

Trademark Information
Silicon Laboratories Inc.®, Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo®, Bluegiga®, Bluegiga Logo®, EFM®, EFM32®, EFR, Ember®, Energy Micro, Energy Micro logo and combinations thereof, “the world’s most energy friendly microcontrollers”, Redpine Signals®, WiSeConnect , n-Link, ThreadArch®, EZLink®, EZRadio®, EZRadioPRO®, Gecko®, Gecko OS, Gecko OS Studio, Precision32®, Simplicity Studio®, Telegesis, the Telegesis Logo®, USBXpress® , Zentri, the Zentri logo and Zentri DMS, Z Wave®, and others are trademarks or registered trademarks of Silicon Labs. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. Wi-Fi is a registered trademark of the Wi-Fi Alliance. All other products or brand names mentioned herein are trademarks of their respective holders.

Silicon Laboratories Inc.
400 West Cesar Chavez Austin, TX 78701 USA
www.silabs.com

SILICON LABS logo

References

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>

SILICON LABS User Manuals

Related Manuals