STM32 MCUs products

Showing results for 
Search instead for 
Did you mean: 

Forum Posts

New possibilities for the ultra-low power segment!

STM32U0 is the first Cortex-M0+ with a static consumption of only 160 nA in standby mode with RTC (Real-Time Clock) and 16 nA in shutdown. It also achieves 118 points in CoreMark and targets SESIP level 3 and PSA level 1 focusing on firmware code pro...



Posted on May 16, 2018 at 20:06In NUCLEO-H743ZI  environment using the STM32CubeMX the:HAL_SPI_Receive_DMA(&hspi1, (uint8_t*)u8SpiRxBuffer, SIZE) function in Master Mode.It generates the clocks on the output pin correctly up to 16 byte of data.If th...

Need help with CRC unit

Posted on May 10, 2018 at 09:28STM32L452CMy code:__HAL_RCC_CRC_CLK_ENABLE(); CRC->POL = (uint32_t) 0x1021;//CRC-16-CCITT CRC->INIT = (uint32_t) 0xFFFF; CRC->CR = (uint32_t) 0x09;//REV_OUT = 0, REV_IN = 00, POLYSIZE = 01, RESET = 1 CRC->DR = '1'; CRC...

SVD files - SPI4 on STM32F303ZE, STM32F302XE

Posted on May 15, 2018 at 19:44The .SVD files ( for the STM32F303ZE and STM32F302XE seem to be incorrect with respect to the SPI4 IRQn, R...


Posted on March 30, 2018 at 20:42I'm trying to get working code from STM32CubeMX on STM32F746G-DISCO board. I'm using LwIP TCP/IP stack (which works fine - obtains IP address over DHCP) and STemWIN GUI library and there is the problem. LTDC has been...

zenobik by Associate II
  • 5 replies
  • 0 kudos

Resolved! STM32F412G-DISCO arduino pin assignment error

Posted on May 09, 2018 at 15:46When I create a project in CubeMX 4.25.0 with the STM32F412G-DISCO board, the arduino pin assignments are all wrong.I have attached a partial screenshot of the CubeMX project showing the incorrect assignment and a scre...

0690X0000060B5pQAE.png 0690X0000060B6jQAE.png

Power On reset behavior of STM32L071KZU3

Posted on May 16, 2018 at 16:29             We are using STM32L071KZU3 MCU in our design and providing 1.8V to VDD,VDDIO2 and VDDA domains of MCU.         The on-board source voltage to MCU is exactly 1.78V(instead of 1.8V). During power-up, we coul...