STM32 MCUs

MT tools is mess of Eclipse-RCP based tools (CubeIDE) and tools with hand-made GUI, whichresembles GUI of 90x (CubeMX, CubeProgrammer).Hand-made GUI applications has a lot of code which can be thrown out after switch to Eclipse RCP.Anyway, CubeMX is Java GUI application. CubeMX and CubeProgrammer has primitive Java GUIdeveloped from scratch.Instead of use a lot of existing functionality of Eclipse RCP, developers had to write own codeand invent a lot of wheels. It increase costs of development and maintanence.It is not much effort to move CubeMX functionality to Eclipse RCP application.A lot of code can be thrown away. It will decrease costs.With Eclipse 4 one can make GUI XML model with visual tool and make several simple adaptersto inject existing Java panels in corresponding model views.With such approach MX-relative perspectives can be used as standalone application and used withany IDE. And can be integrated in CubeIDE.It is very flexible solution. Current CubeMX is old monolithic

Hello, I'm trying read core temperature. I use NUCLEO-U575ZI-Q board. I wrote code: RCC->AHB3ENR |= RCC_AHB3ENR_PWREN; PWR->SVMCR |= PWR_SVMCR_ASV; RCC->AHB2ENR1 |= RCC_AHB2ENR1_ADC12EN; ADC12_COMMON->CCR |= ADC_CCR_VSENSEEN; ADC1->CR &= ~ADC_CR_DEEPPWD; ADC1->CR |= ADC_CR_ADVREGEN; while(!(ADC1->ISR & ADC_ISR_LDORDY)); ADC1->CR |= ADC_CR_ADCAL; while (ADC1->CR & ADC_CR_ADCAL); ADC1->CR |= ADC_CR_ADEN; while (!(ADC1->ISR & ADC_ISR_ADRDY)); ADC1->DIFSEL = 0; ADC1->PCSEL = ADC_PCSEL_PCSEL_19; // preselection ADC1->SQR1 = (19 << ADC_SQR1_SQ1_Pos); ADC1->SMPR2 |= (7 << ADC_SMPR2_SMP19_Pos); // max sample time ADC1->CR |= ADC_CR_ADSTART; while (!(ADC1->ISR & ADC_ISR_EOC)); uint16_t raw = ADC1->DR; volatile float temperature_c = ( (float)(raw - TS_CAL1) * (130.0f - 30.0f) ) / (float)(TS_CAL2 - TS_CAL1) + 30.0f;Unfortunately it doesn't work correctly. ADC1->DR returns

I am using an STM32L433 with a W25Q128JVSIQ flash.I can read and write data but the W25Q does not seem to respond to the power down command.When I send the power down command 0xB9, reading data from the W25Q should not be possible until the release command 0xAB is sent.  However, I am not sending this release command but can read data from the W25Q, which indicates it did not enter power down.  Below is a scope capture of the power down command and it looks correct...I am using the following driver for the W25Q...https://github.com/mengguang/w25qxxBelow is the function I wrote to power down the W25Q... #define W25QXX_POWERDOWN 0xB9 void w25qxx_powerDown(W25QXX_HandleTypeDef *w25qxx) { uint8_t tx[1] = {W25QXX_POWERDOWN}; cs_on(w25qxx); w25qxx_transmit(w25qxx, tx, 1); cs_off(w25qxx); }I even tried adding a delay (1ms) before the CS pin is raised high after the 0xB9 command has been sent, but it still did not enter power down.With a previous setup I had many

IAR version: 9.70.2Board: MB1930-N6570-C02Project: STM32Cube_FW_N6_V1.2.0\Projects\STM32N6570-DK\Templates\TemplateBoard is in DEV mode, LED2 is on after reset.Hi, I'm unable to debug the template project, once debug session is launched the core just stucks in the bootrom:Also there are some error in the log:Sat Jan 31, 2026 12:25:55: IAR Embedded Workbench 9.70.2 (C:\iar\ewarm-9.70.2\arm\bin\armproc.dll) Sat Jan 31, 2026 12:25:55: Loaded macro file: C:\iar\ewarm-9.70.2\arm/config/debugger/ST/STM32N6xx_DBG.dmac Sat Jan 31, 2026 12:25:55: Loaded macro file: C:\iar\ewarm-9.70.2\arm/config/debugger/ST/STM32N6xx_Trace.dmac Sat Jan 31, 2026 12:25:55: Loaded macro file: E:\mcu\STM32Cube\STM32Cube_FW_N6_V1.2.0\Projects\STM32N6570-DK\Templates\Template\EWARM\FSBL\setup.mac Sat Jan 31, 2026 12:25:55: PC-locked license - IAR Embedded Workbench for ARM Sat Jan 31, 2026 12:25:57: Connected to ST-LINK/V3 [SWD mode 1000 kHz] [Access port: 1] Firmware V3.J17.M10 (Probe no: 002900304142

Dear Sir/Madam,We used the STM32F429ZIT6 processor in a project we carried out for the railway sector, and as stated in the link below, we currently need a SIL certificate to be able to submit it to the auditing firm.Link: https://www.st.com/resource/en/product_presentation/stm32_stm8_functional-safety-packages.pdf

Hi all, Im currently designing my own pcb with a STM32WBA65CIU6 MCU in the UFQFPN48 package.Im doing this for the first time (still gaining all the knowledg needed) and currently ran into the following problem:I'm having trouble understanding the footprint and EDA symbol given for the STM32WBA65CIU6 on the product site and shop. According to those, eg OSC32 are Pins 16 and 17:But according to the data sheet and also in CubeMX the OSC32 should be pin 19 & 20:  Is this not a problem and can be solderd anyway? Also some other pin names are also missmatched :\Thanks for the help :)

After obtaining the motor configuration parameters using the P-NUCLEO-IHM03, I applied the same motor parameter values to the EVSPIN32G4-DUAL board, which is used to drive two motors.However, when operating the motors with these settings on the EVSPIN32G4-DUAL, an overcurrent error occurs.Could you please explain the possible reasons for this overcurrent condition?In particular, I would like to know whether differences in the power stage, current sensing topology, or dual-motor operation could cause this issue, even when the same motor parameters are used.Thank you for your support.Best regards,Pelino

Hi,I'm developing a secure boot application for STM32H563ZI microcontroller. I started with a very simple application following ST template code and tutorials like this one: https://wiki.st.com/stm32mcu/wiki/Security:How_to_start_with_STM32CubeMX_OEMiRoT_Boot_path_on_STM32H563  Everything runs as expected when I try to run my application using the NUCLEO-H5 board. However, this is not true when I do the same provisioning process in my H5 custom board. The only difference I can see between the two tests is that in the custom board I'm using the STLink-V2 programmer, while the Nucleo is programmed by the embedded STLINK-V3EC.Here are some additional points:1) in both cases the provisioning script reaches the end, saying "The board is correctly configured".2) in the custom board, I see the flash full of zeros after provisioning; I checked it with stm32CubeProgrammer3) I have no problems in flashing firmware through stm32CubeProgrammer or stm32CubeIde in my custom board

I'd like to use the DTCM ram in my code; how can I do ? Thank you

Hello everyone, I am using a custom board with STM32H750 and I am trying to develop a file system with FILEX. The file system' s media is a uSD card with 10 MB/s baudrate which is communicating with the micro thanks to the SDMMC peripheral. The SDMMC peripheral's configuration is copied from one of the many examples that are available in STMCubeMX ( it has a 50 Mhz clock, 4 bit mode, no power mode save and no transceiver).The uSDcard has been formatted through the api given by FILEX (fx_media_format) following the information available during uSD card initialization ( for example sector size is 512 bytes, number of sectors and so on...).I am using the drivers given by ST for FILEX (in my case SD with IDMA) and I am trying different media size buffer (512, 1024 and 4096) which I allocate in AXI SRAM ( SDMMC1 IDMA can access only in AXI SRAM).I am experiencing two different behaviour:  If I am doing a reading operation the SDMMC is very fast while writing operation is

I’m working with an STM32G473QETx.Does the IWDG window value cause the MCU to reset if the watchdog is refreshed too often (i.e., refreshed too early)?if I set the IWDG window value to something smaller (e.g., 1600), will the MCU reset if I refresh the watchdog more frequently than expected?Any clarification on how the IWDG window works on the STM32G4 series would be appreciated.

Hello ST Community,@pavel_A@erwan_CI am working on a project using STM32 NUCLEO-F446RE and the SmartElex Power Meter (ACS37800) for voltage, current, and power measurement over I²C.https://robu.in/product/1-month-warranty-1276/?gad_source=1&gad_campaignid=18585959909&gbraid=0AAAAADvLFWd-Gp59GIu3AsyVYZj3ppOY9&gclid=Cj0KCQiA7fbLBhDJARIsAOAqhsePuiSx2qOJKlmgFcZN2-_7bfwkDHpCOUyG6G9Q4REJXpOXr7KYUEIaAq3dEALw_wcBHardware details:MCU: STM32F446RE (NUCLEO-F446RE)Sensor: SmartElex ACS37800 (Allegro ACS37800 IC)Interface: I²C1SCL: PB6SDA: PB7VCC: 3.3 VExternal pull-ups: 4.7 kΩ on SDA/SCLI²C speed: 100 kHzSoftware details:STM32CubeIDE v1.19.0The sensor works correctly with ESP32 using the SparkFun Arduino library, but I am looking for a proper STM32 HAL-based reference or sample code specifically for:Correct I²C initialization and addressing16-bit register access required by ACS37800Reading instantaneous voltage, current, and powerRecommended power-up timing and initialization sequenceI

I work on an STM32F407G-DISC1 pedometer project, in which the program is supposed to use built-in lis3dsh accelerometer via SPI to detect and count steps and display the number of steps on the screen (ILI9341 SPI).I have tested my screen code, and it works properly, so problem lies in how I use accelerometer or detect steps.To detect steps, I read lis3dsh registers with 100HZ frequency by making a call to SPI from a 100HZ timer interrupt. These snippets are interrupt and timer configuration respectively.void HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef* htim) { if (htim->Instance == TIM2) { if ((draw_ready == 1) && (accelerometer_ready == 1)) { accelerometer_read_all_axes_dma(xyz_data, &hspi1); } } //else if (htim->Instance == TIM3) { // if (draw_ready == 1) { //steps_count += 1; //update_lcd_flag = 1; // } //} }static void MX_TIM2_Init(void) { /* USER CODE BEGIN TIM2_Init 0 */ /* USER CODE END TIM2_Init 0 */ TIM_ClockConfigTyp

When using USB CDC to communicate via USART, and interacting with USART data, in code is it recommended to interact with it at the USB side, or to interact with it at the USART side?From what I can tell, both offer both polling and interrupt methods. The USART offers DMA access, but apart from that it's not clear what, if any, tradeoffs there are between USB CDC and USART.

Github link to code    Hi everyone, I am currently working on a project with the NUCLEO-L432KC board, trying to interface a generic SPI MicroSD Card module (the standard blue one, powered via 5V). I am stuck with the FatFS error FR_NOT_READY (Error 3) during f_mount. After extensive troubleshooting, I suspect a hardware failure on the MISO pin (PA6), but I would like a sanity check on my diagnosis before I remap the pins. Hardware Setup: Board: NUCLEO-L432KC (STM32L432) SD Module: Generic SPI adapter (Powered via 5V VIN pin) Wiring: CS: PB6 (D5) SCK: PA1 (A1) MOSI: PA7 (A6) MISO: PA6 (A5) <-- The problematic pin Software Configuration: IDE: STM32CubeIDE FatFS: _MAX_SS and _MIN_SS set to 512. SPI1: Master, Prescaler 256 (Low speed for init), CPOL Low, CPHA 1 Edge. The Issue & Diagnostics: The communication fails at the very beginning. When sending CMD0 to wake up the card, the SPI RX buffer always returns 0x00 instead of 0xFF (Idle) or 0x01 (Su

I've downloaded archive "en.STM32CubeExpansion_Crypto_v4.0.1.zip", now I'm trying to install it in STM32CubeMX with "From Local..." feature, but I'm getting error. How can I install the library in CubeMX?Thank you.

Hi Starting my first project testing VSCode integration of ST tools instead of using Eclipse... Just reporting an issue with build analyzer, it is indicating that I have 188% of FLASH used...The compiler output gives the correct information:It seems an issue parsing the map or elf file to operate the tool. 

Hello, I'm having trouble getting the CubeMX code generation to work reliably with X-CUBE-AI package.After first adding X-CUBE-AI to the project, and adding one of the models from the ST model zoo, i get this warning:If i click Yes, the code generation takes about 5 minutes and works.Note that in the above picture, X-CUBE-AI ExtMemLoader is selected. This is also where the warning comes from. AFAIK, i don't need X-CUBE-AI ExtMemLoader, just the Application. If i remove the checks from the checkboxes "Artificial Inteligence X-Cube-Ai" and "Device Appliccation", and then reopen MX, the X-CUBE-AI ExtMemLoader will disappear, and just the X-CUBE-AI Application remains. However, after trying to generate code with that setup, the code generation hangs to the below phase of code generation: At that state, the OpenJDK Platform binary uses over 6000 MB of RAM, and about 10% of my CPU but seemingly nothing happens. I waited over the weekend to see if the genera

Hi,I would like to report that STM32CubeIDE is freezing when running on Wayland session.The solution I found is to start Ubuntu in a X session.Best regards,Daniel

Hi Team,   We are using the STM32WB55CGU6 for one of our application. Since, the product has internal bluetooth functionality, we are usin for our application. However, the expected range is not meeting with the application that we anticipated. Kindly review the attached circuit and provided your insights.   Regards, Abinaya.M

It is very inconvenient to have regenerated C files in C++ project.Problem is not main.c only, *_it.c as well. In C++ project one have to call methods of class from interrupt handlers.It is not possible to make directly from *_it.c. Indirect call chain is lost of time.I renamed main.c to main.cpp in C++ project, made call from main.cpp to method of class. All is OK.Flashed microcontroller with main.cpp, all is working.ST done great work to support C++. And made it useles by generating new code to C files. Why not to generate code in C++ project to CPP files? 

Hi,I have some CubeMX-generated code which works properly. Originally it was created to run from default address 0x08000000.Now I have a bootloader at address 0x08000000 which is responsible for handling updates and other stuff and then jumps into the target-code, so I moved that code via linker script to 0x08020000. This also works fine, the code works as desired.In a next step I decided to have some additional information stored in flash prior to the CubeMX generated code to make it easier for the bootloader to manage firmware versions, so I shifted the code by additional 128 bytes and now have the following section in my linker script:MEMORY { FLASH_BOOT (rx) : ORIGIN = 0x08000000, LENGTH = 128K FLASH (rx) : ORIGIN = 0x08020080, LENGTH = 1024K - 128K - 128 EEPROM_EMUL (xrw) : ORIGIN = 0x080E0000, LENGTH = 128K DTCMRAM (xrw) : ORIGIN = 0x20000000, LENGTH = 128K RAM_D1_DMA (xrw) : ORIGIN = 0x24000000, LENGTH = 64K RAM_D1 (xrw) : ORIGIN = 0x24010000, LENGTH = 320K - LEN

Would writing to the crossbar registers (SETx1R, RSTx1R, SETx2R, RSTx2R of all 6 timers) on every PWM cycle (max 200kHz) affect long term reliability? I'm running this in an interrupt routine for a power converter and I'm wondering if doing this would make sense to have a more consistent processor delay. Preload is enabled on all 6 timers and master timer. Register updates on timers 1-6 occur on master timer register update.

I am trying to use the gprof editor/viewer within cubeide but it doesn't work, everything just freezes then crashes with no error messages, i also found nothing in the logsI'm trying to use gprof profiling arm-none-eabi-gprof.exe, i have my code instrumented and got a valid gmon.out file, it is small ~15kb, the file is valid as i can process is manually with gprof.exe and get a textual representation of the profiling data.However i don't want text output, i want the included viewer in the cubeide, to see in a nice tree view the data, i have the option to open the gmon.out file with the gprof editor but when i do, it asks for the corresponding elf file then after that everything freezes then crash. What am i doing wrong? Is this expected to work at all? Did anyone use it?Cube ide1.18 stm32f429 discovery project

I'm trying to configure DMA in Memory-to-Peripheral mode for the STM32WB09KE, specifically to transfer data from memory to a Timer channel (TIM2_CH3 for Addressable LED's). However, in STM32CubeMX, I cannot see the expected DMA options under the DMA Settings tab for my Timer.