Product forums

Hello,   I designed a custom control board based on STM32G431CBT6 and before manufacturing the PCB I would like to make sure there are no fundamental hardware mistakes.   My main concern is not firmware but hardware connections.   I would appreciate if you can review especially:   SWD programming interface connections Power supply and decoupling capacitors BOOT0 and NRST configuration VDDA and VREF+ connections CAN transceiver interface (TJA1051/3 with VIO = 3.3V) Anything that may prevent programming or startup     The goal is to verify that the MCU can be programmed and start reliably after assembly.   I am attaching the schematic below.   Thank you very much for your time.   MCU: STM32G431CBT6 Supply: 3.3V regulator Debugger: ST-Link via SWD

Hi everyone,the update to CubeMX 6.17 seems to introduce a new valid range of the "First RX Descriptor Address" of the Ethernet setup on a NucleoH755 board. This is also the case for the STM32H745.This is the valid range according to the CubeMX field description (there is also a typo for the Parameter Description "Fisrt"):First Rx Descriptor AddressFirst Rx Descriptor Address must be between 0x24000000 and 0x30047fff.Parameter Description:Fisrt Rx Descriptor address must be only in the D2 Domain AHB SRAM. Rx descriptor address must not exceed Max value and must no overlap with Tx descriptor and Rx buffer. These areas must not be cacheable.This contradicts the knowledge base article: How to create a project for STM32H7 with Ethernet and LwIP stack working The reference manual also states that 0x3004000 - 0x3004FFFF should be part of the D2 Domain AHB SRAM3 and hence be part of the intended area. Is this just a bug or do I overlook something?Kind regards

I am currently working on the STM32N6570-DK board and need support for MIPI camera interfacing using CSI (not USB).RequirementInterface a MIPI camera using CSIRead camera dataEncode the dataSend it to a PC via Ethernet using UDP streamingSupport NeededHow to configure and enable CSI (MIPI camera interface)Any reference examples/projects for camera bring-upGuidance on reading camera data from CSIAny examples for encoding + Ethernet (UDP) streamingKindly provide any documentation or example projects that can help achieve this.

Post edited by ST community moderator. In next time please use </> to share a code. HI, I have Implemented ADC1 - DMA with one channel and ADC2 - DMA with 7 channels and im transmitting data through UART IT. I want to know if this code works usually. void HAL_ADC_ConvCpltCallback(ADC_HandleTypeDef* hadc) { if (hadc->Instance == ADC1) Print_ADC_Values_IT(); if (hadc->Instance == hadc2.Instance) Print_ADC_Values_IT(); } hadc2 is workin only when i disable HAL_ADC_Start_DMA(&hadc1, (uint32_t*)&adc1_value, 1); Here's the overview of my code: MX_GPIO_Init(); MX_DMA_Init(); MX_ADC1_Init(); MX_ADC2_Init(); MX_USART1_UART_Init(); /* USER CODE BEGIN 2 */ // HAL_ADCEx_Calibration_Start(&hadc1, ADC_SINGLE_ENDED); HAL_ADCEx_Calibration_Start(&hadc2, ADC_SINGLE_ENDED); // Start ADC1 (1 channel) // HAL_ADC_Start_DMA(&hadc1, (uint32_t*)&adc1_value, 1); // Start ADC2 (7 channels) HAL_ADC_Start_DMA(&hadc2, (uint32_t*)adc2_values, ADC2_CHANNE

Hello, I am using an STM32H755 Nucleo board in a system where the board is plugged into a custom PCB via headers. The system has been working for about two weeks without any issues. Occasionally I remove the Nucleo board to update the firmware and then plug it back into the PCB. Today the system stopped responding to UART commands. When I connected the board to my PC, STM32CubeIDE reported: "No ST-LINK detected! Please connect ST-LINK and restart the debug session." I also tried STM32 ST-LINK Utility and got: "Can not connect to target! Please select 'Connect Under Reset' mode..." However, STLinkUpgrade is able to detect the ST-LINK and perform a firmware upgrade. Another important observation: The ST-LINK MCU on the board (STM32F7) is getting very hot. Additional diagnostics: - The board was completely removed from the external PCB. - Even when powered independently, the ST-LINK MCU still overheats. - The board draws significantly higher current than normal. - I cannot measure proper

Hi everyone,I’m currently working with STM32 Secure Boot and Secure Firmware Update (SBSFU) and integrating it with my custom application. I’m trying to design the project in a modular and scalable way for long-term use, and I would really appreciate some guidance from those who have worked with SBSFU in production. Current ScenarioMCU: STM32 (Cortex-M series)Bootloader: SBSFUApplication: Custom firmware using HAL, middleware, and CubeMX-generated codeDevelopment tool: STM32CubeIDE Challenges I’m Facing1. Shared Drivers & MiddlewareBoth my bootloader and application require:HAL DriversSome middleware components What is the best way to manage duplication vs sharing?Should bootloader and application maintain completely separate copies of Drivers/Middleware?Is there any recommended way to keep them in sync without tight coupling? 2. Impact of .ioc ChangesI use CubeMX via .ioc for peripheral configuration.If I:Add a new peripheralModify clock or pin configurationHow

Hi,I am using STM32H755 where M7 and M4 runs bare-metal firmware using OpenAMP (RPMsg).Sampling rate is set to 250 SPS. The data is sent from M4 to M7 using OPENAMP_send() function.Observation: Data loss of approximately 10% is observed during transmission from M4 to M7. The loss does not follow a fixed pattern.Questions:- Is this an expected behavior with RPPMsg/OpenAMP at this rate?- How can I ensure reliable transfer without data loss? Thanks & Regards,Bhagyashree Ghosh Roy

Hello!I'm working on a STM32MP257F-EV1 board. So far, I've been modifying the kernel device tree that came with the kernel after building the openstlinux distribution, and have that working. I'd like to move to CubeMX-generated device trees though, to adapt to a future custom design (still on the EV1 board for now though). I'm using CubeMX 6.17.0 on Ubuntu Linux.However, I was surprised to find out that simply doing "Start My Project from ST Board" and selecting the EV1 doesn't actually configure the board with the same functionality as the defaults from the distribution:* In my earlier post, I noted that eMMC booting doesn't work [1] (now works, but after changes)* I have bluetooth connected to USART6, also doesn't work out of the box (and still doesn't)* A SDIO-connected wifi card sits on the sdmmc1 (the SD card slot). Works with my modifications to the kernel device tree, but not with the same modifications to the /* USER CODE BEGIN ... END */ sections in the CubeMX-generated tree.*

I do not know what happened. If I double-click ioc file, it used to open inside CubeIDE. But now it will open inside another separated cubemx window. I may have changed some settings by mistake.How to change the settings back so I can open ioc file inside CubeIDE?

I am currently working with MC Workbench and the ST Motor Pilot tool for motor control development. While setting up and attempting to establish a connection using the latest version of ST Motor Pilot, I am encountering a connection issue that appears to be caused by a bug in the current release.As suggested in the community forums, I also tried using an older version of ST Motor Pilot. However, this introduces dependency conflicts, as other required components and tools in the workflow depend on the latest versions and are not fully compatible with the older Motor Pilot version.Board- STEVAL-ESC001V1  

Hello, I am currently working with the NUCLEO-WB05KN1 development board (STM32WB05KN MCU) and I would like to implement FOTA (Firmware Over-The-Air) / OTA update over Bluetooth. However, I could not find any clear reference documentation, application note, or example project related to: Bootloader implementation for OTA Memory partitioning (dual bank / slot usage) BLE-based firmware update flow Any official FOTA example for STM32WB05 series I checked the datasheet and reference manual, but there is no clear explanation of: Whether a built-in/system bootloader supports OTA via BLE How to structure the flash (bootloader + application separation) Any middleware/library support for firmware update Currently, my memory usage is: FLASH: ~34% RAM: ~49% So I still have space to implement a custom bootloader if needed. My questions: Is there any official ST example or application note for OTA/FOTA on STM32WB05KN? Does STM32WB05 series support BLE OTA natively (like STM32WB55)? If not, wh

Hi All,I've this requirement, can someone suggest how do I proceed.I'm using stm32u535 and over usart it's connected to Silicon labs chip. Silicon labs chip has Wi-Fi and I want to update firmware of STM32U535. This silicon labs chip is connected to cloud over Wi-Fi. 

Where can I find the Option in the Preferences  to set the text of the function Name to “Bold”?

Hi everyone,I'm using an STM32H723 for a project with Hall sensor encoders on two BLDC motors.**Hardware:**- Left motor: PE7, PE8, PE9 (U,V,W)- Right motor: PD3, PD4, PD2 (U,V,W)**Problem:**Right motor encoder works perfectly. Left motor has issues:1. Tick count is much lower than right motor (82 vs 236 ticks for same movement)**Debug Output:*ENC:0,1|DIR:STOP,CW ← Left STOP, Right movingENC:6,11|DIR:CW,CW ← Both OK brieflyENC:8,21|DIR:STOP,CW ← Left STOP againENC:82,236|DIR:CW,CW ← Huge tick difference**What I've Tried:**- Added debouncing- Removed direction reset on invalid transitions- Verified signals on oscilloscope (clean)- External pull-ups (4.7kΩ)**Key Difference:**- Right motor: Dedicated EXTI2, EXTI3, EXTI4 handlers → WORKS- Left motor: Shared EXTI9_5_IRQHandler for all 3 pins → PROBLEMS**Questions:**1. Can shared EXTI9_5_IRQHandler cause missed transitions when two pins change simultaneously?2. Should I move left motor to pins with dedicated EXTI lines (0-4)?3. Is there any w

 Hello,We are currently looking for a 2-terminal active (ideal) bypass diode that can be directly soldered to the ribbons inside our solar modules. Please note that the component must be able to withstand the lamination process.We previously evaluated the SM74611KTTR; however, our new module design requires a higher current rating of approximately 25A or more.Could you please recommend any alternative products that meet the following specifications?Forward Current: 25A – 30AReverse Voltage: 20V – 40VMaximum Thickness: 2.0 mm or lessRequirement: Must be an active/MOSFET-based (smart bypass) diode to minimize heat generation.Thank you for your time and review. We look forward to your recommendation 

We are currently working with a custom PCB using an STM32N6 chip and an MX25UM512G flash chip. The flash is connected identically to the Nucleo development board.When powering up the board in Dev Boot mode, it is not possible to read the flash chip using CubeProgrammer. The MCU crashes, which we assume based on the reduced power consumption observed afterward.If we first load a firmware image into SRAM using CubeIDE (which successfully connects to and reads the flash memory), then reading and writing the flash via CubeProgrammer works as expected.However, after a power cycle without reloading the firmware into SRAM, the flash becomes inaccessible again.Additionally, after flashing the firmware using this workaround (i.e., initializing the flash via our own firmware and then booting in Flash mode), the software is not executed from flash and the system does not boot.Our assumption is that the flash is not correctly initialized by the boot ROM. Any help or suggestions would be highly app

I got a panic message from drivers/st/clk/clk-stm32-core.c at Trusted Firmware. My question is: What is clock ID 5? Is that MSI clock or LSE clock?Is there any information I could read about this ID?int clk_stm32_enable_call_ops(struct stm32_clk_priv *priv, uint16_t id) { const struct stm32_clk_ops *ops = _clk_get_ops(priv, id); if ((ops->is_enabled != NULL) && ops->is_enabled(priv, id)) { return 0; } if (ops->enable != NULL) { ops->enable(priv, id); } if ((ops->is_enabled != NULL) && !ops->is_enabled(priv, id)) { ERROR("failed to enable clock id: %u\n", id); panic(); } return 0; } The output isNOTICE: Early console setup ERROR: failed to enable clock id: 5 BACKTRACE: START: clk_stm32_enable_call_ops 0: EL3: 0xe017bac 1: EL3: 0xe01be2c 2: EL3: 0xe01beb0 3: EL3: 0xe01bf54 4: EL3: 0xe01c240 5: EL3: 0xe01db28 6: EL3: 0xe029a2c 7: EL3: 0xe0170dc BACKTRACE: END: clk_stm32_enable_call_ops PANIC at PC : 0x000000000e01be

Hello community,  I am working with different ibis model of STM32H7, however, this is the only one that's giving me an error in my Altium Designer – could you have a look at it? The file is stm32h723_730_733_lqfp144.ibs Kind regards,Javier.

I am developing a project using the STM32U5G9J. In particular I based our board on the STM32U5G9J-DK2 board. My project includes over the air update for which I am using the external flash that comes on the DK2 board for temporary firmware swapping storage. The external loader MX66LM1G45G_STM32U5G9J-DK2.stldr looks like is not accessing beyond 64MBytes, giving the impression of mirroring the first 64MBytes. I need to be able to have the external loader handle fully the 128 MBytes, as well as my application being able to access the 128 MBytes by code. I am using the STM32CubeIDE 1.19.0. which the IOC file configuration for HSPI is in OCTO SPI mode with the capacity to read 128MBytes. I am using the external loader to manually write certain pieces for debugging purposes. I cannot verify if my code works until the external loader is being able to access the full 128MBytes. Please help me providing the right external loader, as well as the certainty that the IOC file can have the HSPI acce

Hello,I am facing an issue with DFU mode on an STM32MP157C when Secure Boot is enabled (OTP locked) and SCMI is active via OP-TEE, and I would like to confirm whether this is an expected behavior or a known limitation.I am using STM32CubeProgrammer to load FSBL and the FIP image into RAM, then entering U-Boot DFU mode in order to flash the eMMC. This workflow is used for recovery and reprogramming purposes.I am using the same software stack (ATF 2.12, OP-TEE 4.3.0, U-Boot 2025.01, device tree with SCMI configuration) on the two boards (based on stm32mp157c-dk2).The only difference between them is the Secure Boot state: one board is not locked, the other one has Secure Boot enabled.On the non-locked board, DFU works reliably with STM32CubeProgrammer. I can enter DFU mode, send the FlashLayout, and perform multiple DFU transactions without any issue. OP-TEE does print errors related to SCMI TA loading, but DFU continues normally.On the locked board, DFU becomes unstable. T

Hi ST community,We are bringing up a brand-new custom board based on STM32MP131C (Rev.Y) and are facing an issue while flashing SPI-NAND over USB DFU.Boot statusTF-A (BL2/BL31) boots correctlyOP-TEE OS boots and hands off to normal worldU-Boot starts normally and detects SPI-NANDSo the full boot chain up to U-Boot looks healthy.SPI-NAND detailsPart: GigaDevice GD5F4GM8UExxGSize: 512 MiBBlock size: 128 KiBPage size: 2048OOB: 128Detected correctly by U-Boot.Issue descriptionWhen flashing over USB DFU from U-Boot, erase/write operations fail due to many bad blocks at very low addresses, including block 0.Example output:Marking bad block at 0x00000000 (-5)Skipping bad block at 0x00020000Skipping bad block at 0x00040000Skipping bad block at 0x00060000Limit reached 0x80000 while erasing at offset 0x80000Error: DFU write errorBecause of this, DFU flashing fails consistently.Are there specific U-Boot or TF-A configurations recommended for SPI-NAND on STM32MP13?Please find the attached patches

Hi ST Team,I am currently working with the STM32MP257F-EV1 based custom carrier board and experiencing an issue during the flashing process(boot mode is eMMC).Initially, the board works fine and flashing completes successfully. Over the time, the flashing is failing.From the flash logs, I observe that the failure occurs at partition 0x03 (refer the attached flash_log.txt).At the same time, the UART console shows panic logs during boot (attached in uart_boot_logs.txt).Could you help us to know the root cause of this issue and steps to recover?Thank & regards,Kaviya 

Title edited to clarify that this refers to a NUCLEO-WBA65RI board.Hello, I am currently using STM32WBA65RI with Standby mode. According to datasheet, this mode should be able to reach 120nA current consumption with the 16 GPIO wake-up pins (RTC disabled). However running the Standby example and shutting down the RTC I am still getting 3uA of current consumption. What can I do to decrease the current consumption up to the nanoA?Best regards.

Section 2 of this page shows how to setup python for building firmware.  It seems the rest of the tutorials assume you are building on a modern Ubuntu, so I would suggest changing the following lines:pip install pyelftoolspip install pycryptodomexto:sudo apt install python3-pyelftoolssudo apt install python3-pycryptodomeI would also suggest adding:sudo apt install python-is-python3 My reasons are that you can not/should not install the above packages to the global python environment with pip.  Also, the makefiles for M33 firmware call 'python' which does not exist on a new ubuntu install (well, it didn't on mine).  Installing python-is-python3 is the recommended way to resolve this.  Alternately use a virtual environment, but the firmware build system seems to assume use of the global python.

Hi , I recently acquired an ST4SIM-300M eSIM and I am unsure how the ST4SIM-300M should be activated initially.I also watched your video about Remote SIM Provisioning using the Motive eSIM Secure Connect portal, and I would like to ask whether the activation and profile download for this SIM should be done through that portal.Additionally, I would like to understand whether the SIM already contains a bootstrap profile by default. If so, how can I verify this from the device?Finally, I would appreciate it if you could share a list of your eIM partners that support the ST4SIM-300M for testing purposes