Data Sheet

<docnum>: <title>
WGM160P pin description
silabs.com | Building a more connected world. Rev. 0.1 | 6
3.7 Multifunction pins
The multifunction pins refer to WGM160P pins directly connected to the embedded MCU EFM32GG11.
3.7.1 Software architecture consideration
The WGM160P module has a lot of flexibility regarding configuration of these MCU pins, as described in the data sheet, but all software
architectures do not support all functions.
3.7.1.1 Bootloader
All devices come pre-programmed with a UART bootloader. This bootloader resides in flash and can be erased if it is not needed. More
information about the bootloader protocol and usage can be found in AN0003: UART Bootloader. Application notes can be found on the
Silicon Labs website (www.silabs.com/32bit-appnotes) or within Simplicity Studio in the [Documentation] area.
WGM160P pin 44 (GG11 PF0) and pin 45 (GG11 PF1) provide respectively TX and RX access to bootloader.
3.7.1.2 Implementation with GG11 open software
Full flexibility can be achieved when using the source software based on the Full MAC driver provided by Silicon Labs. The configuration
of multifunction pins is achieved within Simplicity Studio similarly to a software development for EFM32GG11. For more details regarding
these pins, refer to tables 6.2 and 6.3 of WGM160P datasheet.
3.7.1.3 Implementation with Gecko OS
The table below provides the details on the various multifunction pin features supported through Gecko OS 4.0. Features such as SPI
slave and USB will be supported in future release of Gecko OS.
Table 3.6 WGM160P Multifunction Pin Configuration With GeckoOS
WGM160P
Pin
GG11
Port
Default
Function
GPIO
1
(GOS_
GPIO_x)
UART
2
(GOS_
UART_x)
SPI
3
(GOS_
SPI_x)
I2C
(GOS_
I2C_x)
ADC
(GOS_
ADC_x)
PWM
(GOS_
PWM_x)
Ethernet
(RMII)
14
PE14
GPIO
0
0
0
TXD1
15
PE15
GPIO
1
-
1
TXD0
16
PA0
SPI Master MOSI
2
SPI0 MOSI
6
2
TXEN
17
PA1
SPI Master MISO
3
SPI0 MISO
-
3
RXD1
18
PA2
SPI Master CLK
4
SPI0 CLK
10
4
RXD0
19
PA3
GPIO
5
-
5
REFCLK
20
PA4
GPIO
6
11
6
CRSDV
21
PA5
GPIO
7
-
7
RXER
22
PB3
Bulk sflash MOSI or
4
UART TX (logging)
8
UART1 TX
SPI1 MOSI
-
8
1
The prefix _x in GOS_GPIO_x is replaced with the numbers in the column: GOS_GPIO_1, GOS_GPIO_2, etc. SDK have all those symbols defined in header files.
2
all UART IO’s are relevant to WGM160P, so when RX is used it means WGM160P receives, and TX means WGM160P transmits.
3
SPI can be configured as master or slave. At the moment, only SPI master is supported in Gecko OS. SPI slave is coming in a future release. SPI interface does not define
fixed SPI_CS pin. CS is configurable and any unused GPIO can be used for this function.
4
PB3 and PB4 showing 2 default functions means that those pins can be assigned using Gecko OS command API (variables and command) to one of those functions. For
example, “set bus.data_bus uart1” or “set system.bflash.port spi1”. Once one of these variables is assigned, the other one will give an error that pins are already
in use. UART (logging) is used to print Gecko OS log messages: https://docs.silabs.com/gecko-os/4/standard/latest/cmd/variables/bus#bus-log-bus