No best answer

Hi everyone,I am currently working on repairing my NUCLEO-F767ZI board (Revision: [MB1137 Rev B]). The 3.3V LDO regulator (U6) was damaged and needs to be replaced.While working on it, I found a hardware discrepancy: According to the official schematic, U6 is specified as LD39050PU33R (a 6-pin DFN package). However, on my physical board, the PCB footprint for U6 clearly has 8 pads. The damaged original IC I removed is an 8-pin package with the marking code "PH 2kE". Since a 6-pin IC cannot fit on this 8-pin footprint, has anyone encountered this before? Could you please help me identify the correct 8-pin LDO part number to replace it?I have attached pictures of the physical 8-pin IC and the 8-pad PCB footprint for reference.Any advice would be greatly appreciated. Thanks in advance! Figure 1: The removed original 8-pin LDO IC with the marking code "PH 2kE".Figure 2: The physical 8-pad PCB footprint for U6 on the NUCLEO-F767ZI board. 

I have created a dev board based on the STM32H743IIT6 MCU. On first power up I have managed to destroy two MCUs and I cant figure out what is killing them. On first power up 3V3 is immediately shorted to GND, after removing the MCU the pins are permanently shorted.Here is my schematic. The only changes I have made from the physical PCB is adding 10K pull up to PDR_ON, 10K in line from VBUS to the MCU and connecting the VCAP pins. Does anything stand out in the schematic?I have created modules from multiple STM MCUs(F1,G0,G4,WB,H5,N6) and this is the first time I am running into a power issue with a PCB.

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. 

I would like to move the project from:C:\ST\STM32Cube_FW_WB_V1.24.0\Projects\P-NUCLEO-WB55.Nucleo\Applications\BLE\BLE_HeartRateFreeRTOSto:C:\Projects\Myprojectso that I can make modifications at will and not worry about corrupting the original code. At the same time, I want all the libraries, etc. to fall under the same directory as the new code will eventually be submitted to version control.How can I do this?Note: All my other projects under the C:\Projects directory were started with CubeMX and all seem to do as I want.

I’m looking for data related to peak pulse Power Rating of this TVS, that includes pulse width (tp) of up to 10ms. Also, I wanted to know if there is any reliability data that is available for this component.  

I was finding non-deterministic behavior entering standby -- small code changes unrelated to the standby code or devices seemed to prevent standby.  Many hours of debugging later using a joulescope and claude automation, the following fixed the problem -- declare the standby code as noinline (by default, my builds inline small funcitons) void __attribute__((noinline)) enter_standby_mode(void) Also, an attribute to not optimize works as well.   It did not appear that the generated assembly for the standby code changed, but what did change, due to inlining, is the code alignment.  This suggests, but doesn’t confirm, that the fetch pipeline can impact the ability to enter standby on this part.  This was never an issue on the stm32l432.

Hello, I am using VL53L9CX with adapted drivers for ESP32 / Arduino environment. I am able to read values and play with the settings but I am a bit worried with the precision I get. I run the sensor in precision mode, 4ms exposure time. My bench is indoor. Sensor facing the ground ( 1 m ish, wood) or the roof (1.6m ish, white ceiling). Resolution is 8 x 6 (Binning 12). I have radial to perpendicular conversion enabled so I am expecting to see all distances being equal +/- precision across the cells of the frame (excluding corner cells maybe). According to table 34: Precision for “ambient mode 24x20” profile from the sensor datasheet: (results are better for 24*20 then they are for 54*42, so I assume it is the same or better for 8*6 compared to 24*20)I am expecting less than 0.8 mm difference between the values but instead I get 50 mm - 100 mm or more of difference. So I was wondering, is there some specific settings to enable to achieve such precision / accuracy ? PCB is of my own (not

I am looking for the STEVAL-VL53L9 evaluation board for vl53l9cx, but it is out of stock at all distributors I checked.could you please let me know the expected availability / ETA, where i can buy it or, if there is any similar alternative board with same specs.

I’ve been using STM32CubeIDE, STM32CubeMX, STM32CubeProgrammer, and STM32CubeMonitor on a Mac currently running macOS 26.6.When I run env or export in Terminal (which uses Zsh by default), I find these two STM32-related environment variables.STM32CubeMX_PATH=/Applications/STM32CubeMX.app/Contents/ResourcesSTM32_PRG_PATH=/Applications/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/Resources/binExamined Zsh dotfiles in my home folder and found the following two *export*s in ~/.zshrc that set them.export STM32CubeMX_PATH=/Applications/STM32CubeMX.app/Contents/Resourcesexport STM32_PRG_PATH=/Applications/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/Resources/binWhich apps have added these; CubeMX, CubeProg, or perhaps the respective plugins from CubeIDE? What is their intended purpose, and in particular, which other STM32Cube tools rely on them? Also, do the apps add these every time on launch or only once during installation?

STM32CubeIDE v2.2 has left all of our code in question. We need guidance with the CMake since we no longer have any helper dialogs of the old IDE to create a project within the new framework that matches the old IDE. list of helpful guidesNo HAL is neededa CMSIS and DFP environment for the selected processorCMake snippets that allow us to create and include legacy library code (adjusted for new processor)methods to control code optimization for code sections and filesdirectory structure methodsbasic commands to show what size of code we just compiled and output formats ie .hexWe believe this would be a great tutorial to ease the transition. I’m sure I have missed many other features of the old environment that you will quickly attend to.Any guidance that doesn’t require 200 hours of head banging appreciated. Glenn

We have been evaluating the pre-trained model yamnet_e1024_64x96_tl_qdq_int8.onnx from the STM32 Model Zoo (ESC-10 variant) and noticed a potential discrepancy between the class label order in the provided YAML configuration and the actual output behaviour observed on target.While the model itself appears to perform well, the mapping between output indices and class names does not seem to match the order documented in the YAML file. Observed behaviour:The YAML file lists the classes as:0: dog1: chainsaw2: crackling_fire3: helicopter4: rain5: crying_baby6: clock_tick7: sneezing8: rooster9: sea_waves However, on our target, the outputs appear to correspond to the following order:0: chainsaw1: clock_tick2: crackling_fire3: crying_baby4: dog5: helicopter6: rain7: rooster8: sea_waves9: sneezing This is consistent across multiple input samples, which makes us suspect a systematic label remapping rather than random misclassification. Preliminary hypothesis:We suspect that this could be caused

Hello, I was wondering where can I find the Pick n place file to create the dev board. on the official site there is the BOM and the gerber files, but without the pick N place I can’t actually assemble it.Thanks for the helpRoman

So I have an STM32 project in VSC and when I first set up this project and started debugging, I vaguely remember being asked by VSC to create a launch.json file.Now it seems I can build a ‘debug’ session, and launch it, and debug with all the usual features like step-in, step-out, continue, and so on. But how do I now add a ‘release’ build, which strips debug info and allows me to program a device without debugging it? [I am trying to be a good citizen and get along with STM32 for VSC, but so far it seems like i) A retrograde step ii)A mix of modern UI’s and very old looking Java (MX) and iii)You need a science degree in CMAKE to understand anything. ]My launch.json looks like this:{ // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "stlinkgdbtarget", "requ

I am currently working with an STM32 MCU and facing an issue while trying to connect the board to my PC using an ST-LINK debugger. The board powers on normally and there does not appear to be any obvious hardware issue, but STM32CubeProgrammer is unable to detect the target device. The connection attempt either fails or reports that no target is found, so I am currently unable to program or debug the MCU.So far, I have checked the basic connections and setup:USB cable and ST-LINK connection Board power supply and voltage SWDIO and SWCLK connections STM32CubeProgrammer installation ST-LINK firmware and connection settingsI am not sure if the problem could be caused by the MCU configuration, SWD interface, boot mode, or some setting that may have been changed in the firmware. I would also like to know if there are any recommended STM32CubeProgrammer options or recovery procedures that should be tried when the target MCU is not detected.Has anyone experienced a similar issue with an STM32

I want to get the scroll position of a ScrollList widget in the view, and also set the scroll position in the view.However, the `setOffset` and `getOffset` functions of `ScrollBase` are protected.How can I get and set the scroll position of a scrolllist?

I have redrawn the NUCLEO-H5E5ZJ schematic as a personal exercise in understanding the architecture of the board and the STM32H5E5. I have consolidated the original multi-sheet design into a main STM32H5E5 schematic and a separate STLINK schematic, using port objects to make the principal interconnections explicit. During the redraw, I cross-checked the connectivity against ST's original Altium design files and the more recent PDF schematics.My aim was to show the MCU GPIO ports rather than their alternate functions, as I found this gave me a different picture of how the MCU is connected to the board. The exercise also revealed just how much functionality is exposed by the NUCLEO-H5E5ZJ PCB: the usefulness of the M.2 Key A socket, the extensive possibilities offered by the other headers, and, in particular, the surprisingly large number of MCU GPIOs that are brought out to them and are available.I have a great deal of respect for the NUCLEO-H5E5ZJ PCB and for the STM32H5E5. The capabil

As shown in the picture above, on Fedora 43, the CubeProgrammer application is not matching the OS scaling and there are no options to configure it like in CubeMX. CubeProgrammer is the latest version (v2.22.0), installed today.My computer is a laptop with a 2256x1504 screen and OS-level scaling is set to 133%. All other applications behave as expected, I only ever have issues with ST’s applications.This issue has been reported multiple times in the past on different linux distributions. I have tried all suggested fixes in those posts, none worked. Links to other issues that had no solutions: 

Hi STM Team,We are currently using the 25 MHz crystal configuration based on the NUCLEO-H723ZG reference design for our STM32H723 + LAN8742 Ethernet implementation.The original/reference crystal used is:NX2016SA 25 MHz – EXS00A-CS11321 (NDK)Frequency: 25 MHz Load capacitance (CL): 6 pF ESR: 80 Ω Reference design uses approximately 5.1/5.6 pF load capacitors.However, the above crystal is currently not readily available in the market, so we evaluated the following alternatives:ECS-250-6-37-JTN-TR – 25 MHz, 6 pF, 80 Ω X2C025000DZ1H-U XRCGB25M000F1SBAR0With the above replacement crystals, we are observing significant data loss during Ethernet communication through the LAN8742.We have already tried the recommended/reference crystal configuration and compared the Ethernet behavior with the replacement crystals, but the issue is still observed with the alternate parts.Could you please help us identify a suitable 25 MHz crystal for the STM32H723 + LAN8742 configuration, preferably a currently

I have encountered a specific issue using the STM32F411RE NUCLEO Board and I2C peripherals:The problem:When i plug in the board with I2C devices (DFROBOT BMM150, MPU6050, ADAFRUIT ICM20948) already connected to the board my PC (LINUX) cannot find the device.when trying to flash CUBEIDE says something along the lines of ‘STLINK not found’ and PROBE-RS says:ERROR nusb::error: interface not found (errno 2) WARN probe_rs::probe::list::linux: Make sure you have reloaded udev rules after setting everything up WARN probe_rs::probe::list::linux: Read more under https://probe.rs/docs/getting-started/probe-setup/ Error: Failed to open probe: Failed to open the debug probe. Caused by: 0: The debug probe could not be created. 1: A USB error occurred. 2: interface not found (errno 2)The fix:1) UNPLUG BOARD2) DISCONNECT I2C peripherals3) PLUG in BOARD4) RECONNECT I2C peripherals5) the STLINK is found again and I can flash code like normalWill this be an issue if I design a PCB with permanently conne

 I have redrawn the NUCLEO-H5E5ZJ schematic as a personal exercise in understanding the architecture of the board and the STM32H5E5. I have consolidated the original multi-sheet design into a main STM32H5E5 schematic and a separate STLINK schematic, using port objects to make the principal interconnections explicit. During the redraw, I cross-checked the connectivity against ST's original Altium design files and the more recent PDF schematics.My aim was to show the MCU GPIO ports rather than their alternate functions, as I found this gave me a different picture of how the MCU is connected to the board. The exercise also revealed just how much functionality is exposed by the NUCLEO-H5E5ZJ PCB: the usefulness of the M.2 Key A socket, the extensive possibilities offered by the other headers, and, in particular, the surprisingly large number of MCU GPIOs that are brought out to them and are available.I have a great deal of respect for the NUCLEO-H5E5ZJ PCB and for the STM32H5E5. The capabi

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 Team,I am using the STM32N657x0-Q Nucleo board with the STEVAL-66GYMAI1 (VD66GY) camera board connected via FFC. Both CN8 and CN10 are connected to the PC, and I am viewing the camera stream through UVC.I tested the official precompiled HEX files from: X-CUBE-N6 Camera Capture STM32N6 Getting Started Object Detection In all cases, the image is heavily blurred. Objects appear relatively clear only at approximately 1–2 cm from the lens, while anything beyond that distance becomes significantly out of focus.I attempted to adjust the M12 lens focus across its full rotation range, but no noticeable improvement was observed. The same behavior occurs with multiple example projects and unmodified hardware.Could you please advise which of the following areas is most relevant to investigate? Camera board compatibility with STM32N657x0-Q Sensor/lens configuration in the example firmware Lens focus or alignment issue Defective lens or hardware issue Recommended reference project/co

  Hi,       Summary. The ONNX importer in ST Edge AI Core 2.2.0 (X-CUBE-AI 10.2.1) ignores the  dilations attribute of Conv. It applies the padding but convolves as if dilation = 1,  so the output length is L + 2*pad - (k-1) instead of L. The TFLite importer handles  the same operator correctly.  Minimal reproducer (attached, 51 KB): a single Conv1d(64->64, kernel 3, dilation 4,  padding 4), input 1x64x80. The ONNX node is Conv {pads:[4,4], strides:[1], dilations:[4]}.  Per the ONNX spec the output is (80 + 4 + 4 - ((3-1)*4 + 1)) / 1 + 1 = 80.  PyTorch and onnxruntime both produce 1x64x80.      stedgeai analyze --model dil_f32.onnx --target stm32u5  | model handed to stedgeai                      | reported output     | expected |  |------------------------------------------------------|-------------------------|--------------|  | ONNX float32                                          | f32(1x64x86)       | 1x64x80  |  | ONNX int8 QDQ (per-channel)               | int8(1x64x86)     

Hello, I am experiencing a reproducible issue with STM32CubeMX when generating a project for the first time on our U: drive. Our environment is part of an Active Directory domain, and each user has a U: drive mapped to their personal network home folder. Error in STM32CubeMX.logDuring generation, CubeMX successfully creates several temporary files in:  U:\FreeRTOS_M2\testv10\MXTmpFiles\ For example:  17:02:54.994 oldGeneratedFile ...\rtos_kernelStart.tmp_save17:02:55.076 Generated code: ...\rtos_kernelStart.tmp However, during the next generation pass, CubeMX tries to access the .tmp_save file again:  17:02:56.195 oldGeneratedFile ...\rtos_kernelStart.tmp_save17:02:56.200 ERROR ProjectBuilderjava.io.FileNotFoundException:U:\FreeRTOS_M2\testv10\MXTmpFiles\rtos_kernelStart.tmp_save(The system cannot find the file specified) 2026-09-03 17:02:55,707 [INFO] CodeEngine:297 - oldGeneratedFile, U:\FreeRTOS_M2\testv10\MXTmpFiles\rtos_threads.tmp_save2026-09-03 17:02:55,774 [INFO] CodeEngine:321

I am using STM32CubeIde, No RTOS, USART1, RX DMA (Circular), TX DMA in normal mode with DMA_IT_HT disabled.I’ve got main loop periodically outputting a simple message on the USART. System appears to hang when commanded to change baud. I’ve tried perhaps dozens of variations that have been recommended by “STM32 Sidekick” and Google AI.  Most work with the debugger connected.  None work without the debugger which is making this difficult to troubleshoot.  Sidekick example shown below.  // 1. Wait for any ongoing transmissions to finish safely // This prevents splitting a character mid-air. while (__HAL_UART_GET_FLAG(huart, UART_FLAG_TC) == RESET) { // Optional: Implement a timeout mechanism here } // 2. Temporarily de-initialize the UART peripheral // This turns off the UART but keeps your GPIO and DMA settings intact. if (HAL_UART_DeInit(huart) != HAL_OK) { return; //H