STM32 MCUs Products

Can someone tell me if I’m understanding this correctly?In the documentation for the STM32F030R8T6 chip, specifically the "RM0360 Reference Manual", there’s a diagram showing how to connect an external crystal oscillator ("Figure 12. HSE/LSE clock sources"). In this diagram, the crystal is connected directly to the OSC_IN and OSC_OUT pins, with no series resistor on the OSC_OUT line to limit the drive level.However, on the STM32F030 DISCOVERY board, there is such a resistor – R22 – even though the crystal is not installed by default. I added the crystal I wanted to use and measured the current through it (using a current clamp), and it became clear that it was being driven beyond its specified power limits. That’s when I realized the need for the series resistor (R22). I calculated the appropriate resistance value and installed it – but it didn’t reduce the current through the crystal at all.After fur

Hello,I am working with the STM32H503CBT6 and using the I3C Transmit_IT in Controller mode for communication.However, I encountered a problem, when I sent more than 260+ bytes, the data sent by the logic analyzer to capture, found that the captured data and I sent the data does not match, the following data will be the previous data directly off, suspected its FIFO overflow, but I do not know how to modify or how to find its error；Thank you for your help!

I am designing an STM32N657X0 based custom PCB which has a USB Type C port. The USB device would be self- powered, i.e, it will not be powered from VBUS. The intended use of this port is to plug the PCB to a host PC, similar to USB flash drive for data transfer. How should the VBUS be managed on the circuit? Should it be monitored by the MCU to sense VBUS? Please share any reference designs if available for self-powered USB C sink devices implemented with STM32.

Hi,The recent webinar with your partner Edge Impulse on 26th March was useful to taste the capabilities of STM32N6. Until now in my previous STM32 MCU projects are built with ST official tools like STM32CubeMX. But there is no much information available on using official ST tools (not your partner tools) to use STM32N6 devices. Can you please provide more training material on this new device and using it with the ST official tools, probably providing a workshop on STM32N6 please?

Hi, I'm following the steps on the reference manual to perform in-application programming by first writing the new firmware to bank 2 and then swapping the banks after doing some checks. After completing the steps and performing a software reset, the new firmware was updated. However, after closing the st-link debugger and reopening it, the debugging session immediately closes. I'm trying to figure out why. I have written the new firmware starting at address 0x0810 0000 according to the following:

hello. I was using PA9 pin as an interrupt in a project made with Stm32F072CBT6. I am working as Stm32F072CBTx in cubeide. The card I am working on accidentally installed Stm32F072C8T6. only difference is that it is visible in flash but PA9 pin can be defined as interrupt in the same way but the function does not work. Is the fact that the processors are different a reason why the interrupt cannot work?. I do not get any overflow error caused by flash.

This is a long and weird one.My boss gave me a board with an STM32L433 that wouldn't communicate or do anything after power-on. After a lot of debugging and code tracing, I discovered that the function HAL_RTC_WaitForSynchro returns a HAL_TIMEOUT error code. The auto-generated code then jumps to the error handler with the infinite loop.I have checked the RTC registers, and found an anomaly that may back this up. On a functioning board, the RTC_ISR register reads 0x00000037. On the bad board, the same register reads 0x00001017. Bit 5 (RSF) being 0 on the defective board indicates that shadow registers are not synchronized.So, what can keep the RTC from synchronizing its shadow registers?I found this line in the reference manual:"The RSF bit must be cleared after wakeup and not before entering low-power mode."Now, this board distributes 24 V to some other boards. In this particular case, the supply wires to one of the

Hi,I am trying to interface the IMP34DT05TR microphone with our custom board. After soldering with custom board, we are unable to read data from the microphone, and the sample data appears incorrect. data look like this when open the audio file in notepad {€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€€....etc}

Hii, I am using hrtim in stm32G474RET6 mcu, so i want to know how we generate a counter of 500ns in which i call adc in it.If somebody know about it please help me.

Posted on June 07, 2017 at 18:46I need to have a PC algorithm that produces the same result as the hardware CRC (using an F0 chip).I can produce identical results between hardware and software when doing a byte by byte crc calculation.I would like to use the word based calculation since it is much faster.However, the result produced using the word by word in the hardware CRC is different than the one produced using the byte by byte option. I've tried all combinations of bit and byte ordering on the word value in the software based calculation (taking 4 bytes at a time and re-ordering bits and bytes) but I haven't come up with a combination that works.It isn't necessary for me to have the hardware word vs byte calculation produce the same result (would be good if it did though).  However the software and hardware calculations must obviously match.Does anyone have any tips to share on this?

hello, where can i download win11 STM virtual com port?  i install both VCP_V1.5.0_Setup_w7_x64_64bits and W8_x86_32bit all not working ! i din seeSTM Virtual Com port at device manager! only STM STLink visual com port appear ... 

Hi, I set the button on the board to WAKE_UP2 to wake up from standby mode, but it doesn't work. Also, waking up through the RTC interrupt doesn't work either. The LSE source is an external crystal. This is my code: int main(void) { /* USER CODE BEGIN 1 */ /* USER CODE END 1 */ /* MCU Configuration--------------------------------------------------------*/ /* Reset of all peripherals, Initializes the Flash interface and the Systick. */ HAL_Init(); /* USER CODE BEGIN Init */ /* USER CODE END Init */ /* Configure the System Power */ SystemPower_Config(); /* Configure the system clock */ SystemClock_Config(); /* USER CODE BEGIN SysInit */ /* USER CODE END SysInit */ /* Initialize all configured peripherals */ MX_GPIO_Init(); MX_ICACHE_Init(); MX_USART1_UART_Init(); MX_RTC_Init(); /* USER CODE BEGIN 2 */ if(__HAL_PWR_GET_FLAG(PWR_FLAG_SBF) !=RESET) { __HAL_PWR_CLEAR_FLAG(PWR_FLAG_SBF); c

I'm configuring the timings for an APS6408L-3OBMx PSRAM on my custom hardware, based on the STM32H725IGK6, in memory mapped mode, to be used principally as Frambuffer for the LTDC controller.I have to enable the Delay Block parameter in STM32CubeMX to get a partial working PSRAM (I still have some errors on the Display), but there seems to be non possibility to configure the Delay Block inside STM32CubeMX and/or STM32CubeIDE. (The function for the Delay Block are in stm32H7xx_ll_delayblock.c/.h but this files are not included when enabling the Delay Block inside the OCTOSPIx configuration).So my questions:- Is there a known good configuration for the APS6408 PSRAM?- How can I configure the Delay Block for the OCTOSPIx interface?Martin

I tried following STM32 AN5418 but the EvaluateSinkCapabilities method is not getting called. I added debug prints everywhere in the code and here is what I am receiving:1. VBusInit (this always happens)2. DPM notification 104 (Stack init)3. Cable detection4. Unimplemented SetDataInfo 8 (USBPD_CORE_EXTENDED_CAPA)5. SetDataInfo 6 (USBPD_CORE_DATATYPE_RCV_REQ_PDO- I haven't implemented anything in this, but I had it print out what it received and it looked good (e.g. 5V 3A 9V 3A 20V 5A etc.)6. Notification: 30 (USBPD_NOTIFY_HARDRESET_RX)7. Hard reset callback8. Device turns off, turns on a few seconds later and goes through this same loopWhat d

Bonjour,I've been able to use I2C to communicate with I/O extender and display drivers with HAL. I'm now trying to use the I2C with HAL using DMA.The problem is that UM1785 Description of STM32F0 HAL and low-layer drivers is a bit vague on explanations. STM32 offers examples, but that's not really what I'm looking for, and videos, but I'd rather have a written article (with a written article I can read at my own speed, easily skip or re-read parts, copy text, and so on).Are their learning tools such as UMs or Application notes dedicated to the subject?M.R.

Hello ST Community,I’m working on a project using the STM32G0B0VET6 MCU where the ESP8266 Wi-Fi module communicates over USART5. The ESP module’s TX and RX are connected to PD2 (USART5_RX) and PD3 (USART5_TX) respectively.In my current working firmware, the ESP8266 initializes correctly, starts the Access Point mode, and communicates with the STM32 over UART5 without any issues.However, when I flash another firmware version (which was originally written for a LoRa module but modified for Wi-Fi), the ESP8266 doesn't turn ON or respond. The same hardware works perfectly with the first firmware, which makes me believe this is a firmware-side GPIO/UART5 configuration issue rather than a hardware fault.When i disconnect the Rx and Tx from the board the module turns on but when

There appears to be a discrepancy between the STM32U073 reference manual and the header file for the part.  Given that STM32CubeProg seems to agree with the header file, I'm inclined to think it's an error in the reference manual.I'm looking at programming the brownout detection bits in the STM32U073.  If I look at stm32u073xx.h (STM32Cube FW_U0 v1.2), I see this:/******************* Bits definition for FLASH_OPTR register ****************/ #define FLASH_OPTR_RDP_Pos (0U) #define FLASH_OPTR_RDP_Msk (0xFFUL << FLASH_OPTR_RDP_Pos) /*!< 0x000000FF */ #define FLASH_OPTR_RDP FLASH_OPTR_RDP_Msk #define FLASH_OPTR_BOR_EN_Pos (8U) #define FLASH_OPTR_BOR_EN_Msk (0x1UL << FLASH_OPTR_BOR_EN_Pos) /*!< 0x00000100 */ #define FLASH_OPTR_BOR_EN FLASH_OPTR_BOR_EN_Msk #define FLASH_OPTR_BORR_LEV_Pos (9U) #define FLASH_OPTR_BORR_LEV_Msk (0x3UL << FLASH_OPTR_BORR_LEV_Pos) /*!< 0x00000600 */ #define FLASH_OPTR_

I am working on a project using an STM32G4. I have a new board spin that I am bringing up and one of the four boards that I have brought up is exhibiting strange behavior exiting STOP1 mode.I have code that can put the micro into one of 2 low power modes (Low power SLEEP, or STOP1) for a specified length of time. This has been working on our previous board rev without issue.I have an 8 second watchdog running so I have set up a LPTIM to wake the device every 4 seconds to refresh the watchdog and then go back to either SLEEP or STOP1. With the one board in question, Low power SLEEP works exactly as expected; the device will sleep for 4 seconds, then wake up and refresh the watchdog, and go back to sleep. However, when this particular board is put into STOP1 mode, the LPTIM never wakes up the micro and the watchdog times out and system reboots.I am only seeing this one of four new board and I have never seen this on previous board revs. This board does not seem to

  I have designed a PCB that connects an Artix-7 XC7A35T-1FTG256C FPGA with an STM32F469VET6 (LQFP 100) MCU. My goal is to transfer data between these two devices, with the MCU as the QUADSPI master and the FPGA as the slave. For communication, all QUADSPI pins of the MCU are connected to the FPGA. I need to perform periodic data transfers every 10 microseconds. Specifically, the FPGA should send 10 16-bit values to the MCU, which will process them and then send back 10 16-bit values to the FPGA.As a starting point, consider sending 10 16-bit data to the FPGA, and reading 10 16-bit data from the FPGA. To ensure periodic transfers, I initially used a TIM2 interrupt, triggering every 10 microseconds. However, I am facing difficulties in perfo

I try to get the CAN working. But currently I'm not sure what I'm missing.I use the STM32CubeIDE v1.18.0. The boards I use is own hardware with SN65HVD232.The hardware seems to work well. on the picture you see the screenshot from my oscilloscope, CANTX, CANRX, CANL, CANH after calling:HAL_CAN_AddTxMessage(&hcan1, &TxHeader, &TxData[0], &TxMailbox)The complete code is here:/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2025 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * If no LICENSE

Hi there!I've created a custom STM32F411CEU6 Board with external HSE und LSE. While the HSE works when running my user program, the Bootloader hangs within boot phase (i think).When starting bootloader, BOOT0=1 und BOOT1=0. I powered direcly on VDD, no USB. I received no answer on both uarts after sending 0x7F. I also can't connect via stmcubeprogrammer. Only can only connect with stlinkv2.I think it may be a hardware issue, but I can't find a solution.Crystal 25Mhz: https://atta.szlcsc.com/upload/public/pdf/source/20240329/19D5F850207469550BEB00D7DFEDBC7A.pdfLSE:https://atta.szlcsc.com/upload/public/pdf/source/20240418/0E0FF5

I've read many posts here and on the web, even tried CoPilot, but I could not find how to get the USB controller to send data when the volume keys are pressed.My Host keyboard driver works perfectly, but USBH_LL_GetURBState() is not returning with data for anything but "standard" key presses.After many hours invested due to a total lack of documentation from STM, I found that the report descriptor of 146 bytes is read back by USBH_HID_GetHIDReportDescriptor() but the "consumer device" entry is not used.But if STM had one support person publish a short guide it would save many developers many hours.USBH_StatusTypeDef USBH_HID_KeybdInit(USBH_HandleTypeDef *phost) { uint32_t x; HID_HandleTypeDef *HID_Handle = (HID_HandleTypeDef *) phost->pActiveClass->pData; keybd_info.lctrl = 0U; keybd_info.lshift = 0U; keybd_info.lalt = 0U; keybd_info.lgui = 0U; keybd_info.

Hello everyone, I tried to put Canopen node for stm32 into operation. I used the standard pinning from STMCubeIde, i.e. pa 11 and 12. But this does not seem to work. void FDCAN1_IT1_IRQHandler(void) { /* USER CODE BEGIN FDCAN1_IT1_IRQn 0 */ /* USER CODE END FDCAN1_IT1_IRQn 0 */ HAL_FDCAN_IRQHandler(&hfdcan1); is not called. Is something known here? Solution was to change the pins to PB9 and PB8. Now the function was called and the stack ran. Is there a workaround to use pa11 and 12 anyway ? Thanks for your support.

I'm trying to interface the STM32F446RET6 with M95P32-IXCST/EF, a QuadSPI EEPROM. For the 64 pin STM32F446RET6 pin PB2 (pin 28) is used both as BOOT1 and QUADSPI_CLKI don't see any other pins that can be used as QUADSPI_CLK for the 64 pin package. Is there a way to interface with the EEPROM?

Currently I am just trying to share some data between cores, and right now I'm just trying to send a constant value to confirm operation.I have this code located in a file called share.h,typedef struct {   // shared data goes here   int16_t data;   }shared_data_t;and then I havevolatile shared_data_t * const shared_data = (shared_data_t *)0x30040000;saved in each core's main.c file.The location is SRAM3 and according to the RM this is an optimal place to share values. It updates properly in M7, but when I check the struct in M4 it's not the same value. When googling, this was the number 1 answer, the second was the linker. I don't know where to begin with the linker, so if that is the option is there any good guides? Thank you for reading this