LQFP48 (7 x 7 mm)
LQFP64 (10 x 10 mm)
LQFP80 (12 x 12 mm)
LQFP32 (7 x 7 mm)
UFBGA64
(5 x 5 mm)
UFQFPN32 (5 x 5 mm)
UFQFPN48 (7 x 7 mm)
WLCSP49
(Pitch 0.4)
FBGA
LQFP100 (14 x 14 mm)
Arm® Cortex®-M4 32b MCU+FPU, 170 MHz / 213DMIPS,
up to 128 KB Flash, 32KB SRAM, rich analog, math accelerator
Features
• Core: Arm® 32-bit Cortex®-M4 CPU with FPU,
Adaptive real-time accelerator (ART
Accelerator) allowing 0-wait-state execution
from Flash memory, frequency up to 170 MHz
with 213 DMIPS, MPU, DSP instructions
• Operating conditions:
– VDD, VDDA voltage range:
1.71 V to 3.6 V
• Mathematical hardware accelerators
– CORDIC for trigonometric functions
• Up to 86 fast I/Os
– All mappable on external interrupt vectors
– Several I/Os with 5 V tolerant capability
supply for RTC and backup registers
BAT
to 48 MHz crystal oscillator
Internal 32 kHz RC oscillator (± 5%)
STM32G431xB
Datasheet - production data
• Interconnect matrix
• 12-channel DMA controller
• 2 x ADCs 0.25 µs(up to 23 channels).
Resolution up to 16-bit with hardware
oversampling, 0 to 3.6 V conversion range
• 4 x 12-bit DAC channels
– 2 x buffered external channels 1 MSPS
– 2 x unbuffered internal channels 15 MSPS
• 4 x ultra-fast rail-to-rail analog comparators
• 3 x operational amplifiers that can be used in
PGA mode, all terminals accessible
• Internal voltage reference buffer (VREFBUF)
supporting three output voltages (2.048 V,
2.5 V, 2.95 V)
• 14 timers:
– 1 x 32-bit timer and 2 x 16-bit timers with up
to four IC/OC/PWM or pulse counter and
quadrature (incremental) encoder input
– 2 x 16-bit 8-channel advanced motor
control timers, with up to 8 x PWM
channels, dead time generation and
emergency stop
– 1 x 16-bit timer with 2 x IC/OCs, one
OCN/PWM, dead time generation and
emergency stop
– 2 x 16-bit timers with IC/OC/OCN/PWM,
dead time generation and emergency stop
– 2 x watchdog timers (independent, window)
– 1 x SysTick timer: 24-bit downcounter
– 2 x 16-bit basic timers
– 1 x low-power timer
May 2019DS12589 Rev 11/198
This is information on a product in full production.
www.st.com
STM32G431x6 STM32G431x8 STM32G431xB
• Calendar RTC with alarm, periodic wakeup
from stop/standby
• Communication interfaces
– 1 x FDCAN controller supporting flexible
data rate
– 3 x I
2
C Fast mode plus (1 Mbit/s) with
20 mA current sink, SMBus/PMBus,
wakeup from stop
– 4 x USART/UARTs (ISO 7816 interface,
LIN, IrDA, modem control)
–1 x LPUART
– 3 x SPIs, 4 to 16 programmable bit frames,
2 x with multiplexed half duplex I
2
S
– 1 x SAI (serial audio interface)
– USB 2.0 full-speed interface with LPM and
BCD support
– IRTIM (infrared interface)
– USB Type-C™ /USB power delivery
The Arm® Cortex®-M4 with FPU processor is the latest generation of Arm processors for
embedded systems. It was developed to provide a low-cost platform that meets the needs of
the MCU implementation, with a reduced pin count and with low-power consumption, while
delivering outstanding computational performance and an advanced response to interrupts.
The Arm
efficiency, delivering the expected high-performance from an Arm core in a memory size
usually associated with 8-bit and 16-bit devices.
The processor supports a set of DSP instructions which allows an efficient signal processing
and a complex algorithm execution. Its single precision FPU speeds up the software
development by using metalanguage development tools to avoid saturation.
With its embedded Arm core, the STM32G431x6/x8/xB family is compatible with all Arm
tools and software.
Figure 1 shows the general block diagram of the STM32G431x6/x8/xB devices.
®
Cortex®-M4 with FPU 32-bit RISC processor features an exceptional code-
The ART accelerator is a memory accelerator that is optimized for the STM32 industrystandard Arm
the Arm
processor to wait for the Flash memory at higher frequencies.
®
®
Cortex®-M4 processors. It balances the inherent performance advantage of
Cortex®-M4 over Flash memory technologies, which normally requires the
3.3 Memory protection unit
The memory protection unit (MPU) is used to manage the CPU accesses to the memory
and to prevent one task to accidentally corrupt the memory or the resources used by any
other active task. This memory area is organized into up to 8 protected areas, which can be
divided in up into 8 subareas each. The protection area sizes range between 32 bytes and
the whole 4 gigabytes of addressable memory.
The MPU is especially helpful for applications where some critical or certified code has to be
protected against the misbehavior of other tasks. It is usually managed by an RTOS (realtime operating system). If a program accesses a memory location that is prohibited by the
MPU, the RTOS can detect it and take 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.4 Embedded Flash memory
The STM32G431x6/x8/xB devices feature 128 kbytes of embedded Flash memory which is
available for storing programs and data.
Flexible protections can be configured thanks to the option bytes:
• Readout protection (RDP) to protect the whole memory. Three levels of protection are
available:
– Level 0: no readout protection
– Level 1: memory readout protection; the Flash memory cannot be read from or written
to if either the debug features are connected or the boot in RAM or bootloader are
selected
– Level 2: chip readout protection; the debug features (Cortex-M4 JTAG and serial
wire), the boot in RAM and the bootloader selection are disabled (JTAG fuse). This
selection is irreversible.
•Write protection (WRP): the protected area is protected against erasing and
programming.
•Proprietary code readout protection (PCROP): a part of the Flash memory can be
protected against read and write from third parties. The protected area is execute-only
and 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. An
additional option bit (PCROP_RDP) allows to select if the PCROP area is erased or not
when the RDP protection is changed from Level 1 to Level 0.
•Securable memory area: a part of Flash memory can be configured by option bytes to
be securable. After reset this securable memory area is not secured and it behaves like
the remainder of main Flash memory (execute, read, write access). When secured, any
access to this securable memory area generates corresponding read/write error.
Purpose of the Securable memory area is to protect sensitive code and data (secure
keys storage) which can be executed only once at boot, and never again unless a new
reset occurs.
The Flash 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
•1 Kbyte (128 double word) OTP (one-time programmable) bytes for user data. The
OTP area is available in Bank 1 only. The OTP data cannot be erased and can be
written only once.
3.5 Embedded SRAM
STM32G431x6/x8/xB devices feature 32 Kbytes of embedded SRAM. This SRAM is split
into three blocks:
•16 Kbytes mapped at address 0x2000 0000 (SRAM1). The CM4 can access the
SRAM1 through the System Bus or through the I-Code/D-Code bus.
•6 Kbytes mapped at address 0x2000 4000 (SRAM2). The CM4 can access the SRAM2
through the System Bus or through the I-Code/D-Code bus. SRAM2 can be kept in
stop and standby modes.
•10 Kbytes mapped at address 0x1000 0000 (CCM SRAM). It is accessed by the CPU
through I-Code/D-Code bus for maximum performance.
It is also aliased at 0x2000 5800 address to be accessed by all masters (CPU, DMA1,
DMA2) through SBUS contiguously to SRAM1 and SRAM2.
The 32-bit multi-AHB bus matrix interconnects all the masters (CPU, DMAs) and the slaves
(Flash memory, RAM, AHB and APB peripherals). It also ensures a seamless and efficient
operation even when several high-speed peripherals work simultaneously.
Figure 2. Multi-AHB bus matrix
3.7 Boot modes
At startup, a BOOT0 pin (or nBOOT0 option bit)and an nBOOT1 option bit are used to select
one of three boot options:
•Boot from user Flash
•Boot from system memory
•Boot from embedded SRAM
The BOOT0 value may come from the PB8-BOOT0 pin or from an nBOOT0 option bit
depending on the value of a user nBOOT_SEL option bit to free the GPIO pad if needed.
The boot loader is located in the system memory. It is used to reprogram the Flash memory
by using USART, I2C, SPI, and USB through the DFU (device firmware upgrade).
The CORDIC provides hardware acceleration of certain mathematical functions, notably
trigonometric, commonly used in motor control, metering, signal processing and many other
applications.
It speeds up the calculation of these functions compared to a software implementation,
allowing a lower operating frequency, or freeing up processor cycles in order to perform
other tasks.
•Supports 16-bit and 32-bit fixed point input and output formats
•Low latency AHB slave interface
•Results can be read as soon as ready without polling or interrupt
•DMA read and write channels
3.9 Filter mathematical accelerator (FMAC)
The filter mathematical accelerator unit performs arithmetic operations on vectors. It
comprises a multiplier/accumulator (MAC) unit, together with address generation logic,
which allows it to index vector elements held in local memory.
The unit includes support for circular buffers on input and output, which allows digital filters
to be implemented. Both finite and infinite impulse response filters can be realized.
The unit allows frequent or lengthy filtering operations to be offloaded from the CPU, freeing
up the processor for other tasks. In many cases it can accelerate such calculations
compared to a software implementation, resulting in a speed-up of time critical tasks.
•24+2-bit accumulator with addition and subtraction
•16-bit input and output data
•256 x 16-bit local memory
•Up to three areas can be defined in memory for data buffers (two input, one output),
defined by programmable base address pointers and associated size registers
•Input and output sample buffers can be circular
•Buffer “watermark” feature reduces overhead in interrupt mode
•Filter functions: FIR, IIR (direct form 1)
•AHB slave interface
•DMA read and write data channels
3.10 Cyclic redundancy check calculation unit (CRC)
The CRC (cyclic redundancy check) calculation unit is used to get a CRC code using a
configurable generator with polynomial value and size.
Among other applications, the CRC-based techniques are used to verify data transmission
or storage integrity. In the scope of the EN/IEC 60335-1 standard, they offer a mean to verify
the Flash memory integrity.
The CRC calculation unit helps to compute a signature of the software during runtime, which
can be ulteriorly compared with a reference signature generated at link-time and which can
be stored at a given memory location.
3.11 Power supply management
3.11.1 Power supply schemes
The STM32G431x6/x8/xB devices require a 1.71 V to 3.6 V V
Several independent supplies, can be provided for specific peripherals:
•V
•V
= 1.71 V to 3.6 V
DD
V
is the external power supply for the I/Os, the internal regulator and the system
DD
analog such as reset, power management and internal clocks. It is provided externally
through the VDD pins.
= 1.62 V to 3.6 V (see Section 5: Electrical characteristics for the minimum VDDA
DDA
voltage required for ADC, DAC, COMP, OPAMP, VREFBUF operation).
V
is the external analog power supply for A/D converters, D/A converters, voltage
DDA
reference buffer, operational amplifiers and comparators. The V
is the power supply for RTC, external clock 32 kHz oscillator and backup registers
BAT
(through power switch) when V
•V
REF-, VREF+
V
is the input reference voltage for ADCs and DACs. It is also the output of the
REF+
internal voltage reference buffer when enabled.
When V
When V
DDA
DDA
< 2 V V
2 V V
must be equal to V
REF+
must be between 2 V and V
REF+
The internal voltage reference buffer supports three output voltages, which are
configured with VRS bits in the VREFBUF_CSR register:
–V
–V
–V
V
REF-
= 2.048 V
REF+
= 2.5 V
REF+
= 2.95 V
REF+
is double bonded with V
3.11.2 Power supply supervisor
The device has an integrated ultra-low-power brown-out reset (BOR) active in all modes
(except for Shutdown mode). The BOR ensures proper operation of the device after poweron and during power down. The device remains in reset mode when the monitored supply
voltage V
The lowest BOR level is 1.71 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 VPVD threshold. The interrupt service routine can then generate a warning
message and/or put the MCU into a safe state. The PVD is enabled by software.
is below a specified threshold, without the need for an external reset circuit.
DD
power supply and compares it to the VPVD threshold. An
DD
voltage and should preferably be connected to VDD when
is not present.
DD
.
DDA
.
DDA
.
SSA
drops below the VPVD threshold and/or when VDD is
DD
In addition, the device embeds a peripheral voltage monitor which compares the
independent supply voltages V
, with a fixed threshold in order to ensure that the
DDA
peripheral is in its functional supply range.
3.11.3 Voltage regulator
Two embedded linear voltage regulators, main regulator (MR) and low-power regulator
(LPR), supply most of digital circuitry in the device. The MR is used in Run and Sleep
modes. The LPR is used in Low-power run, Low-power sleep and Stop modes. In Standby
and Shutdown modes, both regulators are powered down and their outputs set in highimpedance state, such as to bring their current consumption close to zero.
The device 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.
The main regulator (MR) operates in the following ranges:
•Range 1 boost mode with the CPU running at up to 170 MHz.
•Range 1 normal mode with CPU running at up to 150 MHz.
By default, the microcontroller is in Run mode after system or power Reset. It is up to the
user to select one of the low-power modes described below:
•Sleep mode: In Sleep mode, only the CPU is stopped. All peripherals continue to
operate and can wake up the CPU when an interrupt/event occurs.
•Low-power run mode: This mode is achieved with VCORE supplied by the low-power
regulator to minimize the regulator's operating current. The code can be executed from
SRAM or from Flash, and the CPU frequency is limited to 2 MHz. The peripherals with
independent clock can be clocked by HSI16.
•Stop mode: In Stop mode, the device achieves the lowest power consumption while
retaining the SRAM and register contents. All clocks in the VCORE domain are
stopped. The PLL, as well as the HSI16 RC oscillator and the HSE crystal oscillator are
disabled. The LSE or LSI keep 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 mode, so as to get clock for processing the wakeup event.
•Standby mode: The Standby mode is used to achieve the lowest power consumption
with brown-out reset, BOR. The internal regulator is switched off to power down the
VCORE domain. The PLL, as well as the HSI16 RC oscillator and the HSE crystal
oscillator are also powered down. The RTC can remain active (Standby mode with
RTC, Standby mode without RTC). The BOR always remains active in Standby mode.
For each I/O, the software can determine whether a pull-up, a pull-down or no resistor
shall be applied to that I/O during Standby mode. Upon entering Standby mode, SRAM
and register contents are lost except for registers in the RTC domain and standby
circuitry. The device exits Standby mode upon external reset event (NRST pin), IWDG
reset event, wakeup event (WKUP pin, configurable rising or falling edge) or RTC
event (alarm, periodic wakeup, timestamp, tamper), or when a failure is detected on
LSE (CSS on LSE).
•Shutdown mode: The Shutdown mode allows to achieve the lowest power
consumption. The internal regulator is switched off to power down the VCORE domain.
The PLL, as well as the HSI16 and LSI RC-oscillators and HSE crystal oscillator are
also powered down. 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, switching to RTC domain is not
supported. SRAM and register contents are lost except for registers in the RTC
domain. The device exits Shutdown mode upon external reset event (NRST pin),
IWDG reset event, wakeup event (WKUP pin, configurable rising or falling edge) or
RTC event (alarm, periodic wakeup, timestamp, tamper).
3.11.5 Reset mode
In order 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.11.6 VBAT operation
The VBAT pin allows to power the device VBAT domain from an external battery, an external
supercapacitor, or from V
supercapacitor is present. The VBAT pin supplies the RTC with LSE and the backup
registers. Three anti-tamper detection pins are available in VBAT mode.
when there is no external battery and when an external
The VBAT operation is automatically activated when VDD is not present. An internal VBAT
battery charging circuit is embedded and can be activated when V
is present.
DD
Note:When the microcontroller is supplied from VBAT, neither external interrupts nor RTC
alarm/events exit the microcontroller from the VBAT operation.
Several peripherals have direct connections between them. This allows autonomous
communication between peripherals, saving CPU resources thus power supply
consumption. In addition, these hardware connections allow fast and predictable latency.
Depending on peripherals, these interconnections can operate in Run, Sleep and Stop
modes.
The clock controller distributes the clocks coming from different oscillators to the core and
the peripherals. It also manages clock gating for low-power modes and ensures clock
robustness. It features:
•Clock prescaler: to get the best trade-off between speed and current consumption,
the clock frequency to the CPU and peripherals can be adjusted by a programmable
prescaler
•Safe clock switching: clock sources can be changed safely on the fly in run mode
through a configuration register.
•Clock management: to reduce power consumption, the clock controller can stop the
clock to the core, individual peripherals or memory.
•System clock source: three different sources can deliver SYSCLK system clock:
–4 - 48 MHz high-speed oscillator with external crystal or ceramic resonator (HSE).
It can supply clock to system PLL. The HSE can also be configured in bypass
mode for an external clock.
–16 MHz high-speed internal RC oscillator (HSI16), trimmable by software. It can
supply clock to system PLL.
–System PLL with maximum output frequency of 170 MHz. It can be fed with HSE
or HSI16 clocks.
•RC48 with clock recovery system (HSI48): internal HSIRC48 MHz clock source can
be used to drive the USB or the RNG peripherals.
•Auxiliary clock source: two ultra-low-power clock sources for the real-time clock
(RTC):
–32.768 kHz low-speed oscillator with external crystal (LSE), supporting four drive
capability modes. The LSE can also be configured in bypass mode for using an
external clock.
–32 kHz low-speed internal RC oscillator (LSI) with ±5% accuracy, also used to
RNG) have their own clock independent of the system clock.
•Clock security system (CSS): in the event of HSE clock failure, the system clock is
automatically switched to HSI16 and, if enabled, a software interrupt is generated. LSE
clock failure can also be detected and generate an interrupt.
•Clock-out capability:
–MCO: microcontroller clock output: it outputs one of the internal clocks for external
use by the application
–LSCO: low speed clock output: it outputs LSI or LSE in all low-power modes.
Several prescalers allow to configure the AHB frequency, the High-speed APB (APB2) and
the low speed APB (APB1) domains. The maximum frequency of the AHB and the APB
domains is 170 MHz.
Each of the GPIO pins can be configured by software as output (push-pull or open-drain), as
input (with or without pull-up or pull-down) or as peripheral alternate function. Most of the
GPIO pins are shared with digital or analog alternate functions. Fast I/O toggling can be
achieved thanks to their mapping on the AHB2 bus.
The I/Os alternate function configuration can be locked if needed following a specific
sequence in order to avoid spurious writing to the I/Os registers.
3.15 Direct memory access controller (DMA)
The device embeds 2 DMAs. Refer to Table 4: DMA implementation for the features
implementation.
Direct memory access (DMA) is used in order to provide a high-speed data transfer
between peripherals and memory as well as from memory to memory. Data can be quickly
moved by DMA without any CPU actions. This keeps the CPU resources free for other
operations.
The two DMA controllers have 12 channels in total, each one dedicated to manage memory
access requests from one or more peripherals. Each controller has an arbiter for handling
the priority between DMA requests.
When a peripheral indicates a request for DMA transfer by setting its DMA request line, the
DMA request is pending until it is served and the corresponding DMA request line is reset.
The DMA request router allows to route the DMA control lines between the peripherals and
the DMA controllers of the product.
An embedded multi-channel DMA request generator can be considered as one of such
peripherals. The routing function is ensured by a multi-channel DMA request line
multiplexer. Each channel selects a unique set of DMA control lines, unconditionally or
synchronously with events on synchronization inputs.
For simplicity, the functional description is limited to DMA request lines. The other DMA
control lines are not shown in figures or described in the text. The DMA request generator
produces DMA requests following events on DMA request trigger inputs.
The STM32G431x6/x8/xB devices embed a nested vectored interrupt controller which is
able to manage 16 priority levels, and to handle up to 71 maskable interrupt channels plus
the 16 interrupt lines of the Cortex
•Interrupt entry vector table address passed directly to the core
•Allows early processing of interrupts
•Processing of late arriving higher priority interrupts
•Support for tail chaining
•Processor state automatically saved
•Interrupt entry restored on interrupt exit with no instruction overhead
The NVIC hardware block provides flexible interrupt management features with minimal
interrupt latency.
3.17.2 Extended interrupt/event controller (EXTI)
The extended interrupt/event controller consists of 39 edge detector lines used to generate
interrupt/event requests and to wake-up the system from the Stop mode. Each external line
can be independently configured to select the trigger event (rising edge, falling edge, both)
and can be masked independently.
A pending register maintains the status of the interrupt requests. The internal lines are
connected to peripherals with wakeup from Stop mode capability. The EXTI can detect an
external line with a pulse width shorter than the internal clock period. Up to 86 GPIOs can
be connected to the 16 external interrupt lines.
The device embeds two successive approximation analog-to-digital converters with the
following features:
•12-bit native resolution, with built-in calibration
•4 Msps maximum conversion rate with full resolution
–Down to 25 ns sampling time
–Increased conversion rate for lower resolution (up to 6.66 Msps for 6-bit
resolution)
•One external reference pin is available on all packages, allowing the input voltage
range to be independent from the power supply
•Single-ended and differential mode inputs
•Low-power design
–Capable of low-current operation at low conversion rate (consumption decreases
linearly with speed)
–Dual clock domain architecture: ADC speed independent from CPU frequency
•Highly versatile digital interface
–Single-shot or continuous/discontinuous sequencer-based scan mode: 2 groups
of analog signals conversions can be programmed to differentiate background and
high-priority real-time conversions
–Each ADC support multiple trigger inputs for synchronization with on-chip timers
and external signals
–Results stored into a data register or in RAM with DMA controller support
–Data pre-processing: left/right alignment and per channel offset compensation
–Built-in oversampling unit for enhanced SNR
–Channel-wise programmable sampling time
–Analog watchdog for automatic voltage monitoring, generating interrupts and
trigger for selected timers
–Hardware assistant to prepare the context of the injected channels to allow fast
context switching
–Flexible sample time control
–Hardware gain and offset compensation
3.18.1 Temperature sensor
The temperature sensor (TS) generates a voltage VTS that varies linearly with temperature.
The temperature sensor is internally connected to the ADC1_IN16 input channel which is
used to convert the sensor output voltage into a digital value.
The sensor provides good linearity but it has to be calibrated to obtain good overall
accuracy of the temperature measurement. As the offset of the temperature sensor varies
from chip to chip due to process variation, the uncalibrated internal temperature sensor is
suitable for applications that detect temperature changes only.
To improve the accuracy of the temperature sensor measurement, each device is
individually factory-calibrated by ST. The temperature sensor factory calibration data are
stored by ST in the system memory area, accessible in read-only mode.
TS ADC raw data acquired at a
temperature of 30 °C (± 5 °C),
V
DDA
TS ADC raw data acquired at a
temperature of 110 °C (± 5 °C),
V
DDA
3.18.2 Internal voltage reference (V
The internal voltage reference (VREFINT) provides a stable (bandgap) voltage output for
the ADC and the comparators. The VREFINT is internally connected to the ADC1_IN18
input channel. The precise voltage of VREFINT is individually measured for each part by ST
during production test and stored in the system memory area. It is accessible in read-only
mode.
Calibration value nameDescriptionMemory address
Table 6. Internal voltage reference calibration values
Raw data acquired at a
VREFINT
temperature of 30 °C (± 5 °C),
V
DDA
= V
REF+
= V
REF+
REFINT
= V
REF+
0x1FFF 75A8 - 0x1FFF 75A9
= 3.0 V (± 10 mV)
0x1FFF 75CA - 0x1FFF 75CB
= 3.0 V (± 10 mV)
)
0x1FFF 75AA - 0x1FFF 75AB
= 3.0 V (± 10 mV)
3.18.3 V
battery voltage monitoring
BAT
This embedded hardware enables the application to measure the V
the internal ADC1_IN17 channel. As the V
voltage may be higher than the VDDA, and
BAT
thus outside the ADC input range, the VBAT pin is internally connected to a bridge divider by
3. As a consequence, the converted digital value is one third of the V
3.19 Digital to analog converter (DAC)
Four 12 bit DAC channels (2 external buffered and 2 internal unbuffered) can be used to
convert digital signals into analog voltage signal outputs. The chosen design structure is
composed of integrated resistor strings and an amplifier in inverting configuration.
battery voltage using
BAT
voltage.
BAT
30/198DS12589 Rev 1
Loading...
+ 168 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.