Recently active topics

HelloWe are currently using the ASM330LHH in our product and conducting ATP (Acceptance Test Procedure). During the thermal cycling/temperature test phase of the ATP, we have observed significant fluctuations and instability in the sensor outputs.To resolve this issue, we are considering migrating to the ASM330LHHXG1.While we have already reviewed the standard datasheets for both parts, we would like to request additional engineering insights or internal test data regarding their temperature stability. Specifically, we would appreciate your guidance on the following:Does the ASM330LHHXG1 feature any hardware, packaging, or calibration improvements that provide better thermal stability or lower thermal drift compared to the standard ASM330LHH? Have there been any reported cases or internal ST data showing that the ASM330LHHXG1 delivers more stable and repeatable results under stressful temperature environments like ATP? Beyond the datasheet specifications, are there any specific PCB lay

 @JL. Lebon Hello ST Engineer,I would like to ask a follow-up question regarding the LPD pin timing.In the ST25 application manual, I found a timing diagram for LPD and VCC in ultra-low power mode. It states that when the RF field is absent and LPD switches to LOW, we need to wait for tbootLPD (0.6 ms) before communication, as shown in the figure below. However, I also noticed another description in the ST25 datasheet regarding the LPD pin. It mentions that to ensure the internal regulator turns on, its turn-on time (approximately  0.1 ms) must be added to the boot duration, as shown in the figure below.Given these two pieces of information, could you please clarify: Does this mean that after pulling LPD low, I need to wait for a total of 0.7 ms (0.6 ms + 0.1 ms) before starting communication? Or does the specified tbootLPD (0.6 ms) already include the 0.1 ms regulator turn-on time?I look forward to your reply.

Hi HelloI would like to confirm whether the LDO regulator is available on the STM32H725REV6 with VFQFPN68 encapsulation. The documentation is ambiguous, as AN5419 says the following in item 2.1.6:The low drop out (LDO) voltage regulator is always enabled after Power-on reset. If it is disabled, it remainsdisabled even after any reset source except for a Power-on reset. For system supply configuration where thisregulator is not needed, it will be switched OFF by the user software after system start-up. On some packages,the LDO power supply is available on external VDDLDO pins. When it is not available on an external pin, VDDLDOis connected internally to VDD.Can you clarify?

Hello, community,I try to  develop power supply  based on VIPER35L, but  it  runs only in burst mode never reaching steady regulation. I have made almost a copy  of  STEVAL-ISA171V1, except of transformer, which was made by myself. According application note  AN4812.  What might be the culprit?  Are  transformer data  correct in it ?  I mean ratio  8:1:1. Isn’t  it too  small to power  self? Several oscilloscope  snapshots are taken.  Any advice appreciated. Bnx  

Rather than having to select my IDE every time I create a new Project, it would be nice to be able to set my own default.Similarly for other settings; eg, I always like to have the generated code as .c + .h file pairs.

Hello to all, I follow the creation of OEMiROT_Boot, app secure, app not secure with NUCLEO-H563ZI like suggested into  https://wiki.st.com/stm32mcu/wiki/Security:How_to_start_with_STM32CubeMX_OEMiRoT_Boot_path_on_STM32H563.I want to use Visual studio Code with  extension STM32CubeIDE.Follwing the instructions into the web page “:How_to_start_with_STM32CubeMX_OEMiRoT_Boot_path_on_STM32H563.” I have to compile the OEMiROT_Boot, if I import the project OEMiROT_Boot from STM32Cube_FW_H5_V1.7.0 for NUCLEO-H563ZI, into vs code there are error I have to copy  “stm32h5xx_bl2.ld” to utput.ld into the same folder to let vs code to import without error but it’s not possible to compile the project, then I’ll compile the other with keil without problem.After I’ve follwed the list of operation to do but at the point “ 5. Debug Authentication configuration” I cannot select configure (into the project configuratione of MXCube I’ll try to create a project KEIL and CMAKE without lack because I can comp

I am unable to change profile/username name can someone help me out 

Hey everyone,I'm having a rough time getting my NUCLEO-H755ZI-Q board to talk to my PC. Whenever I try to connect using STM32CubeProgrammer or debug from STM32CubeIDE, I keep hitting the same error: Error: No STM32 target found!I'm using the onboard ST-LINK/V3 plugged in via the USB ST-LINK port. The board lights up fine, and the OS detects the ST-LINK interface without issues, but the moment I try to probe or connect to the target MCU, it fails.Here is what I've tried so far to troubleshoot: Switched between Normal, Hardware Reset, and Software Reset modes in CubeProgrammer. Lowered the SWD frequency down to 480 kHz. Updated the ST-LINK/V3 firmware to the latest version. Double-checked physical jumpers and power source configuration. Has anyone run into this specific issue on the H755 before, or know a reliable way to force it into bootloader mode to erase the flash? Thanks in advance for any advice!

Hi,May I know the ASIl rating of L9663?If this device is functional safety complaint, Is there a safety manual existing that I can request for?

Here the UIF waveform shifted to high when counter register equaled to 0x02. Isn’t it supposed to shift at the moment the UEV is set? Figure148 also has this problem. And I traced back to the earlier versions. As far as I can reach, the figures were good until rev11, and they were changed since rev17 or earlier. 

Dear all,I am using an application on the NUCLEO-F401RE board. I wrote and successfully compiled a program (with no errors), but I am encountering an error during debugging with the message: "Failed to execute MI command: remote target localhost:61234".The ST-LINK (ST-LINK GDB server) is configured as the debug probe and SWD interface.I have replaced the communication cables and reinstalled the STM32CubeIDE software. It used to work normally.The log is attached below:

Error MessageDebugger Settingsi am trying to upload the firmware into the co-processor of the stm32mp157fdk-2 board and struggling with this error I shared the error details and my debug configurations In the drop down menu of the Serial Port nothing is over there but I can able to use putty and can able to view the booting messages, and I am not trying to upload the code while connected with the putty, I also tried the engineering mode tooAnd now I am on the windows, is this windows specific error or what? cause when I was trying to upload using the linux everything was running very fine. Now I create elf file everytime and scp into the board then manually start the co processor, I don’t want to do this again and again 

When using an STM32 timer to control LED brightness, is it generally better to keep the timer period fixed and adjust the compare value, rather than changing the timer period as well?My understanding is that changing the compare value allows the duty cycle to vary while keeping the PWM frequency constant. Are there any practical considerations when selecting the timer prescaler and auto-reload value, particularly when aiming for smooth dimming across the full brightness range?I’d appreciate any guidance on the timer configuration and potential trade-offs.

Hellow everyone, i am facing this issue that when  connect my nulceo-WL55JC1 with perfectly working cable to my PC it rapidly connects and disconnects again and again i tried to update its driver and mass erase but it connect and disconnects so fast i am not able to do it and i read its quick guide and all the jumpers are in its place once is tried to upload the code to it and in between it got connect the again disconnect some behavior every time.  This is the log when is was able to upload the code on it :STMicroelectronics ST-LINK GDB server. Version 5.7.0Copyright (c) 2020, STMicroelectronics. All rights reserved.Starting server with the following options:        Persistent Mode            : Disabled        Logging Level              : 1        Listen Port Number         : 61234        Status Refresh Delay       : 15s        Verbose Mode               : Disabled        SWD Debug                  : Enabled        InitWhile                  : EnabledWaiting for debugger connection...

Hi,Do enabling BDU also protect temperature data registers from getting refreshed while reading the data? Or is it just for accelerometer data registers? BR,KJ

Hi there, I tried to build NetXDuo stack with IPV6 and SLAAC version on H563ZI Nucleo boardHowever compilation of system libraries failed due to not linked symbols, it happened in all 3 ways of generations form CubeMX (copy all files, copy only required files, reference libraries).I.e. linker complained about lack of symbol _nx_nd_cache_add_entry and I noted filed is nx_nd_cache_add_entry.c is not compiled nor copied to project sources.

I’ve recently installed stm32cubemx2-1.1.1-X64-Windows-installer.exe on Windows 22H2, and after reboot found my PATH to be broken. I have confirmed this in a fresh VM.Before the installer, PATH is an “Expandable String” - hex(2) is REG_EXPAND_SZ[HKEY_CURRENT_USER\Environment]"Path"=hex(2):43,00,3a,00,5c,00,55,00,73,00,65,00,72,00,73,00,5c,00,[...]After the installer, PATH is a plain “String” / REG_SZ[HKEY_CURRENT_USER\Environment]"Path"="C:\\Users\\[...]Please resolve this ASAP (checking the uninstaller too), and consider notifying users. Re-creating the key isn’t too onerous, but could be an elusive and risky fix for many.

Hi,Can we use a ferrite bead with STM8S MCU for VCC pin along with the recommended decoupling capacitors at the VCC pin. Thanks in advance.

In the topic “STM32U5G9J-DK2 application example \"Fx_NoR_Write_Read_File\" is not working” there is a problem described which I fear still is present today. The ticket mentioned there is 180260, can someone please check if the patch mentioned is available by now?Thanks.

HiMCSDK 6.4.2when a start is aborted, it can happen, that the code can get stuck in __weak void *R3_2_TIMx_UP_IRQHandler(PWMC_R3_2_Handle_t *pHandle) while (0x0u != pHandle->pParams_str->ADCDataReg1[0]->JSQR) { /* Nothing to do */ }i added this to fix it  if (true == pHandle->_Super.PWMState) {by the way I don’t like having whiles in the code at all. And if nessesary please add a timeout.In MCSDK 6.2.1 an overvoltage event, when no motor is running will also end up in a stuck while __weak void R3_2_SwitchOffPWM(PWMC_Handle_t *pHdl) while (0U == LL_TIM_IsActiveFlag_UPDATE(TIMx)) { /* Nothing to do */ } that seams to be fixed in newer versions

Hi,I bought the STEVAL-DRONE02 and STEVALFCU001V2 last week. But I couldn’t download the Android app ST BLE Drone  on my smart phone which has Android version 14. Which Android version does ST_BLE_DRONE support?I checked with Google and it say:The ST BLE Drone application supports Android 4.4 and higher. It acts as a Bluetooth Low Energy (BLE) remote controller designed to work with evaluation boards like the STEVAL-FCU001V1.

Heyho,preparing the BOM for the next PCB version with the STM32H733ZGT (LQFP-144, 1024kB).And finding that these are not available at our standard webshops. :-(Started CubeMX to look for 100% pin compatible MCUs, and lo and behold: none found!But I’m pretty sure that the following types are at least pin-compatible and mostly function-compatible (some only missing stuff like hardware encryption):STM32H723ZGT, STM32H725ZGT, STM32H730ZGT, STM32H735ZGTAm I correct, or are these not pin-compatible - maybe some internal LDO / SMPS stuff or some peripheral missing that I oversaw? I’m using the following peripherals:SAI1, SAI4, I2S3, Ethernet + PTP, I2C1, I2C4, 2x OctoSPI, DAC, ADC, UART3, SDMMC2, timers, … Oh my, what a project… there’s no way I’m gonna switch to some completely different MCU. Thanks in advance!

## Setup- Module: ST67W611M1 on X-NUCLEO-67W61M1- Host MCU: STM32C562RE (NUCLEO-C562RE), Zephyr 4.4.0 st67w611m1 driver  (SPI netif path equivalent to W6X_Netif_output / ST67W6X_CLI_LWIP)- Module firmware: st67w611m_mission_t02_v2.0.106.bin (X-CUBE-ST67W61 v1.3.0)- Target network: enterprise SSID managed by FortiAP (WPA2)## ProblemUnder mission T02 the station associates successfully, but DHCP nevercompletes on our enterprise AP. Host-generated DHCP DISCOVER frames sentthrough the SPI network-STA path ARE visible on the LAN (captured by a PCon the same SSID) and are byte-comparable to DISCOVERs from workingclients — yet no OFFER is ever returned.Control tests:- T01 firmware, SAME module, SAME MAC, SAME SSID: internal DHCP client  gets a lease within seconds (172.16.1.26).- T02 firmware on a phone hotspot: SAME host firmware completes DORA  and binds 172.30.234.14.- Other clients (ESP32, Windows, Android) on the enterprise SSID: work.So the host stack and the T02 raw frame path are prov

Hi Team, We are performing the ISO 16750-2:2023 Superimposed Alternating Voltage test on our DUT. The 12 V main supply is provided to the TPSM64406RCHR buck converter, which generates a nominal 3.3 V supply for the STM32H563VIT3Q controller.During the test, a 6 V peak-to-peak AC ripple is superimposed on the 12 V input, causing the input voltage to vary between approximately 9 V and 15 V. Under this condition, communication with the STM32 controller fails.We attempted to reflash the firmware multiple times, but the issue persisted. However, when we performed a Full Chip Erase using STM32CubeProgrammer and then reflashed the firmware, the controller started working properly.Could you help us identify the possible root cause of this issue and explain why repeated firmware flashing did not resolve it, whereas a full chip erase followed by reflashing restored normal operation? We would also appreciate recommendations for further debugging to determine whether the issue is related to power

Hi there!I'd like to use the STEVAL-CAM-M01 P-board to evaluate the VD55G0 BrightSense image sensor with the Discovery kit for the STM32N6 MCU (STM32N6570-DK). The discovery kit does have a camera connector, however, looking at the schematics it seems that the polarity of the CSI data and clock lines is swapped compared to the P-board. Everything else looks fine.Is it possible to use the P-Board with the Discovery kit without destroying either of the two? ST's marketing material (slide 33) seems to suggest it is possible but the schematics are unclear. Note that a similar question has been asked in the MCU forum, but it was suggested to ask in this forum to be sure. Also note that I'm not asking about software driver support here, only hardware compatibility.Camera connector on STM32N6 discovery kit: Connector on P-board:Thanks a lot!Michael