Solved

IssueHigher ambient temperatures cause communication malfunctions with XSPI memories.DetailsOur design is heavily adopted from STM32H7S78-DK which also has the same issue described below.The application uses memory-mapped mode for both Flash and RAM as the main operational units. These memories are configured in the bootloader and everything generated using CubeMX. According to the datasheets, all three components (CPU, Flash, and RAM) are specified to operate reliably under the given conditions, and they do function correctly under normal temperatures.The problem arises when the ambient temperature increases from 25°C to 60°C. These temperatures are within the acceptable operating range for all components, as stated in their specifications. Upon reaching higher temperatures, the memories start to exhibit failures. However, further investigation revealed that the issue is not with the memories themselves. When the memories alone are heated, they continue to operate reliably, even at el

Hello,  I am currently looking at the reference designs for STM32WLEx and am interested in board reference STDES-WL5I4IHH. (high band, high power with optimized BOM target for 915MHz/22dBm). As seen on page 6 of:  Data brief - STDES-WL5xxxxx - Reference designs for STM32WL5x and STM32WLEx microcontrollers   When looking at the BOM, the only difference I see between STDES-WL5I4IHH and STDES-WL5I4IHL is the IPD with designator U4. But when looking at the schematics, inductor L3 has no value attached. The BOM states it is 47nH and recommends LQW15AN47NG00. I also checked for STDES-WL5I4ILH which also has 47nH for L3. Is this correct?Do all 3 of these use an L3 inductor with value 47nH?  STDES-WL5I4IHH | Product - STMicroelectronics STDES-WL5I4IHL | Product - STMicroelectronics STDES-WL5I4ILH | Product - STMicroelectronics I am mainly asking this question because when looking at the eval board NUCLEO-WL55JC, there is a switch that changes that i

STM32WL55 BPSK modulation bitrate for transmission and reception. Transmission is mentioned in data sheet is 600 bit/sec, but need to know reception max bit/sec. Is that same 600 bit/sec?

In the documentation on STM32N657X0, it says that the memory must be connected with match length track on the boards.It says:Match length (including BGA package length)- DQS0 with IO0..7 (Byte0), all in 50 mils,- DQS1 with IO8..15 (Byte1), all in 50 mils,- CLK is100 mils from any signal of Byte0 or Byte1- NCS can be CLK +/-700 milsBut I can't find any documentation on "BGA package length".It seems reasonable that the BGA package should be taken into account, since it is 12.8 mm.and a precision of 1.27mm (50 mils) is specified.I hope someone can help me find that documentation.Keld

I'm doing can-bus work with F103 and having a problem I can't figure out.I'm listening for a specific message, it's on a 20ms interval, and then when that message arrives I right away broadcast a new message using the same id but with different data.  To do this I'm setting a flag inside HAL_CAN_RxFifo0MsgPendingCallback and then monitor this flag inside the main loop. If the flag is set I'm calling HAL_CAN_AddTxMessage to send a new message and resetting the flag.  This repeats. Now, everything seems to be working most of the time, but at random times, it can be a minute or several minutes or longer, my messages are not sent for a second or few seconds or randomly sent/not sent for few seconds.  Then everything will go back to normal for a while and then it might get "broken" again.  This will repeat. HAL_CAN_AddTxMessage() is always returning OK. HAL_CAN_TxMailbox[0-2]CompleteCallback() are not being called when I notice the failures. There are 3 other n

Hello,I am working with a custom PCB using STM32H745XI6 (dual core CM7 + CM4).I wanted to boot only the CM4 core.So, in STM32CubeProgrammer --> Option Bytes --> User Configuration:I unchecked BCM7 (CM7 boot disabled)BCM4 remained enabledI clicked ApplyThe operation completed successfullyNo mass erase warningNo security warningNo RDP Level 2 warningRDP was never changed manually.Problem After ApplyingAfter applying the option bytes, I can no longer connect via ST-LINK.STM32CubeProgrammer shows:Error: Unable to read device id from ROM tableError: ST-LINK error (DEV_CONNECT_ERR)Error: Cannot identify the deviceEven in:Under Reset modeHardware reset modeHot Plug mode50 kHz SWD frequencyConnection always fails.What I Have Already TriedConnect under reset (holding NRST manually)BOOT0 high and lowVery low SWD frequency (50 kHz)Hot Plug modeHardware reset modeDifferent USB cableST-LINK V3SET firmware is detected correctlyI also even tried with J-link  Target voltage is ~3.2Vacc

With HPDMA configured for SAI1A, no DMA setup code is generated with CubeMX 6.17.0. See attached IOC file as an example. Possible that I'm missing a required setting, but I can't find anything.Edit: Fully deleting and re-creating project seems to have fixed it :shrug:.

Hello,We have been using CANbus as our form of communication for a system with multiple nodes. Each node was individually tested with CAN and all of them work without issue. However, when we started system integration testing, we noticed significant noise on the CANbus channel that caused data to stop. To give more details, we are running 2 battery packs, a power electronics DC/AC converters (to create a 120Vac signal) and a central supervisory controller, which are all using STM32 MCUs to communicate to each other via CANbus. We are using an STM32H7AGI6, STM32F401RE, STM32F303RE. When we send a CANbus command to start the DC/AC converter, that is when the noise appears and we cannot communicate with the MCUs until the DC/AC converter is turned off. We have termination resistors at the end of the bus and I have verified that the 60 Ohm resistance is seen on the bus. I've also attached a copy of our schematic for the CANbus, which all of the nodes use (except that the 120 Ohm

Hi,Have this working on STM32F302R8 but cannot seem to get my SD Card working on an STM32F446RE. Using hal 0.23.0 with stm32F446 and embedded-sdmm 0.9.0); let sd_mosi = gpiob.pb15.into_alternate::<5>(); let sd_miso = gpiob.pb14.into_alternate::<5>(); let sd_sck = gpiob.pb13.into_alternate::<5>(); let mut sd_spi = Spi::new( dp.SPI2, (Some(sd_sck), Some(sd_miso), Some(sd_mosi)), Mode { polarity: Polarity::IdleLow, phase: Phase::CaptureOnFirstTransition, }, 400.kHz(), &mut rcc, ); let sd_spi_dev = ExclusiveDevice::new_no_delay(sd_spi, sd_cs).unwrap(); rprintln!("Reading file..."); let num_bytes = sdcard.num_bytes().unwrap(); rprintln!("SD Card Size: {} bytes", num_bytes);Which gives[2026-03-01T05:30:04.085Z, +020837ms] panicked at both_test/src/main.rs:184:40: [2026-03-01T05:30:04.085Z, +020837ms] called `Result::unwrap()` on an `Err` value: CardNotFoundVery new to all this but certain of wiring. The SD Adaptor has an Ams117 chip but I have tried in

We've been using STiROT + OEMuROT for STM32H7S on our system, with our own application.The secure bootloader handles most of its functionality very well, and the security aspects in particular. The scripts provided by ST were very helpful, as was the documentation on the ST wiki. We are grateful to ST for providing these.However, it proved extremely challenging to get the secure bootloader working with our application, mainly because the secure bootloader makes a number of important assumptions about the user application which are not documented.These unstated assumptions initially prevented our application from running, and it took a considerable amount of time and effort to solve all the problems associated with them.AssumptionsThe main assumptions are:OEMuROT assumes that the application will use the same clock setup as itself (especially PLL1 and PLL2): as documented in a separate post, we needed to change the clock settings in our application compared to OEMuROT, and thi

Hi everyone,I'm using the new STM32Cube.AI Studio with a NUCLEO-N657X0-Q board. Since the STM32N6 is flashless, I used the --split-weights flag to allocate the NN weights to the external xSPI memory (address 0x71000000).The project builds successfully, but the automated flashing step fails with Error: failed to download Sector[0]. It seems that STM32Cube.AI Studio calls STM32CubeProgrammer in the background without configuring the required External Loader for the external flash.Is there a native way to set up the External Loader directly within STM32Cube.AI Studio's settings, or is the officially recommended workflow right now to flash the weights manually via the standalone CubeProgrammer?Thanks in advance!

  After more debugging, the jump function works correctly (PC reaches 0x080208xx, SP and RST are valid), but the app never sends any UART message after jump — even with SystemClock_Config() completely commented out and only HAL_Init() + MX_UART_Init() remaining. The bootloader resets the clock to HSI before jumping. SCB->VTOR is set in SystemInit(). Linker is at 0x08020000. The app works perfectly when flashed directly at 0x08000000 via ST-Link. Something is killing the app immediately after the bootloader jumps but we can't figure out what — any ideas?this is the project : https://github.com/said-sketch/Flashing-by-UART---STM32-Bootloader/tree/main  

In all the areas which currently have labels for the other peripherals.   See: STM32H5E4/E5/F4/F5 with PLAY: boards availability?.

Hi,When I posted a question, the following warning message appeared on the post:Marked as spam.This is the URL for my post.https://community.st.com/t5/stm32-mpus-embedded-software-and/sd-card-read-issue/m-p/881342#M5615This post doesn't appear on the forum board and can't be found through searches...Best Regards,Karsten 

 Hi. I am new to STM32 microcontroller. I started with STM32Cube IDE. So far everything is good until a build of a template project failed. I changed the directory structure of template project and moved folders Src, Inc and Startup to project root and removed Core folder. Now project wouldn't build. Although it generates binaries but with errors. I have also updated the Include paths in project properties but linker keeps failing. This is not a big deal I can move everything back to its original position and it will compile and link without any issue. I am just curious that what is missing. Just want to know what is going wrong. This is the error I am getting multiple times.STM32CubeIDE_2.0.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.13.3.rel1.win32_1.0.100.202509120712/tools/bin/../lib/gcc/arm-none-eabi/13.3.1/../../../../arm-none-eabi/bin/ld.exe: STM32CubeIDE_2.0.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-st

To follow up this thread, CTS signal on USB CDC - STMicroelectronics Community I'm experiencing a similar issue. USBser.sys  have some problem 1. Only DTR Break can control alone you can set  DTR is 1  or 0,  but  RTS have change，RTS only change with DTR. 2.  CDC Serial State I  have test this code,  it  send from Endpoint 81h successfully,  but  PC USB Host  have no message CDC_IN_Buf[0] = 0xA1; /* bmRequestType 0xA1 (10100001B) */ CDC_IN_Buf[1] = 0x20; /* 0x21 (SERIAL_STATE) */ CDC_IN_Buf[2] = 0x00; /* wValue LowByte */ CDC_IN_Buf[3] = 0x00; /* wValue HiByte */ CDC_IN_Buf[4] = 0x00; /* wIndex LowByte Default 0 */ CDC_IN_Buf[5] = 0x00; /* wIndex HiByte */ CDC_IN_Buf[6] = 0x02; /* wLength LowByte Serial State Length 0x0002 */ CDC_IN_Buf[7] = 0x00; /* wLength HiByte */ CDC_IN_Buf[8] = 0x14; /* Data LowByte */ CDC_IN_Buf[9] = 0x00; /* Data HiByte */ /* CDC Serial State bit define (USB CDC 1.1 6.3.5 ) bit0 bRxCarrier 0x

Excited to see a new connector on new STM32 Nucleo 144 boards like the Nucleo-H5E5ZJ. Is the Connector intended for customers to design their own modules only, or will ST offer a module as well?   PS: I still hope to also see a Qwiic connector, or at least a footprint for it, on Nucleo boards some time in the future. 

One small issue I have. I have a custom STM32F411CEU6 board, quite similar to the WeAct Black Pill in terms of connections, except for the fact that I have a LED on pin PB13, and whenever I try to blink it using:while (1) { /* USER CODE END WHILE */ HAL_GPIO_TogglePin(GPIOB, GPIO_PIN_13); HAL_Delay(500); /* USER CODE BEGIN 3 */ } in the STM32CubeIDE, everything works fine and dandyThe moment i switch to using the Arduino Framework, albeit with the Arduino IDE or PlatformIO, with parameters of:platform = ststm32 board = genericSTM32F411CEusing the code:#define LED PB13 void setup() { pinMode(LED, OUTPUT); } void loop() { digitalWrite(LED, HIGH); delay(1000); digitalWrite(LED, LOW); delay(1000); }or anything similar, it just doesn't work! It always says the upload is successful, and it verifies successfully too! But why then, it refuses to work? Any suggestions?

Hi everyone,I’m working on an STM32U5G9 using USBX + ThreadX.I was able to make the device work as:MSC onlyCDC-ACM onlyMSC + CDC-ACM simultaneouslyThat part is fine. What I need now is more dynamic behavior: start the device as MSC, and when a button is pressed, stop USB, change the class to CDC-ACM and restart it (long term I’d like to switch arbitrary combinations of classes, but for now switching from MSC to CDC-ACM is the goal.)From what I understand, I must stop USB so the host will re-enumerate using the new device descriptor, and I’m OK with that. However, every approach I tried ends in a HardFault when I restart with the other class. I suspect I’m missing a call or doing things in the wrong order.How I start the device (this works):/* Start device with MSC only (initial boot) */ /* First I insert CLASS_TYPE_MSC is "UserClassInstance" variable in ex_device_descriptors.c (not shown here), then: */ ux_device_stack_initialize(...); /* Register MSC-only */ ux_device_stack_class_regi

Hello, I have a question about STM32CubeMX regarding the STM32U5G7VJT6 MCU.STM32CubeMX 6/17.0 indicates that a non-existent SMPS power supply must be enabled for the STM32U5G7VJT6.However, this is the version without the 'Q' specified in the part number:Q = Dedicated pinout supporting SMPS step-down converter.When I call SystemPower_Config(), the microcontroller does not work; without calling this function, it works fine.Is this a bug in the STM32CubeMX, assuming only Q versions of this MCU exist?Best regards, Jack

Hello ST experts,I configured an STM32H745 dual core to read data from ADC1/ADC2 in dual mode. I dedicated the M7 core to initialize ADCs, timer and DMA. But after running the code it seems that the ADC is not working either DMA.  I used the similar code on the STM32H750 single core. The code is correct.I think I have to configure extra settings for dual core such as managing the memory. Could you please help me.The DMA is in circular mode with "Word" data length.TIM2 triggers the ADCs. 

Hi ST team,Is VREFINT in STM32C011F4P6 internally fixed and stable, independent of VDDA fluctuations?If VDDA fluctuates (for example due to LDO load or battery discharge), will the ADC raw readings change proportionally because ADC reference = VDDA?Is it officially recommended for STM32C0 users to read VREFINT periodically and compute real VDDA to correct all ADC channels, especially when VDDA is not stable? Example : - ADC accuracy change if VDDA fluctuation like 3.3v to 2.9v. ? or it can take ref from Vrefint ?

I am trying to create a signal that changes its frequency in dynamic way using timers  but i am having some issues to do it can anyone give me some tips for easy implementation to do this task

 Hello,When I try to change the supply source in power parameters STM32CubeMX 6.17.0 does not seems to generate anything when LL is selected. With HAL the configuration is changed in the generated code. Am I missing something ?Thank you for your help !