DS14928 · DatasheetArm® Cortex®-M33 32-bit MCU with FPU, 144 MHz, 593 CoreMark®, up to 512‑Kbyte dual‑bank flash memory, 128-Kbyte RAM
Download .pdfOpen in the full document

Real-time clock (RTC), tamper and backup registers

Real-time clock (RTC), tamper and backup registers

Real-time clock (RTC)

The real-time clock (RTC) supports the following features:
  • Calendar with subsecond, seconds, minutes, hours (12 or 24 format), weekday, date, month, year, in BCD (binary‑coded decimal) format
  • Binary mode with 32-bit free-running counter
  • Automatic correction for 28, 29 (leap year), 30, and 31 days of the month
  • Two programmable alarms
  • On-the-fly correction from 1 to 32767 RTC clock pulses. This can be used to synchronize it with a controller clock.
  • Reference clock detection: a more precise second source clock (50 or 60 Hz) can be used to enhance the calendar precision.
  • Digital calibration circuit with 0.95 ppm resolution, to compensate for quartz crystal inaccuracy
  • Timestamp feature that can be used to save the calendar content. This function can be triggered by an event on the timestamp pin, or by a tamper event.
  • 17-bit auto-reload wake-up timer (WUT) for periodic events with programmable resolution and period
  • Privilege protection support:
    • Alarm A, alarm B, wake-up timer, and timestamp individual privileged protection

The RTC is functional in all low-power modes when it is clocked by the LSE.

All RTC events (alarm, wake-up timer, timestamp) can generate an interrupt and wake up the device from the low‑power modes.

Tamper and backup registers (TAMP)

The antitamper detection circuit is used to protect sensitive data from external attacks. Thirty-two 32‑bit backup registers are retained in all low-power modes. The backup registers, as well as other secrets in the device, are protected by this antitamper detection circuit with three tamper pins and six internal tampers. The external tamper pins can be configured for edge detection or level detection with or without filtering.

The TAMP main features are:

  • A tamper detection can optionally erase the backup registers, SRAM2, ICACHE, and cryptographic peripherals. The device resources protected by tamper are named “device secrets”.
  • 32 × 32‑bit backup registers
  • Up to three tamper pins for three external tamper detection events:
    • Passive tampers: Ultralow-power edge or level detection with internal pull-up hardware management
    • Configurable digital filter
  • Six internal tamper events to protect against transient attacks
  • Each tamper can be configured in two modes:
    • Confirmed mode: immediate erase of secrets on tamper detection, including backup registers erase
    • Potential mode: most of the secrets erase following a tamper detection are launched by software
  • Any tamper detection can generate an RTC timestamp event
  • Tamper configuration and backup registers privilege protection

Inter-integrated circuit interface (I2C)

The device embeds two I2C interfaces. Refer to Table 7 I2C implementation for feature implementation.

The I2C bus interface handles communications between the microcontroller and the serial I2C bus. It controls all I2C bus‑specific sequencing, protocol, arbitration, and timing.

It supports Standard-mode (Sm), Fast-mode (Fm), and Fast-mode Plus (Fm+).

The I2C peripheral is also system management bus (SMBus) and power management bus (PMBus®) compatible.

It can use DMA to reduce the CPU load.

The I²C peripheral supports:

  • I²C-bus specification rev03 compatibility:
    • Controller and target modes
    • Multicontroller capability
    • Standard-mode (up to 100 kHz)
    • Fast-mode (up to 400 kHz)
    • Fast-mode Plus (up to 1 MHz)
    • 7-bit and 10-bit addressing mode
    • Multiple 7-bit target addresses (2 addresses, 1 with configurable mask)
    • All 7-bit addresses acknowledge mode
    • General call
    • Programmable setup and hold times
    • Easy-to-use event management
    • Clock stretching (optional)
  • 1-byte buffer with DMA capability
  • Programmable analog and digital noise filters
  • SMBus specification rev 3.0 compatibility:
    • Hardware PEC (packet error checking) generation and verification with ACK control
    • Command and data acknowledge control
    • Address resolution protocol (ARP) support
    • Host and device support – SMBus alert
    • Timeouts and idle condition detection
  • PMBus rev 1.3 standard compatibility
  • Independent clock
  • Wake-up from Stop mode on address match
Table 7. I2C implementation
Features(1)I2C1I2C2
Standard-mode (up to 100 Kbit/s)XX
Fast mode (up to 400 Kbit/s)XX
Fast mode plus (Fm+) with 20 mA output drive I/Os (up to 1 Mbit/s)XX
Programmable analog and digital noise filtersXX
SMBus/PMBus hardware supportXX
Independent clockXX
Wake-up capabilityXX
1 X = supported.

Improved inter-integrated circuit interface (I3C)

The I3C interface handles communication between this device and others, such as sensors and the host processor, connected on an I3C bus.

An I3C bus is a two-wire, serial single-ended, multidrop bus, intended to improve a legacy I2C bus.

The I3C SDR-only peripheral implements all the features required by the MIPI® I3C specification v1.1. It can control all I3C bus-specific sequencing, protocol, arbitration, and timing, and can act as a controller (formerly known as master) or as a target (formerly known as slave). When acting as a controller, the I3C peripheral improves the features of the I2C interface while preserving some backward compatibility: it allows an I2C target to operate on an I3C bus in legacy I2C fast mode (Fm) or legacy I2C fast mode plus (Fm+), provided that the latter does not perform clock stretching. The I3C peripheral can be used with DMA to offload the CPU.

The I3C peripheral supports:

  • MIPI® I3C specification v1.1, as:
    • I3C SDR-only primary controller
    • I3C SDR-only secondary controller
    • I3C SDR-only target
  • I3C SCL bus clock frequency up to 12.5 MHz
  • Registers configuration from the host application via the APB target port
  • Queued data transfers:
    • Transmit FIFO (TX-FIFO) for data bytes/words to be transmitted on the I3C bus
    • Receive FIFO (RX-FIFO) for received data bytes/words on the I3C bus
    • For each FIFO, optional DMA mode with a dedicated DMA channel
  • Queued control/status transfers, when controller:
    • Control FIFO (C-FIFO) for control words to be sent on the I3C bus
    • Optional status FIFO (S-FIFO) for status words as received on the I3C bus
    • For each FIFO, optional DMA mode with a dedicated DMA channel
  • Messages:
    • Legacy I²C read/write messages to legacy I2C targets in Fm/Fm+
    • I3C SDR read/write private messages
    • I3C SDR broadcast CCC messages
    • I3C SDR read/write direct CCC messages
  • Frame-level management, when controller:
    • Optional C-FIFO and TX-FIFO preload
    • Multiple messages encapsulation
    • Optional arbitrable header generation on the I3C bus
    • HDR exit pattern generation on the I3C bus for error recovery
  • Programmable bus timing, when controller:
    • SCL high and low period
    • SDA hold time
    • Bus free (minimum) time
    • Bus available/idle condition time
    • Clock stall time
  • Target-initiated requests management:
    • Simultaneous support up to four targets, when controller
    • In-band interrupts, with programmable IBI payload (up to four bytes), with pending read notification support
    • Bus control request, with recovery flow support and hand-off delay
    • Hot-join mechanism
  • HDR exit pattern detection, when target
  • Bus error management:
    • CEx with x = 0, 1, 2, 3 when controller
    • TEx with x = 0, 1, ... , 6 when target
    • Bus control switch error and recovery
    • Target reset
  • Individual programmable event-based management:
    • Per-event identification with flag reporting and clear control
    • Host application notification via flag polling, and/or via interrupt with a per-event programmable enable
    • Error type identification
  • Wake-up from Stop mode(s), as controller:
    • On an in-band interrupt without payload
    • On a hot-join request
    • On a controller-role request
  • Wake-up from Stop mode(s), as target:
    • On a reset pattern
    • On a missed start
  • Multiclock domain management:
    • Separate APB clock and kernel clock, driven from independently programmed clock sources via the RCC, in addition to SCL clock
    • Minimum operating frequency for the kernel clock and the APB clock vs. the application-driven SCL clock
Table 8. I3C peripheral controller/target features versus MIPI® v1.1
Features(1)MIPI® I3C v1.1

I3C
peripheral when controller

I3C
peripheral when target

Comments
I3CSDR messageXXX-
Legacy I2C message (Fm/Fm+)XX-

Mandatory when controller and the I3C bus is mixed with (external) legacy I2C target(s).
Optional in MIPI v1.1 when target.

HDR DDR messageX--Optional in MIPI v1.1
HDR-TSL/TSP, HDR-BTX--
Dynamic address assignmentXXX-
Static addressXX-No (intended) support of I3C peripheral as a target on an I2C bus.
Grouped addressingXX-Optional in MIPI v1.1
CCCsXXXMandatory CCCs and some optional CCCs are supported.
Error detection and recoveryXXX-
In-band interrupt (with MDB)XXX-
Secondary controllerXXX-
Hot-join mechanismXXX-
Target resetXXX-
Synchronous timing controlXX-Optional in MIPI v1.1
Asynchronous timing control 0XX-
Asynchronous timing control 1, 2, 3X--
Device-to-device tunnelingXX-
Multilane data transferXX-
Monitoring device early terminationX--
1 X = supported.