Solved

I have a custom board using STM32H735ZGT6 and the LAN8742 Ethernet PHY using RMII. During the execution of CubeMX generated Ethernet initialization code, the MAC software reset bit is not cleared triggering an error. I have read a lot of forum posts about this issue and have verified the following:The RMII reference clock is supplied by the PHY using a 25MHz crystal as in the H723 nucleo board. The 50MHz clock generated by the PHY is present at PA1 pin and verified with an oscilloscope. (see osci image below) VDDCR voltage is 1.2V generated by internal regulator on PHY The PHY hardware reset is supplied by a MCU GPIO, and the resistor straps seem to function properly during reset (probed all with oscilloscope). I also have a pulldown resistor on the LED2 pin so that REFCLKO is generated by PHY. I can communicate through MDIO with the PHY to read out and write to registers, confirming that straps work ok.  The output side of the PHY works, a link is established in both 10 and 100Mbps mo

Hello,We are using STM32U585QII6QTR in our device that is powered via USB and batteries. We observe that some devices do not startup anymore after some time of use. It is unclear which impact causes this. Everything that can be measured outside the MCU looks as expected.Debugging the device shows that everything is working normally, for example the bootloader checks successfully that a valid firmware is flashed by using HAL_HASHEx_SHA256_Start/Finish.However, the Systick is not triggered and GetTick remains 0, but SysTick->VAL is counting.Similartly, when starting the FreeRTOS Scheduler the device crashes when the SVC 2 instruction is called. The SVCHandler interrupt is not called. So, it looks like interrupts are not activated anymore.I created a no-RTOS project with CubeMX and checked directly after HAL_Init if the Systick is triggered. On a “damaged” device there is no SysTick triggered after HAL_Init whereas on a good device it is as expected.I attached a dump of important regis

Can the STM32MP231 simultaneously capture or stream four 2-lane MIPI CSI-2 camera streams through a DS90UB960/TDES960 using VC0–VC3?I have reviewed ST’s documentation on “How to use one or multiple multi-stream MIPI CSI cameras.” But did not get complete clarity on simultaneous capture of four camera streams. The documentation example appears to show routing for up to three streams/channels through the DCMIPP pipes (Dump, Main, and Aux).

Hello everyone,I am experiencing a persistent debugging issue using AutoDevKit Studio. The debugger connects successfully to the target, but the application never reaches the main() function, immediately hanging at an exception handler.Here are the details of my setup and the issue:1. Part Number Target Board: AEK-MCU-C4MINI1 Debugger: AEK-MCU-SPC5LNK  2. Environment IDE: AutoDevKit Studio (Eclipse-based) on Windows 11. Toolchain/Debugger: GDB OpenOCD Debugging (OpenOCD 0.12.0+dev).  3. Schematics Standard ST evaluation board (no custom schematics). 4. Details When I launch a debug session, OpenOCD connects successfully, halts the target, and identifies the chip. However, the execution is stuck with the following error: Break at address “0x404100 with no debug information available, or outside of program code.I am fully aware that the "Source not found" window shown by the IDE is simply a consequence of the core hanging at this specific exception handler address (which naturally la

Hello, I would like to use a magnetometer to develop a small system that can discern the presence of a certain object with a magnet mounted on top of it. For this reason I got a X-NUCLEO-IKS5A1 as a starting point.From my understanding the faster approach was to connect the NUCLEO board NUCLEO-F401RE (which I already had) to the aforementioned X-NUCLEO board with the software MEMS-Studio.So I followed the procedure explained here:  and applied it to the “new” X-NUCLEO -IKS5A1 board (instead of the IKS4A1 described in the video).I’ve successfully programmed the board with the supplied firmware (STMicroelectronics/MEMS Studio/firmware/mems-studio/x-nucleo-iks5a1/nucleo-f401re/DataLogExtended.bin, Interface MASS STORAGE, Device_ NODE_F401RE).But when I try to connect the board it says:And I cannot go further with the procedure.Is there something wrong with my procedure? Any idea of the issue?If not, how can I start using this board? Starting from an STM32CubeMX project?Thank you for your

STM32CubeMX v6.16.1 has a small bug. Under Project Manager - Code Generator - HAL settings is an option to pick under which context the free pins should be set as a analog. I am using STM32N6 which has 3 contexts (FSBL, App, ExtMemLoader).The problem is that CubeMX doesn't store (or recall) this setting. I want to set them under Appli, but on every program start it sets the context to FSBL. After doing same "fix" for tens of times it gets quite annoying.

Is it possible to get the schematic or direct me to the link of the STEVAL-IKR002Vx (RF motherboard) The RF motherboard has an STM32L microcontroller used for driving the SPIRIT1 transceiver and to communicate to a PC via USB.  Thank you

将LSPHB焊接至FPC上进行测试，测试时发现输出压力会随时间发生无规律的漂移，请问这是什么原因，应该如何解决

Our application is an intelligent antenna pointing system that uses two identical sets of IIS2MDC magnetometer + ISM330DHCX accelerometer/gyroscope — one pair on our base board, and one pair attached to the moving gimbal. Our overall hardware design was based on the IOT02A board: we got the DataLogFusion running flawlessly on the ST IOT02A first, then subsequently ported that code-base to our own STM32U5-based system.Our code currently runs MotionFX sensor fusion with two instance memory pointers, with each pair of MEMS sensors feeding into the MotionFX library at a 100 Hz interval — as recommended, and as we saw done in the DataLogFusion example for a single set of magnetometer, accelerometer and gyroscope sensors.  Our firmware design used the DataLogFusion example application and setup as a starting point and then adapted it with multiple instances as we have two sets of sensors in our hardware controlled by a single STM32U575ZIT MCU.Most of the MotionFX API takes an explicit instan

Confirming that CubeMX loading problem has been fixed. But I need to point out that RAMCFG enabling still comes with issue: AXISRAM clocks enabling code is not generated. As I wrote in another post, clocks are partially enabled by RIF code: STM32N6 RIF and MMT autoconfiguration errors - STMicroelectronics Community But AXISRAM3 clock is not enabled, so firmware halts. And power needs to be enabled also. My workaround is to enable all the AXISRAM clocks and power in HAL_RAMCFG_MspInit: void HAL_RAMCFG_MspInit(RAMCFG_HandleTypeDef* hramcfg) { /* USER CODE BEGIN RAMCFG_MspInit 0 */ /* USER CODE END RAMCFG_MspInit 0 */ /* Peripheral clock enable */ __HAL_RCC_RAMCFG_CLK_ENABLE(); /* USER CODE BEGIN RAMCFG_MspInit 1 */ /* AXI SRAM1-2 is already enabled by BootROM. * Enable AXI SRAM3-6 clocks manually because CubeMX doesn't do it. */ __HAL_RCC_AXISRAM3_MEM_CLK_ENABLE(); __HAL_RCC_AXISRAM4_MEM_CLK_ENABLE(); __HAL_RCC_AXISRAM5_MEM_CLK_ENABLE(); __HAL_RCC_AXISRAM6_MEM_CLK_ENABL

Hi Support Team, We are assessing a 125°C manufacturing burn-in process for a medical electronics product and would like to understand whether AIS2IH has undergone any qualification or reliability testing at or above 125°C.Are there any available data or reports relating to:HTOL (High Temperature Operating Life) HTSL (High Temperature Storage Life) Burn-in testing Accelerated life testing Other high-temperature qualification activitiesWe are not seeking approval for continuous operation beyond the datasheet limits, but rather any information that may support the assessment of a limited-duration burn-in process.Any relevant data, reports, or guidance would be greatly appreciated.

Hi all,I am using ST link v3 mini when i try to connect the controller using the st link v3 it is showing as theError : unable to get the core ID.But when i try to connect the controller using the DFU mode.i am able to connect to the controller and able to program the controller and option bytes are also AA(RDP 0)>. What is issue why i am not able to connect to the mcu using the St link (SWD) but able to connect to the controller using the DFU mode.is there anything i have to make changes in the cube programmer. 

Hi,I am evaluating the LSM6DSV16X for a project that requires gyroscope Angular Random Walk (ARW) and In-Run Bias Stability specifications. I understand these AVAR (Allan Variance) parameters are not tested at production level and therefore not included in the datasheet.However, I noticed that ST has previously shared characterization data for related parts under the same request:- LSM6DSR: https://community.st.com/mems-sensors-48/what-is-the-bias-in-run-stability-instability-of-the-lsm6dsr-gyros-and-accelerometers-41777- LSM6DSV16BX: https://community.st.com/t5/mems-sensors/bias-instability-and-random-walk-of-lsm6dsv16bx-and-ism330dlc/td-p/574922 Could someone from ST please share the equivalent characterization results for the LSM6DSV16X (gyroscope, and accelerometer if available)? Specifically, if possible, could you provide the full Allan Deviation plot (σ(τ) vs. averaging time τ) rather than just the extracted ARW / bias instability numbers — we need to see the noise floor and cor

We are looking for a more details on STDES-ESP01 product and product which does cuffless BP measurement as discussed in this video. 

Hello ST Community,I am using an STM32G431RBT3 on a custom-designed PCB. The STM32 is used to control a DRV8334 3-phase motor driver for a blower motor application.I am facing a critical issue where the controller works correctly when using ST-LINK debugging, but it does not run correctly when the PCB is powered on standalone.HardwareMCU: STM32G431RBT3 Package: LQFP64 Motor driver: DRV8334 PCB: Custom-designed PCB IDE: STM32CubeIDE Programmer/debugger: ST-LINK MCU supply: 3.3 VProblemWhen I power the PCB directly without ST-LINK, the following happens:The STM32 starts executing the firmware. A GPIO that I set HIGH in main() becomes HIGH. The GPIO that I toggle inside the while(1) loop does not toggle. I added a GPIO HIGH operation inside HardFault_Handler(). That HardFault GPIO becomes HIGH.Therefore, it appears that the MCU reaches main() but subsequently enters HardFault before the normal while(1)  execution continues.When ST-LINK is connectedIf I connect ST-LINK and program/debug/ru

CubeMX 6.18 does not persist two critical STM32U5A5 USBX and FileX settings when their values are entered as multiplication expressions in the form N*1024. This results in incorrect macros being generated in the app_azure_rtos_config.h header. The correct minimum values are provided below.UX_APP_MEM_POOL_SIZE    40*1024FX_APP_MEM_POOL_SIZE     2*1024USBX_MEMORY_STACK_SIZE 24*1024In the case of the STM32U5G9, CubeMX does not persist the USBX System Stack Size setting. The minimum required value is 24 KB. 

Support request: STM32WL33CC — DEEPSTOP average current rises well above datasheet spec, even within a single uninterrupted dwellPart / packageSTM32WL33CC (custom board, not a Nucleo/eval board).SummaryOn our custom board, DEEPSTOP average current starts near the expected low-µA range on entry but climbs over tens of seconds to a plateau of roughly 360–390 µA — two to three orders of magnitude above the datasheet's Table 13 "Current consumption in DEEPSTOP mode" figures (≈1.2–2.1 µA ICORE across all listed LSI/LSE/RTC/IWDG/LPUART configurations). This is reproducible, happens within a single uninterrupted DEEPSTOP dwell (i.e. it is not an artifact of repeated entry/exit cycling), and we have ruled out every peripheral, sensor, and firmware-level cause we can identify. We'd like ST's input on whether this is a known/expected behavior of the DEEPSTOP power architecture (e.g. an internal analog settling time not captured in the static spec table) or points to a board- or configuration-lev

Hello, I have an ST Nucleo U5A5ZJ-Q board. I am powering the board through the CN1 connector and using the ST-LINK at the same time.In the project I am working on, I would like to connect a USB device to the hardware. For this purpose, I want to use the USB Type-C connector.When I connect the sensor to the Type-C connector, it does not receive any power. My assumption is that I cannot power the device through the USB Type-C connector. Also, LD7 does not light up.I wanted to consult you about this before doing anything that might damage the board.In addition I use usb standalone(STM32Cube FW_U5 V1.8.0).Thank you in advance for your support. Best Regards,Faruk

i can't get to download stm32cubeide. download jus

I am using the STM32F405RGT6 built-in System Memory CAN bootloader for firmware update.Configuration:MCU: STM32F405RGT6 CAN: CAN2 (PB5 RX / PB13 TX) External HSE: 24 MHz CAN bitrate: 125 kbps Host: Jetson Linux / SocketCAN Standard 11-bit CAN IDI am facing an issue with the CAN Erase command (0x43).For example, to erase Sector 8:cansend can0 043#08The STM32 responds with the first ACK:043 [1] 79but I never receive the second/final ACK after the erase operation.So the sequence is: Jetson -> 043#08STM32 -> 79 <-- received <-- final 79 is NOT receivedImportant observations:Mass erase using 043#FF works. Individual sector erase using STM32CubeProgrammer + ST-Link/SWD works, including Sector 8. RDP = AA (Level 0). WRP0–WRP11 are unprotected. Sector 8 address is 0x08080000. CAN communication with the ROM bootloader otherwise works.Therefore, it appears that the 0x43 command is being accepted by the ROM bootloader, but the sector erase operation doe

Hi,I'm measuring the power consumption of the LIS2DUXS12 for FSM, MLC, and the step counter with or without Smart Power mode (SMART_POWER_EN bit in CTRL1). The current reduction matches my expectations (e.g. ~13.3 µA down to ~8.2 µA with 1 FSM program running). AN5909 describes the mechanism as dynamically scaling the supply current of the embedded function hardware blocks between "operating level" and "lower non-operating level".My question: Is there any trade-off to enabling Smart Power mode besides the current savings? For example:Any added latency? Any impact on accuracy? Any recommended ODR for Smart Power? Any settling time when switching between operating and non-operating levels?I couldn't find this addressed in the AN5909 or the datasheet, and I haven't found any existing thread relating to this. Any clarification would be appreciated.Thanks!

Hello ST Expert,We have been experiencing a number of shorts and opens on the IIS2DLPC and suspect issues with our solder mask layer. We have tried opening the solder mask under the component and have tried leaving the solder mask under the component, please see images below.  We have experienced shorts and opens using both of these methods. Could you please provide the recommended solder mask layer for this component? Thanks, Sam 

Hi, STNow for my STEVAL-MKI225A Board which contains LPS28DFW Barometer sensor I Used the application “read_data_polling.c” which is running on “NUCLEO-F401RE Board” to test the sensor with the default example configurations which are:md.odr = LPS28DFW_4Hz;md.avg = LPS28DFW_16_AVG;md.lpf = LPS28DFW_LPF_ODR_DIV_4;md.fs = LPS28DFW_1260hPa;and I noticed that when I’m getting the data in the while loop, It works correctly only with I2C Standard Mode (100KHz) and it stucks with fast mode.but the main problem is when I’m adding delay or another code execution to the while loop, It also stucks and doesn’t work unless I removed the delay or the code added. 

Good afternoon, We are currently working on the development of a board intended for use in explosive areas. For the design calculations, could you please confirm the junction-to-ambient thermal resistance (θJA) of the LSM6DSV80XTR? In the Datasheet it is not avaliable.

Hi everyone, I am facing an long-standing issue with a STM32L476RE-powered device loosing UART frames when waking up from UART3 from Stop Mode (will be analyzed on another issue).Prompted by this, I have a generic question for clock configuration after Stop1-2 mode.The device uses HSI & LSE for all of its peripherals, in a bare-metal CubeMX project.Q1: The function __HAL_RCC_WAKEUPSTOP_CLK_CONFIG(RCC_STOP_WAKEUPCLOCK_HSI);is called 1 time before while(1){} loop. Should it be called just once or should it be called every time before calling HAL_SuspendTick();HAL_PWREx_EnterSTOP1Mode(PWR_STOPENTRY_WFI);?Q2: Should we call SystemClock_Config();every time after waking up from Stop mode, despite the fact that the clock selection ( HSI & LSE ) remains the same and no PLL or MSI is used ?Q3: Could calling SystemClock_Config();HAL_ResumeTick();disrupt an ongoing UART-RX ( running on Idle-line callback ) , despite the fact that clock selection is not changing ? Thank you in advance