STM32 MCUs Products

When a USART is configured without a clock, the code generator treats it as a UART and assigns HAL_UART_IRQHandler as the interrupt handler. However, within this handler, there is a blocking operation during the idle process:(void)HAL_DMA_Abort(huart->hdmarx);When certain error conditions occur, the code can become stuck in HAL_GetTick(). This happens because the SysTick priority is lower than that of the UART interrupt. I have observed this behavior multiple times, particularly when noise is present on the UART signal line.Has Anyone seen this situation before?

Hello,I have two Winbond W956D8MBYA (64Mb, x8) HyperRAM chips connectedto XSPI1 on STM32H7S3 in dual memory mode (DMM=1):- Chip #0 → IO[7:0] + DQS0- Chip #1 → IO[15:8] + DQS1- Shared: CLK, NCLK, NCSI need to run at 200 MHz, so I need to configure CR0 on both chips:- Initial latency = 7 cycles (default is 6, valid only up to 166 MHz)- Fixed latency (required for dual mode per RM0477)Problem:According to RM0477, in HyperBus 16-bit dual mode:1. Variable latency is not supported (LM bit in XSPI_HLCR must be set)2. Register space access uses only IO[7:0]. Quote from RM0477:"IO8 to IO15 being not used but driven by the controller"So I can only access registers of chip #0.I also tried MSEL bit in XSPI_CR to switch to IO[15:8] in single memHyperBus mode - no effect.Questions:1. How to write CR0 to chip #1 connected to IO[15:8]?2. Is there any way to initialize each chip separately beforeswitching to dual mode?3. Does the controller duplicate data on IO[15:8] during registerwrite in dual mode?M

Hi ST Family,We are using STM32H745BIT6 MCU in our design and interfaced the same to multiple I2C slaves. For I2C lines, we have connected pull up of 2.2K to 5V power rail. In STM32CubeMX, we are enabling "No pullup or No pull down" for I2C lines.Since this MCU family is "not true open drain" ( Page 202 of datasheet), we need to know if we can continue with this configuration.Over the long run, do we see any issues of I2C engine going bad because of this configuration.?Regards..

Hey there community, I am having trouble fixing an interesting scenario on Usart communication,With the same software doing a reception on a given usart interface, It has been noticed the reception segregates one connection but not the other, Both connections having the same configurationIt has been tested that the board on which it fails has connection on that line and that the connection actually reaches the intended pin for sure by testing the Usart Rx pin when set up as a both a GPIO input and latter as an output.by playing with this GPIO input and output mechanisms on that pin. and observing respectively from both the led toggles on the board intended to signify sign of life on the pin and, logic analyzer to see the GPIO state when toggled from with in the system.Note, we are able to see the usart signals on both and are able to decode the messages on a logic analyzer for both, but the stm does not receive the message on one connection.We appreciate any insight into the Issue

My design uses a STM32H750VBT6 MCU with the USB3300-EZK PHY for high-speed USB. The hardware and software implementations are complete and in general everything works extremely will. The only issue I am seeing is that there are occasional startup problems with the host computer (both Mac and Linux) reading the device descriptor. This occurs about 10% of the time. The Linux error log is: <6>[19177.992026] usb 1-1.1.4: new full-speed USB device number 75 using xhci-hcd<3>[19178.072046] usb 1-1.1.4: device descriptor read/64, error -32<3>[19178.260043] usb 1-1.1.4: device descriptor read/64, error -32<6>[19178.448021] usb 1-1.1.4: new full-speed USB device number 76 using xhci-hcd<3>[19178.528074] usb 1-1.1.4: device descriptor read/64, error -32<3>[19178.716051] usb 1-1.1.4: device descriptor read/64, error -32 A normal connection log as follows: <6>[19166.984026] usb 1-1.1.4: new high-speed USB device number 74 using xhci-hcd<6>[

I'm in need to scan a bunch of contacts in a 4 rows, 8 column diode matrix configuration. PA0-PA7 are the inputs, PB12-PB15 the outputs. What I'm wondering about is the PA0-WKUP special function in contrary to the rest of inputs (PA1-PA7). Do I have to  care about this circumstance?

Hi community !I was working on a custom STM32 board as part of a robotics project. We started evaluating STM32H7 through the Nucleo boards, and now that we've confident with our chip selection, I designed a custom nucleo-type board, which can later be integrated on our main robot PCB. Since we didn't need any additional features, main focus was to have a board with just the STM32 chip (STM32H755ZIT6) along with the basic components needed. During the evaluation, I am not able to establish connection between ST-Link V3 MiniE, it shows "No target found". The board is powered by an 5V external supply, which powers the STM LDO, providing 3.3V for the chip. I tried playing around with the ST-Link config settings like Frequency, Mode, Reset Mode and Speed, but it doesn't help in fixing the error.Upon testing the ST-Link with the Nucleo board, it is able to connect to the STM32 onboard (so the ST-Link board is working fine). Upon reviewing my schematic, I realized that there were tw

hello community ! I'm facing issue wiht RS485 mod on USART3. Please find here a TL;DR of the issue, context, workaround and finaly request for answers. HARDWARE PLATFORMMCU: STM32U595USART: USART3 configured in RS485 modePROBLEM DESCRIPTION:During development of RS485 communication firmware for the STM32U595, we encountered anunexpected issue that challenged our understanding of the USART configuration: USART3 is configured with RS485 mode via HAL_RS485Ex_Init() which correctly sets the DEM (Driver Enable Mode) bit in CR3 for hardware-controlled driver enable:HAL_RS485Ex_Init(uart_handle, UART_DE_POLARITY_HIGH, 16, 16);This is the documented, correct approach for RS485 with automatic driver enable pin control.However, after extensive investigation and troubleshooting, we discovered that working RX/TX communication on this specific hardware appears to require ALSO calling:HAL_HalfDuplex_EnableTransmitter(); // - before transmission HAL_HalfDuplex_EnableReceiver(); // - in tran

Hello,I'm reading the article on "How to create an STM32N6 FSBL load and run" and have a couple of questions about DFU implementation on the STM32N6:1. Is DFU possible with the application as part of the FSBL?2. Is there an example on how to implement DFU for when the application is part of the FSBL and also where the application is separate from the FSBL?https://community.st.com/t5/stm32-mcus/how-to-create-an-stm32n6-fsbl-load-and-run/ta-p/768206I'm using the stm32n6570-dk eval board.Thanks!

Is there an easy way to find devices that support specific CAN buffer configurations?For example, some only have receive queues whilst others allow a number of receive buffers to be configured (which is what I want). I know the H7x7 supports this, but does anything else?

Hello everyone,We are having trouble getting tracing to work with our target at full clock speed and would like to understand why, we have an application running on STM32U575 @ 160MHz CPU clock, we also connected the J-Tracer to it using a connector glued next to the uC and short wires (~10mm) to PE2 ... PE6 (pins 1 to 5 on the LQFP100), the GPIO pins are all configured (using a JLinkScript) as AF and at maximum speed, and from what we understood on the documentation (Arm trace technical specification - SEGGER Wiki​) the trace clock and trace data operate at half the CPU speed, I checked the ST datasheet and the GPIOs we are using should be good up to 100MHz, so in theory the trace should be possible with the CPU running at 160MHz and outputting trace data @ 80MHz, or?- I have tested with the CPU at 160MHz and 2 trace data pins instead of 4, and it works, but the trace buffer overflows every time, as only 2 data lines are too slow for the amount of information.- I also tested with the

Hi,I do not plan to use USB, and the STM32N6's VDD is 1.8V.However, creating a new 3.3V power supply just only for the VDD33USB pin is too inefficient.The datasheet lists the absolute maximum ratings for VDD33USB as ranging from 0V to 3.6V when USB is not used, and the comment below states the following:1. All main power and ground pins must always be connected to the external power supply, in the permitted range.Therefore, Finally if I do not plan to use USB on the STM32N6, which of the following options should I choose for the VDD33USB pin?(have to consider leakage current in stop mode)1) NC2) 3.3V (by creating a new power supply)3) 1.8V4) GNDthanks in advance.

I am developing a multi-node system (16 nodes) based on the STM32G0C1MET6. During normal operation, all nodes communicate at 500k (Standard CAN). To perform a firmware update, the Master initiates the following transition sequence: Reconfiguration: The Master sends a global command. All nodes switch their FDCAN configuration to 250k (CAN FD) and enter Listen-Only Mode. Trigger: The Master then sends a specific SDO command to a single target node to trigger a jump to the System Bootloader (System Memory). Reflash: Once in Bootloader mode, the target node is expected to respond via FDCAN1 (as per AN2606/AN5405) to begin the reflash process. The Master repeats this node-by-node. The Issue: While most nodes perform the jump and reflash successfully, some specific units enter the bootloader (confirmed by status LEDs) but never respond to CAN messages. These units appear "deaf" to the Master's CAN FD frames at 250k. Environment: MCU: STM32G0C1MET6 Interface: FDCAN1 (Pins: PD0/PD1) Trans

Hi, I am tring to write data by the FDCAN bootloader of system memory, my target is STM32H563. Now, I can read the device ID, perform the mass erase command, but I can't write data to SRAM/Flash, the FDCAN bootloader doesn't response any CAN message after the Write_Memory command. Below picture is the CAN message log when I try to write 64 bytes data to flash at 0x0802_0000. I also check the 'Write_Unprotect' command, so the MCU is not write protect.Do I miss something have to do?Thank you.

Hello,I am writing to seek advice on connecting an APMemory APS12808 OSPI memory to the STM32H723ZGT6 microcontroller.Initially, I attempted to adapt the code from this thread ( https://community.st.com/t5/stm32-mcus-products/stm32h7-octospi-mode-hyperbus-hyperram-access-and-delay-block/td-p/143237/page/2 )  from @Alex - APMemory  to the STM32H723ZGT6. You can find the result in the attached file `main_1.c`. With this configuration, read and write operations do work, but I am encountering issues with data mismatches/corruption.Subsequently, I tried to enable the Memory Mapped mode based on Application Note AN5050. This is where significant problems began I cannot get this mode to activate. The relevant code is in the attached file `main_2.c`.My specific questions are:1. Is there a known working example for enabling the Memory Mapped mode for this type of memory?2. Why does AN5050 not cover the MR (Mode Register) configuration and memory initialization sequence?

Hi, I am using an STM32F767ZI to communicate with a Dacai HMI display over UART7 at 9600 baud. Sending data from the STM32 to the HMI works perfectly, but receiving data from the HMI is unreliable. The same HMI works fine when communicating with other MCUs—both TX and RX work reliably.When I touch: screen ID = 0 control ID = 12 HMI tool shows this frame:   EE B1 11 00 00 00 0C 11 31 32 00 FF FC FF FF ( Data : 12 ( 31 32 ) ) Data reception does not match actual touch event HMI → STM32 reception is very unreliable Callback (HAL_UART_RxCpltCallback) is triggered rarely Breakpoint inside callback is almost never hit void HAL_UART_RxCpltCallback(UART_HandleTypeDef *huart) { if (huart->Instance == UART7) { HAL_GPIO_TogglePin(GPIOB, LD1_Pin); // debug uint8_t b = rx_byte; if (frameIndex == 0 && b != 0xEE) { HAL_UART_Receive_IT(&huart7, &rx_byte, 1); return; } if (frameIndex == 1 && b != 0xB1) { clearFrameBuffer();

Hi, I don't know where to post this message. There's an error in the RM0090 Rev21 reference manual, page 121: "bit 15 of the PWR_CR register" should be "bit 14 of the PWR_CR register". And most importantly, the debugger doesn't have bit 14 (VOS) of the PWR_CR register. I'm using an STM32F407ZET. I downloaded the archive https://www.st.com/resource/en/svd/stm32f4-svd.zip, and this bit is indeed missing from the STM32F407.svd file! Please email whoever needs this information, and have them fix it.

Hello, I hope to reach the appropriate contact regarding Country of Origin (CoO) information at ST.We have identified a conflict between the CoO listed on the website and other documents (such as PCN and the attached FMD chemical document). These documents indicate that the CoO for part STM32H523RCT7 is China, while the website lists the CoO as France.Could you please clarify this discrepancy and specify what the France CoO refers to? Based on our documents, the CoO China corresponds to the country of assembly.Your clarification on this matter would be greatly appreciated. Website CoO FRANCE : https://www.st.com/en/microcontrollers-microprocessors/stm32h523rc.html#sample-buy 

A new STM32 sub-family (as part of the 'H5 family) came out. They have everything but the kitchen sink. As far as I can tell, 'H5E4 and 'H5E5 differ only in that the higher one has USB-HS with PHY (the 'H5Fx are crypto-enabled variants, as usually) What's new is also the PLAY peripheral, which is a small programmable logic element, fully documented and configurable through registers. It's based around 16 simple logic elements (4-input LUT and an optional register), complete with an extensive input multiplexer matrix+filter, interconnected to a variety of peripherals (timers, DMA, ADC...) and also GPIO. I wonder, if there's a Disco around... JW  

After encountering an issue with a Hyperbus flash chip we moved our flash to what we thought would be a simpler OctoSpi Nor Flash. I am working with an STM32H7S7 chip with a NOR Flash S28HS512T. I cannot get the chip to communicate in the desired mode. Here are my steps so far:Configuration code from CubeMX:/* XSPI1 parameter configuration*/ hxspi1.Instance = XSPI1; hxspi1.Init.FifoThresholdByte = 4; hxspi1.Init.MemoryMode = HAL_XSPI_SINGLE_MEM; hxspi1.Init.MemoryType = HAL_XSPI_MEMTYPE_MICRON; hxspi1.Init.MemorySize = HAL_XSPI_SIZE_512MB; hxspi1.Init.ChipSelectHighTimeCycle = 3; hxspi1.Init.FreeRunningClock = HAL_XSPI_FREERUNCLK_DISABLE; hxspi1.Init.ClockMode = HAL_XSPI_CLOCK_MODE_0; hxspi1.Init.WrapSize = HAL_XSPI_WRAP_NOT_SUPPORTED; hxspi1.Init.ClockPrescaler = 3; hxspi1.Init.SampleShifting = HAL_XSPI_SAMPLE_SHIFT_NONE; hxspi1.Init.DelayHoldQuarterCycle = HAL_XSPI_DHQC_ENABLE; hxspi1.Init.ChipSelectBoundary = HAL_XSPI_BONDARYOF_NONE; hxspi1.Init.MaxTran = 0; hxspi1.In

Hello,I want to use the TW9992 NTSC/PAL Video Decoder for STM32N6 to transfer an NTSC camera (720x480 resolution) to the MCU via MIPI-CSI and display it on the screen. I have attached the code below.static void MX_DCMIPP_Init(void) { /* USER CODE BEGIN DCMIPP_Init 0 */ /* USER CODE END DCMIPP_Init 0 */ DCMIPP_CSI_PIPE_ConfTypeDef pCSI_PipeConfig = {0}; DCMIPP_CSI_ConfTypeDef pCSI_Config = {0}; DCMIPP_PipeConfTypeDef pPipeConfig = {0}; /* USER CODE BEGIN DCMIPP_Init 1 */ /* USER CODE END DCMIPP_Init 1 */ hdcmipp.Instance = DCMIPP; if (HAL_DCMIPP_Init(&hdcmipp) != HAL_OK) { Error_Handler(); } /** Pipe 0 Config */ pCSI_PipeConfig.DataTypeMode = DCMIPP_DTMODE_DTIDA; pCSI_PipeConfig.DataTypeIDA = DCMIPP_DT_RGB565; pCSI_PipeConfig.DataTypeIDB = DCMIPP_DT_RGB565; if (HAL_DCMIPP_CSI_PIPE_SetConfig(&hdcmipp, DCMIPP_PIPE0, &pCSI_PipeConfig) != HAL_OK) { Error_Handler(); } pCSI_Config.PHYBitrate = DCMIPP_CSI_PHY_BT_1600; pCSI_Config.DataLaneMapping =

I am currently working on the LoRaWAN_END_NODE example project for a stm32WL . And I want to receive external data via uart and use the LoRaWan process continually, however I am getting problems. The UART is giving invalid data after the sequencer is being initialized.Edit: I have tried the suggestions below, I have put the gps into a task for the sequencer to run. I have also disabled low power mode. I still get invalid data from the UART that I don't receive when the sequencer is not on.Is this a clock issue? Any ideas?

Good day,I am writing firmware for a custom board using the STM32G0B1KET6 and am experiencing issues related to writing a serial number to the internal flash.As far as I can tell, this MCU has 512 KB of flash split into 2 banks of 128 pages (each page is 2 KB). I am attempting to write to the last page of the first bank (Page 127 @ 0x803F800).I have modified the linker file to reduce the flash area used by my application code like so:MEMORY { RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 144K FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 64K }Here is my flash writing function. uint8_t Flash_Write(uint32_t startAddress, uint64_t data) { __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_OPTVERR); __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_BSY1); __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_BSY2); __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_PGSERR); __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_PGAERR); __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_CFGBSY); if(__HAL_FLASH_GET_FLAG(FLASH_FLAG_CFGBSY) == 1) { return 0; } HAL_StatusTypeDef status;

Newest AN4879 does not list STM32C5 as applicable products.

Hi everyone,I am trying to setup DCMIPP Pipe0 to read data from 256x192 pixel sensor by 16 data lines.Seems everything configured and working fine except of transfer data to destination buffer.DCMIPP frame counter is increasing. Pipe0 dump counter is 0x18000 (256x192x2).HAL_DCMIPP_PIPE_Start return HAL_OK.Pipe0 packer memory address register is qual to Pipe0 memory status address register and correspond to address of buffer in RAM.I checked that DCMIPP don't write zero values by initing frame buffer with 0xFF and it wasn't changed to zeros. I am sure that sensor is working because of frame counter, dump counter, checking lines with oscilloscope and it is working with other pcb with STM32H7 and DCMI interface.  Also I validated that debugger read frame buffer correctly by sending it thought uart. Source code is simple, generated by cube init than I2C configuration of sensor(validated) and than reading in loop with delay:while (1){    HAL