with 1 dB steps
– Integrated balun to reduce BOM
– Support for 1 Mbps
– Dedicated Arm
for real-time Radio layer
– Accurate RSSI to enable power control
– Suitable for systems requiring compliance
with radio frequency regulations ETSI EN
300 328, EN 300 440, FCC CFR47 Part 15
and ARIB STD-T66
– Support for external PA
– Available integrated passive device (IPD)
companion chip for optimized matching
solution (MLPF-WB-01E3)
Ultra-low-power platform
– 2.0 to 3.6 V power supply
– – 10 °C to +85 °C temperature range
– 18 nA shutdown mode
– 700 nA Standby mode + RTC + 48 KB
RAM
– Radio: Rx 7.7 mA / Tx at 0 dBm 8.7 mA
Core: Arm
adaptive real-time accelerator (ART
Accelerator) allowing 0-wait-state execution
from Flash memory, frequency up to 64 MHz,
MPU, 80 DMIPS and DSP instructions
Performance benchmark
– 1.25 DMIPS/MHz (Drystone 2.1)
®
®
32-bit Cortex® M0+ CPU
32-bit Cortex®-M4 CPU with FPU,
STM32WB10CC
with FPU, Bluetooth
®
5.2
®
Low
Supply and reset management
– Ultra-safe, low-power BOR (brownout
reset) with five selectable thresholds
– Ultra-low-power POR/PDR
– Programmable voltage detector (PVD)
–V
The ART Accelerator is a memory accelerator optimized for STM32 industry-standard Arm®
®
Cortex
Cortex
for the Flash memory at higher frequencies.
To release the processor near 80 DMIPS performance at 64 MHz, the accelerator
implements an instruction prefetch queue and branch cache, which increases program
execution speed from the 64-bit Flash memory. Based on CoreMark benchmark, the
performance achieved thanks to the ART accelerator is equivalent to 0 wait state program
execution from Flash memory at a CPU frequency up to 64 MHz.
3.3.2 Memory protection unit
The memory protection unit (MPU) is used to manage the CPU1 accesses to memory to
prevent one task to accidentally corrupt the memory or resources used by any other active
task. This memory area is organized into up to eight protected areas, which can be divided
up into eight subareas. The protection area sizes are between 32 bytes and the whole
4
-M4 processors. It balances the inherent performance advantage of the Arm®
®
-M4 over Flash memory technologies, which normally require the processor to wait
Gbytes of addressable memory.
The MPU is especially helpful for applications where some critical or certified code must be
protected against the misbehavior of other tasks. It is usually managed by an RTOS
(real-time operating system). If a program accesses a memory location prohibited by the
MPU, the RTOS detects it and takes action. In an RTOS environment, the kernel can
dynamically update the MPU area setting, based on the process to be executed.
The MPU is optional and can be bypassed for applications that do not need it.
3.3.3 Embedded Flash memory
The STM32WB10CC device features 320 Kbytes of embedded Flash memory available for
storing programs and data, as well as some customer keys.
Flexible protections can be configured thanks to option bytes:
Readout protection (RDP) to protect the whole memory. Three levels are available:
–Level 0: no readout protection
–Level 1: memory readout protection: the Flash memory cannot be read from or
written to if either debug features are connected, boot in SRAM or bootloader is
selected
–Level 2: chip readout protection: debug features (Cortex
JTAG and serial wire), boot in SRAM and bootloader selection are disabled (JTAG
fuse). This selection is irreversible.
®
-M4 and Cortex®-M0+
14/110DS13259 Rev 1
STM32WB10CCFunctional overview
Table 2. Access status vs. readout protection level and execution modes
Area
Main
memory
System
memory
Option
bytes
Backup
registers
SRAM2a
SRAM2b
1. The option byte can be modified by the RF subsystem.
2. Erased when RDP changes from Level 1 to Level 0.
Protection
level
1YesYesYesNoNoNo
2YesYesYesN/AN/AN/A
1YesNoNoYesNoNo
2YesNoNoN/AN/AN/A
1YesYesYesYesYesYes
2YesNo
1YesYesN/A
2YesYesN/AN/AN/AN/A
1YesYesYes
2YesYesYesN/AN/AN/A
User execution
ReadWriteEraseReadWriteErase
(1)
No
(1)
Debug, boot from SRAM or boot
from system memory (loader)
N/AN/AN/A
(2)
(2)
NoNoN/A
NoNoNo
(2)
(2)
Write protection (WRP): the protected area is protected against erasing and
programming. Two areas can be selected, with 4-Kbyte granularity.
Proprietary code readout protection (PCROP): two parts of the Flash memory can be
protected against read and write from third parties. The protected area is execute-only:
it can only be reached by the STM32 CPU, as an instruction code, while all other
accesses (DMA, debug and CPU data read, write and erase) are strictly prohibited.
Two areas can be selected, with 2-Kbyte granularity. An additional option bit
(PCROP_RDP) makes possible to select if the PCROP area is erased or not when the
RDP protection is changed from Level 1 to Level 0.
A section of the Flash memory is secured for the RF subsystem CPU2, and cannot be
accessed by the host CPU1.
The whole non-volatile memory embeds the error correction code (ECC) feature supporting:
single error detection and correction
double error detection
the address of the ECC fail can be read in the ECC register
The embedded Flash memory is shared between CPU1 and CPU2 on a time sharing basis.
A dedicated HW mechanism allows both CPUs to perform Write/Erase operations.
3.3.4 Embedded SRAM
The STM32WB10CC device features 48 Kbytes of embedded SRAM, split in three blocks:
SRAM1: 12 Kbytes mapped at address 0x2000 0000
SRAM2a: 32 Kbytes located at address 0x2003 0000 also mirrored at 0x1000 0000,
with hardware parity check
SRAM2b: 4 Kbytes located at address 0x2003 8000 (contiguous with SRAM2a) and
mirrored at 0x1000 8000 with hardware parity check
DS13259 Rev 115/110
43
Functional overviewSTM32WB10CC
SRAM2a and SRAM2b can be write-protected, with 1-Kbyte granularity. A section of the
SRAM2a and SRAM2b is secured for the RF sub-system and cannot be accessed by the
host CPU1.
The SRAMs can be accessed in read/write with 0 wait states for all CPU1 and CPU2 clock
speeds.
3.4 Security and safety
The STM32WB10CC contains many security blocks both for the BLE and the Host
application.
It includes:
Secure Flash memory partition for RF subsystem-only access
Secure SRAM partition, that can be accessed only by the RF subsystem
True random number generator (RNG)
Advance encryption standard hardware accelerator (AES-256bit, supporting chaining
modes ECB, CBC, CTR, GCM, GMAC, CCM)
Private key acceleration (PKA) including:
–Modular arithmetic including exponentiation with maximum modulo size of 3136
bits
–Elliptic curves over prime field scalar multiplication, ECDSA signature, ECDSA
verification with maximum modulo size of 521 bits
Cyclic redundancy check calculation unit (CRC)
A specific mechanism is in place to ensure that all the code executed by the RF subsystem
CPU2 can be secure, whatever the Host application.
3.5 Boot modes and FW update
At startup, BOOT0 pin and BOOT1 option bit are used to select one of three boot options:
Boot from user Flash
Boot from system memory
Boot from embedded SRAM
The device always boots on CPU1 core. The embedded bootloader code makes it possible
to boot from various peripherals:
UART
I2C
SPI
Secure Firmware update from system boot is provided.
3.6 RF subsystem
The STM32WB10CC embeds an ultra-low power multi-standard radio Bluetooth® Low
Energy (BLE), compliant with Bluetooth
transfer rate, supports multiple roles simultaneously acting at the same time as BLE sensor
The BLE stack runs on an embedded Arm® Cortex®-M0+ core (CPU2). The stack is stored
on the embedded Flash memory, which is also shared with the Arm
application, making it possible in-field stack update.
3.6.1 RF front-end block diagram
The RF front-end is based on a direct modulation of the carrier in Tx, and uses a low IF
architecture in Rx mode.
Thanks to an internal transformer at RF pins, the circuit directly interfaces the antenna
(single ended connection, impedance close to 50 ). The natural bandpass behavior of the
internal transformer, simplifies outside circuitry aimed for harmonic filtering and out of band
interferer rejection.
In Transmit mode, the maximum output power is user selectable through the programmable
LDO voltage of the power amplifier. A linearized, smoothed analog control offers clean
power ramp-up.
In receive mode the circuit can be used in standard high performance or in reduced power
consumption (user programmable). The Automatic gain control (AGC) is able to reduce the
chain gain at both RF and IF locations, for optimized interference rejection. Thanks to the
use of complex filtering and highly accurate I/Q architecture, high sensitivity and excellent
linearity can be achieved.
The bill of material is reduced thanks to the high degree of integration. The radio frequency
source is synthesized form an external 32 MHz crystal that does not need any external
trimming capacitor network thanks to a dual network of user programmable integrated
capacitors.
®
Cortex®-M4 (CPU1)
DS13259 Rev 117/110
43
Functional overviewSTM32WB10CC
MS53574V1
Note: UFQFPN48: V
SS
through exposed pad, and V
SSRF
pin must be connected to ground plane
PA
BP
filter
ADC
ADC
PLL
Modulator
RF1
Adjust
32 MHz
OSC_OUTOSC_IN
PA ramp
generator
AGC
control
BLE
modulator
BLE
demodulator
BLE
controller
RF control
AGC
Timer and Power
control
LDOLDOLDO
V
DD
Trimmed
bias
V
DDRF
Max PA
level
Adjust
HSE
G
G
LNA
Wakeup
Interrupt
AHB
APB
See
note
RF_TX_
MOD_
EXT_PA
Figure 2. STM32WB10CC RF front-end block diagram
3.6.2 BLE general description
The BLE block is a master/slave processor, compliant with Bluetooth specification 5.2
standard (1
It integrates a 2.4 GHz RF transceiver and a powerful Cortex®-M0+ core, on which a
complete power-optimized stack for Bluetooth Low Energy protocol runs, providing
master
Mbps).
/ slave role support
GAP: central, peripheral, observer or broadcaster roles
ATT/GATT: client and server
SM: privacy, authentication and authorization
L2CAP
Link layer: AES-128 encryption and decryption
18/110DS13259 Rev 1
STM32WB10CCFunctional overview
In addition, according to Bluetooth specification v5.2, the BLE block provides:
Multiple roles simultaneous support
Master/slave and multiple roles simultaneously
LE data packet length extension (making it possible to reach 800 kbps at application
level)
LE privacy 1.2
LE secure connections
Flexible Internet connectivity options
The device allows the applications to meet the tight peak current requirements imposed by
the use of standard coin cell batteries.
Ultra-low-power sleep modes and very short transition time between operating modes result
in very low average current consumption during real operating conditions, resulting in longer
battery life.
The BLE block integrates a full bandpass balun, thus reducing the need for external
components.
The link between the Cortex®-M4 application processor (CPU1) running the application, and
the BLE stack running on the dedicated Cortex
®
-M0+ (CPU2) is performed through a
normalized API, using a dedicated IPCC.
3.6.3 RF pin description
The RF block contains dedicated pins, listed in Table 3.
:
NameTypeDescription
RF1
OSC_OUT
OSC_IN
RF_TX_
MOD_EXT_PA
VDDRFV
VSSRF
1. The exposed pad must be connected to GND plane for correct RF operation.
(1)
RF Input/output, must be connected to the antenna through a low-pass matching network
32 MHz main oscillator, also used as HSE source
I/O
External PA transmit control
Dedicated supply, must be connected to V
DD
VSSTo be connected to GND
Table 3. RF pin list
DD
3.6.4 Typical RF application schematic
The schematic in Figure 3 and the external components listed in Table 3 are purely
indicative. For more details refer to the “Reference design” provided in separate documents.
DS13259 Rev 119/110
43
Functional overviewSTM32WB10CC
MS53575V1
STM32WB
microcontroller
V
DD
OSC_IN
OSC_OUT
VDDRF
VSSRF
RF1
Antenna
Cf1Cf2
Lf1
Lf2
X1
C1
Antenna filter
(including exposed pad)
32 MHz
Figure 3. External components for the RF part
ComponentDescriptionValue
C1Decoupling capacitance for RF100 nF // 100 pF
X132 MHz crystal
Antenna filterAntenna filter and matching networkRefer to AN5165, on www.st.com
Antenna2.4 GHz band antenna-
1. e.g. NDK reference: NX2016SA 32 MHz EXS00A-CS06654.
Table 4. Typical external components
(1)
32 MHz
Note:For more details refer to AN5165 “Development of RF hardware using STM32WB
microcontrollers” available on www.st.com.
3.7 Power supply management
3.7.1 Power supply schemes
The device has different voltage supplies (see Figure 5) and can operate within the following
voltage ranges:
V
DD
system functions such as RF, reset, power management and internal clocks. It is
provided externally through VDD pins. V
V
DDA
be independent from the V
= 2.0 to 3.6 V: external power supply for I/Os (V
= 2.0 to 3.6 V: external analog power supply for ADC. The V
must be always connected to VDD pins.
voltage. When not used V
DD
DDRF
), the internal regulator and
DDIO
must be connected to VDD.
DDA
voltage level can
DDA
20/110DS13259 Rev 1
STM32WB10CCFunctional overview
MSv47490V1
0.3
1
V
BOR0
3.6
Operating modePower-onPower-downtime
V
V
DDX
(1)
V
DD
Invalid supply areaV
DDX
< V
DD
+ 300 mV
V
DDX
independent from V
DD
During power up/down, the following power sequence requirements must be respected:
When VDD is below 1 V the other power supply (V
V
+ 300 mV
DD
When V
is above 1 V all power supplies are independent.
DD
), must remain below
DDA
Figure 4. Power-up/down sequence
1. V
refers to V
DDX
DDA
.
During the power down phase, VDD can temporarily become lower than other supplies only
if the energy provided to the MCU remains below 1 mJ. This allows the external decoupling
capacitors to be discharged with different time constants during the power down transient
phase.
Note:VDD and V
must be wired together, so they can follow the same voltage sequence.
DDRF
DS13259 Rev 121/110
43
Functional overviewSTM32WB10CC
MS53576V2
VBAT
IOs
Wakeup domain (V
DDIO
)
Analog domain
Interruptible domain (V
DD12I
)
Switch domain (V
SW
)
(CPU1, CPU2,
peripherals)
Level shifter
Power switch
V
BAT
ADC
V
DDA
V
REF-
V
DD
HSI, HSE,
PLL,
LSI1, LSI2,
IWDG, RF
IOs
V
SS
V
SS
IO
logic
V
REF+
V
SW
LSE, RTC,
backup registers
IO
logic
Backup domain
Power switch
V
SS
V
BKP12
SRAM1,
SRAM2a,
SRAM2b
Power
switch
V
SS
On domain (V
DD12O
)
Power
switch
V
SS
SysConfig, EXTI,
RCC, PwrCtrl,
LPTIM, USART1
=
=
LPR
MR
RFR
V
DD
RF domain
Radio
V
DDRF
V
SSRF
(including exposed pad)
V
SS
V
SS
V
SS
V
SS
Figure 5. Power supply overview
22/110DS13259 Rev 1
STM32WB10CCFunctional overview
3.7.2 Linear voltage regulator
Three embedded linear voltage regulators supply most of the digital and RF circuitries, the
main regulator (MR), the low-power regulator (LPR) and the RF regulator (RFR).
The MR is used in the Run and Sleep modes and in the Stop 0 mode.
The LPR is used in Low-Power Run, Low-Power Sleep and Stop 1 modes. It is also
used to supply the SRAMs in Standby with retention.
The RFR is used to supply the RF analog part, its activity is automatically managed by
the RF subsystem.
All the regulators are in power-down in Standby and Shutdown modes: the regulator output
is in high impedance, and the kernel circuitry is powered down, inducing zero consumption.
The ultralow-power STM32WB10CC supports dynamic voltage scaling to optimize its power
consumption in run mode. The voltage from the main regulator that supplies the logic
(VCORE) can be adjusted according to the system’s maximum operating frequency.
VCORE can also be supplied by the low-power regulator, the main regulator being switched
off. The system is then in Low-power run mode. In this case the CPU is running at up to
2
MHz, and peripherals with independent clock can be clocked by HSI16 (in this mode the
RF subsystem is not available).
3.7.3 Power supply supervisor
An integrated ultra-low-power brown-out reset (BOR) is active in all modes except
Shutdown ensuring proper operation after power-on and during power down. The device
remains in reset mode when the monitored supply voltage V
threshold, without the need for an external reset circuit.
The lowest BOR level is 2.0 V at power on, and other higher thresholds can be selected
through option bytes.The device features an embedded programmable voltage detector
(PVD) that monitors the V
interrupt can be generated when V
higher than the V
threshold. The interrupt service routine can then generate a warning
PVD
message and/or put the MCU into a safe state. The PVD is enabled by software.
3.7.4 Low-power modes
This ultra-low-power device supports several low-power modes to achieve the best
compromise between low-power consumption, short startup time, available peripherals and
available wakeup sources.
By default, the microcontroller is in Run mode, after a system or a power on Reset. It is up to
the user to select one of the low-power modes described below:
Sleep
In Sleep mode, only the CPU1 is stopped. All peripherals, including the RF subsystem,
continue to operate and can wake up the CPU when an interrupt/event occurs.
Low-power run
This mode is achieved with VCORE supplied by the low-power regulator to minimize
the regulator operating current. The code can be executed from SRAM or from the
Flash memory, and the CPU1 frequency is limited to 2 MHz. The peripherals with
DD
power supply and compares it with the V
DD
drops below the V
DD
threshold and/or when VDD is
PVD
is below a specified
threshold. An
PVD
DS13259 Rev 123/110
43
Functional overviewSTM32WB10CC
independent clock can be clocked by HSI16. The RF subsystem is not available in this
mode and must be OFF.
Low-power sleep
This mode is entered from the low-power run mode. Only the CPU1 clock is stopped.
When wakeup is triggered by an event or an interrupt, the system reverts to the
low-power run mode. The RF subsystem is not available in this mode and must be
OFF.
Stop 0 and Stop 1
Stop modes achieve the lowest power consumption while retaining the content of all
the SRAM and registers. The LSE (or LSI) is still running.
The RTC can remain active (Stop mode with RTC, Stop mode without RTC).
Some peripherals with wakeup capability can enable the HSI16 RC during Stop modes
to detect their wakeup condition.
Two modes are available: Stop 0 and Stop 1.
Stop 1 offers several active peripherals and wakeup sources. In Stop 0 mode the main
regulator remains ON, allowing a very fast wakeup time but with higher consumption.
In these modes the RF subsystem can wait for incoming events in all Stop modes.
The system clock when exiting from Stop 0 Stop1 modes can be either MSI up to
48 MHz or HSI16 if the RF subsystem is disabled. If the RF subsystem is used the exits
must be set to HSI16 only.
Standby
The Standby mode is used to achieve the lowest power consumption with BOR. The
internal regulator is switched off so that the VCORE domain is powered off.
The RTC can remain active (Standby mode with RTC).
The brown-out reset (BOR) always remains active in Standby mode.
The state of each I/O during standby mode can be selected by software: I/O with
internal pull-up, internal pull-down or floating.
After entering Standby mode, register content is lost except for registers in the Backup
domain and Standby circuitry. Optionally, SRAMs can be retained in Standby mode,
supplied by the low-power regulator (Standby with 48 KB SRAM retention mode).
The device exits Standby mode when an external reset (NRST pin), an IWDG reset,
WKUP pin event (configurable rising or falling edge), or an RTC event occurs (alarm,
periodic wakeup, timestamp, tamper) or a failure is detected on LSE (CSS on LSE, or
from the RF system wakeup).
The system clock after wakeup is 16 MHz, derived from the HSI16
24/110DS13259 Rev 1
STM32WB10CCFunctional overview
In this mode the RF can be used.
Shutdown
The Shutdown mode allows to achieve the ultimate lowest power consumption. The
internal regulator is switched off so that the VCORE domain is powered off.
The RTC can remain active (Shutdown mode with RTC, Shutdown mode without RTC).
The BOR is not available in Shutdown mode. No power voltage monitoring is possible
in this mode, therefore the switch to Backup domain is not supported.
SRAM1, SRAM2a, SRAM2b and register contents are lost except for registers in the
Backup domain.
The device exits Shutdown mode when an external reset (NRST pin), a WKUP pin
event (configurable rising or falling edge), or an RTC event occurs (alarm, periodic
wakeup, timestamp, tamper).
The system clock after wakeup is 4 MHz, derived from the MSI.
In this mode the RF is no longer operational.
When the RF subsystem is active, it changes the power state according to its needs (Run,
Stop, Standby). This operation is transparent for the CPU1 host application and managed by
a dedicated HW state machine. At any given time the effective power state reached is the
higher one needed by both the CPU1 and RF sub-system.
Tabl e 5 summarizes the peripheral features over all available modes. Wakeup capability is
detailed in gray cells.
Table 5. Functionalities depending on system operating mode
(1)
Stop0Stop1Standby Shutdow
Peripheral
Run
Sleep
Low-power run
-
Low-power sleep
Wakeup capability
-
Wakeup capability
-
-
Wakeup capability
VBAT
Wakeup capability
CPU1Y-Y----------
CPU2Y-Y--
Radio-system (BLE)YY---
Flash memoryYYOOR
SRAM1Y O
SRAM2aY O
SRAM2bY O
(3)
(3)
(3)
(3)
YO
(3)
YO
(3)
YO
Backup registersYYYYR
Brown-out reset (BOR)YYYYY
Programmable voltage detector
(PVD)
OOO O O
--------
Y-Y-Y
(2)
---
-R-R-R-R
R-R-O
R-R-O
R-R-O
(2)
----
(2)
----
(2)
----
-R-R-R-R
YYYYY- --
OOO- ----
DMAx (x=1)OOOO---------
High speed internal (HSI16)OOOOO
(4)
(4)
-O
------
DS13259 Rev 125/110
43
Functional overviewSTM32WB10CC
Table 5. Functionalities depending on system operating mode
(1)
(continued)
Stop0Stop1Standby Shutdow
Peripheral
Run
Sleep
Low-power run
-
Low-power sleep
Wakeup capability
-
Wakeup capability
-
-
Wakeup capability
VBAT
Wakeup capability
High speed external (HSE)OOOO---------
Low speed internal (LSI)OOOOO
Low speed external (LSE)OOOOO
Multi-speed internal (MSI)OOOO-
Clock security system (CSS)OOOO-
Clock security system on LSEOOOOO
RTC / Auto wakeupOOOOO
Number of RTC tamper pins11111
USART1OOOOO
I2C1OOOOO
-O-O----
-O-O-O-O
--------
--------
OOOOO- --
OOOOOOOO
O1O1O1O1
(5)O(5)O(5)O(5)
(6)O(6)O(6)O(6)
-----
-----
SPIx (x=1)OOOO-
ADC1OOOO-
Temperature sensorOOOO-
Timers (TIMx)OOOO-
Low-power timer 1 (LPTIM1)OOOOO
Low-power timer 2 (LPTIM2)OOOOO
Independent watchdog (IWDG) OOOOO
Window watchdog (WWDG)OOOO-
SysTick timerOOOO-
Touch sensing controller (TSC)OOOO-
True random number generator
(RNG)
OO - - -
--------
--------
--------
--------
OOO- ----
OOO- ----
OOOOO- --
--------
--------
--------
--------
AES hardware acceleratorOOOO---------
CRC calculation unitOOOO-
IPCCO-O--
HSEMO-O--
PKAOOOO-
GPIOsOOOOO
--------
--------
--------
--------
OOO
(7)
2
pins
(8)
(9)
2
pins
(9)
-
26/110DS13259 Rev 1
STM32WB10CCFunctional overview
1. Legend: Y = Yes (enabled). O = Optional (disabled by default, can be enabled by software).
R = data retained. - = Not available. Gray cells indicate Wakeup capability.
2. The SRAM1, SRAM2a and SRAM2b content needs to be retained via the PWR_CR3.RRS bit.
3. The SRAM clock can be gated on or off.
4. Some peripherals with wakeup from Stop capability can request HSI16 to be enabled. In this case, HSI16
is woken up by the peripheral, and only feeds the peripheral which requested it. HSI16 is automatically put
off when the peripheral does not need it anymore.
5. UART reception is functional in Stop mode, and generates a wakeup interrupt on Start, address match or
received frame event.
6. I2C address detection is functional in Stop mode, and generates a wakeup interrupt in case of address
match.
7. I/Os can be configured with internal pull-up, pull-down or floating in Standby mode.
8. The I/Os with wakeup from Standby/Shutdown capability are PA0 and PA2.
9. I/Os can be configured with internal pull-up, pull-down or floating in Shutdown mode but the configuration is
lost when exiting the Shutdown mode.
DS13259 Rev 127/110
43
28/110DS13259 Rev 1
Table 6. STM32WB10CC modes overview
ModeRegulatorCPU1FlashSRAMClocksDMA and PeripheralsWakeup sourceConsumption
Run MRYesON
LPRunLPRYesON
Sleep MRNoON
(2)
(2)
(2)
ONAnyAllN/A91 µA/MHzN/A
Any
ON
except
All except RF and RNGN/A90 µA/MHzTBD µs
PLL
ON
(3)
AnyAll
Any interrupt
or event
28 µA/MHzTBD cycles
(1)
Functional overviewSTM32WB10CC
Wakeup time
LPSleepLPRNoON
(2)
ON
Stop 0MRNoOFFON
Stop 1LPRNoOFFON
SRAMs
Standby
LPR
NoOFF
OFFOFF
ON
(3)
Any
except
PLL
LSE, LSI,
(4)
HSE
(5)
HSI16
LSE, LSI,
(4)
HSE
(5)
HSI16
LSE, LSI
All except RF and RNG
RF, BOR, PVD, RTC, IWDG,
,
USART1
(6)
, I2C1
LPTIMx (x=1, 2)
(7)
All other peripherals are frozen.
RF, BOR, PVD, RTC, IWDG,
,
USART1
(6)
, I2C1
LPTIMx (x=1, 2)
(7)
All other peripherals are frozen.
RF, BOR, RTC, IWDG
All other peripherals are
powered off.
I/O configuration can be floating,
pull-up or pull-down
,
,
Any interrupt
or event
Reset pin, all I/Os, RF,
BOR, PVD, RTC,
IWDG, USART1, I2C1,
LPTIMx (x=1, 2)
Reset pin, all I/Os
RF, BOR, PVD, RTC,
IWDG, USART1, I2C1,
LPTIMx (x=1, 2)
RF, Reset pin
Two I/Os (WKUPx)
(8)
BOR, RTC, IWDG
3.05 µA w/o RTC
3.45 µA w RTC
0.345 µA w/o RTC
0.70 µA w RTC
0.245 µA w/o RTC
0.600 µA w RTC
RTC
All other peripherals are
ShutdownOFFNoOFFOFFLSE
I/O configuration can be floating,
1. Typical current at VDD = 2.4 V, 25 °C. for STOPx, SHUTDOWN and Standby, else VDD = 3.3 V, 25 °C.
2. The Flash memory controller can be placed in power-down mode if the RF subsystem is not in use and all the program is run from the SRAM.
3. The SRAM1 and SRAM2 clocks can be gated off independently.
4. HSE (32 MHz) automatically used when RF activity is needed by the RF subsystem.
powered off.
pull-up or pull-down
(9)
Two I/Os (WKUPx)
RTC
(8)
0.018 µA w/o RTC
,
0.425 µA w/ RTC
27 µA/MHzTBD cycles
100 µATBD µs
TBD µs
TBD µs
-
5. HSI16 (16 MHz) automatically used by some peripherals.
6. U(S)ART reception is functional in Stop mode, and generates a wakeup interrupt on Start, Address match or Received frame event.
7. I2C address detection is functional in Stop mode, and generates a wakeup interrupt in case of address match.
8. I/Os with wakeup from Standby/Shutdown capability: PA0, PA2.
9. I/Os can be configured with internal pull-up, pull-down or floating but the configuration is lost immediately when exiting the Shutdown mode.
DS13259 Rev 129/110
STM32WB10CCFunctional overview
Functional overviewSTM32WB10CC
3.7.5 Reset mode
To improve the consumption under reset, the I/Os state under and after reset is “analog
state” (the I/O Schmitt trigger is disabled). In addition, the internal reset pull-up is
deactivated when the reset source is internal.
3.8 VBAT operation
The VBAT pin allows to power the device VBAT domain (RTC, LSE and Backup registers)
from an external battery, an external supercapacitor, or from V
when no external battery
DD
nor an external supercapacitor are present. One anti-tamper detection pin is available in
VBAT mode.
VBAT operation is automatically activated when VDD is not present.
An internal VBAT battery charging circuit is embedded and can be activated when VDD is
present.
Note:When the microcontroller is supplied only from VBAT, external interrupts and RTC
alarm/events do not exit it from VBAT operation.
3.9 Interconnect matrix
Several peripherals have direct connections between them. This allows autonomous
communication between peripherals, saving CPU1 resources and, consequently, reducing
power supply consumption. In addition, these hardware connections result in fast and
predictable latency.
Depending on peripherals, these interconnections can operate in Run, Sleep, Low-power
run and Sleep, Stop 0 and Stop 1 modes.