STM32 MCUs

Unsure if this has been answered before, however, upon activating the Cube-AI Core and application software pack, the remains static, ie it stays blacked out with a gear icon next to it referring me back to the software packs screen, which already shows a green status icon.However, if I reload the .ioc file, the green status of the X-Cube-AI in the software packs installation tab shows it having never been activated.The files exist in the repository pathway, I am logged into ST, so I am unsure as to the cause. This also seems to occur with other software packs.Any assistance would be appreciated.

Can someone tell me, in “auto calculate” mode of the “observer + PLL (sensorless)”, which method or theory is used to calculate the parameters G1, G2, P, and I?

Hi everyone,I'm working with an STM32F103CB in my project and would like to know the default Brown‑Out Reset (BOR) threshold set for this MCU. Additionally, I’m looking for guidance on how to configure the BOR threshold to a custom level.Any help or pointers would be greatly appreciated!Thanks in advance. 

  Hello everyone, I am facing a confusing behavior with USB SOF events on two identical STM32 boards and I would appreciate any insight. Hardware 2 × NUCLEO-H743ZI2 Same MCU revision (checked device ID, revision ID – identical) Same USB connection to the same PC (USB OTG FS, device mode) Software Exactly the same firmware binary programmed on both boards STM32 HAL + CubeMX generated project USB CDC device (USB OTG FS) No conditional compilation, no board-specific code What I want to measure I wanted to check: Whether USB SOF events are really occurring every 1 ms Whether SOF can be considered a reliable timing source So I implemented a very simple counter in the SOF callback: #if (USE_HAL_PCD_REGISTER_CALLBACKS == 1U) static void PCD_SOFCallback(PCD_HandleTypeDef *hpcd) #else void HAL_PCD_SOFCallback(PCD_HandleTypeDef *hpcd) #endif { sof_eventc++; USBD_LL_SOF((USBD_HandleTypeDef*)hpcd->pData); } Additionally: TIM2 is configured as a 1 Hz timer In t

Hardware Details: Custom Hardware based on the B-G431B-ESC1, 3 phase, Hall sensored FOC,MCSDK: 6.4.1The maximum speed of the motor is 3000 RPM. I have run the motor using motor profiler software and the profiler shows the maximum speed is 2500, Rs = 0.1 Ohm; LS=0.0002Pole Pairs = 5I could achieve the speed of 2500 using FOC, Hall sensor i used Over modulation, Modulation index : 93%. PWM frequency 12KHZ. I am unable to go beyond 93% MI.The problem is i need to achieve speed of 3000 as per motor specifications and customer requirement and this speed is achieved with another standard controller. Few comparisons: DC bus current when i run is 2.6A compared to 3.1 A of standard controllerPhase current is 5A, compared to 10-15A. What changes can i do to reach 3000 RPM without flux weakening. Does motor profiler use Over modulation and showed 2500 RPM?     

Hi guys,I'm try to use Camera FPC 22 pin cable with UVC mode. But it turn out screen are all black and error in console terminal is below========================================x-cube-n6-camera-capture v2.0.0 (3308d6b)Build date & time: Jan 22 2026 09:34:57   Compiler: GCC 12.3.1HAL: 1.3.0========================================Start streaming YUV2 | 224x224@30fpsassertion "ret == CMW_ERROR_NONE" failed: file "Src/app_cam.c", line 173, function: CAM_Init  I used binary from "x-cube-n6-camera-capture-main"I also try to re-compile with github project "STM32N6-GettingStarted-ImageClassification Application"with header with cmw_camera.c USE_VD56G_SENSOR , still not success,(debug then found that driver StartStreaming can ctx->write8 but not response at function about PollReg8(..);Anyone have get experince how to make it work?

 I am currently testing motor operation using the EVSPIN32G4-DUAL board.I am using the motor’s Hall sensors for speed feedback.In the Speed Sensing Configuration, under Auxiliary Sensor, should the Speed Sensor Mode be set to Hall Sensor in this case?Could you please confirm whether this setting is required for proper speed sensing when using Hall sensors?Thank you in advance for your support. 

How to integrate motor suite and motor pilot for STM32F405RGT6 and run motor. I have custom power board and logic board. i tried making one but STM32F405RGT6 is not available in list and don't have idea what i can choose has alternative which has same spec and pin count has STM32F405RGT6. is there anyone who can help me develop.

Hi, I am using StevalESC001 board and MCSDK latest version to implement FOC on a custom motor.  I am facing a few issues while testing it with load. I am unaware of what might be the cause of these issues if anyone could direct me towards what might be happening it would be helpful. First of all, during the startup motor sometimes starts spinning in anticlockwise direction that too at a very high speed. This behavior is random, I haven't yet identified any pattern into it, and it becomes more frequent when testing with load. I also noticed that sometimes Iq value shown in motor pilot is -10A initial which seems wrong, shouldn't it be 0 initially?Another issue is with the Actual RPM and the RPM shown in motor pilot, the RPM shown by motor pilot is 300 to 500 more as compared to actual RPM the motor is spinning at. The difference increases as we increase the throttle. Also, motor seems to reach its capacity at only half throttle. It is producing only 600 g of thrust w

I am working on a project that requires a 320x240 LCD panel (ILI9341).  I use a nucleo board with STM32G071RB chip. The SPI communication works fine when I use a blocking HAL_SPI_Transmit() function, but it takes a while to fill the entire screen. When I use a DMA with SPI to speed it up, all colors get distorted.  I have tried a HAL_SPI_Transmit_DMA()  - transmit only function, and a two way HAL_SPI_TransmitReceive_DMA() function.  I tried switching from 8-bit SPI to 16-bit SPI mode for DMA transfer, but always get the same color distortion problem.A detailed analysis revealed the core problem. While transmitting the RGB565 pixel information 'RRRRRGGGGGGBBBBB', the 16-bit data is broken into two bytes 'RRRRRGGG' and 'GGGBBBBB'. In the blocking SPI transmit function both bytes are transferred.  With any configuration SPI -DMA, the second bit gets lost.  The ILI9341 controller receives a single byte and for some reason reads it, according to

Hi team,I am working on the STM32U585I-IOT02A board and trying to implement USB dual-role functionality (Host + Device).My goal is:USB Host: MSC class (to read firmware from a USB flash drive)USB Device: CDC class (for communication with a PC)I have enabled both the USB Host stack and USB Device stack in CubeMX, but I am unable to get the dual-role setup working reliably.My main objective is to upgrade firmware using a USB flash drive (MSC Host) while still supporting CDC Device communication.I would like to know:Does STM32U5 support USB dual-role operation (Host + Device) simultaneously or via role switching?Is there any example project or reference implementation for USB dual-role on STM32U5?Are there recommended approaches for implementing firmware upgrade via USB MSC Host on this board?Any guidance or example projects would be very helpful.Thank you.

I have an STM32H7A3ZIT running at 280MHz with 4 SPI buses attempting to “simultaneously” communicate with external ADCs. All 4 SPI are set up as full-duplex masters, 16-bit data size, 8.75 MHz clock speed, and software chip select.I’m using the HAL function HAL_SPI_TransmitReceive_IT to sequentially initiate the data transfer for each SPI bus. I expected each transfer to start quickly one after another, but instead I’m finding large time gaps. The TransmitReceive_IT composite image below shows the chip select line (yellow) and the SPI clock signals (cyan) for each sequential SPI bus. You can see the first 2 buses start clocking quickly, but then there is a time gap before the third and fourth buses start clocking. The code functionally works as the received data is correct, but the end of the transfer for the fourth SPI bus is too close to the next CS transaction, not leaving a lot of time for data processing.TransmitReceive_ITOddly enough, if I change the function to just receivi

Hi,I want to fly the STM32F429I-DISC with the 8 MB SDRAM. I use CubeIDE and selected the right board. All units are set to default. I commented out everything that had to do with os.With help of ChatGPT I hacked together an initialization of the SDRAM and set up a SDRAM Test. That seems to work partly but with weird effects. In the following code: start/end 0x00/0xff or 0x100/0x1ff works fine, but start/end 0x00/0x101 reads out 0x100 at  address 0x0. Maybe it is an timing issue with precharged lines.THXCheersDetlef #define SDRAM_BASE_ADDR ((uint32_t)0xD0000000) void SDRAM_Test(void) { volatile uint16_t *p = (volatile uint16_t *)SDRAM_BASE_ADDR; uint32_t i ; uint32_t start = 0x100 ; uint32_t end = 0x302 ; for (i=start; i<end; i++) p[i] = i; sprintf(buf,"start \r\n",i); HAL_UART_Transmit(&huart1, (uint8_t *) buf, strlen(buf), HAL_MAX_DELAY); while(1){ for (i=start; i<end;i++) if (p[i] != i){ sprintf(buf,"no 0x%x 0x%x\r\n",i,p[i]); HAL_UART_Transmit(&

Got a message: " Break at address "0x8001c50" with no debug information available, or outside of program code." and exited. Please help. If you need more info please advise.

Board: STM32H750B-DK (DK32H750B$AT1)IDE: STM32CubeIDE 1.14.1CubeMX: 6.11.1TouchGFX: 4.23.1Firmware: STM32Cube FW_H7 V1.12.1Problem Description:I created a new TouchGFX project for the STM32H750B-DK board. The project builds successfully (0 errors, 1 warning), but I cannot debug it. When starting a debug session, I get the error: "Cannot access memory at address 0x90000000".The project is configured to use external QSPI flash (0x90000000) for code execution (XIP) since the code size (424KB) exceeds the H750's internal flash (128KB).What Works:Project builds successfullySimple non-TouchGFX blinky projects debug successfullyWhat Fails:Debug session fails with memory access errors at 0x90000000Attempts to set SP/PC from external flash vector table failAs found STMicroelectronics ST-LINK GDB server. Version 7.12.0Copyright (c) 2025, STMicroelectronics. All rights reserved. Starting server with the following options:Persistent Mode : DisabledLogging Level : 1Listen Port Number : 61

I’m running micro-ROS on an STM32G474RE (NUCLEO-G474RE) with FreeRTOS (STM32CubeIDE / CubeMX integration) over UART to the micro-ROS agent.The firmware boots and the executor loop runs (LED heartbeat works), but no subscription callback ever triggers, even for a simple topic like std_msgs/msg/Int32.```export ROS_DOMAIN_ID=<id>ros2 run micro_ros_agent micro_ros_agent serial --dev /dev/ttyACM0 -b 115200 -v6``````export ROS_DOMAIN_ID=<id>ros2 topic pub -r 5 /mcu/test std_msgs/msg/Int32 "{data: 1}"```ros2 topic echo on the host shows messages, but the MCU callback never fires. I also tried different QoS and longer spin_some() timeouts.Question: can this happen if I print debug logs (printf/UART) on the same UART used for micro-ROS transport, or are there other common causes on STM32G4?

Hi all,I’m working on an STM32WB55 and trying to run two advertisements “in parallel”:a connectable advertisement (for normal connections / data)a non-connectable advertisement using Additional BeaconI can see both advertisements from an Android device, so the basic setup works.The problem I’m struggling with is synchronising beacon payload updates with the actual beacon transmissions.What I’d ideally like to do is update the beacon payload right before each non-connectable advertising event, so the transmitted packet always contains the latest data, without updating faster than the beacon interval.I looked into using ACI_HAL_END_OF_RADIO_ACTIVITY_EVENT as a pacing mechanism (e.g., update the beacon payload right after an advertising event so the next one carries new data). However, with two advertising roles and other BLE activity (connection events, etc.), this event is generated frequently and not only for the additional beacon advertising. From what I can tell, it also doesn’t clea

..

Code is written using stm32CubeMX. Connecting with stmlink V3 Minie. Executing step by step, it appears that debug fails (lose connection) when executing debug_init. In fact debug_init creates the problem when programming pa13.When removing the initialization of PA13 and PA14 in debug init, things seems to work but I have no idea of potential side effect. An recommendation?

Hello everyone,I am currently working on a project to develop drivers for STM32F4 microcontrollers, based on Reference Manual RM0090 (without HAL, only CMSIS and register access).The goal of the project is to design reusable low-level drivers for the following peripherals:USART / UARTSPII2CI am now in the code implementation phase.I would like the community's help with the following:Examples of source code or references (preferably bare-metal / register level) for:SPI : transmission et réceptionI2C : master transmit / master receiveUART : transmission et réceptionRecommendations on API structure and function naming, for example:SPI_Init(), SPI_Transmit(), SPI_Receive()I2C_MasterTransmit(), I2C_MasterReceive()USART_Transmit(), USART_Receive()Any help, code snippets, links to reference implementations, or feedback would be greatly appreciated.Thank you in advance for your help.Best regards, *This post has been translated from French to comply with the ST Community guidelines.

I want to interface STM32G474 MCU with DS18B20 digital temperature probe in my project. The DS18B20 uses one-wire interface. Is one wire interface supported with this MCU?  Kindly provide a detailed explanation. Help please. Datasheet link for DS1B20: EVVO DS18B20Axx Regards,Sreejith

Hi STM32 experts, I've been digging through the STM32WBA65RI datasheet and the RM0515 STM32WBA6xxx advanced Arm®-based 32 MCUs but can't seem to locate the factory default values for the FLASH_OPTR register for the STM32WBA65. Unliked the solution from this thread, where the RM0440's Option Bytes Descriptions section indicates ST Production Value, the RM0515's Option Bytes Descriptions section starting on page 206 doesn't contain the factory production value. Am I missing this information elsewhere in the RM0515 or STM32WBA65RI datasheet? Thanks and Best Regards,-Eric

Hello everyone, I’m working on a project to interface an OV5640 camera module with an STM32H743 MCU via the DCMI interface. I’ve set up the STM32H743 in CubeMX and generated a basic project, but I’m looking for supporting documents, example projects, or reference drivers to help with the integration. Specifically, I am looking for guidance on: OV5640 initialization sequence (XCLK, SCCB/I2C configuration, reset/power-down sequence) Recommended CubeMX DCMI + DMA settings for QVGA RGB565 capture Memory placement for DMA frame buffers (AXI SRAM vs DTCM vs SDRAM) Minimal working register tables to enable QVGA or VGA output Any ST or community examples of STM32H7 + OV5640 projects   I understand DCMI + DMA basics, but I am aware that OV5640 requires stricter timing and more complex initialization. Any pointers to example projects, application notes, or reference drivers would be extremely helpful.   Thank you in advance!

Split from this thread for a new question. Thank you. I've changed the programmer, and it now programmed without errors. I however get a Hard Fault, sitting in HardFault_Handler(), as soon as I run. It happens before the code gets to main(). It also does not look like it is matching symbols to files correctly, because it is not showing code. I did check that Load Symbols is checked in debugger settings. Can this HardFault be related, or should I start new post to help with that?

Post moved from this thread. @ STTwo-32 I am using the same STM32H755ZIQ board and facing the same issue where the target is not detected by ST-Link after uploading the program.This is the code link: https://github.com/kavyammengineer/stm32debug/tree/main/led_on_offThe code works correctly on the Nucleo-H755ZIQ board, but when I upload it to my customized board, the target gets stuck and is no longer detected by ST-Link.this is my sysclk 64Mhz