STM32F0x2 crystal-less USB 2.0 FS enlarges the STM32 F0 series with up to 128 Kbytes of Flash and 16 Kbytes of SRAM
These new STM32 F0 devices offer a crystal-less USB 2.0 FS interface with a link power management (LPM) feature and compliant with battery charger detection (BCD) specification 1.2, thus eliminating the need for an external crystal oscillator to generate the precision clock required by the USB protocol. Together with the support of CAN, USART, I²C, SPI (I²S) and HDMI CEC, the new STM32 F0 devices enable product developers to increase system integration, reduce costs, and exceed the traditional price/performance limitations imposed by older, proprietary 8-bit or 16-bit microcontrollers for USB device or USB- controller applications.
The STM32F072 series provides 64 to 128 Kbytes of Flash memory in 48-, 64- or 100-pin packages. The STM32F042 series comprises variants with 16 to 32 Kbytes of Flash memory and 20-, 28-, 32- and 48-pin package options.
As part of our embedded online event, we had the pleasure of filming with Reinhard Keil, a Senior Director of Embedded Tools at ARM.
This video is about the STM32L5, our recently announced ultra-low power microcontroller bringing a new security dimension. The STM32L5 is now in full production and all its ecosystem is available including hardware kits, software tools, firmware and all documentations of course. This is our first STM32 based on Cortex-M33 and its Trustzone and using specific ST security implementation - watch the video to find out more!
The STM32L5 is based on Arm® Cortex-M33 and TrustZone® technology combined with STMicroelectronics security implementation. On your STM32L562E-DK discovery board, TrustZone is disabled (factory setting) and you can develop as on any other STM32 device. This video shows how to enable TrustZone on STM32L562E-DK discovery using STM32CubeProgrammer and create, compile and debug or run a new project with STM32CubeIDE. It also shows how to open an example project delivered in STM32CubeL5 MCU Package, modify, compile and debug or run it. For further information, you can refer to AN5394 and AN5424 application notes.