Others: STM32 MCUs related

I am trying to adapt the QSPI Flash (QSPI_MemoryMapped) example found in the STM32WB5MM-DK to run with FreeRTOS. My hardware uses different ports for the QSPI connection but all has been set up through the ST32CubeMX program.What I did then was to copy the code from the example into my project as a FreeRTOS task. However, the code pulls in some header files that don’t make sense to me. For example: stm32wbxx_hal_tim_ex.h results in the error “unknown type name 'HAL_StatusTypeDef”I’m not sure why this is happening, or even why this header file is being pulled int, I so would appreciate any pointers. My guess is that is has to do the the HAL timer versus the FreeRTOS timer, but even then don’t know were to look!Since I am using the flash without a fie system, maybe the QSPI_ReadWrite_DMA or QSPI_ReadWrite_IT would be better. If so, please suggest...Thanks

Hi everyone,I have one question before starting one project.I am working on information system related to Philippines government services like NBI Clearance. We are thinking future version can also work on small self-service kiosk or information terminal, not only website.Main requirements are:Stable for many yearsFast boot timeLow powerTouch display supportEthernet or Wi-Fi optionQR code scanner supportUSB printer support for receipt or documentI see many people using STM32 in industrial products.Do you think STM32 is good choice for this type of public kiosk?Or better use Linux SBC like Raspberry Pi for easier software development?I want something reliable because government/public service devices may run all day without restart.Anyone already build similar public information kiosk using STM32?Thanks for any advice.

我尝试使用 STM32L4R9 与 AD7768 通信，使用 8 个通道。我想知道的是：是否可以使用 DCMI 建立 AD7768 与微控制器之间的通信（微控制器支持，但我不确定 AD7768 是否支持 DCMI。）如果 AD7768 也支持，我想知道 PCB 应该如何正确布线。Translation to English I am trying to communicate with the AD7768 using the STM32L4R9, using 8 channels. What I want to know is: is it possible to use DCMI to establish communication between the AD7768 and the microcontroller (the microcontroller supports it, but I'm not sure if the AD7768 supports DCMI.) If the AD7768 supports it as well, I would like to know how the PCB should be wired correctly.

I create one project for STM32F401 DMA-TIM4_PWM, so far first DMA work, but it didn’t go to handle routing.After debug with Copilot help, find after DMA finish(set DMA_S0CR bit 0 to 1), the ISPR0 bit 11 set to 1, (it related with DMA1-s0.) but code didn’t jump to the vector in 0x6C (DMA1-so interrupt handle).If add one line force ISR0 bit 11 to 1, (NVIC->ISPR[0] = (1 << 11);),  IABR0 bit 11 set to 1. jump to handle routing.Why manual set work, use DMA_S0CR bit 0 to 1 doesn’t work (it same set  ISR0 bit 11 to 1 as manual.)?

 The IssueI'm using **nanoMODBUS** (slave mode) on NUCLEO-F446RE via USART2 (115200 baud, 8N1). The slave exposes two holding registers:- `0x0000`: Potentiometer value (read-only) → `usPotValue`- `0x0001`: LED brightness (read/write) → `usLedBrightness`**The LED is controlled via PWM (TIM2).**BehaviorOperation                                                           Result **Write to `0x0001`** (set LED brightness)      Works consistently — LED dims **Read from `0x0000`** (potentiometer)          Fails most of the time **Read from `0x0001`** (LED brightness)        Fails most of the time **Rare successful read**                                  Both registers return correct values Master Log```Response: emptyResponse: emptyRead OK: [609]              ← Rare successResponse: emptyResponse: emptyResponse: 0180018000         ← Truncated exception (5 bytes instead of 7+)Response: emptyRead OK: [609]              ← Another rare success```The 5-byte response `0180018000`- `01` = Slave addre

I was trying to use the xcube_TOF application inside the st32cubemx for the stm32h7 nucleo board. However, the tof initialisation is keep getting failed. Is it really possible to implement a i2c connection between x_nucleo_53l8a1 and the stm32H7 nucleo board? I tried to implement the hardware connections just like in the stm32nucleof401re.Could anyone please help me with this?

Hello STM Community,I am facing an XCP protocol timeout when trying to use Simulink Monitor & Tune (External Mode) with a custom STM32H750VBTx board and an ST-LINK-V3 (COM10, 115200 baud).The Setup & Symptoms: What works: Code generation and flashing complete successfully. "Build, Deploy and Start" works perfectly (e.g., standard LED blink routines run fine). What fails: Clicking "Connect" for External Mode immediately times out with: XCP internal error: timeout expired, in response to XCP CONNECT command. Hardware verified: Standard UART communication has been tested separately on this custom board and works flawlessly at 115200 baud. No other software is locking the COM port. Questions: Cache/MPU: Since this is an STM32H7, do the buffers used by the Simulink XCP serial stack require specific MPU or D-Cache configurations to prevent data coherency issues? Interrupt Conflict: Is there a known issue where the XCP background task gets starved by higher priority model execut

When using the ISP IQTune application to generate ISP parameters for the STM32N6 DCMIPP, the Auto White Balance expresses an error that I believe is incorrect. The error claims that AWB cannot start becase the R/B ratios for white balance must decrease, as the color temperature increases. The ratio IS decreasing, as shown in the image below.When the temperature is 5100K, the R/B ratio is 2.1/1.9 = 1.105When the temperature is 3800K, the R/B ratio is 2.3/1.9 = 1.210Thus, as the temperature increases, the R/B ratio decreases. Either this is wrong, or I’m missing a key component of this calibration process. 

Hello everyone, I can run my model through the stedgeai / STM32Cube AI Studio and see the following: But when I now go into the resulting application and build it myself, I see these memory sections, which tell a totally different story: How can I fix this? I added the AXISRAMx sections (they are not provided per default) which results in them being used by 0%, so that also can’t be right. Best regards, rphii

Hello,We are evaluating ST microcontrollers for a new product and would like some clarification regarding long-term availability.The STM8 family is now marked as NRND, and I have seen references in community discussions to a possible discontinuation around 2032.Could ST please clarify: What is the official long-term availability plan for the STM8 family and is there currently an announced End-of-Life date for STM8 devices? As STM32C0 is often presented as the migration path from STM8, I would also like to know whether the STM32C011 is covered by ST's longevity program and what its currently committed availability date is.Thank you for your help.

Pls help with FIT rate value for below components:STM32N657X0H3Q    - MCU LSM6DSVTR          - IMU Sensor M24M01E-FMN6TP    - EEPROM ST4SI2M0004TPIFW    - eSIM

Hello,I am ready to use STM32C531 in project. Right now, I am using Keil MDK V5.29 and it does not support this micro. Can anybody help to tell me which Keil version support this micro? If I do not use Keil, does any other IDE/Compiler support this micro develop?  Thanks,  

Hello. I’m facing strange issue in my design with STM32U575RGT6, revision “U”.Finally I discovered what is going on, but I don’t have ideas how to fix this.I’m using electronic switch to power ON and OFF the device:VBATT is 4.2V Li-Ion battery.One half of BAV70 diode is controlled by manual SWITCH (to power ON), second one by IO pin from uC (to maintain ON, and to OFF).Problem is that my program often hangs up in this function (I added LED blinks inside): if (HAL_PWREx_ControlVoltageScaling(PWR_REGULATOR_VOLTAGE_SCALE1) != HAL_OK) { while (1) { HAL_GPIO_WritePin(POWER_ON_GPIO_Port, POWER_ON_Pin, GPIO_PIN_SET); HAL_Delay(100); HAL_GPIO_WritePin(POWER_ON_GPIO_Port, POWER_ON_Pin, GPIO_PIN_RESET); HAL_Delay(1000); } Error_Handler(); }Voltage on VCAP pins is 0.9 V, and often freezes in this level. Rarely steps up to 1.2V and program normally continues.I finally discovered that is caused by slow rising of VDD voltage. This is from my electronic switch:I can bypass the

Hi, Can I Migrate a project from IAR to Cube IDE, It also Has third party Libraries Like, Threadx.

I have a laser engraver that runs on an ESP32 S2 Mini microcontroller. It has the following signature: “Espressif CDC Device” and emulates a COM-type serial port. I had two identical cables; if I connect my engraver to my PC via a serial program (NinjaTerm), I can control GRBL. I cut one of these cables, and they have four wires: VBUS, D+, D-, and GND. After crimping some connectors onto the ends of the wires and testing the cable connected to the port to distinguish between my D+ and D-, Now I’d like to put an STM32F411 (WeAct BlackPill v3.0) between my engraver and my PC to control my homemade Z-axis. The PC side is on a UART port of the STM32 connected to a CH340, and on the engraver side, a USB (D+/D-) CDC Host (Note: I’m not using the USB-C connector already soldered onto the BlackPill). The UART programming side worked perfectly. Where it’s getting stuck is on the CDC side… no response…   #include <stdio.h>#include <string.h>#include <stdarg.h>#include "usbh_cdc

Hello ST Community,I am working with the STEVAL-DPSLLCK1 LLC full-bridge evaluation kit, specifically the STEVAL-DPS334C1 STM32F334 control board. My goal is to access and monitor the LLC firmware variables using STM32CubeMonitor through ST-LINK.For STM32CubeMonitor variable access, I need a firmware executable with debug symbols, such as an IAR .out file or an ELF file. The .bin file is not sufficient because it does not contain variable names or debug information.I downloaded the available ST firmware package for the LLC kit and opened the IAR workspace in IAR Embedded Workbench for ARM 9.70.4. IAR asked to convert the old project to the newer format, and I accepted the conversion. After conversion, the project fails to build, so no .out file is generated.The main errors are:Error[Pe018]: expected a ")"These occur mainly in:Control_Layer.cFault_Processing.cLLC_PWMnCurrVoltFdbk.cStateMachine.cparser.y / y.tab.cThere are also many warnings like:Warning: The header file 'cmsis_iar.h' is

Hi,I am working with an STM32H7 microcontroller and the EVB-LAN9252-SPI board from Microchip Technology.I would like to establish communication between the STM32H7 MCU and the LAN9252 over the SPI interface. Could you please provide guidance on the hardware interfacing, software setup, and initialization procedure required to bring up the communication?Additionally, please let me know the software packages, drivers, middleware, or example projects that would be needed for this implementation.

Hello,I’m working on a design using the STM32H750IBTx (LQFP176) running at 400 MHz with FreeRTOS, and I’ve encountered a strange intermittent issue with the display that only appears after long periods of operation.Problem Description:After about 30–40 days of continuous operation, the display starts to flicker and glitch.Once the flicker begins, it persists continuously for around 24 hours and then self-corrects without reboot.Performing a power cycle or reset also immediately clears the issue.No other functional failure is observed (system remains responsive, logs continue, etc.)System Overview:Display: 800×480 RGB LCD connected via LTDC interface (RGB565 format)SDRAM: 32 MB IS42S16160J-6TLI, 8192 rowsQSPI: 64 MB MX25L51245GConnected via FMCFMC clock: 200 MHz, SDRAM clock: 100 MHz (FMC clock divided by 2)Refresh rate: Configured for standard 64 ms / 8192 = ~7.8 µsREFRESH_COUNT and other parameters are set as below#define REFRESH_COUNT ((uint32_t)1539) /* SDRAM refresh counter 200MHz

I have verified in my code that writing and reading with I2C works as expected, and registers are configured seemingly correctly. I believe there must be a problem with how I write the configuration file to the BMI270, but I am at a loss as to what error exists in my code.Here I present the initialization function and starting function for the BMI270:--------------------------------------------uint8_t BMI270_init(void) { uint8_t address; uint8_t init_addr0 = 0x5B; uint8_t init_addr1 = 0x5C; uint16_t init_val = 0; uint8_t value, val_lsb, val_msb; uint8_t buffer[2] = {0}; uint8_t err = 0; //disable PWR_CONF.adv_power_save (addr=0x7C,val=0x00) address = 0x7C; value = 0x00; //Read address before err = I2C_read(&address, buffer, 1); if (err != HAL_OK) {return err;} //Print result UART_print_char("test pwc 1: ", 12); UART_print(buffer, 2); UART_print_char("\r\n", 2); err = I2C_write(&address, &value, 1); if (err != HAL_OK) {return err;} HAL_Delay(1); //Read address afte

I am working on an STM32 based robot controller using an STM32F4 series board. The system includes IMU, encoders, and multiple sensor modules. During vibration and movement, some jumper connections become unreliable. I am currently using standard Dupont wires for prototyping. However, repeated disconnects are causing unstable sensor readings. I want to move to more robust connector solutions for PCB to wire interfaces.I am confused about which connector types are best for pin based headers. Should I use JST, Molex, or locking header connectors instead of Dupont? What connector systems are commonly used in STM32 embedded designs?I also need something suitable for frequent assembly and maintenance.

Hi everyone,I am working on a project using BNO085 IMU sensor and STM32H7A3ZIT6Q. I have a single sensor working but stuck at 44Hz. The same sensor with SparkFun library on ESP32 achieves 1.2ms read time. I need help understanding why and how to match ESP32 performance on STM32.Hardware:NUCLEO-H7A3ZI-Q (STM32H7A3ZIT6Q, Cortex-M7 @ 280MHz)Adafruit BNO085 breakout boardI2C on PB8 (SCL), PB9 (SDA), PC0 (INT pin)P0 and P1 tied to GND (I2C mode, address 0x4A)Software:STM32CubeIDE with HALOfficial CEVA SH2 library from github.com/ceva-dsp/sh2REPORT_INTERVAL_US = 2500 (targeting 400Hz)SH2_ROTATION_VECTOR (9-axis full quaternion)STM32 performance achieved so far:I2C 400kHz polling: 28Hz, read_ms = 32msI2C 1MHz Fast Mode Plus: 44Hz, read_ms = 19msINT pin wait inside sh2_hal_read(): still 44Hz, read_ms = 19msESP32 performance with same sensor and SparkFun SH2 library:read time: 1.2msData rate: close to 400HzThis is a huge difference. 19ms on STM32 vs 1.2ms on ESP32 with the same SH2 library unde

Here are the logs and waveforms. The slave device of IIC is unable to raise the SCL response. The data cannot be sent out either. The code is provided in the attachment.HAL_I2C_AddrCallback: 开始接收数据接收到字节[0]: 0x40接收到字节[1]: 0x03接收到字节[2]: 0x22接收到字节[3]: 0xFE接收到字节[4]: 0xBEHAL_I2C_ListenCpltCallback: 开始接收数据接收到字节[0]: 0x41HAL_I2C_ListenCpltCallback: 开始发送数据发送字节[0]: 0x05发送字节[1]: 0x62发送字节[2]: 0xFE发送字节[3]: 0xBE发送字节[4]: 0x30发送字节[5]: 0x31 

https://www.linkedin.com/posts/edwin-amaya-63006b225_next-little-free-project-is-a-segger-rtt-activity-7459971377140469760-ik6Vhttps://github.com/EdwinFairchild/ProbeStream 

Hello Community,I have been involved with embedded Rust since 2020 and I noticed most tutorial, examples, dev boards are targeting the ESP32 processors. This made no sense to me outside of the hobbyist community.  I got contacted over a year ago by Manning Publishing about writing a book on Embedded Software with Rust. I decided that I should use STM32 based boards for my examples. The book is now in early release on MEAP (Embedded Software with Rust - David Cabanis). The idea of MEAP is to engage with the early adopters to get feedback to improve the final product (paper book).I was hopping that some of you might want to take a look and offer me some feedback on how to improve the content.  You can see the details of the content on the landing page and the Chapter 1 is freely available. Thanks in advance for any of your feedback. It will contribute to the adoption of Rust and put forward STMicroelectonics products in this context. Kindly, David.

Hello, when I was using the SDIO of F407, I encountered a problem where the SD card could only read but not write. When I enabled "HardwareFlowControl" and set "ClockDiv" to 2, the function was normal. Why is that? When I operate the SDMMC of the H750, it's the same. It must be set to the above Settings.I checked the waveform of the SD card. In terms of waveform quality, it's okay.The waveform of the clock is shown in the following figure